Change Of Control Clauses: Buyer's Guide
How change-of-control restrictions block license transfer after an acquisition, what they cost, and the assignment and survival terms that protect the buyer.
A change-of-control clause lets a software vendor block, re-price, or terminate a license when the customer is acquired, merged, or spun out, and an unfavorable clause can force a full list-price re-purchase of an estate the buyer believed it already owned. In live M&A work, change-of-control restrictions are the single most expensive contract term that diligence teams miss, because the cost only appears after the deal closes and the vendor sends an assignment-fee or re-license invoice. The fix is cheap if it is negotiated into the original contract and very expensive if it is discovered during integration.
This guide explains how the clause works, the three forms it takes, what each one costs, and the assignment and survival language a buyer should demand. It builds on our software contract negotiation guide and the firm's licensing advisory practice.
How a change-of-control clause works
A change of control is defined in most enterprise software contracts as any transaction that transfers more than 50% of the customer's voting equity, a merger, a sale of substantially all assets, or a spin-out of the contracting entity. When such an event occurs, the clause gives the vendor a defined right. That right ranges from a simple notice obligation at the mild end to an outright termination right at the severe end. The license itself is rarely freely assignable by default; the standard position in vendor paper is that the license is personal to the original legal entity and cannot move without consent.
The practical effect is that the acquiring company does not automatically inherit the target's licenses. If the contract prohibits assignment without consent, the acquirer must ask the vendor for permission, and the vendor is free to attach a price to that permission. That price is the leverage the clause creates.
The three forms and what each costs
Change-of-control terms cluster into three severities, and the cost difference between them is large.
| Clause form | Vendor right | Typical buyer cost |
|---|---|---|
| Notice only | Customer must notify within 30 to 60 days | Administrative only |
| Consent required | Assignment void without written consent | 5% to 20% assignment or transfer fee |
| Re-price on control change | Vendor may reset to current list and re-tier | Full re-price, often 2x to 4x the legacy rate |
| Termination right | Vendor may terminate for convenience | Forced re-purchase at new-customer pricing |
The re-price and termination forms are where eight-figure surprises live. A target that negotiated a 65% discount five years ago, then gets acquired, can find the vendor terminating the agreement and offering the acquirer a fresh contract at a 20% discount off a higher current list. The delta between those two positions is the real cost of the clause, and it is almost never modeled in the deal's synergy case.
Negotiation lever: Ask for an affiliate and successor assignment right that permits transfer to any entity that acquires the customer or substantially all of its assets, with no consent and no fee, provided the successor assumes the obligations. Vendors concede this far more often than buyers expect, because at signing the vendor is competing for the deal and a future acquisition feels remote. The language costs nothing to insert today and removes the vendor's entire leverage position later.
Diligence: finding the exposure before signing
In a target estate of 80 to 150 software agreements, expect 30% to 60% to carry some assignment restriction. The diligence task is to read every material agreement for three things: the assignment clause, the change-of-control definition, and any survival language that says the restriction continues after termination. Rank the findings by annual contract value, because the vendors with the largest spend have the most to gain from re-pricing and will press hardest.
The output of diligence should be a single schedule listing each restricted agreement, the vendor right it grants, the estimated re-license cost, and the consent timeline. That schedule belongs in the purchase agreement as a known liability, and the re-license cost belongs in the deal model. Skipping this step is how integration teams inherit seven-figure invoices in the first quarter after close. Our entitlement reconciliation method is the fastest way to assemble the underlying ownership picture before the legal read begins.
Deal structure changes the trigger
How the transaction is structured determines whether the clause fires at all. An asset purchase, where the buyer acquires specific assets including named contracts, almost always requires vendor consent to assign each contract, so every restricted agreement is in play. A stock or equity purchase, where the contracting legal entity survives unchanged and only its ownership shifts, may avoid triggering an assignment restriction entirely, because the counterparty entity is the same. This is exactly why change-of-control definitions specifically name equity transfers: vendors learned that a pure assignment clause was easy to sidestep through a stock deal.
| Deal structure | Contracting entity | Trigger risk |
|---|---|---|
| Asset purchase | Changes (contracts assigned) | High: consent needed per contract |
| Stock purchase | Survives, ownership changes | Medium: fires only if CoC clause names equity change |
| Merger (target dissolves) | Disappears into acquirer | High: assignment by operation of law |
| Internal reorganization | Affiliate transfer | Low if affiliate-assignment right exists |
Tax and accounting usually drive whether a deal is an asset or stock transaction, so the software exposure rarely changes the structure on its own. But knowing which agreements fire under the chosen structure tells the integration team exactly which vendor conversations to start, and when.
Negotiating the clause into a new contract
When signing a new agreement, four terms neutralize most change-of-control risk. First, a successor-assignment right with no fee and no consent for any acquirer of the customer or its assets. Second, a price-protection survival clause that fixes the discount and the unit price for the remainder of the term regardless of any control change. Third, a cap on any transfer or administrative fee, set in dollars rather than as a percentage, so it cannot scale with the deal size. Fourth, a continuity-of-service obligation that prevents the vendor from suspending access during any consent process.
These four terms work together. The assignment right removes the consent gate, the price-protection clause removes the re-price weapon, the fee cap removes the toll, and the continuity obligation removes the leverage of a service interruption. A buyer that secures all four has effectively removed change of control as a negotiating threat for the life of the contract. For the broader set of protective terms that belong alongside this clause, see our guides to escalation clauses and contract red flags, and the planning sequence in our co-terming contracts guide.
The buyer's checklist
Before signing, confirm the contract permits assignment to a successor without consent or fee, defines change of control narrowly enough that ordinary financing events do not trigger it, caps any transfer fee in fixed dollars, and protects the negotiated price for the full term. Before closing an acquisition, confirm every material agreement has been read for these terms, the re-license exposure is scheduled and priced into the model, and the consent timeline is mapped against the integration plan. The clause is invisible until a transaction makes it expensive, which is precisely why it has to be handled at signing, long before any deal is on the table. Engagements that start at the contract stage cost a fraction of those that start after an invoice arrives; our advisory team handles both.
Survival and the post-termination trap
Roughly one in three enterprise agreements contains a survival clause that keeps the assignment restriction alive after the contract itself ends, so a buyer cannot escape the restriction simply by letting the agreement lapse. The vendor drafts survival language precisely to close that escape route: even after termination, the obligation not to transfer the license without consent continues to bind, and any perpetual license the customer paid for remains locked to the original entity. For a divested unit holding perpetual licenses, this is the difference between carrying an owned asset out of the parent and leaving it behind.
The practical defense is to read the survival clause as carefully as the assignment clause and to negotiate an explicit successor-assignment right that itself survives termination. A buyer that secures the right to transfer to an acquirer, expressed as surviving any termination of the agreement, neutralizes the trap. Without that language, the restriction outlives the contract, and the vendor retains a veto over the asset long after the commercial relationship has ended. This is one of the terms covered in our broader contract red flags guide, because it is invisible at signing and expensive only later.
How clause severity varies by software category
Change-of-control severity is not uniform across the market; it tracks how much pricing power the vendor holds. Infrastructure and database vendors with deep lock-in write the hardest clauses, because they know a customer mid-acquisition cannot easily migrate. Commodity SaaS vendors in competitive categories write softer clauses, because a customer that resents a transfer fee can switch with little pain.
| Software category | Typical clause posture | Buyer exposure |
|---|---|---|
| Database and middleware | Consent required, re-price common | High: deep lock-in raises the toll |
| ERP and core platforms | Consent required, large transfer fee | High: migration cost backs the vendor |
| Specialized enterprise apps | Consent required, moderate fee | Medium: some switching pressure |
| Competitive SaaS | Notice or light consent | Low: easy alternatives cap the toll |
The lesson for diligence is to weight the read toward the lock-in heavy agreements. A database vendor's change-of-control clause can dwarf the combined exposure of a dozen SaaS subscriptions, so the diligence hours belong with the contracts that carry the most pricing power, not spread evenly across the estate.
A four-step playbook for the integration team
An integration team that inherits a software estate should run the same four-step sequence on every restricted agreement, regardless of how the deal was structured. The discipline turns a scattered set of contract risks into a managed program.
- Inventory and rank. List every agreement with an assignment or change-of-control restriction, ranked by annual contract value, because the largest-spend vendors will press hardest for a re-price.
- Map the trigger. Confirm whether the chosen deal structure actually fires each clause, so the team spends its consent effort only where a trigger genuinely exists.
- Open early, quietly. Start the consent conversation with each material vendor as soon as the deal is public, before the integration deadline creates pressure the vendor can exploit.
- Negotiate continuity, not just consent. Use the moment to secure a price-protection survival clause and a fee cap, converting a forced conversation into an opportunity to improve the inherited terms.
Teams that run this sequence treat change of control as a managed workstream with a schedule and an owner. Teams that skip it discover the clauses one vendor invoice at a time, on the vendor's timeline, at the vendor's price. The cost difference between the two approaches, across a large estate, routinely runs into seven figures, which is why the work belongs in diligence rather than in the first quarter after close. Our advisory team runs this playbook on either side of a transaction.