Every acquisition, divestiture, and reorganisation during a ULA term moves Oracle workloads across legal boundaries that your customer definition is watching. This checklist keeps each move visible so scope stays intact all the way to certification.
Corporate change is the most common reason a clean ULA breaks at exit. Acquisitions, sales, and internal reorganisations move workloads across the entities your contract names, and certification converts whatever scope exists on its date. Run every deal through a scope review against the ULA clock, and the picture you certify is the picture you intended.
A ULA covers a defined customer: a named set of legal entities, often within a named territory. The unlimited right reaches those entities and no further. Corporate change rearranges the entities. An acquisition adds a company that may or may not be inside the definition. A divestiture removes one and takes its deployments with it. A reorganisation or shared services consolidation moves workloads between entities without anyone asking whether the destination is in scope. Each of these is a licensing event wearing the clothes of a corporate one, and the licensing question usually goes unasked until certification, when it is too late to fix cleanly.
The ULA clock does not stop for a deal. Manage corporate change against the certification date, not just the transaction timeline, or the two will collide on the worst possible day.
Run this list at the start of any transaction or reorganisation that touches an entity where Oracle runs. It is ordered so the highest leverage questions come first, while the deal is still open and the terms can still move.
Before anything moves, list every Oracle deployment and the legal entity it runs in. You cannot judge a scope change without knowing where the software sits today. This map is the baseline the whole review depends on.
For each entity that is joining, leaving, or being merged, check whether it is inside or outside your customer definition and territory. Read the actual clause. Do not assume an acquired company is covered or that a sold one stays covered.
Many ULAs say something specific about companies you acquire during the term, often a size threshold above which a new acquisition is excluded. Confirm what yours says and whether the deal sits inside or outside the threshold.
Decide whether the corporate change should complete before or after certification. The sequence changes the count you keep, and it is a choice you control only while the deal is open.
Put the license outcome in the purchase agreement: who certifies what, whether any entitlement is assigned, and what transition window applies. Settling it in the documents is far cheaper than settling it in an audit.
Snapshot the deployment, the entity, and the transfer date before systems move. The evidence behind your certified count is your audit defense, and corporate change is exactly what erodes it.
Worked through early, this list prevents the three failures we see most. The first is the out of scope deployment, where a workload lands in an entity the definition does not cover and becomes unlicensable. The second is the lost count, where deployments leave with a sold unit that was certified into a number the parent will never own. The third is the evidence gap, where a later audit reads a departed or moved system as a current shortfall because no one recorded what happened and when. Each is avoidable, and each is expensive once certification has frozen the picture.
If a transaction or reorganisation is live and Oracle is anywhere inside it, do not wait for certification to surface the scope questions. A scope reconciliation now maps every deployment to its entity, tests each against your contract, and tells you what to fix while you still can. Two companion notes go deeper: acquisitions during the ULA term on the buy side, and divesting a business unit with Oracle inside on the sell side. The wider method sits in our ULA exit strategy guide.
Because acquisitions, divestitures, and reorganisations move Oracle workloads across the legal entities your customer definition names. A move into an out of scope entity makes usage unlicensable, and a move out takes deployments off your count. Every corporate change is a scope question that needs answering before certification freezes the picture.
Before the deal closes, while you still control where workloads live and what the agreements say. After close the entities are set and certification will convert whatever scope exists on its date. Reviewing the ULA during due diligence is far cheaper than discovering a scope break in an audit two years later.
No. Coverage depends on your customer definition and any clause governing acquired entities. Some ULAs extend automatically up to a size threshold, some require the entity to be added by agreement, and some exclude it entirely. The answer is contract specific and should never be assumed.
We map every Oracle deployment to its entity, test each change against your contract, and keep scope intact through to certification. Book a confidential assessment.