Oracle annual support — charged at 22% of net licence fees and escalating with a built-in annual uplift — is one of the largest and most predictable line items in enterprise IT budgets. Many organisations pay millions annually for Oracle support without questioning whether they are getting appropriate value, whether their support obligation is correctly calculated, or whether credible alternatives exist. This guide examines every lever available to reduce your Oracle support spend.
This article is part of our complete Oracle licence negotiation guide. It focuses on reducing Oracle annual support and maintenance costs — one of the most consistent areas of overPayment in enterprise Oracle relationships. Related articles include our guide to Oracle OCI pricing negotiation, which covers how cloud migration can restructure your support relationship, and our Oracle Database licensing guide, which explains the licence base from which support is calculated.
Oracle annual support — formally called Oracle Software Technical Support — is charged at 22% of the net licence fee for each product in your Oracle licence estate. For perpetual licences, this creates a perpetual obligation: as long as you maintain Oracle support, you pay 22% of the original licence acquisition cost (or a recalculated base following a negotiation) every year, indexed to annual price uplifts. Oracle's standard support contract includes a "Lifetime Support Policy" that provides Premier Support for a defined period, followed by Extended and Sustaining Support at increasing cost or reducing scope.
The 22% rate is not fixed — it represents Oracle's standard rate and the baseline from which negotiation proceeds. For very large Oracle customers, support rates of 18–20% have been achieved through direct negotiation. However, the rate itself is less easily negotiated than the base — reducing the licence value on which 22% is calculated, through licence rightsizing or buy-back, often produces larger cost reductions than modest rate adjustments.
Oracle applies an annual support uplift — typically 3–5% per year — that increases the support cost each renewal cycle even if your licence estate does not change. Over ten years, this uplift compounds significantly: a $1 million annual support obligation growing at 4% per year reaches $1.48 million after ten years without any licence additions. Negotiating caps on the annual uplift rate is one of the highest-value provisions in any Oracle support renewal negotiation.
For a large enterprise with $50 million in Oracle perpetual licence value, the annual support obligation at the standard 22% rate is $11 million per year. A 3% annual uplift increases this to $12.5 million after five years. Even a modest negotiated reduction — to 20% with a 2% annual cap — would save $1.8 million annually and $10+ million over a five-year horizon. The financial stakes make Oracle support negotiation one of the highest-ROI exercises in enterprise IT spend management.
Since Oracle support is calculated as a percentage of your licence base, reducing the licence base reduces the support obligation proportionally. Licence rightsizing — identifying products in your Oracle estate that are over-licenced, unused, or redundant — is therefore a direct mechanism for reducing support costs. The challenge is that Oracle's standard contract terms make it difficult to return licences once purchased: Oracle does not typically accept licence terminations or buy-backs as a matter of standard policy.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
However, licence rightsizing is achievable in specific circumstances. Enterprise License Agreement (ELA) renewals provide the most natural opportunity: at ELA renewal, the entire Oracle commercial relationship is renegotiated, including the licence scope. Organisations that can demonstrate genuine reductions in Oracle product usage — through platform migrations, application retirements, or deployment consolidation — have negotiated ELAs with reduced licence scope and correspondingly reduced support obligations. The key is documenting the reduced usage clearly before the renewal negotiation begins, so that Oracle's account team has the data they need to justify internal approval for a reduced-scope agreement.
Oracle may also accept licence terminations as part of a broader commercial restructuring — particularly if the organisation is making new commitments that are commercially valuable to Oracle, such as an OCI migration commitment or a new SaaS subscription. Framing licence reduction as part of a commercial restructuring that gives Oracle something it values, rather than a unilateral cost reduction demand, significantly improves the likelihood of Oracle's cooperation.
Oracle's standard support terms are not immovable. Organisations that engage in structured commercial negotiations — typically at renewal but also outside the renewal cycle with sufficient commercial leverage — can achieve meaningful improvements in support terms. The most commonly achievable negotiated improvements include reductions in the annual support rate (from 22% towards 18–20% for very large customers), caps on annual support uplift rates, extended periods at current rates before uplift applies, and restructuring of the support base calculation following licence optimisation.
Direct negotiation with Oracle requires commercial leverage and negotiation discipline. Oracle's account teams are experienced negotiators who manage large volumes of renewal cycles — they know exactly which concessions Oracle will approve and which require escalation. Understanding Oracle's internal approval hierarchy for different types of support restructuring, and knowing at what level of Oracle's organisation your negotiation needs to be conducted, is essential context that experienced Oracle negotiation advisors bring to the table.
Timing matters significantly in Oracle support negotiations. The period 60–90 days before your support renewal date is Oracle's preferred negotiation window — Oracle has the most leverage because the administrative disruption of not renewing creates urgency. Experienced negotiators deliberately extend the negotiation window, starting discussions 9–12 months before renewal and refusing Oracle's pressure to close early. This extended timeline allows you to develop credible alternatives (including third-party support evaluation) and demonstrate commercial sophistication that Oracle's account team recognises as a signal that standard tactics will not work on your organisation.
The most disruptive lever available to Oracle customers seeking support cost reduction is switching to third-party software support. Providers like Rimini Street and Spinnaker Support offer Oracle Database, Middleware, and application support at rates typically 50% below Oracle's annual support fee, with service level commitments that many customers report as superior to Oracle's standard support model. Third-party support has become a mainstream enterprise IT strategy, with thousands of organisations — including large enterprises in regulated industries — running mission-critical Oracle systems under third-party support contracts.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
The strategic value of third-party support as a negotiation lever extends beyond the cost savings of actually switching. The credible threat of moving to third-party support — demonstrated by a formal evaluation and a documented proposal from Rimini Street or Spinnaker — gives Oracle's account team the internal justification needed to approve deeper support rate reductions or more favourable renewal terms. Many organisations use third-party support evaluations specifically as negotiation leverage, ultimately renewing with Oracle at improved terms rather than switching — but achieving savings that would not have been available without the credible competitive alternative.
Third-party support is not appropriate for all Oracle products or all organisations. Products where Oracle is actively investing in new features — including Oracle's cloud applications (Fusion ERP, HCM, CX) — typically require Oracle support to access new functionality and patches. Third-party support is most appropriate for stable, mature Oracle technology products (Database, E-Business Suite, JD Edwards) where organisations are not planning feature upgrades and simply need ongoing break-fix support and regulatory patch coverage.
When Oracle workloads migrate to Oracle Cloud Infrastructure (OCI), the commercial relationship between on-premises licence costs and cloud consumption costs changes in ways that create support restructuring opportunities. Oracle is commercially motivated to accelerate OCI adoption and is willing to make concessions on on-premises support costs to secure OCI migration commitments. Organisations that are genuinely considering OCI migration — or that can credibly frame an OCI evaluation — can use the migration discussion as a mechanism to restructure their support relationship.
The most common OCI-linked support restructuring takes one of two forms. In the first model, Oracle reduces on-premises support costs for licences that are being migrated to OCI under BYOL, recognising that the on-premises deployment is winding down. In the second model, Oracle restructures the entire Oracle commercial relationship — combining an OCI commitment with a renegotiated on-premises support base — in a way that reduces the total Oracle cost even though the on-premises support obligation continues for remaining on-premises deployments. Both models require skilled commercial negotiation to ensure the OCI commitment terms are favourable and the on-premises support reduction is genuinely material. Our guide to OCI pricing negotiation covers the cloud side of these deals in detail.
Organisations can choose to terminate Oracle support entirely — ceasing annual support payments and operating Oracle software without the benefit of Oracle's ongoing patches, updates, and technical support. This is a legitimate option that many organisations — particularly those running Oracle on stable, mature platforms with limited change requirements — have successfully implemented. The financial benefit is significant: eliminating a multi-million dollar annual support obligation immediately reduces IT operating costs.
The risks of terminating Oracle support require careful consideration. Without Oracle support, you do not receive security patches, regulatory compliance updates, or bug fixes. For some Oracle products — particularly Oracle Database running financial or regulated data — this creates a compliance risk that may outweigh the cost savings. Additionally, if you wish to reinstate Oracle support after terminating, Oracle typically requires reinstatement fees based on the support that would have been paid during the termination period — potentially making reinstatement very expensive. Before terminating Oracle support, a detailed risk assessment of your specific Oracle product usage, regulatory environment, and future plans is essential.
Third-party support providers like Rimini Street offer an alternative to full termination: their support contracts include security and regulatory patch coverage for Oracle products, addressing some of the compliance risk that makes unsupported Oracle deployment problematic. This makes the "terminate Oracle support and switch to third-party" model more viable for organisations with regulatory requirements than simple termination would be.
Even if you cannot reduce your current support rate, negotiating a cap on Oracle's annual support uplift is a highly valuable provision that compounds significantly over a multi-year support contract. Oracle's standard support renewal language gives Oracle the right to increase support fees by a set percentage each year — typically 3–5%, sometimes linked to an index. Organisations that accept Oracle's standard renewal terms without negotiating an uplift cap lock themselves into a support cost that grows automatically, year after year, regardless of whether Oracle's support quality or your Oracle usage has changed.
Uplift caps of 0–2% per year — or fixed-price support periods of 2–3 years with no uplift — are achievable in Oracle support renewals where the customer has prepared a strong commercial case and engaged Oracle's account team with clear alternatives. The commercial argument is straightforward: in exchange for a multi-year support commitment (which Oracle values because it provides revenue certainty), Oracle accepts a cap on the annual increase. This trade — commitment length for price certainty — is a standard commercial exchange that Oracle's approval processes accommodate, provided the customer asks for it formally and demonstrates the willingness to explore alternatives if the ask is not met.
Before investing in a support cost reduction strategy, it is worth honestly assessing the value that Oracle support actually provides to your organisation. For some Oracle products — particularly Oracle's cloud applications and any Oracle technology products with significant ongoing development — Oracle support provides real value through new feature access, security patches, and access to Oracle's technical resources. For other products — particularly legacy Oracle technology stacks that you are planning to migrate away from — Oracle support may provide little practical value beyond the technical compliance requirement to maintain support on licenced products.
The value assessment should cover: how frequently you actually use Oracle support (log a support request, receive a patch, or access Oracle's knowledge base); whether the Oracle product versions you are running are still within Oracle's Premier Support window (products in Extended Support or Sustaining Support receive materially reduced service); whether Oracle's patch and update cadence matches your own deployment and change management cycles; and whether third-party support would provide equivalent or better service for your specific needs at lower cost. This honest assessment — done before the renewal negotiation, not during it — provides the foundation for a rational support cost optimisation strategy.
Paying too much for Oracle support?
Based on the strategies above, a structured Oracle support cost reduction programme should follow these steps:
Oracle support costs are negotiable — and the savings available are substantial. Get specialist support to benchmark your current obligation and identify where reductions are achievable.