A change of control clause is a contract term that gives a software publisher rights when the ownership of the licensee changes, often the right to consent, terminate, or reprice.
What is a change of control clause? It is a provision in a software contract that is triggered when the company holding the license changes ownership. Depending on how it is written, it can require the publisher consent to the transaction, allow the publisher to terminate the agreement, or let the publisher reprice the license to reflect the new owner. For an acquirer, it is one of the first contract terms that decides whether a target software estate transfers cleanly or becomes a negotiation with the vendor.
A change of control clause sits dormant until a transaction triggers it. The trigger is usually a change in the ownership or voting control of the licensee, but the exact wording matters. Some clauses fire on any sale of the entity. Others fire only on a change above a stated threshold. Once triggered, the clause hands leverage to the publisher: the right to withhold consent, to terminate for convenience, or to demand a new price for the same software under new ownership. Reading these clauses before signing is how a buyer learns where that leverage sits.
Whether a change of control clause bites depends heavily on how the deal is structured. A stock purchase, where the legal entity survives and only its owner changes, often triggers change of control language directly. An asset purchase, where contracts are assigned to a new entity, can instead trigger anti assignment terms. A merger or a carve out raises its own questions about which agreements move and which stay. The same software estate can transfer cleanly under one structure and require dozens of vendor consents under another.
The practical response is to inventory the agreements, identify which contain change of control or assignment triggers, and map those against the chosen deal structure before signing. Where consent is required, the timeline for obtaining it belongs in the deal plan, not as a post close surprise. Where a publisher could reprice, the potential cost belongs in the model. This work is commercial and licensing advisory, not legal advice, so the interpretation of any specific clause should sit with the buyer own counsel.
| Deal structure | What changes | Clause most likely to bite |
|---|---|---|
| Stock purchase | Owner of the entity | Change of control |
| Asset purchase | Contracts assigned to new entity | Anti assignment |
| Merger | Entities combine | Change of control and assignment |
| Carve out | Unit separates from parent | Both, plus shared license splits |
Related reading: see the M&A software glossary hub, plus anti assignment clause and deemed assignment.
Map and quantify the licensing exposure in your target or portfolio before it becomes a post close audit. Independent, buyer side, paid only by the acquirer.
Talk to a software M&A advisor