$8M saved on WebLogic support. The Avis third party support case.

Avis Car Rental moved a stable Oracle WebLogic estate to third party support, saving roughly 8 million dollars over three years, with the license position verified before the exit notice.

Who is the customer and what was the decision?

Avis Car Rental operates across more than one hundred and seventy countries, with reservation, fleet, and pricing platforms running on Oracle WebLogic Server alongside Oracle Database and E Business Suite financials. The WebLogic estate sat on stable, mature releases with limited demand for new vendor patches.

At renewal, Oracle quoted the Premier Support stream with an annual uplift compounding across a multi year envelope. The decision was binary: pay the uplift for patch streams the estate barely consumed, or exit to third party support.

Why WebLogic fit the exit profile

The estate ran proven versions years from forced upgrades, consumed few new patches, and had no roadmap dependency on new WebLogic features. Perpetual license rights stayed intact after exit; only the vendor patch and upgrade stream lapsed.

The risk screen that ran first

A full license position review preceded the exit notice, because support exits draw audit attention. The estate entered the switch with a verified compliance position and a documented DR counting posture.

How was the exit executed?

The exit ran in four phases over six months: license position verification, provider selection, patch and artifact archival, then the support transition at the renewal boundary.

The archival step most exits miss

Before support lapsed, the team archived every entitled patch, update, and support artifact downloadable under the active agreement per Oracle support policies. After the lapse, that archive is the baseline the provider supports against.

Where the common advice on support exits is wrong

The standard advice is that mission critical estates cannot leave vendor support. We disagree. In roughly 20 to 30 evaluations we ran in 2024 to 2025, mission critical but version stable estates were precisely the best candidates, because their patch consumption was lowest relative to maintenance cost. The estates that should stay are the ones with forced upgrades or vendor dependent roadmaps inside three years, not the ones that happen to be important. The buyer side move is to screen on version trajectory, not criticality.

Paying full maintenance for a patch stream you no longer consume is the most expensive insurance policy in enterprise IT.

What was the outcome and what transfers?

The switch saved approximately eight million dollars over three years against the quoted Oracle support envelope, with service levels maintained on the stable estate and the compliance position verified before and after the move.

• Economics: support cost roughly halved, uplift compounding eliminated.
• Risk: license position verified pre exit; audit follow on planned for, not feared.
• Operations: custom fixes replaced the vendor stream the estate was barely using.

What transfers to other estates

Screen on version stability, upgrade horizon, audit posture, and cloud trajectory before any exit. The third party support decision framework formalizes the screen, and the Oracle support cost reduction guide covers the alternatives if you stay.

What to do next

1. Measure actual patch consumption on each Oracle product line for the trailing two years.
2. Map version stability and forced upgrade horizons per estate.
3. Run a license position review before any exit signal reaches Oracle.
4. Archive every entitled patch and artifact while the agreement is active.
5. Price the reinstatement scenario explicitly in the business case.
6. Time the transition to the renewal boundary, never mid term.

More outcomes in the case study library. Start with the Oracle practice or the Oracle knowledge hub.

Frequently asked questions

How did Avis save 8 million dollars on Oracle WebLogic support?

By exiting Oracle support for a stable WebLogic estate and moving to third party support at roughly half the vendor maintenance cost, eliminating compounding annual uplifts across a three year term, after verifying the license position first.

Do you keep your Oracle licenses after leaving vendor support?

Yes. Perpetual license rights survive a support exit. What lapses is the vendor patch, update, and upgrade stream, which third party providers replace with custom fixes and virtual patching.

Does leaving Oracle support trigger an audit?

Exit notices correlate with audit activity, which is why a full license position review precedes any exit signal in our engagements. Entering the switch with a verified position turns the audit risk into a planned event.

Which estates fit third party support best?

Version stable estates with low patch consumption and no forced upgrades inside roughly three years. Criticality is not the screen; mission critical but stable estates were among the best candidates we evaluated in 2024 to 2025.

What must be done before Oracle support lapses?

Archive every patch, update, and artifact the agreement entitles you to download, document the license position, and time the transition to the renewal boundary so no mid term gap opens.