White Paper — M&A Due Diligence
Oracle Licensing in M&A: The Due Diligence Checklist That Protects the Deal
Oracle licensing exposure is one of the most underestimated risks in enterprise M&A. Oracle licences are not automatically assignable — every acquisition, merger, or divestiture that involves Oracle software requires Oracle's formal consent, and Oracle's commercial team uses that consent process to extract substantial additional licence fees. This checklist gives deal teams, ITAM professionals, and integration leads the forensic framework for identifying Oracle risk before close, quantifying the exposure in target company environments, and structuring the post-close integration to avoid triggering audit claims.
What Oracle's contract team won't volunteer in M&A discussions: Oracle's Master Agreement contains assignment restrictions that prohibit the transfer of Oracle licences to an acquiring entity without Oracle's written consent. Oracle's consent process is not a formality — it is a structured commercial negotiation where Oracle's team reviews the combined entity's Oracle footprint and presents a "true-up" requirement as a condition of consent. Acquirers who proceed to close without Oracle consent, or who integrate Oracle environments without proper assignment, discover the exposure only when Oracle's LMS team initiates a compliance review of the combined estate. This checklist shows exactly what to look for before that happens.
What This Checklist Covers
- Oracle's assignment restrictions — the specific contractual language in Oracle Master Agreements and Order Forms that prohibits assignment without Oracle's consent, and the difference between stock acquisitions and asset acquisitions for Oracle licensing purposes
- Pre-close due diligence framework — the 47-point checklist for assessing Oracle exposure in target companies, including database estate mapping, Java SE deployment analysis, ULA status, support schedule review, and pending audit activity
- ULA and PULA behaviour in M&A — what happens to an Unlimited License Agreement when the ULA holder is acquired, how the certification obligation transfers, and when M&A activity triggers an automatic ULA certification requirement
- Oracle's consent process — how to approach Oracle's M&A team, what Oracle reviews during the consent process, typical timelines, and how Oracle prices the consent "true-up" relative to the target's Oracle estate value
- Divestitures and spin-offs — how Oracle handles licence splits in divestiture transactions, the "temporary licence" provisions that apply during the transition period, and the compliance risk of operating divested entities on the parent's Oracle licences
- Post-close integration — the 90-day Oracle integration roadmap, environment separation requirements, how to manage Oracle during the integration window without triggering additional licence requirements, and the ITAM governance framework for the combined estate
- Negotiating Oracle's M&A pricing — how Oracle values the consent true-up, typical discount levels achievable with proper preparation, and the commercial levers that create pressure in the consent negotiation
- Case study: PE firm acquires manufacturing group with undisclosed Oracle ULA — how Oracle's LMS team identified the acquisition and used it to trigger a $6.2M certification claim, and how we negotiated this to $1.4M with a new three-year EA
Checklist Chapters
Chapter 01
Oracle Contract Assignment — What the Law Says
Chapter 02
Pre-Close Due Diligence — The 47-Point Checklist
Chapter 03
ULA & PULA Behaviour in Corporate Transactions
Chapter 04
Oracle's Consent Process — Timeline & Tactics
Chapter 05
Divestitures & Spin-Offs — Licence Split Framework
Chapter 06
Post-Close Integration — 90-Day Oracle Roadmap
Chapter 07
Negotiating Oracle's M&A True-Up
M&A Reality
"Oracle's consent process is not a legal formality — it is Oracle's most effective mechanism for extracting value from customers who have no alternative. Acquirers who approach it without preparation routinely pay 2–4x what a well-prepared negotiation would achieve."
Hidden Exposure
"In our experience, over 60% of target companies in enterprise acquisitions have undisclosed Oracle compliance gaps. The most common: unlicensed Database options, Java SE deployed beyond entitlement, and ULA deployments that exceed what the target's contract covers."