The Default Is Non-Transferable
Software licence assignment and transfer rights rest on a principle most buyers discover at the worst possible moment: in the absence of express provisions to the contrary, an intellectual-property licence is presumed non-assignable and non-transferable. Licences do not automatically pass in the sale or merger of a business — and many software agreements reinforce that default with explicit anti-assignment language barring the licensee from assigning the agreement "whether voluntarily or involuntarily, directly or indirectly, or by operation of law, merger, consolidation or otherwise".
The practical consequence is stark. An acquirer that assumes it is buying a target's software estate may find that a material share of it cannot lawfully transfer without vendor consent — and that consent has a price. This is why assignment and transfer belong in the same governance discipline as the rest of the compliance and governance programme, and why the underlying entitlement records from your licence position are the starting point for any transaction.
How Change-of-Control Clauses Bite
Even where a contract does not address assignment directly, a change-of-control clause can achieve the same effect. Many software agreements treat a merger or acquisition as a deemed assignment, triggering a consent requirement — or, in the harsher versions, a termination right. The acquirer's integration plan can therefore be derailed by a clause that was invisible during ordinary operations and only activates on a change of ownership.
These clauses cut in every direction of a transaction. In an acquisition, the target's licences may require consent to continue. In a divestiture, licences cannot simply be carved out to the separated entity without the vendor's agreement, which is why divestiture flexibility is a term worth negotiating into major agreements in advance. And in a straightforward internal reorganisation, an "operation of law" trigger can still fire. The same continuity logic that drives software escrow decisions applies here: terms that look like boilerplate become decisive at the moment of corporate change. The SAP vendor hub illustrates how strict major vendors can be — SAP licences are generally non-transferable without consent.
A licence you "own" can be one a vendor has the right to terminate the moment your ownership changes. Change-of-control clauses convert a routine deal into a renegotiation the vendor controls.
Why Vendors Hold the Leverage
Vendors know they sit in a position of significant leverage when a customer needs consent to assign or transfer licences. The timing is the source of that power: consent is usually sought during a live transaction, when the buyer is on a deadline, integration depends on continuity, and walking away is not an option. A vendor approached in that window can condition consent on a re-purchase at current list pricing, a forced migration to a newer product, an uplift in the support base, or the removal of historic discounts — converting a transaction milestone into a revenue event.
The defence is to remove the time pressure by addressing assignment before it becomes urgent. Scrutinise the assignment and change-of-control clauses in every critical software agreement well before any purchase agreement is signed, ideally as standing contract hygiene rather than transaction-driven panic. An estate where assignment terms are known and, where possible, pre-negotiated is one where a deal proceeds on the buyer's timeline. Treat this as part of structured third-party risk management and M&A due diligence, not a last-minute legal review.
What to Negotiate — and When
The terms to seek are specific. Aim for an assignment right that permits transfer to an affiliate or to a successor in a merger or acquisition without consent, or at minimum with consent that "shall not be unreasonably withheld". Negotiate divestiture flexibility — the right to transfer a proportionate share of licences to a separated entity — into major agreements at renewal, when you have leverage, rather than mid-transaction, when you have none. Clarify how a change of control is defined, since a narrow definition reduces the surface area of the trigger. And document the consent process and any associated fees, so a future transaction faces a known cost rather than an open-ended demand. The right moment for all of this is at original signature or renewal; the wrong moment is the week before a deal closes. To map your assignment exposure ahead of a transaction, request a confidential briefing.
Divestitures, Carve-Outs, and the Defence
Divestitures present the mirror image of the acquisition problem, and often the harder one. When a business unit is separated, the software licences it depends on cannot simply be carved out and handed to the new entity — the same anti-assignment and change-of-control terms that complicate acquisitions prevent a clean split, and the separated entity may find itself operating critical software with no valid licence. Transitional service agreements buy time, but they are temporary, and the underlying licences still have to be addressed with the vendor, who once again holds the leverage of consent.
The defence is to negotiate divestiture flexibility into major agreements before it is needed. A clause permitting the transfer of a proportionate share of licences to a divested entity — without consent, or with consent not to be unreasonably withheld — is far cheaper to secure at renewal than to extract during a live separation. Forward-looking enterprises treat this as standard commercial hygiene for any vendor whose product spans business units that might one day be sold.
Underpinning both acquisition and divestiture scenarios is the same prerequisite: an accurate entitlement record. You cannot assess assignment exposure for licences you have not catalogued, which is why the effective licence position built for audit defence doubles as the foundation for transaction readiness. An enterprise that knows exactly what it owns, on what terms, and with what assignment restrictions can move through a transaction on its own timeline; one that discovers its position during due diligence negotiates from weakness. Assignment risk, in the end, is not primarily a legal problem to be solved at deal time — it is a governance discipline to be maintained continuously, so that a transaction never becomes the moment a vendor sets the price.