Oracle
Oracle ULA exit, $42M kept off the table.
Oracle quoted $48M to renew. The retailer certified 41,000 processors instead, kept every license, and walked. The certification play, step by step.
Oracle quoted $48M to renew. The retailer certified 41,000 processors instead, kept every license, and walked. The certification play, step by step.
Oracle priced the renewal at $48M for growth that had already stopped. Certification turned the same estate into 41,000 perpetual licenses at no license cost.
The retailer exited because the renewal quote was $48M for three years while its Oracle deployment had stopped growing 18 months earlier. A ULA renewal prices Oracle's forecast of your growth; certification prices what you actually deployed.
The decision gate was simple: if measured growth could not consume the renewal price, certification wins. It could not, so the team built the exit.
The team maximized the certified count by sweeping every legally countable deployment before the ULA expired, landing at 41,000 processor licenses. Certification converts unlimited deployment rights into a fixed perpetual grant, so every properly deployed processor on the certification date becomes a permanent asset.
A 14 week sweep inventoried every Oracle instance across data centers, VMware clusters, and authorized cloud environments against the Oracle pricing and licensing definitions. Standby, disaster recovery, and partially deployed environments were validated line by line against the ULA certification clause.
The certified position came in at 41,000 processor licenses across Database, RAC, and Diagnostics and Tuning. Oracle challenged the VMware cluster counting; the contract language and deployment evidence held, and the certification letter was accepted without adjustment.
The exit avoided the $48M renewal entirely, kept 41,000 perpetual processor licenses, and held annual support flat under Oracle's support policies. Net avoided cost against the renewal path was roughly $42M over three years after advisory and sweep costs.
Renewal path versus certification path, three year view
| Dimension | Renew the ULA | Certify and exit |
|---|---|---|
| License cost | $48M over three years | $0, existing rights certified |
| License position | Unlimited during term, recount at next exit | 41,000 perpetual processor licenses |
| Support | Recalculated on the new agreement | Flat, tied to the existing CSI base |
| Audit posture | Deferred to next certification | Fixed entitlement, defensible count |
| Flexibility | Locked to Oracle growth assumptions | Free to move workloads off Oracle |
The reusable pattern is measure first, decide second. Every ULA decision should start from deployment telemetry, not from the renewal quote.
The standard Oracle account team advice is that growing companies should renew the ULA because certification caps your rights at a moment in time. We disagree. In the ULA certifications Fredrik Filipsson ran in 2024 to 2025, most estates had plateaued on Oracle 12 to 24 months before expiry while growth claims in the renewal pitch reflected Oracle's forecast, not the customer's telemetry. The buyer side move is to pull 18 months of deployment data before engaging Oracle at all, then price both paths. A renewal that prices phantom growth is the most expensive insurance a CIO can buy.
Three numbers define this engagement.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The dollar figure scales with estate size, but the ratio does not change: when deployment has plateaued, certification converts a recurring negotiation into a one time exercise with a permanent asset at the end.
A ULA renewal prices the vendor's forecast of your growth. Certification prices what you actually built. Measure before you believe either number.
The decision sequence below is the one this retailer ran. It applies to any ULA inside 18 months of expiry.
White Paper · Oracle
Oracle ULA Exit Strategy Playbook
The buyer side playbook for exiting an Oracle ULA: the certification trap, the support reset, and the timing that protects your renewal leverage. Read it free.
Certification is the exit process at the end of an unlimited license agreement where you count deployed processors and convert them into a fixed perpetual license grant at no additional license cost.
Oracle can challenge the count but cannot refuse a certification run per the contract. This retailer's 41,000 processor count was challenged on VMware grounds and accepted once evidence was presented.
Yes. Properly certified deployments become perpetual licenses you own permanently. The unlimited deployment right ends; the certified entitlement does not.
Support continues on the existing base and stays flat if the CSI structure is preserved. The renewal path, by contrast, recalculates support on the new agreement value.
Deployed Oracle software on VMware clusters is countable when the deployment is real and the contract definitions support it. Counting positions must be evidenced; this is where Oracle pushes back hardest.
Nine to twelve months. The deployment sweep alone took 14 weeks in this engagement, and the count, evidence, and certification letter consumed the rest.
Then a renewal can be rational, but price it against measured growth, not Oracle's forecast. Most estates we measured in 2024 to 2025 had plateaued despite growth claims in the renewal pitch.
The ULA decision gates, the certification math, and the audit posture that protects the exit.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The most expensive insurance a CIO can buy is a ULA renewal priced on growth that already stopped.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Pricing moves, audit signals, and the levers that work. No vendor spin.
