CIO Checklist for Oracle Licensing in M&A
Due Diligence Steps Before, During, and After a Merger

This article is part of our Oracle Knowledge Hub. See also: Oracle Pricing Benchmarks, Oracle Contract Negotiation Service, and Oracle Audit Defense Service.

01 — Why Oracle Licensing Due Diligence Matters in M&A

Oracle licensing is among the most complex and financially significant elements of any technology estate. When two organisations merge — or when a business unit is divested — the licensing implications can be severe. Oracle contracts contain restrictive assignment clauses, change-of-control provisions, and territorial limitations that do not automatically transfer with corporate ownership changes.

More critically, Oracle actively monitors M&A activity and frequently uses mergers as a trigger for licence audits. The period immediately following an acquisition is when organisations are most vulnerable: systems are being integrated, deployments are expanding onto new infrastructure, and contract ownership may be ambiguous. Oracle’s License Management Services (LMS) team knows this, and they time their audit notifications accordingly.

Financial Exposure: Oracle compliance claims in post-M&A audits routinely reach $2 to $8M for mid-to-large enterprises. The combination of expanded deployments, inherited non-compliance from the target company, and Oracle’s aggressive pricing methodology creates significant financial risk that must be quantified before closing.

Audit Timing: Oracle typically initiates audit activity within 60 to 90 days of a publicly announced merger or acquisition. Their opening compliance claims are routinely 3 to 5 times the actual exposure — but without thorough documentation, you lack the evidence to challenge their methodology.

Contract Complexity: Oracle contracts contain assignment restrictions that may require Oracle’s written consent for transfer, change-of-control clauses that could trigger renegotiation rights, and territorial limitations that become problematic when the combined entity operates in new geographies.

ULA Complications: Unlimited License Agreements are particularly dangerous in M&A. A ULA may not extend to the acquired company’s deployments, and certifying a ULA during an integration period can lock you into an unfavourable licence position before understanding the full scope of the combined estate.

The checklist below provides a structured approach to managing Oracle licensing through every phase of an M&A transaction. Each step includes specific actions, responsible parties, and practical guidance drawn from real-world M&A advisory engagements.

02 — Phase 1: Pre-Merger Inventory and Contract Review

The pre-merger phase is where the foundation for licensing success is built. Without a thorough understanding of both organisations’ Oracle estates, you are negotiating and integrating blind.

Step 1: Inventory All Oracle Software Across Both Organisations

Before the merger closes, inventory every Oracle product deployed at both companies. Document each deployment with product name, version, edition, platform (operating system and hardware), and usage metrics (Named User Plus counts, processor cores, partitioning configuration). Include development, test, disaster recovery, and non-production environments — these are frequently where compliance gaps hide. Use Oracle’s own measurement scripts (LMS Collection Tool) to gather raw data, but analyse the results independently rather than sending them to Oracle. This inventory becomes the baseline for every subsequent step.

Step 2: Analyse Every Oracle Contract and Ordering Document

Gather all Oracle licensing contracts from both organisations: Oracle Master Agreements (OMAs), ordering documents, Unlimited License Agreements, support renewal documents, Cloud subscription agreements, and any amendment letters. Review each contract for assignment and change-of-control clauses, territorial restrictions, entity-specific limitations, and special pricing terms. Map which legal entities are authorised to use which licences — Oracle licences are typically granted to the specific entity named on the ordering document, not to the parent company or “the group” broadly. Note contract expiry dates, renewal terms, and any ULA certification deadlines that may fall within the integration window.

Step 3: Map Licence Entitlements to Actual Deployments

Create a reconciliation matrix that maps every Oracle deployment (from Step 1) against the corresponding licence entitlement (from Step 2). This is the effective compliance position (ECP) — the gap analysis that reveals where each organisation stands individually before any integration begins. Document the reconciliation methodology clearly: which processor count rules were applied, how virtualisation was assessed, and what Named User Plus minimums were used. This documentation becomes critical if Oracle audits post-merger.

03 — Phase 2: Identify Gaps, Overlaps, and Cost Impact

With the inventory and contract review complete, the next phase focuses on quantifying the financial implications and building the licensing cost model into the deal structure.

Step 4: Identify Licence Gaps and Compliance Exposure

Compare the combined usage across both organisations against current entitlements. Identify every compliance gap: under-licensed products, deployment on unauthorised platforms, exceeded Named User Plus counts, and products installed but not covered by any contract. Quantify the exposure at Oracle list pricing (worst case), negotiated pricing (likely case), and optimised pricing (best case with remediation). Pay particular attention to Oracle Database Options and Packs (Partitioning, Advanced Security, Diagnostics Pack, Tuning Pack) which are frequently installed but unlicensed, and Java SE deployments which may have been overlooked entirely in the target company’s licensing assessment.

Step 5: Identify Licence Overlaps and Optimisation Opportunities

Where both organisations hold licences for the same Oracle products, identify redundancies that can be consolidated. If both companies run Oracle E-Business Suite, for example, one instance can be decommissioned post-merger, freeing licences for redeployment. Map which licences are on support (and the annual support cost) versus which are unused — unused licences on support represent immediate savings through support termination. Document any ULA certification opportunities: if either company holds a ULA approaching certification, the merger may affect the optimal certification timing and strategy.

Step 6: Build Oracle Licensing Costs into the Deal Model

Include Oracle licensing costs as a defined line item in the M&A financial model. This should include: cost to remediate any pre-existing compliance gaps in the target company, cost of additional licences needed for the integrated environment (especially if consolidating onto shared infrastructure), annual support cost implications of the combined estate, and potential savings from licence optimisation and redundancy elimination. Present three scenarios (worst, likely, best) to the deal team. If the compliance exposure is material, negotiate appropriate purchase price adjustments, indemnification provisions, or escrow arrangements in the acquisition agreement.

Critical Risk — Virtualisation Compliance: Oracle’s virtualisation licensing rules require licensing all physical cores in a VMware cluster unless using Oracle-approved “hard partitioning.” This single issue generates the largest compliance claims in post-M&A audits, often exceeding $5M for enterprises running Oracle on VMware.

High Risk — Options and Packs: Oracle Database options (Partitioning, RAC, Advanced Security) and management packs (Diagnostics, Tuning) are frequently enabled by default or by DBAs unaware of licensing implications. Each option must be licensed separately at significant cost. Audit both organisations’ databases for enabled features using Oracle’s DBA_FEATURE_USAGE_STATISTICS view.

Moderate Risk — Java SE Licensing: Since Oracle’s Java licensing changes in 2023, Java SE deployments require commercial licences in most enterprise scenarios. Many organisations, particularly acquisition targets, have not assessed their Java compliance posture. A single unmanaged Java deployment across the target company can generate exposure of $500K to $2M.

04 — Phase 3: During the Deal — Engage Oracle and Negotiate

The deal execution phase is where licensing strategy meets commercial negotiation. How and when you engage Oracle can significantly affect both the cost of compliance and the terms of any new agreements.

Step 7: Notify Oracle Strategically

If your contract contains assignment or change-of-control clauses requiring notification, plan the timing and messaging carefully — typically around closing. Coordinate with legal counsel to draft a concise notice to Oracle regarding the change of entity. Confirm that you intend to remain compliant and will work with Oracle on any necessary contract updates. Do not volunteer details about internal licence positions, deployment specifics, or known compliance gaps. Oracle will use any information you provide to build leverage. Keep the notification factual and limited to what is contractually required.

Step 8: Negotiate Licence Transfers and Contract Updates

Work with Oracle to execute any necessary licence transfers or contract amendments. The goal is to carry over favourable terms from the acquired company’s contracts and obtain Oracle’s written consent for entity changes. If Oracle proposes a new enterprise agreement, ULA, or “migration” deal for the combined company, evaluate it critically rather than agreeing under time pressure. Oracle sales teams are skilled at using M&A uncertainty to push large, bundled agreements that may not represent value. Benchmark any proposed pricing against independent market data and your actual requirements.

Step 9: Establish Transition Terms and Interim Arrangements

If the integration or divestiture requires one company to temporarily use the other’s Oracle licences, establish a Transition Services Agreement (TSA) with explicit Oracle licensing provisions. Get Oracle’s written acknowledgment for any interim shared-use period (e.g., allowing a spun-off unit to use the parent’s licences for 90 days post-separation). Without this documentation, Oracle can claim both entities require full independent licensing from day one of separation.

05 — Phase 4: Post-Merger Integration and Compliance Management

Step 10: Execute Infrastructure Integration Decisions

As infrastructure integration proceeds, each decision about server consolidation, virtualisation, and cloud migration has direct Oracle licensing implications. Before consolidating workloads onto a shared VMware cluster, assess the licensing impact. Migrating Oracle databases to new hardware may require licence reassignment. Moving Oracle workloads to Azure or AWS requires understanding BYOL and authorised cloud partner rules. Every integration decision should be reviewed against the Oracle licensing position before execution.

Step 11: Reconcile the Combined Licence Estate

Within 90 days of close, complete a full reconciliation of the combined Oracle estate. Update the effective compliance position document to reflect the integrated environment. Identify any new compliance risks created by integration activities. This reconciliation becomes the baseline for ongoing compliance management and provides the evidence base for any Oracle audit that arrives in the 60 to 90 day window.

Step 12: Renegotiate Support Costs

The combined entity’s Oracle support spend is now a larger negotiation target. Request a commercial review with Oracle’s account team to explore consolidation pricing on support. If you are now terminating one company’s duplicate Oracle installations, negotiate support credit or reduction. If the combined spend qualifies for volume pricing, ensure you are receiving the appropriate tier. Annual Oracle support costs are almost always negotiable, particularly in the 12 months following a major M&A event.

Step 13: Establish Ongoing Compliance Governance

Post-merger is the right time to implement a sustainable Oracle compliance programme. Assign clear ownership for Oracle licence management across the combined entity. Implement quarterly licence reconciliation as a standard process. Document all Oracle deployments in a central repository. Establish change management procedures that require licence review before any new Oracle deployment, virtualisation change, or cloud migration. This governance framework prevents the compliance debt that accumulates between audits and positions you for a stronger negotiating outcome in your next Oracle renewal.

For further resources, see our Oracle Licensing in Mergers and Acquisitions guide, Oracle Pricing Benchmarks, Oracle Partitioning Policy and Contract Terms, Oracle Fusion Subscription Models, and our Oracle Audit Defense service. The Oracle Assessment Tools page provides resources for independent compliance analysis. Contact our Oracle contract negotiation team for M&A advisory engagements.