Why does a divestiture trigger an Oracle review?
A divestiture triggers an Oracle review because corporate change alters who is using the software, and Oracle treats that change as a reason to check whether the existing licenses still cover the new shape of each entity. Mergers, acquisitions, and divestitures all sit on the list of recognised audit triggers, alongside virtualization, Java downloads, and cloud migration, because each disturbs the relationship between the entitlement and the deployment. A divestiture disturbs it sharply, splitting one licensed organisation into two with one set of licenses between them.
The risk is that the change is operational long before it is contractual. The divested business starts running on day one, often still using the parent's Oracle deployments, while the license position that should govern that use has not yet been resolved. That gap between operational reality and contractual entitlement is exactly what an audit prices, and a divestiture creates it by design. Treating the licensing as a closing day detail rather than a deal term is how both entities end up exposed. This article links up to the Oracle license compliance guide, and it sits beside compliance after a merger or acquisition and the Oracle license compliance guide blog.
Do Oracle licenses transfer in a divestiture?
Oracle licenses do not transfer freely in a divestiture; they are governed by the assignment and transfer terms in the agreement, and a divested business usually cannot simply take its share of the licenses without Oracle's consent. The signed contract, not a general assumption about ownership, decides what can move and on what terms. Some agreements permit assignment to a successor entity under defined conditions; others restrict it, require consent, or trigger a re pricing of what remains. The only reliable way to know is to read the specific clause, because the answer is contract dependent.
This is where the divestiture meets the principle that contract language beats policy. A buyer who assumes the licenses will follow the divested business may find the agreement says otherwise, and a buyer who assumes nothing can transfer may give up rights the contract in fact allows. The assignment clause, the territory and entity definitions, and any change of control language together set the rules, and they vary enough between agreements that no general statement substitutes for reading them. Where consent is required, it becomes a negotiation, and that negotiation is far easier before the deal closes than after, when leverage has gone. To prepare the contract side, read reading your Oracle Master Agreement and contract repository hygiene for Oracle.
| Term | What it controls | Why it matters |
|---|---|---|
| Assignment clause | Whether licenses can move | May require Oracle consent |
| Entity and territory definition | Who may use the licenses | Defines the divested user |
| Change of control | Effect of the deal itself | Can trigger review or re pricing |
| Support set grouping | How support reprices on a split | Matching service levels apply |
Why is the transition period a trap?
The transition period is a trap because the divested business often keeps using the parent's Oracle deployments under a transition service arrangement, and that shared use can breach the license terms of both entities unless it is explicitly permitted and documented. A transition service agreement that covers the commercial relationship between the parties does not automatically grant the right to use Oracle software across the new boundary; that right comes from the Oracle agreement, and the Oracle agreement may not contemplate it.
The exposure here is mutual and quiet. The parent may be providing access to software for an entity that is no longer part of its licensed organisation, and the divested business may be using software it has no entitlement to, both at once, for the length of the transition. Because the arrangement is temporary and operational, it is easy to leave undocumented, which is precisely what makes it an audit finding waiting to happen. The fix is to define the Oracle usage explicitly within the transition arrangement, time bound it, and resolve the permanent license position before the transition ends rather than after. Where matching service levels affect how support reprices when the estate splits, the grouping decided now shapes the cost both sides carry. To see how support repricing works on a reduction, read repricing risk when dropping licenses.
A divestiture splits one licensed organisation into two with one entitlement between them. Licenses transfer only as the contract allows, so resolve the split and any shared transition use before the deal closes.
We map the Oracle estate to each entity, read the assignment terms, and resolve the license split and transition use before close. Fixed Fee or Gainshare, a share of verified savings with no risk to you. We reduce your Oracle exposure or we reimburse our service fee.
What is the buyer move in a divestiture?
The buyer move is to map the Oracle estate to each entity early, read the assignment and change of control terms in the agreement, secure any required consent while you still have deal leverage, and define and time bound any transition use before close, so neither side inherits an undefined compliance gap. Start the mapping during diligence, not at signing. Treat the assignment clause as a deal term and negotiate consent as part of the transaction. Write the Oracle usage into the transition service arrangement explicitly rather than relying on a general access provision. Resolve the permanent position before the transition ends. To carry these disciplines into the acquiring side, read across to compliance after a merger or acquisition and up to the Oracle license compliance guide.
FAQ
Is a divestiture an audit trigger? Yes. Corporate change is a recognised trigger, because it disturbs the match between entitlement and deployment.
Do licenses transfer? Not freely. The assignment terms in the agreement govern it, and consent is often required, so it is contract dependent.
What is the buyer move? Map the estate early, treat assignment as a deal term, and document any transition use before close.