Guide
The Complete M&A Software Licensing Guide
Mergers, acquisitions and divestitures change who owns each license and on what terms. This guide covers the challenges, what to watch for, and how LicenseFortress helps buyers and sellers find licensing liabilities before close and turn integration into savings.
Key takeaways
Enterprise software licenses rarely transfer automatically in an acquisition.
Change-of-control clauses can require vendor notice or consent, or trigger renegotiation.
Compliance gaps in the target become the buyer's liability after close.
Vendors monitor public M&A activity and often follow it with audits.
Start licensing due diligence early, so findings can shape price, structure and warranties.
Divestitures need a license separation plan for both the retained and the divested entity.
Base every position on enforceable contract terms, not vendor policy. Include legal review.
Integration is also an optimization opportunity: consolidate, rightsize and renegotiate.
Why M&A changes your licensing position
M&A transactions dramatically change the software licensing landscape. Licenses may not transfer. Contract terms may change. New entities may lose favorable pricing. Compliance gaps in the acquired entity become your liability.
These issues are often discovered too late: after the transaction closes and the opportunity to address them in the deal has passed. By then, you are left with unexpected costs, compliance exposure and vendor leverage.
Proactive due diligence and licensing strategy can identify and address these issues before they become expensive problems.
The 8 core M&A licensing challenges
Licenses may not transfer
Most enterprise contracts include change-of-control provisions that require vendor notification or consent. Some licenses may not transfer at all, requiring new purchases.
Change of control triggers renegotiation
A new owner can reopen contract terms. New entities may lose favorable pricing or volume discounts the original customer negotiated.
Inherited compliance gaps
Compliance gaps in the acquired entity become your liability. They are often discovered after close, when the chance to address them in the deal has passed.
Blind spots across combined environments
Integrating multiple environments, legacy systems and historical entitlements creates inconsistencies vendors can exploit during an audit.
Incompatible license types and metrics
Merging entities may hold different license types, metrics and contract structures that cannot simply be combined.
Revenue- and size-based metrics stop fitting
Structures tied to revenue or organization size can drift badly as acquisitions and divestitures grow or shrink the business. Fees rarely adjust downward on their own.
Divestiture separation
You need to decide which licenses stay, which go, and whether existing licenses can be split or new purchases are required for each entity.
Shelfware and duplicate spend
Shelfware often accumulates through acquisitions and divestitures. Overlapping products and underused subscriptions are common after a merger.
Vendors are watching your deal
Public signals
Vendors monitor public information, such as RFPs, mergers and acquisitions, and layoffs, to find organizations that may be vulnerable to compliance issues.
Audits follow change
Major infrastructure changes are seen as an opportunity to start audits and assert compliance concerns. In one case, Oracle used a public RFP to claim a $2.4M compliance issue.
Casual questions, real risk
Vendors under revenue pressure, especially after big acquisitions, use growth as justification for new license demands. Questions about new users or regions can be treated as evidence. See Ambush Audits™.
Step by step, by deal phase
Phase 1
Due diligence
- 1.Inventory the target's publisher contracts, amendments and order documents
- 2.Identify the legal entity that owns each entitlement
- 3.Flag change-of-control, assignment and affiliate-use clauses
- 4.Build or request an Effective License Position for high-risk publishers
- 5.Surface open audits, disputes and unresolved true-ups
Phase 2
Deal protection
- 1.Quantify licensing exposure before price is final
- 2.Reflect findings in representations and warranties
- 3.Plan vendor notifications and consent requests
- 4.Assess loss of volume discounts or favorable pricing
- 5.Agree who owns remediation for pre-close gaps
Phase 3
Post-merger integration
- 1.Reconcile both entities' entitlements into one position
- 2.Resolve incompatible license types and metrics
- 3.Consolidate duplicate products and contracts
- 4.Retire shelfware before the next renewal
- 5.Renegotiate from a combined, validated baseline
Divestitures
License separation
- 1.Decide which licenses stay and which go
- 2.Confirm whether licenses can be split or assigned
- 3.Confirm whether licenses can be used by acquired or transferred employees
- 4.Identify new purchases the divested entity will need
- 5.Keep both entities compliant from day one
What to check by publisher
| Publisher | M&A focus areas |
|---|---|
| Oracle | Change of control, license transfer, Oracle Cloud; ULAs for organizations expecting M&A growth |
| Microsoft | EA assignment, tenant migration, Microsoft 365 consolidation and rightsizing |
| IBM | License transfer rules, ELA implications, integration |
| VMware by Broadcom | Subscription transfer, environment consolidation |
| SAP | License transfer rules, indirect access, integration |
| Adobe | Creative Cloud, Document Cloud, Experience Cloud transfer |
Contract clauses that decide the outcome
"If you're doing an acquisition or divestiture, do the licenses split? Can they be used if you buy a new company and acquire their employees? A lawyer should look at it."
Customer stories
Energy · Oracle · Audit Defense
Post-merger Oracle audit becomes a $5.2M win
- Months after a merger, Oracle issued an audit claim of more than $6.3M.
- Integrated environments exposed accidental Advanced Compression and Active Data Guard use, plus a disputed cloud vCPU claim.
- With Beeman & Muchmore on legal review, the claim was cut to about $1.09M.
- $125K engagement, more than $5.2M saved, 4,200% ROI.
Fortune 100 · Oracle · Negotiation
Fixing a revenue-based contract after years of M&A
- A revenue-based Oracle structure stopped fitting after years of acquisitions and divestitures.
- Fees did not adjust downward; the client was repeatedly told to 'pay the bill' for eight years.
- LicenseFortress mapped purchases to entitlements and led a coordinated renegotiation with legal support.
- $2.5M first-year savings on a $40K project, 6,150% ROI.
M&A licensing checklist
Related reading
Frequently asked questions
Do software licenses transfer automatically in an acquisition?
Rarely. Most enterprise software contracts include change-of-control provisions that require vendor notification or consent. Some contracts may not transfer at all, requiring new purchases.
When should licensing due diligence start?
As early as possible in the transaction process. Ideally during initial due diligence so findings can influence deal structure, pricing, and representations and warranties.
What are the biggest M&A licensing risks?
Hidden compliance gaps in the target, non-transferable licenses, loss of volume discounts, change-of-control triggers, and incompatible license types between merging entities.
Does an acquisition increase audit risk?
Often, yes. Software vendors monitor public information such as mergers and acquisitions to identify organizations that may be vulnerable to compliance issues, and integrating environments can create blind spots vendors exploit.
How do divestitures affect software licensing?
Divestitures require careful license separation. You need to determine which licenses stay, which go, and whether existing licenses can be split or if new purchases are required.
Can we consolidate licenses after a merger?
Often yes, and this creates significant optimization opportunities. However, it requires careful analysis of contract terms, usage, and vendor consolidation policies.
Do we need legal review?
Yes. Whether licenses split in a divestiture, or can be used by employees you acquire, are contractual questions. LicenseFortress includes legal review through Beeman & Muchmore.
The bottom line
Licensing issues found after close cost more and leave less leverage. LicenseFortress independently reviews contracts and deployments, with legal review included, so licensing risk is priced into the deal, not discovered after it.