Oracle Licence Compliance in M&A Due Diligence: Risks, Rules and the Essential Checklist

Why Oracle Is a Special Risk in M&A

Most enterprise software licensing is managed quietly between a customer and their account team. Oracle licensing in mergers and acquisitions is different. Oracle has dedicated deal monitoring processes, a salesforce structure that rewards revenue from restructuring events, and licence agreements that explicitly address — and restrict — what happens when the licensed entity changes.

The combination of these factors means that an Oracle audit or commercial conversation is almost certain to follow any material M&A transaction involving a significant Oracle footprint. Oracle's approach is not punitive in intent — it is commercial. Every acquisition that brings a new entity's Oracle deployments into scope represents a revenue opportunity for Oracle. The deal team that understands this dynamic can plan for it. The deal team that does not typically discovers it during integration, after close, when negotiating leverage has already been surrendered.

Oracle does not offer blanket multi-entity licence umbrella arrangements that automatically cover combined entities. Contracts are structured as Customer Support Identifiers (CSIs) tied to specific named entities. A ULA (Unlimited Licence Agreement) or PULA (Perpetual Unlimited Licence Agreement) that covers the acquirer does not automatically cover the acquired entity. An OCS (Oracle Cloud Services) arrangement does not transfer to a new parent without amendment. Each of these structures must be explicitly reviewed and renegotiated to cover the post-transaction entity.

Oracle's Licence Transfer and Non-Transferability Rules

Oracle's standard licence agreements contain explicit restrictions on licence transfer. The core rule is that Oracle licences are non-transferable without Oracle's prior written consent. This means a licence granted to Company A cannot be used by Company B — even if Company B has acquired Company A — without Oracle providing formal written authorisation for the transfer.

Asset Purchases vs Share Purchases

The type of transaction structure significantly affects Oracle's licence treatment. In a share purchase (where the acquirer purchases the shares of the target company), the target entity survives as a legal entity and its Oracle licences remain with that entity. The acquirer owns the entity, and therefore indirectly holds the Oracle licences. This is generally the lower-risk structure from an Oracle licensing perspective because the licensed entity has not changed — it is still the same legal entity, now under different ownership.

In an asset purchase (where the acquirer purchases specific assets of the target company rather than its shares), Oracle licences are typically not automatically included in the transferred assets. They remain with the selling entity and cannot be moved to the acquiring entity without Oracle's consent. Buyers in asset purchase transactions who assume they have acquired Oracle software licences as part of the deal often discover post-close that they have no Oracle entitlements — a compliance gap that requires a new licence purchase or a retroactive transfer agreement with Oracle.

Mergers and Amalgamations

Where two entities merge and cease to exist as separate legal entities, Oracle's position is that the surviving entity requires a new licence agreement or a formal amendment to cover the merged entity's operations. Oracle treats mergers as a change of entity that voids the prior licences unless the Oracle agreement is updated to reflect the new legal entity. This is not a theoretical risk — Oracle's audit team routinely identifies the corporate structure change in public records and initiates a compliance conversation shortly after the transaction closes.

M&A as an Oracle Audit Trigger

Oracle's Global Licensing and Advisory Services (GLAS) team tracks M&A activity through public announcements, regulatory filings, press releases, and the commercial intelligence gathered by Oracle's account teams. An acquisition announcement is frequently followed within weeks by contact from the Oracle account team or GLAS, initiating a "licence review" or "compliance assessment" that is, in practice, an audit.

The timing is not accidental. Oracle knows that organisations involved in M&A transactions are distracted by integration work, leadership changes, and IT consolidation projects. Attention to Oracle licence compliance is typically low during this period, which is precisely when Oracle's audit exposure is highest. The combination of distracted IT teams, merged Oracle deployments, and unresolved licence transfer questions creates a compliance gap that Oracle's audit team is structured to identify and monetise.

Common M&A audit triggers include: the acquirer extending access to Oracle systems to acquired entity employees before updating the licence scope, consolidating the target's Oracle databases onto the acquirer's servers under the acquirer's licence without notification, decommissioning the target's Oracle CSIs and assuming their entitlements are absorbed by the acquirer, and allowing combined deployment under a ULA without confirming that the target entity is within scope of the ULA's permitted entity definition.

Oracle M&A Due Diligence Checklist

The following checklist covers the essential Oracle licence due diligence tasks that deal teams should complete before transaction close. For significant Oracle footprints, each item should be assessed by an independent Oracle licensing expert rather than the target entity's internal team, whose familiarity with their own agreements creates blind spots.

Phase 1: Pre-LOI or Early Diligence

• Identify Oracle product footprint: What Oracle products does the target entity use? This includes database (Enterprise Edition, Standard Edition 2), applications (EBS, JD Edwards, PeopleSoft, Siebel), middleware (WebLogic, SOA Suite), Java, and cloud services (OCI, SaaS).
• Obtain licence inventory: Request all Oracle licence order forms, contract amendments, CSI numbers, and Oracle Master Agreement (OMA) terms. This inventory must include both on-premises perpetual licences and any cloud or subscription-based arrangements.
• Identify ULA or PULA status: If the target entity has an active or recently expired ULA or PULA, obtain the agreement terms, the certification date, the certified quantities, and the entity scope. A ULA that covered the target entity may or may not transfer to the acquirer's corporate structure.
• Check support status: Verify that all Oracle products are on active support (CSI status). Lapsed support creates reinstatement costs that can represent a significant liability — Oracle charges back-support fees plus a reinstatement penalty of up to 150 percent of missed fees, and the 8 percent annual escalation applies to the reinstated support base.

Phase 2: Detailed Licence Review

• Assess licence gap for current deployment: Compare current Oracle licence entitlements to actual deployment. This requires running Oracle's discovery scripts or equivalent ITAM tool queries across the target's estate. Identify any compliance gaps under the current entity structure before the transaction changes the compliance picture.
• Review entity scope clauses: Oracle agreements frequently define the permitted entity or permitted use group. Confirm whether the agreement covers subsidiaries, affiliates, and joint ventures, and identify whether the acquirer's entity falls within or outside that definition.
• Identify change-of-control provisions: Oracle OMA terms and specific order forms sometimes include change-of-control provisions that allow Oracle to terminate, modify, or renegotiate the agreement upon a qualifying transaction. Review these clauses with legal counsel before close.
• Assess virtualisation compliance: Oracle's virtualisation and partitioning policies are a frequent source of compliance gaps. Verify that all Oracle database deployments on virtualised infrastructure (VMware, Hyper-V, KVM) are either hard-partitioned and correctly licensed, or that the full host physical processor count is licensed. VMware-based deployments are a particularly common source of audit exposure.
• Review Java licensing status: If the target entity uses Oracle JDK, determine whether they are subscribed to the Java SE Universal Subscription under the enterprise-wide employee metric introduced in January 2023. If not, assess the unsubscribed deployment as a compliance gap to be disclosed in the deal valuation.

Phase 3: Pre-Close Remediation and Negotiation

• Quantify total Oracle compliance liability: Combine identified compliance gaps, unlicensed deployments, unsupported licences, and potential ULA out-of-scope deployment into a single financial exposure estimate. This figure should be included in the deal's representations and warranties section.
• Engage Oracle pre-close (with caution): In transactions where the Oracle footprint is large and complex, proactively engaging Oracle to discuss licence transfer or restructuring can reduce post-close risk. However, this must be done carefully — announcing the deal to Oracle before close can accelerate Oracle's audit response and give Oracle negotiating leverage during a vulnerable transition period. Engage only with clear legal guidance and an experienced Oracle licensing adviser.
• Negotiate deal terms that address Oracle liability: Ensure that representations and warranties in the transaction documents accurately reflect Oracle licence compliance status. Consider requiring the seller to remediate identified gaps before close, or structuring an escrow to cover Oracle compliance costs that arise post-close from pre-close deployments.

Phase 4: Post-Close Integration

• Obtain Oracle written consent for licence transfers: For asset purchase transactions, engage Oracle immediately post-close to obtain written consent for licence transfer. Document all communications in writing.
• Separate or combine CSIs deliberately: Decide whether to maintain the acquired entity's CSIs separately or consolidate them with the acquirer's. Consolidation can simplify management but may change the licence terms, support tiers, or ULA scope. Do not consolidate CSIs without advice.
• Update software asset management records: Integrate the acquired entity's Oracle deployments into the acquirer's ITAM system before any infrastructure consolidation occurs. Integration work that moves Oracle deployments without ITAM tracking creates compliance gaps that are difficult to reconstruct.
• Establish a 90-day Oracle review post-close: Plan a dedicated Oracle licence review within ninety days of close to establish the combined entity's true position. This creates a defensible baseline before Oracle initiates its own review.

Divestitures: The Often-Forgotten Licensing Risk

While most M&A Oracle licensing attention focuses on acquisitions, divestitures carry equal or greater risk. When a business unit is sold, the divesting organisation typically retains its Oracle licences and the divested entity must establish its own Oracle relationships. The receiving party has no Oracle entitlements unless they are explicitly transferred (with Oracle consent) or newly purchased.

Transitional service agreements (TSAs) that allow the divested entity to continue using the divesting organisation's IT systems — including Oracle software — for a defined period post-close are common. Oracle's position is that such TSA arrangements require Oracle's consent if they extend Oracle licence usage to a party that is no longer within the licensed entity's scope. TSA arrangements should explicitly address Oracle licensing, ideally with written confirmation from Oracle that the arrangement is permitted under the existing licences.

Summary

Oracle licence compliance in M&A is not a back-office detail — it is a commercial risk that can materially affect deal value and post-close integration cost. Oracle's non-transferability rules, audit monitoring of deal announcements, and ability to renegotiate terms at transition points make independent Oracle due diligence essential for any transaction involving a significant Oracle footprint. The checklist above is a starting point. For complex transactions, dedicated Oracle licence advisers working alongside the deal team provide the depth of expertise needed to quantify and manage the Oracle risk before it crystallises post-close.