An asset purchase is a deal structure where the buyer acquires chosen assets and contracts rather than the company itself, which reshapes how software licenses move and whether publisher consent is needed.
What is asset purchase? An asset purchase is a transaction in which the buyer acquires specific assets, contracts and liabilities of a target rather than its shares. Because the legal entity does not pass to the buyer, software licenses do not move automatically. Each agreement has to be assigned, and most publisher contracts make assignment conditional on consent. That single difference is why an asset purchase can convert a routine renewal into a fresh negotiation, a repurchase, or an unplanned audit, and why buyers map software exposure before they sign.
In a share purchase the target entity survives, so its contracts and licenses ride along untouched. In an asset purchase the buyer cherry picks what it takes, and the licenses it wants must be transferred one by one. Software publishers anticipate this. Most master agreements contain anti assignment language that requires written consent before a license can move to a new owner, and consent is a moment when the publisher can decline, reprice, or demand a true up.
The practical effect is that an asset purchase strips away the assumption that the target keeps its software on the same terms. Volume agreements negotiated years earlier may not survive the move. Discounts tied to the old entity can disappear. Maintenance and support contracts may need re signing at current list. A buyer that treats licenses as automatically inherited in an asset deal often discovers the gap only when the publisher responds to the assignment request or opens an audit after close.
The exposure is rarely visible in standard financial due diligence because it does not sit on the balance sheet. It is latent and unquantified until a publisher acts on it. Public disputes show the scale. As of June 2026, reporting on SAP indicated claims of a reported 600 million dollars against AB InBev and a reported 60 million against Diageo over disputed and inherited licensing, illustrating how transfer and usage questions become eight figure events.
Whether a clause bites depends on wording and structure. Some contracts treat any assignment as a consent event, others carve out internal reorganisations, and a few deem a change of the contracting party an automatic termination. Reading the assignable and non assignable agreements before signing tells the buyer which licenses transfer cleanly, which need negotiation, and which may have to be repurchased. This is commercial and licensing advisory, not legal advice, so the buyer should engage its own counsel to interpret each clause.
| Structure | License transfer | Buyer risk |
|---|---|---|
| Asset purchase | Each contract assigned, usually with consent | Repricing, repurchase, audit on assignment |
| Share or stock purchase | Entity survives, licenses ride along | Inherited non compliance carries over |
| Merger | Surviving entity absorbs contracts | Deemed assignment may still trigger clauses |
| Carve out | New entity needs its own entitlements | Coverage gaps and standalone repurchase |
Related reading: see the M&A software glossary hub, plus stock purchase and change of control clause.
Map and quantify the licensing exposure in your target or portfolio before it becomes a post close audit. Independent, buyer side, paid only by the acquirer.
Talk to a software M&A advisor