Why M&A and ULAs collide
An Oracle Unlimited License Agreement is written around a fixed organisation, and corporate transactions change that organisation in ways the contract did not assume. The result is that oracle ula mergers and acquisitions questions arise on almost every deal where either party holds a ULA, and the answers turn on two clauses most dealmakers never read: the growth or merger and acquisition clause, and the assignment clause. Getting these wrong can convert a ULA from an asset into a liability mid transaction, which is why the topic recurs throughout the Oracle ULA pillar guide.
The core tension is that a ULA grants unlimited deployment to a defined set of legal entities, and an acquisition introduces new entities and new Oracle usage that the contract did not contemplate. Whether the acquirer's unlimited right extends to the acquired business, or whether the acquired business's own Oracle estate is stranded, depends entirely on the contract terms and the deal structure. Buyers and sellers who model this before signing the deal price it correctly; those who do not inherit a surprise.
When the acquirer holds a ULA
When the acquiring company holds a ULA and buys a target, the question is whether the target's Oracle deployment can shelter under the acquirer's unlimited right. The growth clause usually answers this. Many ULAs permit acquired entities to deploy in scope products only if the acquisition keeps the organisation under a stated growth threshold, frequently expressed as a percentage of revenue or employee headcount, often around ten percent. An acquisition within the threshold can typically be absorbed; one above it falls outside the ULA and the target's usage must be licensed separately or folded in through a renegotiation Oracle will price to its advantage.
A ULA does not automatically cover what you buy. The growth clause decides, and a transformational acquisition can blow straight through it.
This makes the growth clause a live input to deal valuation. An acquirer planning a large acquisition should model the clause during diligence, because a deal that breaches the threshold carries an Oracle licensing cost that belongs in the transaction model. The same discipline applies to a series of smaller acquisitions that cumulatively cross the threshold. The mechanics of how this growth is reconciled connect directly to the ULA true-up triggers, since an out of threshold acquisition is one of the few events that creates a payable position.
When the target holds a ULA
When the company being acquired holds the ULA, the central question is whether its unlimited right and certified entitlement survive the change of control. This is governed by the assignment and change of control provisions. Oracle's standard drafting frequently terminates or restricts the ULA on a change of control, meaning the acquirer may not inherit the unlimited right at all, and may face a renegotiation or a requirement to certify earlier than planned. A target that has not yet certified can find its unlimited right curtailed precisely when the new owner wants to rely on it.
The defensive move for a seller is to certify the ULA before the transaction closes, converting the unlimited right into perpetual licences that are a more durable and transferable asset, subject to the assignment clause. Whether those certified licences can move with the business depends on the assignment terms, which is why a seller preparing for sale should examine both clauses early. The timing of a pre transaction certification is a specialised application of the certification process, and it interacts with the broader exit strategy.
| Scenario | Governing clause | Typical outcome |
|---|---|---|
| Acquirer holds ULA, small target | Growth clause | Target absorbed under threshold |
| Acquirer holds ULA, large target | Growth clause | Breach, separate licence or renegotiation |
| Target holds ULA, change of control | Assignment / change of control | ULA may terminate; certify first |
| Divestiture of a business unit | Assignment clause | Certified licences may not transfer |
Divestitures and carve outs
A divestiture is the mirror image of an acquisition and often the more painful one. When a company sells a business unit, the unit's Oracle deployment was licensed under the parent's ULA, and the assignment clause determines whether those licences can travel with the divested business. Oracle's standard drafting frequently prohibits assignment, which means the buyer of the business unit may need to license its Oracle usage afresh, and the seller may be left certifying and supporting licences for a footprint it no longer owns. Either way, the divestiture carries an Oracle cost that should be identified in carve out planning.
The cleanest approach is to address Oracle licensing in the transaction agreements, allocating responsibility for the divested unit's licences and, where possible, negotiating Oracle's consent to assignment as a condition of the deal. Sellers who plan this early can sometimes certify and assign certified licences to the buyer, preserving value on both sides; those who do not leave the buyer exposed and themselves over licensed. This is a recurring theme in ULA negotiation engagements that arise from corporate activity.
Building Oracle into deal diligence
The remedy for all of these scenarios is the same: bring Oracle licensing into deal diligence as a standard workstream rather than discovering it after close. On the buy side, diligence should establish whether the target holds a ULA, what its certification position is, whether a change of control terminates it, and what the target's true Oracle deployment and entitlement gap looks like. On the sell side, preparation should establish whether to certify before sale and whether certified licences can be assigned to the buyer.
This diligence protects against two distinct risks: paying for Oracle entitlement that will evaporate at close, and inheriting an unlicensed position that surfaces in a post acquisition audit. The latter is a frequent trigger for Oracle review activity, which is why M&A driven licensing questions sit alongside Oracle audit defence in any well run programme. A clear understanding of the contract, validated against actual deployment, lets the dealmakers price and allocate Oracle risk accurately.
The buyer side view
The practical takeaway is that a ULA does not automatically follow corporate transactions, and the growth and assignment clauses decide whether it helps or hurts. An acquirer with a ULA can usually absorb small targets but not large ones; a target with a ULA may lose its unlimited right at change of control and should consider certifying first; a divestiture may strand certified licences unless assignment is negotiated. None of this is visible from the fee, and all of it belongs in deal diligence.
Read the growth and assignment clauses against your transaction pipeline, certify before a sale where it protects value, and allocate Oracle licensing explicitly in deal documents. To work through a specific transaction, read the ULA pillar guide and the exit strategy guide, then engage the ULA negotiation service before the deal closes.
Oracle ULA Mergers and Acquisitions: frequently asked questions
Does an Oracle ULA cover an acquired company?
Only within the limits of the growth clause. Many ULAs permit acquired entities to deploy in scope products if the acquisition keeps the organisation under a stated growth threshold, often around ten percent of revenue or headcount. Acquisitions above the threshold fall outside the ULA and require a separate licence or renegotiation.
What happens to a ULA in a change of control?
Oracle's standard drafting frequently terminates or restricts a ULA on a change of control, so an acquirer may not inherit the unlimited right. A target preparing for sale should consider certifying before the transaction closes to convert the unlimited right into transferable perpetual licences, subject to the assignment clause.
Can ULA licences transfer in a divestiture?
Only if the assignment clause permits it. Oracle frequently prohibits assignment, which can strand certified licences when a business unit is sold and leave the buyer needing fresh licences. Assignment should be negotiated and allocated explicitly in the transaction agreements.
Should Oracle licensing be part of M&A diligence?
Yes. Diligence should establish whether either party holds a ULA, its certification position, whether change of control terminates it, and the real deployment versus entitlement gap. This prevents paying for entitlement that evaporates at close and inheriting an unlicensed position that surfaces in a later audit.