Software licensing in a transaction: where the hidden liability sits
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.
What You'll Learn
- 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
Inside This Paper
1. 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.
2. 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.
3. Transfer and Anti-Assignment Clauses
Read the clause at the centre of every deal and separate clean transfers from contracts that need consent.
4. 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.
5. 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.
6. Vendor-by-Vendor Mechanics
How Oracle, Microsoft, SAP and VMware each treat a transaction, and the pressure point on every one.
7. 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.
Who This Is For
Corporate Development and M&A Teams
Pricing software liability into the deal model before signing
CIOs and IT Leaders
Integrating or separating estates across a transaction
Private Equity Operating Partners
Protecting value across buy-side diligence and carve-outs
General Counsel and Procurement
Negotiating consent, TSA scope, and pre-close indemnities
A transaction reopens every vendor agreement. Price the licensing risk before you sign.
Book a 30 Minute Call