Why Oracle Licensing Is a Critical M&A Risk Factor

Oracle's licence agreements contain a fundamental principle that creates immediate complexity in any corporate transaction: licences are granted to specific legal entities and are non-transferable without Oracle's prior written consent. This principle applies whether you are acquiring a company with an Oracle estate, divesting a business unit that uses Oracle software, or merging two organisations with overlapping Oracle deployments.

Unlike software vendors who take a pragmatic approach to corporate transitions, Oracle treats every merger, acquisition, and divestiture as a commercial event — an opportunity to conduct a licence review, identify under-licensing, and expand the commercial relationship under the pressure of transition. Oracle's License Management Services (LMS) team actively monitors corporate announcements and news feeds, and it is common for organisations to receive an Oracle audit request within weeks of a major corporate transaction being publicly announced.

The financial consequences of inadequate Oracle licence management during M&A can be substantial. Organisations that fail to inventory, assess, and plan their Oracle licensing position before a deal closes regularly face seven-figure compliance findings that were entirely preventable. Oracle licence management should be a standard component of M&A due diligence, treated with the same rigour as financial, legal, and operational due diligence.

Oracle Licence Rules in Acquisitions

The Non-Transferability Principle

Oracle's Master Agreement typically states that licences may not be assigned, sublicensed, or otherwise transferred without Oracle's prior written consent. When Company A acquires Company B, Company B's Oracle licences do not automatically transfer to Company A or to the combined entity without Oracle's approval. This creates an immediate compliance question: what happens to Company B's Oracle software during the transition period before formal assignment is completed?

In practice, Oracle recognises that corporate transitions take time and generally provides a grace period for formal assignment processing. However, this grace period is not unlimited and is not contractually defined in most standard agreements. The appropriate response is to notify Oracle of the transaction immediately upon closing and initiate the formal assignment process without delay. Oracle will use the assignment process to conduct a full licence review of both the acquired entity and the acquiring organisation.

Acquired Entity Oracle Footprint Assessment

During acquisition due diligence, a complete Oracle licence assessment of the target company's estate should be conducted before the deal closes. This assessment should identify: every Oracle product deployed by the target, the licence metrics and quantities covered by the target's Oracle agreements, the Oracle support fee base and annual escalation (at 8% per year), any ULA or PULA agreements in place and their terms, any outstanding audit findings or pending LMS reviews, and any compliance gaps that represent inherited liability.

Compliance gaps discovered after deal close become the acquirer's problem. Oracle will treat post-merger under-licensing as the combined entity's liability, and the acquirer's ability to dispute findings is significantly weaker after the transaction is complete than during pre-close due diligence when commercial leverage exists through deal conditionality.

ULA and PULA Complications in Acquisitions

If either party to an acquisition holds an Oracle Unlimited License Agreement (ULA) or Perpetual Unlimited License Agreement (PULA), the transaction creates immediate complications. ULA agreements specify the exact legal entities authorised to deploy under the unlimited rights. An acquired entity is not automatically included in the acquirer's ULA — and the acquirer is not automatically entitled to deploy under the target's ULA.

Oracle's standard ULA terms include provisions that address acquisitions, typically requiring notification and Oracle's approval for an acquired entity to join the ULA scope. Oracle uses this approval process to evaluate whether the acquisition materially changes the deployment footprint and whether the ULA terms remain commercially appropriate for Oracle given the expanded deployment scope. In some cases, Oracle may refuse to extend ULA coverage to a material acquisition and require a separate licence purchase for the acquired entity's Oracle deployments.

Facing an Oracle licensing question in an M&A transaction?

Redress Compliance provides independent Oracle M&A licensing advisory. Buyer side only.
Talk to an Expert →

Oracle Licence Rules in Divestitures

The Divested Entity's Licence Rights

When a business unit or subsidiary is divested — either through a sale to a third party or a spin-off — the divested entity loses its right to use Oracle software covered by the parent's licence agreements from the moment it ceases to be a member of the licenced group. Oracle's licence agreements do not automatically carve out or transfer coverage to the divested entity. The new standalone entity must either negotiate its own Oracle agreements or cease using Oracle software.

This creates a practical challenge: the divested entity's operations may depend on Oracle software that must continue running during the transition. Oracle provides transitional services agreements in some cases, but these are separately negotiated, time-limited, and priced as commercial arrangements rather than rights transfers. The transition period during which the divested entity is operating under a TSA for Oracle software is often an audit opportunity Oracle uses to assess the divested entity's actual deployment footprint.

Licence Carve-Out in Divestiture Agreements

Well-structured divestiture agreements explicitly address Oracle licence treatment. The key commercial question is whether any Oracle licences can be formally transferred to the divested entity. Oracle will need to consent to any licence transfer. The transfer process requires a formal licence assignment agreement between the parent, the divested entity, and Oracle, which Oracle will use as a full licence review opportunity.

When negotiating the licence carve-out, the priority is to identify which Oracle licences are genuinely necessary for the divested entity's operations and to obtain Oracle's consent for their formal transfer before the divestiture closes. Licences that remain with the parent company after the divestiture will have their support base assessed against actual deployment, which may reveal that the parent company is now over-licensed — potentially creating an opportunity to reduce support fees, subject to Oracle's repricing rules.

ULA Treatment in Divestitures

A ULA creates particular complexity in a divestiture because the unlimited deployment rights belong to the legal entity that signed the ULA, not to the business unit being divested. The divested entity cannot take ULA rights with it — it loses access to the unlimited deployment coverage from the divestiture date. Any Oracle software running in the divested entity's environment under ULA coverage becomes unlicensed from that date unless separately licensed.

If the divestiture is occurring during an active ULA term, the parent company may have an incentive to maximise deployment of ULA-covered products across the divested entity's environment before the divestiture date — because any deployments in place at divestiture become part of the certification base when the ULA certifies. The divested entity's right to continue using those deployments after divestiture must be separately negotiated. The parent company retains the perpetual licences for the quantities deployed at certification, not including deployments that moved to the divested entity.

"Oracle monitors M&A announcements as closely as your account team tracks your renewal dates. An unmanaged acquisition or divestiture is Oracle's preferred audit trigger — the compliance confusion of transition creates maximum commercial leverage."

The Oracle Audit Risk in M&A Transactions

Why M&A Is Oracle's Top Audit Trigger

Oracle's LMS team has identified M&A activity as one of the most reliable indicators of compliance risk. The reasons are structural: mergers combine two separate Oracle estates that were each independently managed, often creating overlapping licences, undiscovered compliance gaps, or deployed products that span both legacy environments without consistent licence coverage. The complexity of the combined entity's Oracle position creates blind spots that LMS is trained to identify and monetise.

Divestitures are equally productive for LMS: the operational disruption of splitting an organisation creates compliance gaps as staff and systems move between entities, licence records become unclear, and neither the parent nor the divested entity has a complete picture of who is running what Oracle software under which agreement.

How to Reduce Audit Risk During M&A Transitions

The most effective risk management strategy is to conduct a comprehensive Oracle licence assessment on both entities before engaging with Oracle about the transaction. This provides three advantages: it establishes an accurate baseline before Oracle has access to your data, it identifies any compliance gaps you can address before they become audit findings, and it gives you a defensible record of your licence position at the transaction date that cannot be retroactively challenged.

Engaging Oracle proactively — in writing, with a formal notification of the transaction and a request to initiate the formal assignment process — puts the assignment timeline under your control rather than Oracle's. Oracle's audit rights are strongest when they initiate the review; Oracle's commercial flexibility is greatest when the customer initiates the conversation and has independent advisory support at the table.

Client outcome: In one engagement, a global professional services firm discovered during post-acquisition integration that the acquired entity had deployed Oracle Database Enterprise Edition on a VMware cluster with no hard-partitioning — creating an unplanned licensing exposure of $6.8M. Our Oracle mergers acquisitions advisory team negotiated a structured resolution that capped the liability at $1.1M and secured a licence consolidation agreement. The engagement fee was less than 4% of the avoided exposure. Engage Oracle licensing advisory specialists before any M&A due diligence, not after.

Oracle M&A Licensing Best Practices

Effective Oracle licence management through M&A requires a structured approach built around five principles: early assessment, written communications, independent advisory, commercial strategy, and documented compliance position.

Early assessment means conducting a full Oracle licence review of both entities at the due diligence stage — ideally before exclusivity, and certainly before deal close. Written communications means every interaction with Oracle about the transaction is documented in writing, with Oracle's responses obtained in writing before any reliance is placed on verbal commitments. Independent advisory means engaging Oracle licensing specialists who are not conflated with Oracle's account team or the deal's M&A advisors — their interest is in the correct commercial outcome, not in facilitating the transaction.

Commercial strategy means treating the M&A transaction as a commercial negotiation with Oracle, not merely an administrative notice. The notification to Oracle should be structured to open a commercial conversation about the combined entity's licensing needs, support fee consolidation opportunities, and appropriate treatment of any compliance gaps identified during due diligence. Documented compliance position means maintaining a clear, written record of what each entity owns, what it deploys, and the compliance status at each material date in the transaction — pre-announcement, at close, at assignment, and post-integration.

Oracle's support fees increase by 8% per year regardless of transaction activity. Organisations that combine two Oracle support streams through an acquisition without rationalisation will pay 8% annual growth on the combined support base. A $10 million combined Oracle support base in Year 1 becomes $14.7 million by Year 6 without any incremental licensing. M&A is an opportunity to rationalise the combined Oracle estate, eliminate redundant licences, and right-size the support base — but this rationalisation requires careful execution to avoid Oracle's repricing rules and audit triggers.