Oracle licences do not transfer automatically with assets, employees, or business units. Every M&A event involving Oracle workloads triggers a discrete negotiation with Oracle — often weeks before deal close, frequently months after, and almost always at a price Oracle controls. The exposure cuts both ways: acquirers inherit unknown ULAs and shelfware; divestors leave behind licences that Oracle reclaims at full price.
Oracle's Master Agreement contains a transfer restriction clause that requires Oracle's written consent for any assignment, transfer, or sublicensing of licences — including transfer to a successor entity, a divested business unit, or a new legal entity formed through reorganisation. The restriction applies to acquisitions, divestitures, joint ventures, and most corporate restructurings.
Oracle's consent is rarely refused outright. Instead, Oracle uses the consent requirement as a negotiation entry point: the customer needs the consent, Oracle does not need to give it, and the price of consent is a renegotiation of the broader Oracle relationship. In our experience, the average consent negotiation has Oracle seeking 30–60% of the deal's licence value as new commitment — frequently structured as a ULA conversion, an unlimited deployment rights expansion, or a multi-year support extension.
Oracle agreements typically require notification of any change of control within 30 days of the event. Customers who miss this window are technically in breach, which Oracle's audit team has been known to reference 12–18 months later as additional leverage. The notification clause is procedural but consequential.
The deal team rarely surfaces Oracle exposure until the model is finalised. By then it's too late.
An active ULA at the time of an acquisition or divestiture creates the single highest licensing exposure in any Oracle deal. The standard ULA contract restricts unlimited deployment rights to the original signing entity and its wholly-owned subsidiaries as of the contract effective date. Acquired entities are generally not covered. Divested entities lose coverage at separation. Oracle's audit team is well aware of every ULA in market and tracks corporate restructuring activity actively.
When an Oracle ULA crosses an M&A event, the standard outcomes are: (a) early certification of the ULA before deal close to lock in the deployment count; (b) negotiated extension of ULA coverage to acquired entities, typically at 25–60% of original ULA value; (c) negotiated carve-out for divested entities, structured as a discrete licence package on the divested side; or (d) ULA termination and re-purchase, which is the least common but sometimes the only path Oracle will accept.
The most defensible route is early certification — completing the ULA certification process before deal close to capture the installed-base count at the high-water mark. This preserves the deployed quantity as perpetual licences and removes the ULA's transfer restriction. Oracle frequently resists early certification but rarely blocks it; the customer's contractual right to certify is unambiguous.
Includes the M&A decision tree, ULA carve-out templates, and the change-of-control workflow.
Transition Service Agreements — the post-divestiture arrangements under which the seller continues to provide IT services to the divested entity for 6–24 months — are one of the most under-modelled licensing risks in M&A. During the TSA period, the divested entity is using Oracle software hosted on the seller's infrastructure under the seller's licences. Oracle's audit position is that this arrangement requires either explicit TSA-period licensing or formal transition licences purchased separately.
Customers frequently structure TSAs assuming the seller's licences extend to the divested users. Oracle does not accept this position. We have seen settlement demands of $2M–$15M arise specifically from un-licensed TSA periods, typically surfacing during routine audits 12–24 months after deal close.
The most effective mitigation is to surface the Oracle licensing question during deal modelling, before TSA scope is finalised. The cleanest commercial outcomes involve: (a) the seller purchasing temporary Oracle "split-use" licences for the TSA period; (b) the buyer purchasing transition licences in parallel with the deal; or (c) the deal value being adjusted to reflect the Oracle exposure transferring to one party.
The pre-close diligence is what determines whether Oracle becomes a value leak or a managed expense.
The standard M&A Oracle due diligence questions:
The financial materiality of Oracle findings in M&A diligence is regularly 1–3% of deal value for mid-market targets with significant Oracle footprints.
For any M&A deal with $5M+ in target Oracle spend, independent licensing diligence is the most cost-effective way to surface exposure pre-signing. Once the deal closes, consolidating the combined estate becomes a software license optimization exercise in its own right — often the first place the integration plan recovers real money.
Our Oracle M&A team has supported diligence and post-close cleanup on $1.8B+ in transaction value.
Weekly compliance intelligence for IT leaders.
