Third party Oracle support saves half on the quote. About 42 percent survives the contract terms.

A provider will quote about half your Oracle support fee. After repricing, lost rewards, engineering and transition, the five year saving lands at 30 to 45 percent, and patches and upgrade rights stop the day support ends.

How much does third party Oracle support actually save?

A third party provider will usually quote about half of your Oracle support fee, so a $2.2 million Oracle line comes back near $1.1 million. Over five years, after the costs of leaving are priced, the net saving lands at 30 to 45 percent.

In the worked model below, $5.02 million of the $6.42 million gross difference survives, eight points below the 50 percent the quote implies. The model uses a $10 million net license base, Oracle support at 22 percent of that ($2.2 million a year) and Oracle's 4 percent annual uplift. The provider fee stays flat at $1.1 million.

Every point lost between the quote and the net result comes from a cost you can identify before you give notice. Put all of them in the first draft of the business case, so the board never sees the 50 percent figure.

Why start from 22 percent of net, and never from list?

Oracle charges support at 22 percent of the net license fee you paid, after every discount. A $40 million list purchase bought at a 75 percent discount is $10 million net, which produces the $2.2 million support line in the table. Run the model on list and you overstate both bills by a factor of four.

How much of the saving comes from the uplift you stop paying?

Close to a fifth of it. Five years of 4 percent compounding adds about $0.92 million on top of five flat years of $2.2 million, and a provider's flat fee never pays that increase. First models often leave it out, which understates the case.

If your contract has no negotiated cap, do not assume one. Take your last three support invoices, measure how much each year actually rose, and use that rate in Years 2 to 5.

What costs reduce the saving after you leave Oracle support?

Six costs sit between the provider's quote and the net figure. Some are one time, some recur, and one only appears if you ever return. The model above prices two of them; the rest depend on how your contracts and releases are set up.

• Repricing of retained licenses. When you stop support on part of an Oracle order, the licenses you keep are repriced. In a partial exit this is the largest single cost, and it ended most of the partial business cases we reviewed.
• Forfeited Support Rewards. If you run workloads on Oracle Cloud Infrastructure, the credits you earn reduce your technology support bill. End that support and the credits have no bill left to reduce.
• Internal engineering. Compensating security controls, backports and platform testing now need an owner. On a large Oracle footprint that is one to two full time engineers, which is where the $250,000 a year in the model comes from.
• Recertification work. Every operating system patch, storage refresh and browser change needs testing that Oracle's certification matrix used to cover for you.
• The transition project. Knowledge capture, downloading the patches and documentation you are entitled to, and onboarding the provider. The model carries it at $0.15 million as a one time cost.
• The return premium. Oracle's reinstatement fee, set out below, is what it costs to reverse the decision if a system outlives its planned retirement.

How do Oracle Support Rewards change the comparison?

Oracle Support Rewards pay $0.25 for every $1 of OCI consumption, or $0.33 for customers with an Unlimited License Agreement. The rewards can only be applied to support invoices for Oracle technology programs, and they expire 12 months after issue. Model them in the Support Rewards guide before anything is terminated.

The effect depends on which programs you move. Rewards only offset technology support, so a buyer who takes applications support to a provider and keeps database support on Oracle can still use them.

What does it cost to come back to Oracle support?

Oracle's technical support policies (the August 2026 edition) set the reinstatement fee at 150 percent of the last annual support fee you paid, prorated back to the date support lapsed. You also pay the fee for the new twelve month support period. The longer you stay away, the larger the bill to return.

In both cases the reinstatement fee alone is roughly three times the gross saving banked while away, before the new year of support is added. Treat the exit as permanent for the programs you move, and only move programs you are confident you will retire or replace before you would need Oracle again.

Can you move only part of your Oracle licenses to third party support?

Yes, but only along the lines Oracle's support policies allow, and the numbers often fail. Oracle requires every license in a license set to be supported at the same level. You cannot keep Oracle support on some Database Enterprise Edition licenses and move the rest; to reduce, you terminate the unsupported licenses.

Repricing then does the rest of the damage. When you terminate or reduce licenses on an order, Oracle reprices support for the licenses that remain on that order. Two limits apply:

• The ceiling. The new price, at Oracle's current support list price less the standard discount, cannot exceed what you paid before for the whole order, including the dropped licenses, plus any country annual adjustment.
• The floor. It cannot fall below what you already paid for the licenses you keep, so a reduction never makes the retained support cheaper.

How can a 70 percent partial exit cost more than staying?

In our modeling, matching service levels plus repricing left a 70 percent partial exit roughly $150,000 a year worse off than doing nothing. The illustrative numbers below show how that happens on the same $2.2 million line.

1. The 70 percent you move carried $1.54 million of support. A provider quotes half, $0.77 million.
2. The 30 percent you keep carried $0.66 million at your negotiated discount. Repriced at list less the standard discount, assume it rises to $1.33 million. That is within the cap, which here is the $2.2 million the whole order cost before.
3. Internal engineering adds $250,000 a year for the programs that left Oracle.
4. Total annual cost: $0.77 million plus $1.33 million plus $0.25 million, or $2.35 million, against $2.2 million for staying. That is $150,000 a year worse.

The exits that worked were either clean, with all support on the affected programs ending together, or carved along contract lines the policies permit. The usual clean carve is a whole product family bought on its own orders, such as an applications suite, with the database left on Oracle.

Why we advise against starting with a small pilot

A common suggestion is to test third party support on a small, low risk slice of your Oracle licenses before committing the rest. We disagree, because a pilot is usually a partial exit, and partial exits are where repricing hits hardest.

The pilot's saving is small, the repricing on the retained licenses is not, and the return premium makes the pilot expensive to reverse. Test the provider through references and a detailed service review instead, then decide program by program on complete orders.

Which Oracle releases are a good fit for third party support?

Stable releases with a known retirement date fit best. The buyers who switched successfully could name the release they ran and the year they would retire it. Those who could not name either should not have switched, because patches and upgrade rights stop on the termination date and do not resume until you pay to come back.

The fit profile is mature releases, no planned upgrade inside the five year horizon, and the internal or provider capability to own compensating controls. The release's support status then decides how much you give up.

The Sustaining Support row changes many comparisons. You are paying full support fees for access to an archive, while a provider charges less and still writes fixes for problems you hit. For a release already in Sustaining Support, the case for staying is often only the upgrade right.

How do you check your own position before deciding?

• Support renewal quote and CSIs. Your latest renewal quote lists each Customer Support Identifier and the license orders behind it. That shows which programs share an order and would reprice together.
• Release and patch level. Query v$version on each database and run opatch lsinventory to see the patches applied. Match each release against Oracle's Lifetime Support Policy dates.
• Last three support invoices. They give you the real uplift rate for the model.
• Rewards balance. The OCI console shows the Support Rewards you have earned and when they expire.
• Retirement plan. A named year for each system, signed off by its business owner as well as IT.

Once the numbers hold up, the provider and legal questions follow. Our provider selection guide covers coverage, indemnity and security models, the legal position sets out what the courts actually held, and the Rimini Street guide covers the largest provider. The savings calculator runs a first version of the model.

What have we seen in Oracle support exit decisions in 2024 and 2025?

Across roughly 40 to 45 Oracle support decisions I advised in 2024 and 2025, about two thirds of the buyers who opened the question did not switch. Most stayed because the corrected model, with repricing and rewards included, no longer cleared their internal threshold.

The first model was almost always too optimistic. It compared the provider quote with the Oracle fee and stopped there. Correcting it meant pricing repricing, rewards, engineering and the transition before any decision, because 42 percent is worth pursuing and 50 percent was never real.

Every serious, costed third party quote we saw made Oracle cheaper once Oracle heard about it.

That result holds even for the buyers who stayed. A credible exit changed Oracle's number in every case, which makes the evaluation worth running on its own. It fits inside a wider support cost strategy and the other ways to reduce Oracle support fees.

What will Oracle's account team say when you raise third party support?

Expect five objections: lost patches, legal risk, the cost of returning, matching service levels and, finally, a discount. Each has a factual reply, and having it ready keeps the discussion on price.

• "You will lose all patches and security updates." Reply that you know patches stop on the termination date, that you have named each release and its retirement year, and that compensating controls are priced into the model.
• "Third party support puts you at legal risk." Reply that the litigation concerned how a provider handled Oracle software, not a customer's right to choose a provider, and that your provider's indemnity is in the contract.
• "Coming back will cost you 150 percent." Agree, and say it is already in your model and that you are not planning to return for these programs.
• "You cannot drop support on just those licenses." Agree that matching service levels apply, then ask for the repricing on the retained orders in writing before any notice date.
• "We can put a discount on the table if you renew." Ask for it as a lower renewal fee and a cap on the annual uplift for the full term, both written into the renewal.

What contract terms should you ask for if you stay?

• A cap on the annual uplift for several years. The uplift is close to a fifth of the saving, so capping it captures part of that value without leaving. Our guide to price hold and uplift cap clauses covers the wording.
• A written repricing statement. Oracle's figure for the retained orders if you later end support on named programs, so a future exit can be modeled on facts.
• Consolidation or reduction rights. Permission to drop shelfware from specific orders without repricing the rest, which is worth more than a one year discount.
• Clear rewards terms. Written confirmation of which invoices your Support Rewards can offset.

When should each step happen before your support renewal date?

What to do next

1. Find your net fees. Compute support from net license fees after every discount, because 22 percent of net is what the whole model runs on.
2. Price all six costs. Run the five year model with repricing, rewards, engineering, recertification, transition and the return premium.
3. Test any partial exit against the repricing rule. Get Oracle's figure for the retained orders in writing before you give notice.
4. Name each release and its retirement year. If you cannot, keep that program on Oracle support.
5. Put the costed quote in front of Oracle either way. Every serious one we saw lowered Oracle's price, whether or not the buyer left.
6. Get help if the stakes justify it. Our Oracle practice runs the decision with you, and the transition service covers the exit if you choose to go.

Frequently asked questions