How to reduce Oracle support costs: the complete guide.
Oracle Annual Technical Support runs at 22% of net licence fees and rises 3–8% every year, regardless of whether the software is still developing or simply running in maintenance mode. This note sets out the five proven levers — third-party support, cap negotiation, base reduction, ULA restructuring and cloud migration — and where each cuts cost by 30 to 55%.
Oracle support is a deliberate recurring-revenue engine, not a cost of active development — a $20M licence estate carries roughly $4.4M a year, or $22M over five years, much of it for software running in maintenance mode. The goal is rarely to eliminate support but to right-size it: third-party support saves 40–50% on stable, non-upgrading workloads, and a combined programme layering third-party support, a renewal cap and base reduction typically delivers 35 to 55% total savings. Clean up your compliance position before you announce anything to Oracle.
01 Key findings
The 22% rate is a revenue model, not a service price. A product licensed in 2012 for $2M generates about $10.5M in cumulative support by 2026 at only 3% annual increases. Support now represents the majority of Oracle's software revenue.
The "de-support" threat is what keeps you paying. Stop paying and you lose security patches, bug fixes and the right to reinstall. That risk — not service value — is why cancelling is hard, and why the practical target is reduction, not elimination.
Third-party support is the largest single lever. Rimini Street and Spinnaker Support deliver maintenance, security and regulatory updates at roughly half Oracle's rate. The binding constraint is upgrades: third-party providers do not deliver new Oracle versions.
Base reduction carries a repricing trap. Removing unused products cuts the 22% base, but Oracle terms typically block re-adding at the original value — terminating support on a product you may revive later creates future licence exposure.
Oracle counter-attacks predictably. Audits, upgrade-deadline pressure and support bundling in new deals all target support revenue. A clean, well-advised compliance position changes Oracle's response materially.
Combining levers beats any single move. Third-party support on stable estates, a 3–4% cap on what stays with Oracle, and base reduction executed together typically reach 35–55% total support savings.
02 Why support compounds
Oracle's 22% support rate is a deliberate commercial model designed to generate predictable, recurring revenue that exceeds initial licence fee revenue over the long term. The charge continues regardless of whether you are actively upgrading, actively using support, or even still running the product in production — and it rises 3 to 8% annually in most agreements.
The mechanism that maintains this position is the de-support threat: stop paying and you lose access to critical security patches, bug fixes and the right to reinstall licensed software. For most enterprises that creates a practical inability to cancel support even on legacy systems, because unpatched Oracle Database or middleware in production is a real security exposure. This dynamic shapes which strategies are practical — the goal is to reduce cost while maintaining appropriate coverage for business-critical systems, part of our Complete Oracle Licensing Guide.
03 Oracle vs third-party cost
Third-party providers deliver ongoing maintenance, security patches and regulatory updates at approximately half Oracle's annual rate. The trade is upgrades: only Oracle support carries version upgrade rights, so third-party fits stable, non-upgrading deployments — which describe a substantial share of most Oracle footprints.
| Dimension | Oracle Premier Support (ATS) | Third-party (Rimini / Spinnaker) |
|---|---|---|
| Annual cost | 22% of net licence fees | ~10–11% (roughly 50% of Oracle) |
| Typical saving | Baseline | 40 to 50% |
| Annual uplift | 3–8% compounding | Commonly fixed / capped |
| Security, tax & regulatory updates | Yes | Yes, plus interoperability patches |
| New-version upgrade rights | Included | Not provided |
| Support model | Shared / tiered queue | Named primary engineer |
| Best for | Actively upgrading estates | Stable, non-upgrading estates |
04 Savings by lever
Indicative upper-bound savings for each strategy. Third-party support is the deepest single move; a combined programme across levers reaches the widest range. Model each against your own estate before committing.
Migrating workloads to Oracle Cloud Infrastructure (OCI) — EBS to Fusion ERP Cloud, Database to Autonomous Database, middleware to Integration Cloud — bundles software, infrastructure and support into one subscription, effectively eliminating the separate ATS charge on those workloads. Unit economics vary by workload; see the Oracle Licensing Playbook for OCI analysis.
05 Repricing & eligibility
Two constraints decide whether a reduction sticks: how Oracle reprices what remains, and which products are genuinely eligible to move.
Base reduction is not a clean subtraction. Oracle calculates ATS on net licence fees, and its terms typically prevent re-adding a removed product at its original licence value. Partial termination can also trigger matched-set repricing that lifts the rate on the licences you keep. Independent assessment of what is genuinely decommissioned — versus merely dormant — is essential before executing.
Stability, not product family, is the test. Rimini Street and Spinnaker support Oracle Database, E-Business Suite, PeopleSoft, Siebel and JD Edwards, among others. The right candidates are deployments that are stable, not planned for upgrade in the next three years and not deeply tied to Oracle upgrade workflows. Anything on an active upgrade path needs Oracle support for that process.
06 Stay vs third-party
Four factors decide whether a given workload should stay on Oracle support or move. Weight them per system, not per estate.
Upgrade roadmap
A planned move — Database 12 to 19, EBS 12.1 to 12.2 — requires Oracle support. Only workloads with no upgrade in the 3-year horizon are clean third-party candidates.
Compliance position
Oracle often raises audit pressure when it hears "third-party". Resolve any open compliance exposure first; announcing from a clean position removes Oracle's strongest lever.
Product stability
Mature middleware and stable ERP modules in maintenance mode gain little from Oracle's development pipeline — the strongest case for third-party or base reduction.
Relationship leverage
A credible third-party alternative changes renewal dynamics even if you never switch — it is the most reliable route to a 3–4% cap on the support you retain.
07 Our recommendation
Your workload is in maintenance mode, has no upgrade planned for three years and carries a clean compliance position. Capture the 40–50% saving — but line up specialist advisory support for the transition, because Oracle will lean on audits and renewals.
You are on an active upgrade path or depend on new-version delivery. Keep Oracle support — then negotiate a 3–4% annual cap at renewal, ideally against a Q4 fiscal-year-end deadline and a multi-year commitment.
Most enterprises are not all-or-nothing. Move stable workloads to third-party, cap what stays with Oracle, and strip decommissioned products from the base simultaneously — the route to 35–55% total savings.
08 Migration approach
The sequence matters more than any single tactic. How you approach Oracle decides whether a switch is clean or becomes an audit.
Advised & sequenced Recommended
Audit your own support base, resolve compliance exposure, identify third-party candidates and time the move to renewal — then engage Oracle from a clean, well-advised position with a credible alternative in hand.
Unadvised switch Weaker
Signalling a third-party move before cleaning up compliance invites a re-audit and upgrade-deadline pressure, with any unresolved issue used to argue you are safer keeping Oracle support in place.
Right-size your Oracle support spend
Our licensing advisory practice models your reduction potential across every lever and manages the transition — typically identifying 30 to 55% support cost reduction in the first assessment.
The Licensing Edge
Weekly Oracle support and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.