Oracle Licensing in M and A. The CIO due diligence checklist.

Oracle licensing in mergers and acquisitions is a separate workstream that does not belong inside standard IT due diligence. The Oracle Master Agreement assignment clause makes every Oracle contract personally non assignable: any change of control, divestiture, or asset purchase requires Oracle's written consent, and Oracle's default consent is conditional on commercial terms favorable to Oracle. Customers who close M and A transactions without Oracle pre work routinely find themselves facing a coordinated audit notification within 90 days, frequently with seven figure exposure. The Oracle audit posture is keyed specifically to M and A events because the LMS team treats every assignment, carve out, or acquisition as a measurement opportunity. This article sets out the CIO due diligence checklist for Oracle licensing across the entire M and A lifecycle: pre close discovery, Master Agreement assignment mechanics, post close integration, audit risk management, ULA handling, support consolidation, and the commercial leverage available when the customer prepares properly. Read the related Oracle services practice, the Oracle M and A advisory, the Oracle CIO playbook, the Oracle audit negotiation guide, and the Oracle ULA Decision Framework.

The Oracle M and A lifecycle

Oracle M and A licensing breaks into five distinct phases, each with its own checklist:

• Phase 1: Pre close discovery (typically 30 to 90 days before signing). Inventory target's Oracle contracts, deployment, support entitlements, ULAs, Cloud commitments, Java SE Universal Subscription, audit history.
• Phase 2: Assignment clause negotiation (typically 14 to 30 days before close). Engage Oracle on Master Agreement assignment, negotiate consent terms, secure commercial protection.
• Phase 3: Close to day 30. Execute assignment letters, transfer support entitlements, confirm ULA scope under new entity.
• Phase 4: Post close integration (day 30 to month 12). Consolidate Oracle contracts, rationalize duplicate deployments, optimize support spend.
• Phase 5: Audit defense (month 6 to month 24). Expect Oracle audit notification within 12 months of close. Defend against M and A triggered audit findings.

Pre close due diligence checklist

The pre close Oracle workstream produces seven deliverables, each of which represents a material risk if missed:

1. Oracle contract inventory. Master Agreement, all Order Documents and Schedules, all amendments, all assignment letters. Target's contracts as well as any prior assignment language affecting their position.
2. Oracle deployment inventory. Database Enterprise Edition, Database options (Partitioning, Advanced Compression, Diagnostics Pack, Tuning Pack, Advanced Security, RAC, Active Data Guard, Multitenant), EBS modules, WebLogic, Java SE deployments, OCI consumption, Fusion Cloud subscriptions.
3. Oracle support entitlement reconciliation. Active CSI numbers, support level (Premier, Sustaining, Market Driven), expiration dates, support reinstatement risk if support has been allowed to lapse.
4. ULA inventory. Active ULA agreements, ULA term dates, certified deployments versus actual deployments, ULA exit clauses, PULA (perpetual unlimited) language if applicable.
5. Cloud subscription inventory. Universal Cloud Credits, OCI commitments, Fusion Cloud Applications subscriptions, NetSuite if applicable, contract end dates.
6. Java SE Universal Subscription status. Active subscription versus exposure, total employee count metric implications, OpenJDK migration status.
7. Audit history. Any Oracle LMS audits in the last five years, settlement amounts, settlement scope, residual obligations.

The Master Agreement assignment clause

Every Oracle Master Agreement contains an assignment clause that prohibits the customer from transferring rights or obligations without Oracle's written consent. This applies to:

• Mergers. Even when the customer is the surviving entity, Oracle's position is that the merger requires consent.
• Acquisitions. The acquired entity's Oracle contracts do not automatically transfer to the acquirer's Master Agreement.
• Divestitures. Carving out a business unit requires Oracle consent for the carved out entity to retain Oracle license rights.
• Asset purchases. Buying assets rather than equity does not solve the problem; Oracle still asserts consent rights.
• Internal reorganizations. Some Master Agreements include affiliate use rights that handle internal changes, but most M and A transactions exceed those rights.

The negotiation reality is that Oracle frequently uses the consent requirement as commercial leverage. Oracle's consent letter typically includes commercial obligations: new support commitments, ULA extensions, cloud commitments, or Java SE Universal Subscription expansion. The buyer side discipline is to negotiate the consent terms separately from the wider commercial conversation, refuse forced bundling, and document the assignment as a clean transaction.

Post close integration playbook

The first 90 days after close are critical. The integration workstream covers six streams:

• License consolidation. Combine the parent and target license entitlements under a single Master Agreement where possible. Resolve duplicate licenses (where both entities held the same product), eliminate shelfware, optimize the Named User Plus and Processor counts against actual deployment.
• Master Agreement consolidation. Negotiate a single Master Agreement to replace both legacy agreements. This is the strongest commercial opportunity in M and A, frequently delivering 20 to 40 percent reduction in total Oracle spend.
• Support consolidation. Combine CSI numbers, harmonize support renewal dates, eliminate duplicate support coverage, evaluate third party support migration for legacy products.
• ULA consolidation. Two ULAs combining typically becomes one larger ULA with consolidated terms. The certification clock and exit options need careful management.
• Cloud commitment consolidation. Universal Cloud Credit and OCI commitment merging, with rate harmonization across the combined entity.
• Java SE Universal Subscription rationalization. Two separate subscriptions becoming one combined headcount calculation, with the option to migrate to OpenJDK for the combined entity.

M and A audit risk management

Oracle's audit motion is keyed to M and A events. Customers who close transactions typically face Oracle audit notification within 6 to 12 months. The buyer side discipline is to:

1. Run an internal LMS measurement pre close. Establish the deployment baseline before Oracle measures it.
2. Document all assignment letters. Audit defense relies on contractual proof of what was assigned.
3. Reconcile Database options usage. Partitioning, Diagnostics Pack, Tuning Pack, Advanced Security are the most common audit findings.
4. Verify VMware host counting if applicable. Oracle's position on VMware host pools is the largest single audit exposure for combined entities.
5. Audit Java SE deployments across the combined entity. Java SE audits are now the most common Oracle audit motion, triggered specifically by employee count changes.

Oracle ULA in M and A

Oracle Unlimited License Agreements add complexity in M and A. Three patterns are common:

• Target has an active ULA, acquirer does not. The ULA does not automatically extend to acquirer entities. Oracle's consent typically requires either ULA termination and certification, or ULA scope expansion at additional cost.
• Both parties have ULAs. Two ULAs combining is rarely as simple as consolidating term dates. Oracle frequently requires re scope and re commercial.
• Acquirer has an active ULA, target has standalone licenses. The acquirer's ULA can sometimes be expanded to absorb the target's deployment, but Oracle controls the commercial terms.

The buyer side rule is to engage on the ULA scope question 60 to 90 days before close. Late stage ULA renegotiation under deal pressure produces materially worse outcomes than planned ULA management.

The commercial leverage in M and A

M and A creates real commercial leverage if the customer prepares properly. Combined entities are larger than the parts individually, which qualifies for better tier discounts (Level A through D on standard volume licensing, strategic customer pricing at scale).

The Master Agreement consolidation conversation is the strongest single commercial opportunity in a customer's relationship with Oracle, typically delivering 20 to 50 percent reduction on combined Oracle spend versus the pre merger run rate. The trade off is that customers who fail to manage the assignment workstream cleanly end up paying that same 20 to 50 percent as commercial concessions to secure Oracle consent.

How we engage on Oracle in M and A

• Pre close due diligence. Eight to twelve week buyer side workstream covering target's Oracle contract inventory, deployment inventory, ULA scope, Cloud commitments, Java SE exposure, and audit history. Outputs a numbered risk register with dollar values.
• Assignment clause negotiation. Direct engagement with Oracle on Master Agreement assignment, with separation of consent terms from broader commercial conversations.
• Post close integration. Twelve to twenty four week consolidation engagement covering license consolidation, support harmonization, ULA scope, and the Master Agreement consolidation conversation.
• M and A audit defense. Defense against Oracle LMS audits triggered by M and A activity.
• Vendor Shield. Always on multi vendor engagement covering Oracle alongside Microsoft, SAP, Salesforce, and other M and A relevant vendors. Read the related Vendor Shield, the renewal program, and the benchmarking practice.
• Run the assessment. The software spend assessment sizes the combined Oracle exposure before close.

A worked Oracle M and A example: a private equity carve out

A private equity firm acquired a $1.2B revenue business carved out of a Fortune 500 parent. The target carried:

• An active Oracle Database ULA (year four of five).
• An Oracle Java SE Universal Subscription on 8,000 employees.
• A Fusion Cloud HCM subscription with three years remaining.
• Roughly $4.5M annual Oracle support.

The seller's Oracle Master Agreement explicitly did not assign to the carved out entity. Oracle's opening position was a new Master Agreement at full list pricing with a fresh five year ULA on Oracle Database, fresh Java SE subscription for the new entity's 8,000 employees, and a 10 percent uplift on Fusion. Total Oracle proposal: $22M over three years.

Redress ran the pre close workstream, established that the existing ULA had been over deployed (a positive for the carve out, not Oracle), structured the Java SE conversation around a 60 day OpenJDK migration, and negotiated a clean Master Agreement assignment with no fresh ULA. Final commercial outcome was 39 percent below Oracle's opening proposal.

Common Oracle M and A pitfalls

• Closing without Oracle consent. Customers who proceed without securing assignment consent face Oracle audit notification within 90 days, typically with seven figure exposure.
• Accepting Oracle's first consent terms. Oracle's default consent letter is heavily commercial. Negotiate consent separately from commercial obligations.
• Missing the ULA implications. ULAs add complexity that late stage negotiation cannot solve.
• Forgetting Java SE. The per employee metric means combined entities have larger Java SE exposure. The Universal Subscription cost can double overnight if not planned.
• Skipping internal LMS measurement. Audit defense relies on the customer having established its own deployment baseline before Oracle measures it.

Redress is independent. Buyer side. Industry Recognized. Five hundred plus enterprise software engagements. $2B+ in client spend under advisory. Eleven vendor practices. One hundred percent buyer side. Read the related About Us, management team, locations, and contact. Read the related Oracle license audit defense service, the Oracle CIO playbook, the Oracle M and A advisory, and the white papers library.