Breaking free from Oracle support. The buyer side framework.

Oracle's annual support fee at 22 percent of the original net license cost is the largest single multi year exposure on the Oracle estate at most enterprise customers. The 22 percent is itself reasonable. The 22 percent compounded by 3 to 8 percent escalators, year after year, with no usage based variability, is what produces the cumulative spend that exceeds the original license cost inside ten years on most estates. The compounding is the problem, not the percentage. Third party support is the lever that breaks the compounding. It does not break the licensing.

This article covers the buyer side framework for the Oracle support exit. The 22 percent math, the third party support market and how to evaluate it, what you give up by leaving and what you keep, the transition timeline, the reinstatement risk and how to mitigate it, and the named pitfalls we see at customers that ran the exit without an advisor. For the broader Oracle commercial framework read the Oracle services practice. For the reinstatement specifics read dropping Oracle support and reinstatement. For the deeper cost reduction analysis read Oracle support cost reduction strategies.

1. The 22 percent math

Oracle's standard support fee is 22 percent of the original net license fee, charged annually, with a contractually defined escalator. The escalator depends on the customer's negotiated terms and typically ranges between 3 percent and 8 percent per year. The escalator compounds, which means a customer who pays one million dollars in support in year one is paying between 1.34 million (at 3 percent) and 1.99 million (at 8 percent) by year ten. Over the same ten year window the cumulative support payment is between 11.5 and 14.5 million dollars on a license cost of 4.5 million dollars. The cumulative support is two to three times the original license fee, every ten years, in perpetuity.

2. The third party support market

The third party support market is consolidated around four established providers. Each operates inside the legal boundary set by the Rimini Street litigation that ran from 2010 to 2024 and concluded with a settlement and a permanent injunction. The injunction defines what third party providers can and cannot do, which is now well established law. The providers compete on price, service tier, geographic coverage, and product breadth. The economics are similar across the four. The differentiator at the customer level is the operational fit.

The pricing band is consistent across the providers. The Oracle support exit produces an immediate 50 percent reduction in the support line, with no escalator during the contract term. Over a five year horizon the cumulative saving is between 50 and 70 percent of the equivalent Oracle support spend. Over a ten year horizon, with the avoided Oracle escalators compounded into the calculation, the saving extends to between 70 and 90 percent. The saving is real and it is durable.

3. What you lose. And what is actually fine

Leaving Oracle support is not free. The customer gives up a defined set of entitlements that the provider does not replace. The list of entitlements lost is shorter than most customers expect, and most enterprise estates do not actually use the entitlements that are lost in any meaningful way. The buyer side framework names what is lost, names what is retained, and names what is operationally substituted by the third party provider.

The entitlement most customers worry about is the security patch line. Oracle's marketing positions security patches as the load bearing reason to remain on Oracle support. The buyer side reading is that the patches matter for actively maintained products, but most enterprise Oracle estates run mature products on stable versions that have not received material new security patches in years. Third party providers supply bespoke security patches that address the vulnerabilities relevant to the running version, often faster than Oracle's quarterly patch cadence.

4. The transition timeline

The transition from Oracle support to third party support runs over twelve to eighteen months. The timeline is driven by the contractual notice period in the Oracle support contract (typically 30 to 90 days), the procurement timeline for the third party provider (60 to 90 days), the operational handover of run book documentation (60 to 120 days), and the customer's internal change management cycle. Customers who attempt to compress the timeline below twelve months tend to experience operational gaps in the handover period. Customers who run the full eighteen months experience no operational gap at all.

1. Months 1 to 3. Internal stakeholder alignment. CIO, CFO, Group Counsel, and the application owners. The conversation is financial and operational. Build the multi year saving model and the operational risk register.
2. Months 3 to 6. Third party provider RFP and selection. Two to three providers in the RFP. Site visits to existing provider customers. SLA review and redline. Commercial paper.
3. Months 6 to 9. Run book documentation. Customer documents the operational support patterns the third party will inherit. Patch cadence, incident response, escalation paths, environment topology.
4. Months 9 to 12. Provider onboarding. Provider engineers shadow the existing support engagement. Knowledge transfer sessions. SLA cutover preparation.
5. Months 12 to 15. Oracle support contract non renewal notice issued at the appropriate cycle. Provider takes operational responsibility on the cutover date.
6. Months 15 to 18. Stabilization period under provider support. Initial incidents tested. Operational confidence established. Multi year saving model validated against actuals.

5. Reinstatement risk and how to mitigate it

Reinstatement is the largest single residual risk in the third party support decision. Oracle's standard reinstatement formula is 150 percent of the accumulated unpaid support fees plus interest, calculated from the date support lapsed. The penalty is intentionally punitive. It exists to discourage customers from leaving and reinstating cheaply if the third party experiment fails. The penalty is also the most negotiable line item Oracle holds at any customer engagement, because reinstatement is itself a commercial event that the publisher's account team controls. The risk is real. The mitigation is also real.

6. Common pitfalls

1. Pitfall one. Letting Oracle frame the security patch conversation. Oracle's account team will pitch the security patch line as the load bearing reason to remain on support. The buyer side reading distinguishes between actively maintained products (where patches matter) and mature products (where they typically do not). Most Oracle enterprise estates fall into the latter category.
2. Pitfall two. Compressing the transition timeline. Twelve to eighteen months is the right calendar. Six month transitions tend to produce operational gaps that the customer absorbs at exactly the moment the publisher is watching.
3. Pitfall three. Skipping the run book documentation. The third party provider takes over what is documented. What is not documented becomes a tribal knowledge gap that surfaces at the worst possible moment. Document the support patterns before the cutover, not after.
4. Pitfall four. Not negotiating reinstatement before exit. The reinstatement formula is the largest single line on the residual risk register. Negotiating the formula before the exit decision is the lowest cost mitigation available.
5. Pitfall five. Treating the decision as IT only. The Oracle support exit is a multi million dollar financial decision that touches procurement, finance, legal, and IT. Single function ownership produces poor outcomes. Group sponsorship at the CFO or CIO level is the right governance.

FAQ

How much does Oracle annual support cost?

Oracle's standard annual support fee is 22 percent of the original net license fee, with a contractually defined annual escalator. The escalator is typically between 3 and 8 percent depending on the customer's negotiated terms. Over a ten year horizon, cumulative support payments routinely exceed the original license fee by a factor of two to three.

How much can third party support save against Oracle support?

Third party support providers typically charge 50 percent of the Oracle annual support fee, with no escalator during the contract term. Over a five year horizon the cumulative saving is between 50 and 70 percent of the equivalent Oracle support spend. Over a ten year horizon, with the avoided Oracle escalators compounded, the saving extends to between 70 and 90 percent.

What do I lose by leaving Oracle support?

You lose the right to download new product versions, you lose access to Oracle's My Oracle Support knowledge base, and you lose the right to install Oracle issued security patches on the affected products. You retain everything else. The licenses you own remain perpetual under the original contract. The third party provider supplies break fix support, security advisories, tax and regulatory updates, and operational support for the version you are running.

What is reinstatement and how does it work?

Reinstatement is the process of resuming Oracle support after a lapse. Oracle's standard reinstatement formula is 150 percent of the accumulated unpaid support fees plus interest, calculated from the date support lapsed. The reinstatement penalty is the largest single risk in the third party support decision, but it is also the most negotiable. Read the deeper analysis in dropping Oracle support and reinstatement.

Is third party support legal after the Rimini Street litigation?

Yes. The Rimini Street litigation that ran from 2010 to 2024 ended with a settlement and a permanent injunction that defines exactly what Rimini and other third party providers can and cannot do. The market today operates inside that injunction, with established legal boundaries.

Does Vendor Shield cover the Oracle support exit?

Yes. The Vendor Shield subscription covers Oracle in every tier. Coverage extends to the support exit decision, the third party provider RFP, the run book documentation, the cutover, and the reinstatement risk mitigation. The retainer also includes the buyer side advisory across the broader Oracle estate.