A merger, acquisition, or divestiture triggers software re-licensing under change-of-control clauses that can void existing transfers and create seven-figure exposure, which is why entitlement diligence belongs before the deal closes, not in the post-merger audit. Software licenses are not assets that move freely with a business. Most are personal to the contracting entity and carry change-of-control restrictions that let the vendor block a transfer, demand a transfer fee, or re-price the estate at the new owner's terms. This guide explains how the three deal types affect licensing, where the exposure hides, and how to plan transfer so the deal model is not undone by a contract clause no one read.
Why software does not transfer like other assets
When a business changes hands, its property, contracts, and people generally move with it. Software licenses are the exception. A license is a grant of rights to a named entity, and the agreement almost always restricts assignment. The vendor's logic is commercial: a transfer is an opportunity to re-sell. The result is that the buyer of a business may acquire the right to use software only to discover the licenses cannot legally move, leaving the acquired operations unlicensed from day one. The starting discipline is the same entitlement reconciliation used everywhere else, applied to the deal perimeter, as set out in our license metric mapping guide.
The three deal types and their licensing effect
Each transaction structure affects licenses differently, and the differences decide where the exposure sits.
| Deal type | Licensing effect | Primary exposure |
|---|---|---|
| Stock / share purchase | Entity survives, licenses stay with it | Change-of-control clause may still trigger consent or fee |
| Asset purchase | Licenses do not transfer automatically | Re-licensing of acquired operations, transfer consent |
| Divestiture / carve-out | Licenses stay with the parent | Divested unit left unlicensed, shared-agreement split |
The stock purchase looks cleanest because the contracting entity survives, but a change-of-control clause can still let the vendor demand consent or a fee even when the entity itself does not change. The asset purchase is the most exposed, because licenses bought as part of a business unit usually do not move without the vendor's agreement. Divestitures create the mirror problem: the unit being sold loses access to licenses that stay with the parent, and any shared global agreement must be split.
The transition-services trap: Most carve-outs run on a transition services agreement where the seller keeps providing IT, including licensed software, to the divested unit for a period after close. Vendors frequently treat this as unlicensed third-party use by an entity no longer covered by the agreement. The transition-services period must be explicitly licensed, either through the seller's agreement with vendor consent or through a temporary license, before close. This is one of the highest-frequency findings in post-divestiture audits, and it connects directly to the change of control clauses that govern who is a covered entity.
Where the exposure hides
The largest M&A licensing surprises come from a handful of recurring places. Change-of-control and anti-assignment clauses that block or charge for transfer. Affiliate definitions that no longer cover the post-deal structure. Per-employee and enterprise metrics that re-price when headcount jumps after an acquisition. Indirect-access exposure created when two newly combined systems start sharing data. And duplicate entitlements, where both companies licensed the same product and the combined entity now pays twice. Each of these is a clause or a count that diligence can surface before close, and that a post-merger audit will surface after, at a worse price. The clause-level red flags are catalogued in our contract red flags guide.
The metric shock of combination
Combining two workforces can move an enterprise across pricing tiers overnight, especially under per-employee or per-FTE metrics. The table illustrates the effect.
| Pre-deal position | Combined position | Licensing effect |
|---|---|---|
| Acquirer at 18,000 employees | Combined 26,000 | Per-employee tier breach, mid-term true-up |
| Two separate enterprise agreements | One entity, two EAs | Duplicate spend until consolidation |
| Target on legacy perpetual | Forced onto acquirer subscription | Re-licensing at current list, not legacy rate |
The duplicate-agreement row is where post-deal savings live, but only if the contract allows reduction. A merger creates overlapping entitlements that sit on the books until a renewal, and they can only be unwound with a true-down right. Consolidating the two estates also raises the global-versus-regional question, since the combined entity often inherits a patchwork of agreements that the structure in our global vs regional agreements guide helps rationalize.
Planning transfer before close
The sequence that contains M&A licensing risk: inventory the entitlements inside the deal perimeter, read every change-of-control and assignment clause for the major vendors, model the metric shock of combination against current pricing tiers, identify duplicate entitlements and transition-services exposure, and open vendor consent conversations before signing rather than after. Vendors hold far less bargaining power before close, when they do not yet know the deal is happening, than after, when the unlicensed operations are a fact and the audit clock is running. The timing logic is the same one in our negotiation tactics guide.
Software licensing is one of the most commonly under-scoped areas of deal diligence, and the bill arrives after close when the bargaining power is gone. Our software licensing advisory practice runs entitlement diligence inside the deal timeline, prices the change-of-control and metric exposure, and plans the transfer and consolidation so the synergy case in the deal model survives the post-merger audit.
Reading the change-of-control clause before signing the deal
The change-of-control clause is the provision that decides whether a license survives a transaction at all. Some are benign, requiring only notice. Others let the vendor terminate on a change of ownership, demand a transfer fee, or re-price the estate. The worst convert a routine acquisition into a forced renegotiation at the vendor's chosen moment. Reading these clauses for every major vendor inside the deal perimeter is the core of licensing diligence, and it cannot wait until after close, because after close the vendor knows the deal happened and the buyer has lost the ability to plan around the clause.
The clause interacts directly with the affiliate definition. A narrow affiliate definition means newly acquired entities are not covered and must be licensed afresh. A broad one may pull the acquirer's wider group into scope in ways the vendor can use. The full anatomy of these provisions is set out in our change of control clauses guide.
Divestiture and the carve-out license
Selling a business unit raises the mirror problem of an acquisition. The divested unit has been running on the parent's licenses, and those licenses do not leave with it. From the day of separation, the carved-out entity needs its own agreements, and the buyer of that unit will expect either transferred licenses or a clean licensing position. Neither is automatic. The seller must either secure vendor consent to transfer a defined slice of the estate, or the buyer must license the unit independently, and the cost of doing so belongs in the deal price.
The transition-services period makes this acute, because the seller often keeps running the unit's systems for months after close. Every licensed product used during that period must be explicitly covered, or the seller is providing unlicensed software to a third party and the buyer is using software it has no right to. This is the single most common post-divestiture audit finding.
| Diligence item | Acquisition | Divestiture |
|---|---|---|
| Change-of-control clause | Does it block or charge transfer? | Does it permit a partial carve-out? |
| Affiliate definition | Are acquired entities covered? | Is the divested unit removable? |
| Metric tier | Does combination breach a tier? | Does separation drop a tier? |
| Transition services | Seller-provided software licensed? | Period explicitly covered? |
The pre-signing consent advantage: Opening vendor consent conversations before the deal is public gives the buyer the strongest possible position, because the vendor cannot yet treat the transaction as a forced event. Once the deal closes and the unlicensed operations are a fact, the audit clock starts and the vendor sets the terms. Diligence that surfaces the change-of-control exposure early, then plans consent into the deal timeline, converts a post-close surprise into a managed cost. The reconciliation that scopes it is in our license metric mapping guide.
M&A licensing is rarely a deal-breaker, but it is routinely a deal-mispricer. The exposure is knowable before close and unmanageable after it, which is the entire argument for treating software entitlements as a diligence workstream rather than a post-merger cleanup.
A worked deal: the carve-out that nearly broke the model
Consider a corporate parent divesting a business unit to a private-equity buyer. The unit ran on the parent's enterprise agreements for three major software vendors, and the deal model assumed those licenses would simply follow the unit. Diligence found otherwise on all three.
The first vendor's agreement contained an anti-assignment clause that blocked transfer without consent, and the vendor's opening position was to re-license the divested unit at current list, a 2.4 million dollar annual cost the model had not carried. The second vendor priced per employee across the whole parent group; separating the unit dropped the parent below a volume tier, raising the parent's own per-employee rate, an exposure on the sell side no one had modeled. The third issue was the transition-services agreement: the parent would run the unit's systems for nine months after close, which the first vendor treated as unlicensed third-party use during the very period the consent dispute was unresolved.
The resolution turned on timing. Because the exposures were found before signing, the parent opened consent conversations while it still controlled the narrative, rather than after close when the unlicensed operations would have been a fact and the audit clock running. Vendor one granted a transfer for a one-time fee far below the re-licensing demand, in exchange for the buyer committing to a forward term. Vendor two's tier exposure was managed by timing the separation to a renewal where the parent re-based its own agreement. The transition-services period was explicitly licensed in the separation agreement, closing the most common post-divestiture finding before it could arise.
The deal closed with the licensing cost priced into the purchase agreement rather than surfacing as a post-close surprise, which is the entire point. The same facts discovered six months after close would have arrived as three separate audit claims with no bargaining power and no time to plan, and the synergy case in the model would have eroded quietly. Treating software entitlements as a diligence workstream, not a post-merger cleanup, is what kept the exposure knowable and the cost contained.
The bottom line on M&A licensing
Software licenses do not move freely with a business, which is why a merger, acquisition, or divestiture so often turns into a re-licensing event no one priced. The exposure clusters in a few knowable places: change-of-control and anti-assignment clauses that block or charge for transfer, affiliate definitions that no longer fit the post-deal structure, per-employee metrics that breach a tier when two workforces combine, indirect access created when two systems start sharing data, and duplicate entitlements that leave the combined entity paying twice. Every one of these is discoverable in diligence and unmanageable after close, when the unlicensed operations are a fact and the audit clock is running. The transition-services period is the highest-frequency trap, because seller-provided software to a divested unit is unlicensed third-party use unless explicitly covered. Treat entitlements as a diligence workstream, open vendor consent before the deal is public, and the licensing cost stays priced into the deal rather than surfacing as a post-close surprise.