M&A and Divestiture Software Licensing Guide 2026
Updated June 2026
Software licenses do not move with the assets in a merger, acquisition or divestiture unless the contract and the vendor agree, and that single fact can hide an eight-figure liability inside a deal that looks clean on the invoice. Most enterprise agreements block transfer without written consent, and the consent request is the exact moment a vendor reprices the relationship.
This guide sets out how to price and negotiate licensing as a deal term: the diligence that turns an unknown into a number while it can still change hands, the transfer and anti-assignment clauses that govern every transaction, Transition Service Agreement scope, the carve-out math that splits one entitlement base into two, and the audit risk a change of ownership reliably triggers. The full guide is free to read online, and a copy is available below.
- ◆
Why deal structure, stock versus asset versus merger, decides whether your licenses survive, need consent, or must be repurchased
- ◆
How to run licensing diligence that reconciles deployment against entitlement, not spend against budget
- ◆
Reading the anti-assignment clause before you need it, and the four language patterns that decide the cost of consent
- ◆
Transition Service Agreement scope and the third-party use exposure that catches both buyer and seller
- ◆
Divestiture carve-out math: assignment, repurchase, or a TSA bridge, and how to right-size the retained agreement
- ◆
Vendor-by-vendor mechanics for Oracle, Microsoft, SAP and VMware in a transaction
- ◆
The audit risk a change of ownership triggers, and how the purchase agreement becomes your strongest defence
- Why M&A Breaks Software Licensing Understand how a transaction changes ownership, headcount, and deployment all at once, and why each is a licensing event.
- Pre-Deal Diligence: Surfacing the Liability Before Signing Turn an unknown software exposure into a priced deal term while the number can still change hands.
- Transfer and Anti-Assignment Clauses Read the clause at the centre of every deal and separate clean transfers from contracts that need consent.
- Transition Service Agreements and Third-Party Use Close the unlicensed-use gap that a TSA opens for both the seller and the buyer of a carved-out unit.
- Divestiture: Splitting One Entitlement Base into Two Model the carve-out split on usage and treat the separation as a renegotiation, not an administrative task.
- Vendor-by-Vendor Mechanics How Oracle, Microsoft, SAP and VMware each treat a transaction, and the pressure point on every one.
- The Audit Risk a Change of Ownership Triggers Build the pre-transaction audit defence and push pre-close exposure onto the seller in the purchase agreement.
Pricing software liability into the deal model before signing
Integrating or separating estates across a transaction
Protecting value across buy-side diligence and carve-outs
Negotiating consent, TSA scope, and pre-close indemnities
Across more than 500 enterprise engagements, buyers we advise have negotiated over $2.4 billion in software contracts, at average savings of 38 percent and average audit claim reductions of 72 percent.Atonement Licensing engagement record
Weekly licensing intelligence for enterprise buyers
Oracle, Microsoft, SAP, and cloud licensing intelligence for enterprise buyers.
Need negotiation support, not just a guide?
A transaction reopens every vendor agreement. Price the licensing risk before you sign.