A plain answer for buyers on the clause that decides whether your acquired software contracts survive the deal, and what it can cost when they do not.
A change of control clause in software licensing is a contract term that gives the publisher specific rights when ownership of the licensee changes hands, whether through an acquisition, merger, or a shift in who ultimately controls the entity. So what is a change of control clause in software licensing in practice? It is the lever that decides whether the licenses you are buying actually transfer cleanly, or whether the publisher can demand consent, reprice the agreement, or terminate the license entirely once the deal completes. For a buyer, it is one of the most consequential lines in the contract and one of the most frequently overlooked in standard due diligence.
The clause works by treating a change in ownership as a contractual event. Most software agreements are written so that the license is granted to a named legal entity, not to whoever happens to own that entity. When the owner changes, the publisher argues that the original bargain has changed too, and the change of control clause is the mechanism that lets them respond. The response can take three broad forms. The publisher may require its prior written consent before the license continues, it may reserve the right to terminate the agreement, or it may use the moment to renegotiate price and terms. Each of these is a commercial outcome, and each lands on the buyer.
The reason this matters so much in a transaction is that the value a buyer places on a target almost always assumes the software keeps running. The financial model treats the enterprise resource planning system, the database estate, the productivity suite, and the specialist applications as going concerns that simply continue after close. A change of control clause can break that assumption. If a critical system depends on a license that the publisher can withhold consent on, the buyer has inherited a dependency it does not fully control, and the publisher knows it.
Whether a change of control clause is triggered at all depends heavily on how the deal is structured. In a stock purchase, the legal entity that holds the licenses does not change, only its ownership does, so a narrowly drafted clause that only addresses assignment may not be triggered, while a broader clause that addresses any change in control will be. In an asset purchase, the licenses are being moved from one entity to another, which is an assignment, and assignment provisions and anti assignment language come directly into play. In a merger, the analysis depends on which entity survives and on the precise wording. This is why the same portfolio of contracts can carry very different risk depending on the transaction chosen, and why the clause review has to be read against the actual structure rather than in the abstract. We cover this interaction in depth in stock versus asset purchase and which triggers assignment issues and in how deal structure limits assignment problems.
Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and it tends to land as a publisher audit after close. Legal diligence often reads a sample of material contracts for headline commercial terms and may flag the existence of a change of control provision without measuring what it would cost to satisfy it. Financial diligence rarely opens the contracts at all. The result is a gap: the clause is known to exist somewhere in the estate but its real exposure, which contracts carry it, which systems depend on those contracts, and what consent or repricing would cost, is never quantified. That gap is exactly where publishers operate after a deal closes.
The major publishers that drive this risk are well known. As of June 2026, the most active in pursuing licensing positions around ownership changes are Oracle, SAP, Microsoft, and IBM, with Broadcom increasingly active across the former VMware estate, and Salesforce and ServiceNow rising. Public proof points show the scale that inherited and disputed licensing can reach. SAP reportedly pursued Anheuser Busch InBev for a figure of around 600 million dollars, and Diageo for around 60 million pounds, over disputed and inherited licensing, both figures as reported in the public record rather than firm confirmed, and useful as an indication of magnitude as of June 2026.
| Trigger in the clause | What activates it | Typical buyer impact |
|---|---|---|
| Direct change of control | New owner acquires the licensee entity | Consent request, possible repricing |
| Anti assignment | License moved to a different entity | Consent required before transfer |
| Competitor restriction | Acquirer is a named or implied competitor of the publisher | Consent refused or terminated |
| Notification only | Ownership change of any kind | Notice obligation, lower direct risk |
| Termination on control | Any change in ultimate control | License can be ended at publisher discretion |
Reading the clause type correctly matters because the remedy differs. A notification only obligation is a low cost administrative step. A competitor restriction in a license held by a strategic acquirer can be a genuine deal issue. Mapping every clause to its type across the estate is the first analytical step, and it is the subject of mapping high risk clauses across the software estate. Knowing where the clauses sit before signing is covered in finding change of control clauses before you sign.
The practical answer is to treat change of control language as a measurable exposure rather than a legal footnote. That means reading the whole estate, not a sample, classifying each clause by type, mapping each clause to the system it governs and the business process that system supports, and pricing the cost of satisfying it. With that picture, the buyer can decide which consents to pursue, which to negotiate, and which to structure around, and can hold a number in the deal model rather than a vague risk. This is commercial and licensing advisory work. The interpretation of any specific clause, including whether it is legally enforceable in a given jurisdiction, belongs with the buyer own counsel, and we always recommend that legal reading sits alongside the commercial measurement.
A common reason a change of control clause is missed is that buyers look in the wrong place. The provision is not always in the master agreement. It frequently sits in an order form, a regional addendum, a hosting schedule, or an amendment signed years after the original deal. A single publisher relationship can span dozens of documents, and the controlling language on assignment may be in the least read of them. Reading only the master, or only the contracts above a certain value, leaves the most dangerous clauses undiscovered. This is why a thorough review reads the full document stack for each publisher and reconciles the clauses across them, because a later amendment can override or expand an earlier provision.
The picture is complicated further by subsidiaries. In a group structure, software may be licensed by a holding entity, a shared services entity, or an operating subsidiary, and the contract that governs a system the buyer cares about may sit in a different legal entity from the one being acquired. When the deal touches that entity, the clause in its contract comes into play even though the buyer was focused elsewhere. Mapping which entity holds which contract is part of the same exercise as classifying the clauses, and it is why the review has to be built from a complete inventory rather than a list of headline systems.
A change of control clause is rarely the only licensing exposure in an estate. It sits alongside deployment that has drifted beyond entitlement, metric definitions that no longer match how the software is used, and historic true up obligations that were never settled. A change of ownership tends to bring all of these into focus at once, because the publisher reviews the account as a whole when it is prompted to look. A buyer who treats the change of control clause in isolation can clear the consent and still face an audit on unrelated overuse. The stronger approach is to read the change of control position as one input into a complete licensing picture for each major publisher, so the buyer knows its total exposure before any publisher is engaged. That complete picture is what a license reconciliation produces, and it is the foundation that makes a consent negotiation safe rather than an invitation to a wider review.
Consider an anonymised composite: a private equity backed buyer acquiring a mid sized manufacturer through an asset purchase. The target ran a large database estate from a major publisher, licensed under a master agreement signed eight years earlier with a favorable per processor metric. The master was silent on assignment, which the deal team took as comfort. Buried in an order form signed three years later, however, was a clause stating that any assignment, including by operation of law or change of control, required prior written consent, with consent at the publisher discretion. Standard diligence, which read the master and a sample of order forms, did not surface it. The clause was found only because a complete review read every order form against the master.
The consequence, had it been missed, was material. On an asset purchase the licenses were being assigned, the order form required consent, and the publisher could have conditioned that consent on a move to a current metric that roughly doubled the annual fee, or on a true up of deployment that had grown well beyond the original entitlement. Because the clause was found before signing, the buyer was able to reflect the risk in the purchase agreement and begin the consent conversation early, with accurate usage data in hand, and ultimately secured the transfer without the metric change. The lesson for buyers is that the controlling clause is often not where it is expected, and the cost of finding it late is measured in the publisher leverage it hands over.
We read the estate for change of control and assignment language, quantify the exposure, and build the consent plan, so nothing surfaces as an audit or a repricing after close.
Request a change of control clause review