The provision that decides whether a software license can move with the business, and why an asset deal turns it into a gating item for close.
Anti assignment clauses in software contracts are provisions that restrict or prohibit the transfer of a license from one party to another without the publisher consent. In an M&A context, anti assignment clauses in software contracts matter most when a deal moves contracts between legal entities, because that movement is an assignment, and an assignment is exactly what the clause is written to control. For a buyer, the practical effect is simple and serious: a license you assumed you were acquiring may not transfer at all unless the publisher agrees, and the publisher can attach conditions to that agreement.
An anti assignment clause restricts the licensee from transferring its rights and obligations under the agreement to a third party. The wording varies. Some clauses prohibit assignment outright, some permit it only with prior written consent, and some permit it with consent that may not be unreasonably withheld. A small number carve out assignments to affiliates or in connection with a merger or sale of substantially all assets, which can be a valuable exception for a buyer. The precise language determines everything, because the difference between consent that may not be unreasonably withheld and consent at the publisher sole discretion is the difference between a manageable process and a genuine deal risk.
Anti assignment language is closely related to change of control language but is not the same thing. A change of control clause responds to a change in who owns the licensed entity. An anti assignment clause responds to the license itself moving to a different entity. A stock purchase, where the entity stays the same and only its owner changes, may trigger a change of control clause but not an anti assignment clause. An asset purchase, where contracts are transferred, triggers anti assignment language directly. Understanding which is in play depends on the deal structure, a distinction we set out in what is a change of control clause in software and in deemed assignment and software licensing risk.
In an asset purchase, the buyer acquires assets and assigns contracts from the seller entity to the buyer entity. Every software license in scope is therefore being assigned, and every anti assignment clause is potentially engaged. This turns the contract review into a gating exercise for close, because a license that cannot be assigned and cannot be consented in time is a license the buyer does not have on day one. For a critical system, that is not an administrative inconvenience but an operational risk. The consequence is that an asset deal carries materially more consent work than a stock deal of the same size, and that work has to be planned into the timeline rather than discovered late.
| Clause wording | What it permits | Buyer risk level |
|---|---|---|
| No assignment without consent, not unreasonably withheld | Transfer with consent the publisher must justify refusing | Manageable |
| No assignment without consent, sole discretion | Transfer only if the publisher agrees, for any reason | High |
| Assignment permitted to affiliates or on sale of business | Transfer in a deal without separate consent | Low |
| Assignment prohibited absolutely | No transfer, requires a new license | Very high |
| Silent on assignment | Depends on governing law and deemed assignment | Uncertain |
The wording drives the risk, and a clause that is silent on assignment is not automatically safe, because the governing law may imply a restriction or a deemed assignment may arise from the transaction itself. This is why a buyer cannot rely on the absence of an explicit clause and has to read each contract against its governing law, with counsel. The consent process itself, once the clauses are mapped, is the subject of consent strategy for software license assignment and planning consent requests without tipping off vendors.
Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and it lands as a publisher audit after close. An anti assignment clause that was not satisfied is a particularly clean basis for a publisher to act, because the buyer is using software under a license that, on the publisher reading, never validly transferred. The publishers most active in pursuing such positions as of June 2026 are Oracle, SAP, Microsoft, and IBM, with Broadcom increasingly active across the former VMware estate and Salesforce and ServiceNow rising. Public reporting shows the magnitude that inherited and disputed licensing can reach, 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. The remedy is to find and clear the anti assignment hurdles before close, not to discover them in an audit letter.
Once an anti assignment clause is identified as engaged, it sets in motion a process with its own timeline and risks. The buyer has to decide when to approach the publisher, what to disclose, and how to frame the request, because the consent conversation can itself become a usage review if handled carelessly. The sequence matters: approaching a publisher before the buyer understands its own deployment and entitlement invites a true up demand, while approaching with accurate data in hand allows the buyer to keep the conversation narrow. The consent should be requested for the specific transfer required, not framed in a way that opens the whole relationship, and the request should be timed so the publisher does not sense a closing deadline it can exploit.
The volume of consents in an asset deal also has to be managed as a programme rather than a series of individual letters. A large estate can involve dozens of contracts requiring consent, each with its own contact, its own process, and its own response time. Treating these as a coordinated workstream, with consents sequenced by operational criticality and tracked to a clear owner, prevents the slowest consent on the most critical system from becoming the item that delays close. The detail of running that programme is set out in consent strategy for software license assignment.
A well run anti assignment review does not just produce a consent list, it feeds the purchase agreement. Where consent is uncertain on a critical system, the buyer can require the seller to obtain it as a condition of close, can negotiate a price adjustment for the cost and risk, or can seek a specific indemnity tied to identified contracts. These protections are far stronger when they reference a schedule of named contracts and quantified exposure than when they rely on a general representation that all licenses are transferable. The anti assignment review is therefore both an operational exercise, to keep the systems running, and a commercial one, to allocate the risk between buyer and seller before signing rather than after the audit arrives.
Consider an anonymised composite: a buyer acquiring the software assets of a logistics business through an asset purchase. The estate included around forty active software contracts, of which a routine review flagged twelve as containing assignment language. A complete review found that three of those twelve required consent at the publisher sole discretion and governed systems the business could not operate without, including its transport management platform. Under the asset structure, all three contracts were being assigned, so all three consents were genuine gating items for close. Had the deal proceeded without addressing them, the buyer would have been operating three critical systems on licenses that, on the publisher reading, had not validly transferred.
Because the anti assignment review was completed during diligence, the buyer had options. It required the seller to obtain the two most straightforward consents as a condition of close, began the third, the discretionary consent on the transport platform, early and with accurate usage data prepared, and priced the residual risk into the purchase agreement. The discretionary consent was secured without a metric change because the approach was early and the data left no room for a true up demand. The example shows why anti assignment clauses in an asset deal cannot be treated as a uniform category: the risk concentrates in a small number of discretionary consents on critical systems, and finding those few in time is what protects the deal.
We find the anti assignment clauses across the estate, map them to the systems that depend on them, and run the consent process so the licenses move with the deal.
Request a change of control clause review