A merger, acquisition, or divestiture collides with a PULA through the customer definition and entity clauses, and because a PULA never certifies, those clauses govern every day rather than only at an exit. Get the scope question answered before the deal closes, because remediation afterwards is slow and expensive.
By the Meridian advisory team, former Oracle LMS and GLAS licensing analysts. Updated 4 June 2026.
M&A interacts with a PULA through the customer definition and the entity list, which together decide who is entitled to deploy under the perpetual right. An acquisition may be inside scope automatically, inside after a defined step, or excluded entirely, and a divestiture usually strips the carve out of any right to deploy from separation. Because a PULA has no certification event, these clauses are not a one time exit problem; they govern continuously, so every corporate change is a licensing event whether or not anyone treats it as one.
In a PULA the customer definition is the perimeter of the perpetual right. M&A moves that perimeter, and value either flows in or leaks out depending on how the clause is written and how the deal is structured.
The customer definition names who holds and benefits from the agreement. It may be a single named legal entity, a parent and its majority owned subsidiaries, or a more expansive group. The breadth of this definition decides whether a newly acquired entity is automatically covered or sits outside the perpetual right until something is done. A narrow definition is a trap waiting for an acquisition; a broad one can be an asset, but only if you understand its limits.
Some agreements attach a fixed list of entities entitled to deploy. Where that list exists, an acquired company is outside it by default, and deploying Oracle inside that company under the PULA can create exposure rather than coverage. The entity list is precise and unforgiving, and it is one of the first things to check when a deal is contemplated.
Change of control provisions govern what happens to the agreement if the customer itself is acquired or undergoes a major ownership change. They can constrain assignment, trigger consent requirements, or in some cases put the perpetual right at risk. For a target that holds a PULA, this language is part of the diligence, and for an acquirer it can change the value of what is being bought.
Where the agreement restricts deployment to defined territories, an acquisition that operates outside those territories may fall outside scope even if the entity itself is covered. Cross border M&A makes territory a live question, and silence in the contract is not the same as permission.
Only if the acquired company falls inside the PULA customer definition and any entity list, and within the permitted territories. An acquisition can be in scope automatically, in scope after a defined step such as a formal addition or a consent, or excluded altogether. The instinct after a deal is to assume the perpetual right simply absorbs the new business, but that assumption is where exposure begins. Treat every acquisition as outside scope until the contract language proves otherwise, then act deliberately to bring it in if the agreement allows. Because the PULA never certifies, an undetected gap does not surface at an exit that forces a reckoning; it accumulates quietly until an audit finds it.
A divested business unit usually loses the right to deploy under the PULA from the moment of separation, because the perpetual right belongs to the customer as defined, not to the unit being sold. The PULA rarely travels with the carve out, and the parent keeps the perpetual fee. That leaves the divested entity needing its own Oracle licensing from day one of independence, and it leaves the seller potentially paying a perpetual fee for an estate that has shrunk. Both sides of a divestiture have a licensing problem to solve, and the time to solve it is before close, when it can be priced into the deal, rather than afterwards when it becomes a remediation.
Take an indicative group holding a PULA with a customer definition limited to a named parent and its majority owned subsidiaries. It acquires a competitor and, assuming the perpetual right is generous, begins deploying Oracle databases across the acquired estate. The acquired company is a separate legal entity not yet brought inside the definition, so the deployments sit outside the perpetual right. Nothing forces the issue at an exit, because there is no exit, so the gap grows for two years until an audit surfaces it and Oracle raises a remediation claim for the unlicensed deployment. The figures are indicative and the outcome depends entirely on the contract language, but the mechanism is reliable: in a PULA, scope errors do not announce themselves, they compound.
| Corporate event | Default PULA position | The deliberate move |
|---|---|---|
| Acquisition | Acquired entity outside scope | Check definition, bring in if permitted |
| Divestiture | Carve out loses deployment right | License the carve out before close |
| Change of control of the customer | Agreement may be constrained | Diligence the clause early |
| Cross border expansion | Territory may exclude it | Confirm territory before deploying |
In a standard ULA, the certification at term end forces a moment of truth: deployment is measured, scope is tested, and errors surface. A PULA has no such moment, which is precisely why scope discipline matters more, not less. The clauses that bite a standard ULA at exit are live throughout a PULA, and an M&A error can accumulate for years before anything brings it to light. The reason there is no forcing event is the perpetual structure itself, which we explain in why there is no certification exit from a PULA. Governance has to substitute for the discipline that certification would otherwise impose.
The defense is a standing process rather than a one off review. Before any deal, read the customer definition, the entity list, the change of control language, and the territory clauses, and map the target or carve out against them. During the deal, price the licensing outcome into the transaction, whether that is the cost of bringing an acquired estate into scope or the cost of standing up independent licensing for a divested one. After the deal, document the new scope position and keep a measured baseline of deployment, so that if a conversion or restructuring of the PULA ever becomes possible you negotiate from a clear picture. Keeping that baseline current is also the foundation for comparing the perpetual structure against the alternatives, which we set out in capped ULA versus standard ULA.
M&A under a PULA is a scope question first and a commercial question second, and the scope question is answered by the customer definition, the entity list, the change of control language, and the territory clauses. Answer it before the deal closes, price the outcome into the transaction, and govern the new perimeter continuously, because a PULA gives no exit at which errors are forced into the open. The full treatment of perpetual agreements lives in our pillar, the PULA guide.
A PULA covers an acquired company only if that company falls inside the customer definition, the entity list, and the permitted territories, and a divested unit usually loses the deployment right at separation. Because a PULA never certifies, these scope questions govern every day and an error compounds silently until an audit finds it. Diligence the clauses before any deal, price the licensing outcome into the transaction, and keep a measured baseline ready for any future negotiation.
Only if the acquired company falls inside the PULA customer definition. The customer definition, entity list, and any change of control language decide whether an acquisition is automatically in scope, in scope after a step, or excluded. Because a PULA has no certification, the answer governs every day, not just at an exit, and it depends entirely on the contract.
A divested unit usually loses the right to deploy under the PULA from separation, so its Oracle estate needs its own licensing. The PULA rarely transfers with the unit, and the parent keeps the perpetual fee. Plan the licensing of the carve out before close, because remediation after the fact is expensive and slow.
Book a confidential assessment and we will read your PULA, map the target or carve out against its scope clauses, and tell you what the deal does to your licensing position.