For a stable Oracle estate that is not chasing the next release, third party support is one of the few levers that moves the recurring bill by a large amount rather than a marginal one. The saving is real and well documented. So is the catch: the same decision that halves your support cost also removes the relationship that most discourages an audit, and Oracle treats declining support spend as a reason to look. The move is sound for many buyers, but only when it is sequenced correctly, with the license position settled first so that any audit attention that follows meets a clean estate rather than an undiscovered gap.
How much does third party Oracle support save?
Third party support typically costs around half of Oracle's roughly 22 percent annual support fee, so it can cut the recurring support line materially. Independent providers offer maintenance for existing Oracle releases without the right to new versions or patches from Oracle, and they price below Oracle precisely because that is the trade. For an estate running a stable, supported release that does not need the newest features, the value of staying on Oracle support is largely the patches and the upgrade path, and a buyer that does not use those is paying full rate for an entitlement it does not consume. The saving compounds with the same logic that makes Oracle support expensive in the first place: it recurs every year, so halving it halves a cost you would otherwise pay indefinitely.
Does leaving Oracle support trigger an audit?
Leaving Oracle support can raise audit attention because declining or ending support spend is a recognised audit trigger. From Oracle's side, a customer reducing its support relationship is both a lost revenue signal and a prompt to verify compliance while the commercial leverage still exists. That does not make third party support a mistake, and it does not make an audit a certainty, but it does mean the decision should never be made with an unexamined estate. The correct order is to know your position first, resolve any genuine gaps on your own terms, and only then change the support arrangement, so that if an audit follows it meets records that already answer the obvious questions rather than discovering exposure you had not measured.
| Factor | Oracle support | Third party support |
|---|---|---|
| Recurring cost | Roughly 22 percent, escalating | Around half, broadly |
| New versions and Oracle patches | Included | Not included |
| Audit signal | Neutral | Reduced spend can draw attention |
Can you go back to Oracle support after leaving?
Going back to Oracle support after leaving usually requires paying back support for the lapsed period plus a reinstatement charge, and the exact terms are contract dependent. That reinstatement cost is deliberately high enough to make the exit feel one way, so third party support should be treated as a long term decision rather than a pause you can reverse cheaply. The implication for planning is that the move belongs to estates that are genuinely stable, where the loss of the Oracle upgrade path is acceptable for the foreseeable term. For an estate facing a near term version change or a strategic shift, the reversibility cost can outweigh the saving, and that calculation should be done explicitly before any contract is signed.
A buyer with a stable database estate wanted to halve its support bill by moving to a third party provider. Rather than switch first and hope, it ran a compliance review to settle the license position, corrected a small options exposure it found, and documented the estate completely. Only then did it move support. When the reduced spend did draw a routine audit, the estate it presented was already clean and evidenced, the review closed quickly, and the support saving held. The sequence, position first and support second, was what turned a risky cut into a defensible one.
What is the buyer move?
The buyer move is to settle the license position before you touch the support arrangement, then switch with a clean, documented estate behind you. Run the compliance review, resolve any real gaps on your terms, and keep the records that answer an audit before the reduced spend invites one. Model the reinstatement cost so the decision is made as the long term commitment it is, and confirm the estate is stable enough to forgo the Oracle upgrade path. Done in that order, third party support is a large and durable saving. Done blind, it is an invitation to an audit that finds something. The saving is worth having, and it is worth earning the right way.
For why the support fee dominates the lifetime bill, see the 22 percent and the annual escalation. For planning Oracle cost as the estate shrinks, see budgeting Oracle in a shrinking estate. The full method sits in the Oracle negotiation guide.