Third party support is the most discussed lever on an Oracle support bill and the most misunderstood. It promises a large, immediate cut, which is real, but it is not a free saving. Moving to a third party provider changes what you receive, what you can do with the software, and what it costs to come back. A clear view of both sides of the trade is what separates a sound decision from one that looks good in year one and expensive in year three.
How much does third party support save?
Third party support typically saves around half of the annual support fee, because independent providers price below Oracle's roughly 22 percent and without the same annual escalation. For a stable estate running a mature Oracle version, that saving is substantial and recurring. The reason the number is attractive is the same reason Oracle support feels expensive: the fee is tied to historical license spend and compounds yearly, so any provider pricing on a flat or lower basis looks favourable. The saving is the easy part of the analysis. The constraints are where the real decision sits.
What do you give up with third party support?
What you give up with third party support is access to new Oracle patches, security updates, and version upgrades, because only Oracle can ship them. A third party provider supports the version you are on, often very capably, but it cannot give you Oracle's future fixes or a path to the next release. For an estate that is stable and not planning upgrades, that constraint may not bite. For one that needs the latest security patches or a near term upgrade, it is decisive. The trade is cost against currency, and the right answer depends entirely on the roadmap for that specific estate.
| You gain | You give up |
|---|---|
| Roughly half the support cost | New Oracle patches and updates |
| Flatter pricing, no annual uplift | A supported path to new versions |
| Independence from Oracle support | Smooth re entry without a back fee |
Does third party support change your audit risk?
Third party support can change your audit risk because leaving Oracle support is one of the triggers Oracle watches, alongside virtualization, Java downloads, mergers and acquisitions, and declining support spend. Moving away does not breach your license, and your perpetual licenses remain valid, but it can raise your profile for a compliance review. That is a reason to make sure your position is clean before you move, not a reason to stay. A compliance review before the switch confirms there is nothing for an audit to find, so the cost decision is not undermined by an exposure you did not know you carried.
What does it cost to return to Oracle?
Returning to Oracle costs a back support re entry fee, because Oracle generally requires payment of the support you would have paid during the period you were away, often with a reinstatement charge on top. That re entry math is the hidden cost of the trade, and it should be modelled at the point of leaving, not discovered later. A decision to take third party support is sound when the estate is stable, the savings are durable, and the roadmap does not require Oracle's future patches. It is risky when an upgrade or a return is likely, because the re entry fee can erase several years of saving.
Who is third party support right for?
Third party support is right for an estate that is stable, mature, and not dependent on Oracle's near term patches or upgrades, because that profile captures the saving without feeling the constraint. A buyer running a long lived application on a settled Oracle version, with no upgrade on the roadmap and a clean compliance position, gives up little of value and keeps roughly half the annual fee. The poor fit is the opposite case: an estate that needs the latest security fixes, expects to upgrade, or is likely to return to Oracle, where the lost patches and the re entry fee outweigh the saving. The decision is estate specific, which is why a blanket answer is always wrong.
How do you de risk the switch?
You de risk the switch by confirming the compliance position before you move, because leaving Oracle support can raise your audit profile and you do not want a latent exposure surfacing after the saving is booked. A compliance review before the switch establishes that there is nothing for an audit to find, so the cost decision stands on its own. Pair that with a clear eyed model of the re entry fee, and the trade is made with both the upside and the exit cost visible from the start.
For how the switch interacts with a live or likely audit, see third party support and audit risk. For the cost of going back, see re entering support, the penalty math. The full commercial method sits in the Oracle negotiation guide.