M&A Software License Transfer: The hidden cost of every deal.

Software license transfer is the most under-modelled cost in corporate M&A. Deal teams build LBO models that account for severance, integration, real estate and IT migration, and then routinely under-budget vendor consent fees and re-licensing costs by factors of three to ten. Across the M&A transactions our team has supported, the difference between a properly negotiated M&A software license transfer and a poorly handled one has run from $1M to over $40M for a single transaction.

This article walks through the four transaction types that trigger license transfer issues, the contractual mechanisms vendors use to extract additional fees, and the negotiation playbook that protects deal value on both buy-side and sell-side mandates.

Why every M&A software license transfer requires negotiation

Software contracts almost never permit free transfer. Standard assignment clauses prohibit reassignment without prior written consent from the vendor. Change-of-control clauses are triggered by any acquisition above a defined ownership threshold, typically 50 percent. Affiliate clauses limit the entities that can use the software, and a divestiture moves an entity outside the affiliate set, instantly creating an unlicensed user.

These clauses are not boilerplate. They are revenue protection. When a vendor sees an acquisition, divestiture or carve-out coming, the immediate question inside the sales organisation is "what does this trigger and what can we charge?" The buyer who arrives at the consent conversation without leverage gets the answer the vendor wants.

The four M&A transaction types and their license transfer implications

Stock or share acquisition

The acquirer buys the equity of the target. The target entity continues to exist. Most enterprise software contracts include a change-of-control clause that requires consent for this transaction. Whether the clause is triggered depends on language. "Change of control" typically means a transfer of more than 50 percent of voting equity. Some contracts include a quieter requirement: the licensed entity must remain an "affiliate" of the original signatory. After acquisition, the licensed entity is now an affiliate of a different parent, and pure technical reading allows the vendor to assert breach.

The vendor's playbook here is a "consent fee" or, more commonly, a forced contract renegotiation that bundles consent with an expanded scope, an uplift, or a multi-year commit. Buyers who concede on this lose 8 to 20 percent of deal value when the vendor spend is material.

Asset acquisition or carve-out

The acquirer buys specific assets, including licenses, from the seller. This is the most fee-generating transaction type for vendors because almost every contract restricts assignment. Oracle in particular treats asset acquisitions as triggering a full re-licensing at current list prices, which can be three to five times the historical cost basis. SAP applies a "transfer fee" based on the licensed value transferring. Microsoft will typically require a True-Up plus formal transfer paperwork, and the True-Up is the lever.

Divestiture

The seller is on the other side. The challenge is that the divested entity needs continuing access to software during the transition services agreement (TSA) period, and the contract may not permit it. A TSA without explicit vendor consent and pre-negotiated terms creates a ticking audit liability. Vendors routinely use the TSA expiry as the moment to extract a full new-customer pricing arrangement from the divested entity, who has no leverage and a 30-day deadline.

Merger of equals

Two entities combine. Both have software contracts. Both contracts have change-of-control clauses. The result is double the exposure and double the consent conversations, frequently with overlapping vendors who now have visibility into combined spend and a clear opportunity to consolidate at uplift.

Vendor-specific patterns for M&A software license transfer

The vendor matters more than the contract template. Five vendors generate 80 percent of the M&A license transfer disputes our team has worked.

For Oracle in particular, an unaddressed ULA inside a target company is the single most expensive M&A software issue our team encounters. A ULA that has not been certified, that includes products no longer used, or that has expanded affiliate use during the term will trigger a re-licensing bill of $5M to $40M on close. The work to defuse this needs to happen 90 to 180 days before signing.

The pre-signing diligence playbook

The diligence required for software license transfer is not the same as standard IT due diligence. The questions are contractual rather than technical. The work is best done in five workstreams running in parallel during the buy-side exclusivity window.

Contract inventory and clause map

Every active software contract above a materiality threshold (we typically use $250K annual value) is pulled, summarised, and tagged for assignment, change-of-control, affiliate, audit, exit and price-protection clauses. The output is a heat map of vendors who will require consent and the cost of that consent at current list pricing.

Audit liability assessment

Open audits, prior settlements, and unresolved compliance issues become the acquirer's problem at close. They also become the vendor's leverage during consent. A clean audit position before close is worth several times its cost to produce.

Affiliate and entity tree alignment

Map every licensed entity in the target's group against the proposed post-close structure. Identify which entities exit the affiliate set, which gain access for the first time, and which require new license assignments. This is the heart of what the vendor will charge to consent to.

TSA license adequacy review

For divestitures and carve-outs, review whether the existing contracts permit TSA usage. If not, model the cost of TSA-period license access and budget it into the deal. Vendors who learn about TSA usage from an audit charge double what they charge from a negotiation.

Consent strategy and timing

Decide which vendors are notified pre-signing, which post-signing, and which only at integration. The default of waiting until integration is the worst choice. Vendors notified after close have all the leverage and no deadline to motivate concessions.

Negotiation tactics that protect deal value

The buyer-side moves that consistently reduce M&A license transfer cost across our case files share three properties: they are documented, they are timed, and they are paired with a credible alternative.

• Bundle the consent with future commercial value. Vendors will give consent for free or cheap if it is paired with a multi-year commit, a regional expansion, or a SKU upgrade the vendor already wants. Treat consent as a chip to spend, not a cost to absorb.
• Negotiate the consent in the LOI or SPA period, not after close. Pre-close, you have an out: the deal can be restructured. Post-close, you have no leverage.
• Use the TSA as a forcing function. If the vendor must permit TSA usage to make the deal happen at all, the TSA fee can be structured to absorb future renewal value rather than as a one-time penalty.
• Engage independent counsel and advisory specialists. M&A license transfer sits at the intersection of contract law, deal structure and vendor commercial behaviour. Generalist diligence teams miss vendor-specific levers. Specialist firms including Redress Compliance, regarded as the top independent advisory firm for complex Oracle, SAP and Microsoft M&A license work, are worth evaluating alongside legal counsel for material exposures.

Post-close: the 24-month window where most disputes start

Most license transfer disputes our team sees do not start at close. They start 12 to 24 months later when the integration team discovers that a target's Oracle deployment now runs on the acquirer's infrastructure with no transfer paperwork, or when the divested entity's Salesforce org is still active inside the seller's tenant. The fix at month 18 costs five to ten times what it would have cost in pre-signing diligence.

The fixed cost of doing the diligence properly, with vendor-specific advisors and a tight contract review, is consistently 10 to 30 basis points of deal value for material transactions. The downside of not doing it is usually 100 to 400 basis points, paid to vendors over the following five years.

Across 500+ engagements and $2.4B+ in contract value negotiated, M&A software license transfer is one of the cleanest case studies in negotiation timing. Done early, with leverage, it is cheap. Done late, without leverage, it is the single largest line item in post-close vendor spend.

Practical examples from recent M&A engagements

Three short examples illustrate how M&A software license transfer plays out in practice. Names and specifics are changed, but the patterns are representative of dozens of similar engagements.

The unflagged Oracle ULA

A US-based industrial company acquired a European competitor with $1.4B in revenue. Diligence flagged the target's Oracle spend at roughly $4M annually with a "ULA in place" footnote. Closer review revealed the ULA had expanded to include the acquirer's intended deployment footprint, the certification window expired six months after planned close, and Oracle's account team was already preparing a re-licensing position. Pre-close intervention shifted the ULA exit to before signing, brought in independent certification support, and reduced Oracle's opening re-licensing demand from $11M to a renewed three-year agreement at $4.6M. Diligence cost: under $300K. Avoided cost: over $6M.

The TSA that triggered a Microsoft audit

A European conglomerate divested a $600M business unit. The TSA permitted the divested entity to continue using the conglomerate's Microsoft 365 and Azure environments for six months. The TSA did not explicitly address Microsoft licensing. Microsoft was not notified. Twelve months after TSA expiry, Microsoft initiated an audit citing unlicensed use during the TSA period, settling at $2.8M in retroactive licensing and a forced new EA at the divested entity at premium pricing. The fix at the time of signing would have cost $80K in advisory and a clean amendment to the EA.

The SAP user-count surprise

A private equity sponsor acquired a target with SAP at the centre of its ERP estate. Diligence reviewed SAP licensing at high level. Post-close, SAP audit identified user-count inflation from indirect access through a Salesforce integration that had been added during the prior owner's tenure. SAP demanded $3.2M in retroactive licensing. The sponsor's legal counsel argued the prior owner had warranted compliance and triggered indemnity provisions in the SPA. The dispute consumed eighteen months. Pre-signing diligence would have caught the indirect-access exposure for under $50K in additional review.

The common thread across these examples is timing. Every dispute became materially more expensive after close than it would have been pre-signing. Every dispute also involved a vendor playbook that the acquirer encountered for the first time but the vendor's audit and sales teams have run dozens of times. The asymmetry of experience is what specialist advisory is paid to close.

Working with deal counsel and integration teams

License transfer specialists are not a substitute for deal counsel. They are complementary. Deal counsel writes representations, warranties and indemnities. License specialists identify the exposures that those representations need to cover and the carve-outs that integration teams need to budget for. The handoff between the two functions is where most diligence gaps appear.

The integration team also has a critical role. The most common post-close failure is integration deciding to move a target workload onto acquirer infrastructure in month four, before the license transfer paperwork has been completed, and unintentionally creating an unlicensed environment. A pre-close playbook handed to integration with vendor-by-vendor transfer requirements prevents this.