LVMH carried Oracle support on licenses nobody had run for years. A utilization assessment, a shelving plan, and a termination sequence built around Oracle repricing rules cut 10.5 million euro across three years.
LVMH, the global luxury group with roughly two hundred thousand employees across more than seventy five countries, paid annual Oracle support on a license estate built up through years of acquisitions and projects. A material share of it ran nothing.
A structured utilization assessment and a careful termination sequence saved 10.5 million euro across three years. The care was the point: Oracle support rules punish naive cancellation.
LVMH cut 10.5 million euro from Oracle support across three years by terminating support on licenses with no deployment evidence, shelving licenses with plausible reuse, and sequencing the terminations so Oracle technical support policies could not reprice the remainder upward.
The estate spanned Oracle Database Enterprise Edition, Real Application Clusters, and management packs across dozens of maisons and regions. Years of projects had left entitlements nobody reconciled.
Oracle support bills annually at roughly 22 percent of the net license fee, with yearly uplift. A license bought for a project that ended in 2015 still invoices every year until someone acts.
The assessment matched every supported entitlement against deployment evidence: Oracle Database instances, options usage, and pack telemetry. A material tranche of supported licenses had not run in years.
Oracle support pricing is anchored to license sets and matched service levels. Terminating part of a set can let Oracle reprice the retained support at current list, erasing the saving. Every termination batch was tested against that rule before submission.
Three levers produced the saving: clean termination of dead entitlements, shelving of plausible reuse licenses, and renewal timing that landed the changes before the next support invoice, not after it.
The engagement in numbers
| Metric | Before | After |
|---|---|---|
| Supported entitlements | Full historical estate | Active deployments only |
| Annual support spend | Baseline | Reduced by roughly 3.5 million euro per year |
| Three year saving | n/a | 10.5 million euro |
| Repricing exposure | Untested | Zero, by sequencing |
| Audit posture | Unreconciled estate | Documented entitlement baseline |
For retained products, Oracle lifetime support stages determined what Premier Support actually bought. Where products had aged into Sustaining Support, the value question was asked explicitly rather than renewed by habit.
The closing sequence was utilization evidence, license set mapping, batch design, then termination letters timed against the renewal date with the retained estate protected in writing.
The standard advice from resellers and even some advisors is that Oracle support is untouchable, because termination triggers repricing and audit retaliation, so the safe move is to keep paying. We disagree. In roughly 30 to 40 Oracle support reviews we ran across 2024 and 2025, sequenced terminations built on license set mapping cleared without repricing on the retained estate, and the audit posture improved because the entitlement baseline was finally documented. The buyer side move is to treat the repricing rules as an engineering constraint, not a prohibition: map the sets, batch the terminations, and put the changes in before the invoice. Fear of the rules is what funds the shelfware.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The invoice was paying for our history, not our infrastructure. Separating the two was worth ten million euro.
More Oracle cost analysis lives in the Oracle knowledge hub and the Oracle third party support guide.
The saving came from terminating support on licenses with no deployment evidence, shelving licenses with plausible reuse, and sequencing terminations around Oracle repricing rules so the retained support could not be repriced upward.
Yes, but the sequence matters. Oracle support policies tie pricing to license sets and matched service levels, so partial terminations done naively can trigger repricing of what you keep. Map the sets first, then batch the terminations.
Shelving ends support on a license while preserving the license right itself. It fits entitlements with no current deployment but plausible future reuse. The license can be redeployed later, though without updates or support until reinstated.
In our 2024 to 2025 reviews, 15 to 30 percent of supported licenses showed no deployment evidence in the trailing twelve months. At a 22 percent annual support rate, that waste compounds every year it goes unaddressed.
Not when it is evidence based. A documented utilization baseline built for the termination work doubles as audit defense. In our engagement file, estates that completed the exercise entered subsequent audits with stronger positions, not weaker ones.
Every year we paid for software that retired before some of our staff joined. The assessment made the invisible line items visible.
Confidential consultation. No follow up sales call unless you ask for one.
Oracle support benchmarks, license utilization patterns, ULA signals, and the buyer side moves across the Oracle estate.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
