Selling part of the business during a ULA term separates the buyer from your unlimited right, and the deployments leaving cannot simply travel with them. Plan the carve out against the certification clock so the count you keep is protected and the buyer's position is handled deliberately.
A divestment is the mirror image of an acquisition, and it raises questions that are easy to miss because the licensing detail rarely sits at the centre of a deal. When a business unit is carved out and sold, the Oracle deployments running inside it have been operating under your ULA. The day separation completes, that coverage is in question. Handled early, a carve out is a clean separation that protects your certified count and gives the buyer a defined path. Handled late, it can leave the buyer running unlicensed software and leave you certifying deployments you no longer control. This article sets out how carve outs interact with a ULA and what to settle before exit.
The divested entity usually leaves the customer family, so its Oracle deployments stop being covered by your ULA at the point of separation. You certify the deployments that remain inside your scope, and the deployments leaving with the buyer need their own arrangement. A ULA grants unlimited rights to the customer for the term, but those rights are generally not transferable to a separated business without Oracle's agreement, so the buyer's licensing is a question to negotiate rather than a benefit that travels automatically. Place this inside the wider plan in the ULA exit strategy guide.
The instinct in a deal is to assume the target takes its running software with it. With a ULA that assumption is dangerous. The unlimited deployment right belongs to the customer entity defined in the agreement, and assignment or transfer clauses typically restrict moving licenses to a third party. After certification the perpetual licenses you hold are also tied to the customer, and transferring a slice of them to a buyer requires Oracle's consent on terms. Whether any of this is possible, and on what basis, depends entirely on the assignment and transfer language in your specific contract.
Many carve outs run on a transition service agreement, where the seller continues to operate systems for the buyer for a defined period. If those systems include Oracle software, the seller is effectively providing Oracle to a business that has left the customer family, which can fall outside the ULA permissions. The transition period needs an explicit licensing position agreed with Oracle, because a silent assumption that the ULA still covers it is the kind of gap an audit finds later.
Where the carve out sits relative to your certification window changes your options. A divestment that completes well before the window lets you certify a clean position based on the entities that remain, with the buyer's licensing resolved separately. A divestment that overlaps the window forces you to fix a moving target, certifying while deployments and entities are still in transition. As with mergers, the term clock is unforgiving, and the same discipline described in post merger integration and the ULA clock applies in reverse to a separation.
Before a divestment closes, settle five points. Confirm which entities leave the customer family and on what date. Read the assignment and transfer clauses to see what, if anything, can move to the buyer. Define the licensing position for any transition service period. Decide which deployments you will certify and which leave your scope. Agree the buyer's path with Oracle if a transfer is contemplated. The list is indicative and the answers depend on your contract, but settling them before close is far cheaper than after.
Consider a diversified services group, figures indicative, that agreed to sell a division eighteen months before its ULA certification window. The division ran Oracle Database and several options. Early in the process the team established that the licenses could not transfer without Oracle's consent and that a six month transition service period would keep Oracle running for the buyer post close. They negotiated the buyer's separate arrangement with Oracle in parallel, defined the transition period licensing in writing, and certified only the deployments that remained in the retained group. The retained count was clean and defensible, and the buyer started life with a documented position rather than an exposure. Had the separation been left to overlap the window, both sides would have certified or audited from uncertainty.
The buyer side priority in a carve out is the count you keep. Every deployment that remains inside your scope should be measured, evidenced, and certified to the same standard you would apply without a divestment, while the leaving deployments are cleanly excluded and documented as such. That separation protects you from later claims that you under counted or that divested deployments somehow remained your responsibility. The first step in any carve out, as in any merger, is a scope review that maps entities and deployments to the contract, described for the acquisition case in certifying an Oracle ULA after a merger.
A carve out separates a buyer from your unlimited right, and the deployments leaving cannot simply travel with them, so transferability, transition periods, and timing all have to be settled against the certification clock. Read this alongside the ULA exit strategy guide to fit the divestment into your exit plan. If a sale is in progress, the next step is a scope and transferability review before the deal closes.
Not automatically. A ULA grants unlimited deployment rights to the customer entity for the term, but those rights are generally not transferable to a divested business without Oracle's agreement. The buyer typically needs its own license arrangement, and the terms of any transfer have to be negotiated, not assumed.
The divested entity usually leaves the customer family, so its deployments stop being covered by your ULA at separation. You certify the deployments that remain inside your scope. The deployments leaving with the buyer need a transition agreement or a fresh license, and the timing relative to certification matters.
We map the divested and retained estates to your contract, settle the transferability and transition questions, and protect the certified count that stays with you.