Oracle Mergers and Acquisitions Advisory: Licensing Risks and How to Manage Them

Why Oracle Licensing Is an M&A Risk Priority

Enterprise software licensing rarely receives adequate attention in M&A due diligence. Legal teams focus on contracts, IP, and regulatory compliance. Finance teams focus on revenues, liabilities, and working capital. IT teams are often not involved in early-stage due diligence at all. Oracle licensing sits awkwardly across all three domains and is typically addressed — if at all — only in the final stages of transaction preparation, when remediation options are limited.

The financial stakes are significant. Oracle licences are generally non-transferable without Oracle's consent. Compliance shortfalls in an acquired entity become the acquirer's liability post-close. ULA certification events triggered by a deal can require organisations to quantify Oracle deployments at a point in the integration where accurate data is unavailable. Support fee structures carry 8 percent annual escalation that must be factored into post-acquisition financial models.

Organisations that conduct thorough Oracle licence due diligence before signing can quantify these risks, negotiate price adjustments or indemnities to address them, and develop a post-close remediation plan. Organisations that skip this step discover the liabilities after the deal is closed and Oracle's leverage is maximum.

Pre-Deal Due Diligence: What to Assess

A thorough Oracle licence due diligence assessment covers the target's Oracle licence position, compliance status, contractual structure, and ongoing support obligations. The following areas are essential.

Oracle Licence Inventory and Compliance Position

The first requirement is an accurate inventory of all Oracle software deployed in the target organisation — products, versions, metrics, and quantities — compared against the Oracle licences the target actually holds. This comparison identifies any licence shortfall (compliance risk) or surplus (potential cost savings through support reduction).

Oracle licence inventories are not self-evident from Oracle's records. Oracle's customer portal (My Oracle Support) shows licences purchased and support active, but does not show how those licences align with actual deployments. The target's own IT and procurement systems may not maintain accurate Oracle deployment data. A structured assessment using Oracle-approved inventory methodologies is required to establish a reliable compliance position.

Contractual Structure and OMA Terms

The target's Oracle Master Agreement — and all associated Ordering Documents — should be reviewed for terms that are particularly sensitive in an M&A context. Key provisions include the licence transferability clause (does the OMA permit assignment by the target to the acquirer entity?), any change-of-control provisions that trigger Oracle consent requirements, audit rights and their interaction with the transaction timeline, and any ULA, PULA, or special pricing agreements that may be affected by the deal structure.

Oracle licences are generally non-transferable. However, the specific OMA language varies across customer contracts and across the era in which they were negotiated. Some contracts include assignment rights for transactions meeting certain criteria; others require Oracle's express written consent for any assignment. Understanding the specific terms of the target's OMA before deal signing determines whether Oracle consent is required and, if so, at what cost.

ULA and PULA Complications

If the target organisation holds an active Oracle Unlimited Licence Agreement (ULA) or Perpetual Unlimited Licence Agreement (PULA), the M&A transaction may trigger a certification event. Oracle ULAs typically contain language defining the certification process as triggered by a change of control, expiry of the ULA term, or agreement between the parties. If a ULA certification is triggered by the acquisition, the certifying entity must document all Oracle deployments across both organisations at the certification date — a significant operational challenge during a merger integration.

Equally, the acquirer should assess whether the acquired ULA or PULA covers only the target's pre-acquisition legal entity or whether it can be extended to the combined organisation. Oracle's standard position is that ULA deployments cover the licensee entity and its subsidiaries as defined at the time of signing. Post-acquisition, Oracle may require a new agreement to cover the expanded entity, representing a significant commercial renegotiation opportunity that should be planned in advance, not discovered after the event.

Oracle's M&A Audit Playbook

Oracle's License Management Services monitors M&A activity involving Oracle customers. Transaction announcements — particularly where publicly disclosed — are a trigger for Oracle LMS to consider initiating an audit review of either the acquirer or the target. The rationale is that M&A transactions often create Oracle deployment changes: application consolidation, infrastructure migration, decommissioning of duplicate systems, and new user populations accessing Oracle software.

Oracle's preferred audit timing in M&A contexts is after the deal closes but before the integration is complete. At this point, the acquirer organisation has expanded Oracle usage (because the target's systems are now within the combined entity's perimeter) but has not yet completed the rationalisation that would reduce that usage. The audit window identifies the maximum Oracle exposure before any remediation occurs.

Post-Close Compliance Risk

When an acquisition closes, the acquirer assumes responsibility for the target's Oracle licence compliance. This includes any pre-existing compliance shortfalls — licence deficits the target had accumulated before the deal. If Oracle LMS audits the combined entity post-close, all non-compliance discovered — whether from the acquirer's operations, the target's operations, or the integration of the two — is the combined entity's liability.

Identifying the target's compliance position during due diligence creates the opportunity to adjust the deal valuation for Oracle risk, require the seller to remediate compliance shortfalls before close, or negotiate a specific indemnity for Oracle compliance liabilities arising from the pre-close period.

Post-Close Integration: Oracle Licensing Considerations

The post-close integration period is when Oracle licensing risk is highest and Oracle's audit scrutiny is greatest. The following areas require careful management.

User Access and Named User Plus Licensing

When two organisations merge, employees of the acquired entity gain access to the acquirer's Oracle systems and vice versa. If Oracle software is licensed under the Named User Plus metric, any new user who gains access to Oracle programmes must be counted in the licence calculation. A merger that doubles the addressable user population can double the Oracle Named User Plus licence requirement, depending on deployment architecture.

Integration planning should include a systematic review of which Oracle applications and databases will be accessed by combined entity users, what metric covers those applications, and whether current licence counts accommodate the expanded user population.

Infrastructure Consolidation and Processor Licensing

Infrastructure consolidation — moving workloads from the acquired entity's data centres to the acquirer's infrastructure — changes the Oracle processor licensing calculation. Consolidating Oracle workloads onto larger servers, or into VMware environments without hard partitioning, can inadvertently create new Oracle licensing requirements. Every infrastructure migration decision made during post-close integration should be evaluated for Oracle licensing impact before implementation.

Application Rationalisation

M&A transactions frequently result in duplicate applications: two instances of Oracle E-Business Suite, two Oracle Database environments, two Oracle middleware deployments. Application rationalisation — shutting down one of the duplicate systems — is an opportunity to reduce Oracle licence counts and support costs. However, the process requires careful management to ensure the shut-down systems are fully decommissioned in Oracle's records and the associated licence reduction is properly documented.

Oracle Licensing in Divestitures

Divestitures present a mirror image of the acquisition challenge. When an organisation sells a business unit, the divested entity needs Oracle licences to continue operating. Oracle's non-transferability rules mean that the parent organisation's Oracle licences generally cannot transfer to the divested entity without Oracle's consent.

Oracle typically uses this moment of constraint to negotiate a new commercial relationship with the divested entity — at full list price, without the discount history the parent organisation had accumulated. The parent organisation must also assess whether its remaining Oracle licence position is adequate after the divestiture, since some licences may have been justified by usage in the divested business.

Preparing Divestitures for Oracle Licensing Continuity

Organisations planning a divestiture should begin Oracle licence planning well before the transaction is announced publicly. The planning process should address which Oracle products the divested entity will need, whether those products are currently covered under the parent's OMA or under separate agreements, what Oracle's consent requirement is for any licence transfer, and what new commercial terms Oracle is likely to propose for the divested entity.

Engaging Oracle early — before the transaction announcement — gives the parent organisation leverage to negotiate transition licences as part of a broader commercial discussion, rather than in the post-announcement environment where Oracle holds most of the cards.

What Redress Compliance Delivers in M&A Advisory

Redress Compliance provides Oracle M&A licensing advisory across the full transaction lifecycle: pre-deal due diligence, transaction structuring, post-close integration planning, and divestiture preparation. Our advisers bring direct experience from Oracle's own licensing and audit operations, providing insight into Oracle's commercial incentives and decision-making processes that is not available from general legal or financial advisers.

We have supported Oracle licensing advisory on transactions ranging from bolt-on acquisitions to multi-billion-dollar corporate combinations, across industries including financial services, healthcare, manufacturing, and technology. Our independence from Oracle means our advice is always aligned with the client's interests.