Why a transaction that moves no contract on paper can still put a buyer in breach, and what to check before the merger completes.
Understanding how a merger can breach a software license matters because a merger feels clean on paper, with two entities becoming one rather than contracts physically moving, yet that very mechanism is how a merger can breach a software license. The breach arises not from any deliberate act but from contract language that treats the merger as a deemed assignment or as a change of control, so that the surviving entity is using software under a license that, on the publisher reading, did not validly carry over. The breach is often silent at completion and surfaces later as a publisher audit, which is the most expensive moment to discover it.
A merger combines entities by operation of law. In a forward merger the target merges into the buyer and ceases to exist, while in a reverse merger the buyer subsidiary merges into the target which survives. In both cases the question for each software contract is whether the merger counts as an assignment or a change of control under that specific agreement. Many publishers draft their contracts precisely to capture this, with language stating that a merger, consolidation, or change in control is deemed an assignment requiring consent regardless of which entity survives. Where that language exists and consent was not obtained, the surviving entity holds no valid license, and continued use is a breach even though no one moved a file or signed a transfer.
This is why a merger cannot be assumed to be free of software consent work. The breach risk depends entirely on the wording of each agreement read against the merger mechanics, which is a contract by contract exercise. The relationship between merger mechanics and the broader structure question is set out in stock versus asset purchase and which triggers assignment issues, and the concept of a deemed assignment is explained in deemed assignment and software licensing risk.
Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and it lands as a publisher audit after close. A merger breach is a clean basis for a publisher to act, because the argument is simple: the license required consent on a merger, consent was not given, and the surviving entity has been using the software without a valid right. The publisher can then assert a claim for unauthorized use, which is typically priced at list rather than the discounted rate the original licensee enjoyed, and can include back charges. The publishers most likely to pursue this as of June 2026 are Oracle, SAP, Microsoft, and IBM, with Broadcom increasingly active across the former VMware estate and Salesforce and ServiceNow rising. The scale that inherited and disputed licensing can reach is shown in the public record, with SAP reportedly pursuing Anheuser Busch InBev for around 600 million dollars and Diageo for around 60 million pounds, both as reported and as of June 2026.
| Merger type | Surviving entity | Breach risk driver |
|---|---|---|
| Forward merger | Buyer survives, target dissolves | Target licenses may need consent to carry to buyer |
| Reverse merger | Target survives as subsidiary | Change of control of the surviving licensee |
| Forward triangular | Target merges into buyer subsidiary | Deemed assignment of target licenses |
| Reverse triangular | Buyer subsidiary merges into target | Often lower, but change of control may apply |
Prevention is a pre completion exercise. The buyer reads the estate for every clause that could treat the merger as an assignment or a change of control, classifies each by the merger type planned, and obtains the consents that are genuinely required before completion rather than after. Where consent will be slow or uncertain on a critical system, the buyer can sequence the work early, plan a fallback, or in some cases adjust the merger structure to avoid the trigger, a point developed in how deal structure limits assignment problems. Finding the clauses in time depends on reading the whole estate before signing, which is the subject of finding change of control clauses before you sign. This is commercial and licensing advisory work, and the legal interpretation of whether a particular merger constitutes an assignment under a given contract and governing law belongs with the buyer own counsel.
The reason a merger breach so often goes unnoticed is that nothing visible changes on the day. The systems keep running, the same users log in, the same invoices arrive, and there is no error message announcing that a license has lapsed. The breach is a legal state, not an operational one, and it persists quietly until a publisher chooses to look. That can be months or years later, prompted by a renewal, a support ticket that reveals the corporate change, or a routine audit cycle. Because the gap between the breach and its discovery can be long, the buyer often has no idea the exposure exists, and the cost compounds as continued use accumulates against a license the publisher says never validly transferred.
This delayed discovery is precisely why inherited software licensing exposure is described as latent. It is real from the moment of completion but invisible until surfaced, and standard diligence rarely measures it because it requires reading the assignment language in every material contract against the specific merger mechanics, not just confirming that the contracts exist. The work is contract by contract and structure specific, which is more than a sample review of headline terms delivers.
When a merger breach is found, whether before completion or after, the buyer has a range of remediation options that vary in cost. The cleanest is to obtain the consent that was required, ideally before completion when the buyer still has leverage and no breach has yet occurred. After completion, the buyer can seek a retroactive consent or a novation, though the publisher then knows a breach has happened and can price accordingly. Where consent cannot be obtained on acceptable terms, the buyer can re license the product, migrate to an alternative, or in some cases restructure the holding entity to cure the assignment. Each option has a cost, and the cost is almost always lower the earlier the breach is identified, which is the entire argument for reading the estate against the merger before completion rather than discovering the problem in an audit letter. The choice among these options should be made with the buyer own counsel on the legal position and an advisor on the commercial outcome.
Consider an anonymised composite: two software firms combined through a forward triangular merger, with the target merging into a subsidiary of the buyer. The integration team focused on systems and people and assumed that, because no contracts were being physically transferred, the software licenses simply carried across. Several of the target key agreements, however, contained language deeming a merger or consolidation an assignment requiring prior written consent. No consent was sought, because no one read the contracts against the merger mechanics. The combined business ran on those systems for over a year with no visible problem.
The exposure surfaced when one of the publishers, prompted by a renewal that revealed the corporate change, opened a review. Its position was straightforward: the merger was a deemed assignment, consent was required and never obtained, and the surviving entity had been using the software without a valid license for the intervening period. The publisher priced the unauthorized use at list rather than the discounted rate the original licensee had enjoyed and sought back charges for the period since the merger. Had the agreements been read against the merger before completion, the required consents could have been obtained quietly and at no premium. The example illustrates why a merger that moves no contract on paper can still create a real and growing exposure, and why the contract by contract review against the specific merger structure is not optional. The legal position on whether each agreement was breached would, in practice, be confirmed with the buyer own counsel.
We read the estate for the clauses a merger triggers, secure the consents, and close the gaps before completion, so the combined entity is not in breach on day one.
Request a change of control clause review