Divestiture as the mirror of acquisition
A ULA growth clause governs how acquisitions are absorbed under the unlimited right, a topic covered in the ULA mergers and acquisitions guide. Divestiture is the inverse transaction and the contract treats it with far less generosity. Where an acquisition can often be folded in under a growth threshold, a divestiture typically removes an entity or business from the scope of the agreement, and the licences associated with it do not simply follow the business to its new owner. Understanding this asymmetry is the starting point, and it rests on the basic scope and assignment mechanics described in the Oracle ULA pillar guide.
The asymmetry exists because the unlimited right is granted to specific named legal entities for a fixed fee. Removing a business from that group does not entitle the departing entity to carry the unlimited right out of the door, and Oracle agreements are generally drafted to prevent exactly that. The consequence is that divestiture creates a discontinuity for the divested business and a planning obligation for the parent, both of which must be managed before the deal closes rather than after.
What is the default position on a ULA carve out?
The default position in most ULAs is that the unlimited right is non transferable and that a divested entity, once it ceases to be part of the licensed group, loses the right to deploy in scope products under the agreement. The divested business does not receive perpetual licences for its Oracle estate simply because it ran on Oracle while inside the parent; without a specific arrangement it becomes unlicensed on the day it leaves. This is frequently a surprise to deal teams who assumed the running software carried its own rights.
The unlimited right was granted to the parent, not to the business. Sell the business and the right stays behind, which means the licences must be deliberately created before the doors close.
For the parent, the divested deployment that was previously free under the unlimited right may need to be certified or otherwise accounted for, depending on the timing relative to certification. For the buyer, the acquired Oracle estate needs a licensing path that does not depend on the seller's ULA. Neither outcome happens automatically, and both require the assignment, certification, and transition provisions to be addressed in the sale documentation.
How sale timing interacts with certification
Timing is decisive. A divestiture that closes well before certification removes the divested deployment from the estate, so the parent should ensure the deployment it intends to retain is unaffected and that nothing it wants to count leaves with the sold business. A divestiture that closes near or after certification raises the question of whether the divested deployment was counted at certification, and if so, whether those certified licences can be allocated to support the carve out under a transition arrangement.
| Sale timing | Effect on parent | Effect on divested business |
|---|---|---|
| Early in the term | Retained estate continues unlimited | Needs its own licences from close |
| Shortly before certification | Decide what to count | May rely on transition services |
| After certification | Holds fixed perpetual quantity | Allocation from certified licences if agreed |
| Concurrent with renewal | Restructure scope at renewal | Carve out priced into new deal |
The interaction with certification is why divestiture belongs in the wider ULA exit strategy. A parent approaching certification while contemplating a sale must decide whether to count the divested deployment, which it may then be able to allocate to the buyer under transition terms, or to exclude it, which simplifies the parent's position but leaves the buyer to license from scratch. The right answer depends on the deal value and the relationship the parties want post close.
What the buyer of the business needs
From the buyer's perspective, the acquired business arrives with Oracle software running but, in most cases, without portable rights to it. The buyer therefore needs a licensing solution effective from close, whether that is a set of perpetual licences allocated from the seller's certified entitlement, a transition services agreement that lets it run under the seller's licences for a defined period, or a fresh agreement with Oracle. Each path has cost and risk implications that should be negotiated as part of the purchase price rather than discovered afterward.
Buyers should conduct Oracle licensing diligence on any carve out exactly as they would on a standalone target, because the absence of transferable rights means the Oracle estate can carry a hidden licensing liability. Where the buyer will stand the business up independently, it must size the Oracle requirement and decide how to meet it, often under time pressure created by the transition deadline.
Transition services and continued use
The bridge that makes most carve outs workable is the transition services agreement, under which the seller continues to provide certain services, sometimes including the right to use software, to the divested business for a defined period after close. A well drafted transition arrangement can allow the divested business to continue running Oracle under the seller's licences while it builds its own licensing position, but the seller must ensure that this continued use is permitted under its ULA or successor agreement and does not itself create a compliance breach.
This is delicate, because using the seller's licences to support a business that is no longer part of the licensed group can run against the very non transferability that makes divestiture hard. The transition terms must therefore be drafted with Oracle's rules in mind, and in many cases discussed with Oracle directly, so that the bridge does not become a finding in a later Oracle audit defence exercise. The duration and scope of any continued use should be explicit and time limited.
Protecting parent entitlement on divestiture
The parent's priority is to ensure the divestiture does not erode the entitlement it intends to keep. That means confirming that the retained estate sits within retained legal entities, that nothing the parent wants to certify depends on the entity being sold, and that the sale documentation does not inadvertently assign or extinguish rights the parent needs. Where certification is near, the parent should decide deliberately what to count and what to release, and should sequence the certification and the close so the two do not collide.
Because these decisions sit at the intersection of corporate development and licensing, they are best handled as a single coordinated workstream, which is the approach taken in the ULA negotiation service. Engaging licensing expertise during deal structuring, not after signing, is what keeps a divestiture from quietly stranding entitlement or creating exposure on either side.
The buyer side view
The buyer side view is that divestiture is an active licensing event, not a passive consequence of a corporate decision. The unlimited right stays with the parent, the divested business needs its own path from close, and the timing against certification determines what can be counted and allocated. The organisations that handle this well bring licensing into deal structuring early, decide consciously what to certify and what to release, and draft transition terms that respect Oracle's non transferability rules.
Map the Oracle estate of any business you plan to sell against your licensed entities and your certification timeline, read the mergers and acquisitions guide for the acquisition mirror image, and treat every carve out as a licensing transaction that must be priced and planned before the sale agreement is signed.
Oracle ULA divestiture: frequently asked questions
Does the unlimited right transfer when we sell a business?
Generally no. A ULA is granted to specific named entities and is typically non transferable, so a divested business loses the right to deploy in scope products on close unless a transition arrangement or negotiated assignment is agreed. See the ULA pillar guide.
What happens to the divested business's Oracle licences?
Without a specific arrangement the divested business becomes unlicensed on the day it leaves the group. It needs licences allocated from the seller's certified entitlement, a transition services agreement, or a fresh agreement with Oracle, effective from close.
How does divestiture timing affect certification?
A sale before certification removes the divested deployment from the estate; a sale near or after certification raises whether that deployment was counted and can be allocated to the buyer. Sequence the close and certification deliberately. See the exit strategy guide.
Can a transition services agreement cover continued Oracle use?
Sometimes, if drafted to respect the ULA's non transferability rules. The seller must confirm that continued use by the divested business is permitted and time limited, or it risks creating a compliance breach of its own agreement.