An acquisition, merger or divestiture is one of the most dangerous moments in the life of a software contract — and one of the least planned for. The M&A software license implications of a deal can turn a clean transaction into a multi-million-pound compliance liability, because most enterprise licences are non-transferable by default and many master agreements contain change-of-control clauses that vendors are entitled to enforce the moment ownership changes. Vendors know this: M&A activity is among the top triggers for a software licence audit, and audit teams actively monitor acquisition news to time their reviews for the period when the buyer is most distracted. This guide sets out how to manage licensing through a deal, building on our contract negotiation strategy master guide.
Change-of-Control and Assignment Clauses
The first document to read in any deal is the assignment clause of every material software agreement. Most enterprise licences state that the licence is non-transferable and may not be assigned without the vendor's written consent — which means the target's licences may simply not transfer to the acquirer, or may become unusable until consent is obtained. Some agreements go further, with explicit change-of-control clauses that give the vendor the right to renegotiate or terminate on a change of ownership. Each of these is a point of vendor leverage created precisely when you can least afford a dispute, which is why they sit prominently in our catalogue of software contract red flags.
Why M&A Is an Audit Magnet
Vendors treat corporate change as an opportunity. Oracle's licensing teams, for example, monitor public acquisition announcements and frequently open a "licence review" shortly after a deal closes, knowing the combined organisation is mid-integration and short of bandwidth. The financial exposure is real: the average software audit settlement reached $3.4 million in 2025, and an M&A-triggered audit lands at the worst possible time — when entitlement records from two organisations have not yet been reconciled and nobody can produce a clean effective licence position. The defence is preparation, not reaction, and it is the same discipline set out in our guide to building a software licence compliance program.
Vendors do not audit at random. A public acquisition is a signal that two licence estates are about to merge in confusion — and that the buyer has fresh capital. That combination is why M&A is one of the most reliable audit triggers in enterprise software.
Licensing Due Diligence Before the Deal
Software licensing belongs in the due-diligence checklist alongside the financial and legal review, yet it is routinely omitted until after close. Before signing, the acquirer should obtain the target's complete entitlement records, reconcile them against actual deployment to establish an effective licence position, and identify every agreement with a change-of-control or non-transferability clause. Particular attention belongs on the high-risk publishers — Oracle, IBM, Microsoft and SAP — whose metrics (processor counts, PVU sub-capacity, named users, digital access) are easiest to fall out of compliance on during integration. Where the target runs an Oracle estate, the Oracle vendor hub sets out the specific exposures; for IBM, the IBM vendor hub covers the PVU and ILMT traps that resurface when environments are combined.
| Deal type | Primary licensing risk | Mitigation |
|---|---|---|
| Acquisition | Non-transferable licences; combined over-deployment | Pre-close entitlement review; consent negotiation |
| Merger | Change-of-control termination; metric re-counting | Reconcile both ELPs; renegotiate as one entity |
| Divestiture | Licences stranded with the wrong entity | Negotiate split/transfer rights before separation |
| Carve-out / TSA | Temporary use under transition services | Explicit TSA licensing terms with the vendor |
The Divestiture Problem
Divestitures carry the mirror-image risk: licences stranded with the entity that no longer needs them, while the divested business has no right to the software it depends on. Because licences are non-transferable, the divested unit may need entirely new agreements — at list price, under deadline — unless transfer or split rights were negotiated before separation. The time to secure a divestiture clause is at original signature, not at the point of sale, which is why we counsel clients to build divestiture and transfer rights into every major agreement as standard, a theme we develop in our IT vendor management framework.
Transition Service Agreements add a further trap. When a carve-out continues to use the parent's software for a transition period, that use is rarely covered by the existing licence terms, and the vendor can treat it as unlicensed deployment by a third party. The TSA should specify, in writing and agreed with the vendor where required, exactly which software the separated entity may use, for how long, and under what metric — otherwise the transition period itself becomes a compliance exposure that surfaces in the next audit.
Negotiating From the Deal, Not Against It
Handled well, an M&A event is also a negotiating opportunity. The combined entity has greater volume, and consolidation onto fewer agreements creates the leverage to renegotiate terms across the board — the subject of our vendor consolidation strategy guide. The key is sequence: notify the vendor of the corporate change as the contract requires, but enter that conversation with a reconciled licence position and a clear target, so the vendor's "review" becomes your renegotiation rather than their audit. To plan the licensing workstream of a transaction — before or after close — request a confidential briefing, and structure the governance using our CIO Contract Governance framework. The deals that go badly are the ones where licensing was an afterthought; the ones that go well treated it as a workstream from the first diligence meeting.