The transfer you never signed. How a merger or reorganisation can assign a license by operation of law and hand the publisher a right you did not expect.
Deemed assignment and software licensing risk describes a category of exposure that catches buyers by surprise because no one ever signed an assignment. A deemed assignment happens when a license is treated as transferred, not because the parties executed a transfer, but because the structure of a transaction causes the law or the contract to treat it as one. A merger that vests assets in a surviving entity, a reorganisation that moves a subsidiary, or a change in the controlling shareholder can all be read as an assignment under the wording of a software contract. Understanding deemed assignment and software licensing risk matters because the publisher right it triggers is identical to a signed assignment, even though the buyer never intended to move anything.
The risk arises from the gap between how a buyer thinks about a deal and how a contract reads it. Many software agreements prohibit assignment without consent, and define assignment broadly to include transfers by operation of law, by merger, or by change of control. So even a transaction the buyer considers a pure equity deal can satisfy the contractual definition of an assignment if control of the licensed entity changes. The clause then activates, and the publisher gains the same rights it would have on a signed transfer: consent, repricing, or termination. The danger is that the buyer, focused on the absence of a formal assignment, never looks for the clause and never prices the exposure. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and deemed assignment is one of its most overlooked forms because it hides behind a transaction that looks clean on its face.
Deal structure is decisive. In a straightforward stock purchase, the licensed entity continues to exist and only its ownership changes, so a narrow clause addressing assignment may not be triggered while a broad change of control clause will be. In a statutory merger, the assets of one entity vest in another by operation of law, which is the classic deemed assignment scenario. In an asset purchase, the transfer is explicit rather than deemed, so the assignment language applies directly. Reading the clause against the actual structure is the only way to know whether the risk is real. The interaction is explored in stock versus asset purchase and which triggers assignment issues and in how a merger can breach a software license.
| Scenario | Why it can be deemed an assignment | Buyer exposure |
|---|---|---|
| Statutory merger | Assets vest in survivor by operation of law | High where clause covers operation of law |
| Upstream reorganisation | Licensed entity moved between affiliates | Medium, depends on affiliate carve out |
| Change of ultimate parent | Control of licensee changes | High where change of control is defined broadly |
| Insolvency or administration | Transfer by operation of insolvency law | Variable, often special clause language |
| Share sale of subsidiary | Control of the contracting entity changes | Medium to high depending on wording |
Legal diligence often reads contracts for explicit assignment provisions and flags them, but the deemed assignment risk lives in the definitions section and in the interaction between the clause and the chosen structure. A reviewer who sees no assignment in the transaction may not connect a broad definition of assignment to a merger step planned elsewhere in the deal. Financial diligence rarely opens the contracts at all. The result is that the exposure is real, it is in the documents, and it is never quantified. After close, the publisher reviews the account, identifies the deemed assignment, and asserts its right, often packaged with an audit of deployment that has drifted beyond entitlement. This is the pattern across Oracle, SAP, Microsoft, IBM, and increasingly Broadcom, Salesforce, and ServiceNow, as of June 2026.
The remedy is to read the estate against the actual transaction structure, not in the abstract. That means identifying every contract whose assignment or change of control definition is broad enough to capture the planned steps, mapping each to the system it governs, and pricing what consent or a waiver would cost. Where the deemed assignment risk is high and the system is critical, the buyer can sometimes restructure the relevant step to avoid the trigger, or seek a waiver before close while leverage is highest. This is the kind of mapping covered in mapping high risk clauses across the software estate. As always, the legal reading of whether a particular transaction constitutes an assignment belongs with the buyer own counsel, working alongside the commercial measurement.
Consider an anonymised composite: a corporate acquirer absorbing a 1,400 employee target through a statutory merger, with the target entity ceasing to exist. The deal team treated it as an internal matter because no contracts were being signed over. A complete review found that the target main database agreement defined assignment to include any transfer by operation of law, including merger, and required consent at the publisher discretion. Because the target was disappearing, the license would pass to the survivor by operation of law, squarely within the definition. Had it been missed, the publisher could have asserted that the license never validly transferred and demanded a new agreement at current pricing. Because it was found before the merger step, the buyer obtained a consent and waiver in advance, with deployment reconciled, and the transfer completed cleanly. The lesson for buyers is that a deal with no signed assignment can still carry full assignment risk, and only a structure aware reading of the estate will reveal it.
We read your estate against the actual deal structure, surface deemed assignment exposure hiding in the definitions, and price the consents and waivers before close.
Request a change of control clause review