A comprehensive advisory for CIOs and IT procurement leaders on negotiating third-party Oracle support contracts. Covers discount strategies beyond the standard 50% baseline, provider evaluation criteria, SLA negotiation, compliance safeguards, key contract terms, and how to avoid common pitfalls when moving from Oracle's official support programme. Third-party support is one of the highest-ROI cost optimisation strategies available for organisations running stable, mature Oracle deployments.
This guide is part of the Oracle Licensing Knowledge Hub. For Oracle support cost strategies, see: Oracle Support Renewal Optimisation. For the legal landscape, see: Is Oracle Third-Party Support Legal?. For provider comparisons, see: Major Oracle Third-Party Support Providers.
Oracle third-party support refers to maintenance and support services provided by independent companies instead of Oracle itself. These services include technical assistance, bug fixes, security patches, compliance guidance, and advisory for Oracle software products, all at a fraction of Oracle's official support cost.
| Dimension | Oracle Official Support | Third-Party Support |
|---|---|---|
| Cost | 22% of net licence fee annually, with 3-4% annual uplifts compounding indefinitely. For a $2M licence estate, expect $440K/year growing to $530K+ within five years | Typically 50-70% less than Oracle's fees. Flat pricing with no automatic annual uplifts. The same $2M estate costs $180K-220K/year with price certainty |
| Patches and updates | Quarterly Critical Patch Updates (CPUs), security patches, and product updates delivered through My Oracle Support portal | No access to Oracle's official patches. Providers deliver custom security fixes, workarounds, and virtual patching for vulnerabilities |
| Product coverage | All Oracle products under active support. De-supported versions receive no patches. Oracle dictates end-of-life timelines | Extended support for older versions Oracle no longer patches. Coverage for Database, EBS, PeopleSoft, JD Edwards, Siebel, and middleware |
| Custom code support | Oracle does not support customisations, extensions, or integrations. Standard support covers only Oracle's base code | Providers troubleshoot customisations, extensions, and integrations that Oracle will not touch. Major differentiator for heavily customised estates |
| Service model | Tiered ticket system. Initial contact through generic support agents. Escalation required to reach senior engineers | Dedicated senior engineers assigned to your account. Named support contacts who know your environment. Faster resolution for complex issues |
| Contract flexibility | Annual renewal with automatic uplifts. Reinstatement penalty (150% of lapsed fees) if you leave and return. Rigid terms | Flexible multi-year terms. Flat or capped pricing. Scope can be adjusted as you retire systems. No automatic uplifts |
Third-party support is most compelling for organisations running stable, mature Oracle deployments where the software is in "run and maintain" mode. If you are not planning major Oracle upgrades, if your systems are heavily customised (which Oracle does not support anyway), or if you are paying support on older versions that Oracle has de-supported, third-party support delivers immediate and significant cost savings with often better service quality. It is less suitable for organisations planning near-term upgrades to new Oracle versions or migrations to Oracle Cloud, where access to Oracle's official patches and upgrade paths has direct value.
Thorough preparation is the single most important factor in securing a strong third-party support deal. Before entering negotiations, invest time in understanding the market, your own requirements, and the provider landscape.
| Preparation Step | What to Do | Why It Matters |
|---|---|---|
| Conduct market research | Gather data on prevailing rates for similar third-party support services. Understand what discounts competitors are offering and standard SLA benchmarks | Without market data, you have no basis for evaluating whether a provider's proposal is competitive. Data eliminates guesswork |
| Investigate provider backgrounds | Review client testimonials, case studies, years in business, number of Oracle clients, and security certifications (ISO 27001, SOC 2). Check for past legal issues with Oracle | Provider quality varies significantly. Due diligence protects you from choosing a provider that cannot deliver on commitments |
| Assess industry reputation | Consult Gartner reports, independent reviews, and peer networks. The two dominant global providers are Rimini Street (founded 2005, largest) and Spinnaker Support (founded 2008). Regional providers like Support Revolution (UK-based) also operate | Understanding the competitive landscape helps you identify which providers are credible and which offer the best fit for your requirements |
| Inventory your Oracle estate | Document all Oracle products, versions, customisations, and current support costs. Identify which systems are stable "run and maintain" candidates vs systems that need Oracle's upgrade path | Your estate inventory determines what goes into the third-party support scope. Accuracy prevents scope disputes and ensures correct pricing |
| Calculate your TCO baseline | Know exactly what you pay Oracle today, including annual uplift projections over 3-5 years. This becomes your benchmark for measuring third-party savings | Providers peg their fees as a percentage of your Oracle support bill. Understanding your true Oracle cost (including future uplifts) makes savings calculations accurate |
| Conduct a licence compliance review | Audit your Oracle licence compliance before approaching any provider. Resolve any compliance gaps proactively. If you have an active Oracle ULA, certify it before moving | If Oracle audits you after switching and finds non-compliance, the penalties could exceed your support savings. Compliance must be clean before transition |
Before switching to any third-party support provider, conduct a thorough Oracle licence compliance review. If Oracle audits you after the switch and finds non-compliance, the penalties could exceed your entire support savings. Resolve any compliance gaps proactively. If you have an active Oracle ULA, you must certify it before moving to third-party support. See: Maintaining Oracle Licence Compliance on Third-Party Support.
Understanding that 50% savings is a baseline, not the best deal, is critical for effective negotiation. Third-party support providers typically peg their fees as a percentage of your Oracle support bill. A typical starting offer is 50% of your last annual Oracle support fee. But this is the opening position, not the final number.
| Strategy | How It Works | Expected Impact |
|---|---|---|
| Multi-year commitment | Offer a 2-3 year contract term in exchange for deeper discounts. Providers value revenue predictability and will trade margin for certainty | Additional 10-20% off the baseline. A 3-year commitment is the sweet spot for maximum discount with acceptable lock-in |
| Volume bundling | Bundle multiple Oracle products (Database, middleware, applications) into a single support contract rather than separate agreements | 5-15% further reduction. Providers prefer larger contracts and will discount to capture the full estate |
| Competitive bidding | Get quotes from both Rimini Street and Spinnaker Support. Share competitive offers (appropriately) to drive each provider's best price | Significant leverage on price. Providers know that informed clients with alternatives receive competitive offers |
| Scope optimisation | Ensure you are only paying for software you actually use. Exclude shelfware, retired systems, and unused licences from the support scope | Reduces the base cost immediately. Many organisations pay support on products they no longer use |
| Upfront payment | Negotiate a discount for paying the annual fee upfront rather than in instalments | 2-5% additional discount. Providers value cash flow certainty |
| Reference customer | Offer to serve as a named reference customer or provide a case study in exchange for a pricing concession | Variable. Worth asking, especially for newer providers building their reference portfolio |
An enterprise with $2M in Oracle licence value was paying $440,000/year to Oracle (22% support fee). A third-party provider initially quoted 50% ($220,000). Through negotiation, committing to a 3-year term, and referencing a competitor's lower quote, the company secured an additional discount to $180,000/year. That is nearly 60% savings versus Oracle fees, or $260,000 saved annually and $1.3M over five years. Well-prepared buyers regularly secure 60% or more in total savings through smart negotiation.
Price is important, but the contract terms around service quality, flexibility, and compliance protections matter just as much. These terms determine whether your savings are real and sustainable over the contract lifecycle.
| Contract Term | What to Negotiate | Why It Matters |
|---|---|---|
| Service Level Agreements (SLAs) | Push for concrete commitments: 15-minute response for Severity 1 issues, 1-hour workaround target, 4-hour restoration. Define escalation paths clearly (if unresolved in X hours, escalation to senior architect). Include service credits for SLA misses | SLAs with teeth protect your operations. Without service credit remedies, SLAs are aspirational targets, not enforceable commitments |
| Dedicated support resources | Negotiate a named account manager and dedicated lead support engineer who knows your environment. Avoid being routed to a generic ticket pool | The single biggest service quality differentiator. A dedicated engineer who understands your specific configuration resolves issues faster |
| Annual price caps | Lock pricing for the full contract term or cap annual increases at CPI or 2-3%. Oracle typically raises support by 3-4% annually. Your third-party deal should guarantee price predictability | Price certainty is a core value proposition of third-party support. Any provision allowing provider-initiated price increases undermines this benefit |
| Scope and coverage clarity | Confirm the quote includes support for customisations, integrations, and all Oracle products in your estate. Bundle everything into the base fee during negotiation | Scope gaps discovered post-signing become expensive add-ons. Get everything in writing before committing |
| Flexibility and exit clauses | Avoid punitive early termination fees. Seek the ability to scale support scope up or down as you retire systems. Aim for 60-day notice termination after year one | Your Oracle estate will change over the contract term. Flexibility to adjust scope without renegotiating the entire agreement preserves your options |
| IP compliance guarantee | The contract should explicitly state that the provider will not use Oracle's intellectual property beyond what is licensed. This protects you from legal risk | If a provider infringes Oracle's IP, you could be implicated. Reputable providers include explicit IP compliance language. If a provider resists this clause, that is a red flag |
| Security vulnerability response | Define how the provider handles critical security vulnerabilities. Specify response time for vulnerability assessment and delivery of custom patches or workarounds | Without access to Oracle's quarterly Critical Patch Updates, your provider's security response capability becomes your primary defence |
| Transition support | Negotiate onboarding support during the transition period: knowledge transfer sessions, environment documentation, and a stabilisation period with elevated support levels | The first 90 days after transition carry the highest risk. Dedicated transition support ensures continuity and builds confidence in the new arrangement |
Choosing the right provider is as important as negotiating the right price. The two dominant global players are Rimini Street and Spinnaker Support, with several regional providers serving niche markets. Always evaluate at least two providers to create competitive tension.
| Evaluation Criteria | What to Look For | Red Flags |
|---|---|---|
| Oracle product coverage | Ensure they support all your Oracle products: Database, EBS, PeopleSoft, JD Edwards, Siebel, middleware. Verify version coverage matches your deployment | Gaps in product coverage that would require you to maintain Oracle support on some products, undermining the cost savings model |
| Technical depth | Ask about the profiles of engineers assigned to your account. Senior Oracle experts with specific product knowledge, not a generic pool. Request CVs or summaries of proposed team members | Vague answers about staffing. Unwillingness to identify specific engineers. Over-reliance on junior staff or offshore-only support |
| Global coverage | If you operate 24/7 internationally, verify follow-the-sun support across your regions (Americas, EMEA, APAC). Confirm language capabilities and timezone coverage | Single-region support for a global operation. Reliance on a single timezone that does not cover your critical business hours |
| Security and compliance | Look for ISO 27001, SOC 2 certifications. Ask specifically how they handle critical security vulnerabilities without access to Oracle's patches | No certifications. Vague security processes. Inability to articulate a clear vulnerability response methodology |
| Legal track record | Check for any past legal disputes with Oracle. Ensure any historical issues are resolved and current processes are fully compliant | Active unresolved litigation with Oracle. Unwillingness to discuss legal history. No clear IP compliance methodology |
| Custom code support | Verify they support customisations, extensions, and integrations. This is a major differentiator because Oracle's standard support will not touch custom code | Limitations on custom code support. Additional fees for customisation troubleshooting not included in the base contract |
| Client references | Request references from clients in your industry and of similar scale. Speak with them directly about service quality, response times, and issue resolution | Inability to provide relevant references. References only from very small organisations when you are a large enterprise |
| Contract flexibility | Review termination provisions, scope adjustment rights, and annual increase caps before signing. Compare flexibility across providers | Long lock-in periods with no exit options. Automatic renewal clauses. Uncapped annual price increases |
Getting proposals from both Rimini Street and Spinnaker Support (and potentially a regional player like Support Revolution) creates competitive tension and gives you concrete data to drive better pricing and terms from your preferred vendor. Providers know that an informed client with alternatives receives competitive offers. Never negotiate with a single provider in isolation.
These strategies apply regardless of which provider you are negotiating with. They are designed to maximise savings while protecting your operational and compliance interests.
| # | Strategy | Detail |
|---|---|---|
| 1 | Start from your Oracle baseline | Know your exact Oracle support spend and projected 5-year costs (including 3-4% annual uplifts). This is your "cost of doing nothing" benchmark. Present this to providers to anchor the savings conversation |
| 2 | Solicit competing proposals | Get detailed proposals from at least two providers. Use each provider's offer as leverage against the other. Providers respond to competitive pressure just as Oracle does |
| 3 | Negotiate each component separately | Break down the deal into base support fee, SLA tiers, scope coverage, and value-adds. Negotiate each independently to avoid package-deal opacity where discounts on one component mask overpricing on another |
| 4 | Use multi-year terms as currency | A longer commitment is valuable to providers because it represents predictable revenue. Trade it explicitly for a deeper discount. Do not give multi-year commitment away for free |
| 5 | Lock in price certainty | Demand fixed fees for the full contract term or a cap of 2-3% on annual increases. Avoid any provision that allows provider-initiated price changes beyond the agreed cap |
| 6 | Exclude unused software | Provide an accurate list of active licences. Ensure you are not paying support on shelfware or retired systems. Scope optimisation reduces the base cost before any discount is applied |
| 7 | Maintain relationship balance | Be firm on terms but avoid aggressive tactics that damage the partnership. Your provider relationship is long-term. Positive dynamics produce better service over the contract lifecycle |
| 8 | Get legal review | Have legal counsel review compliance language around Oracle IP, audit cooperation, and data protection before signing. This is not optional for enterprise-scale transitions |
Oracle does not passively accept when customers leave its support programme. Understanding Oracle's typical responses allows you to prepare for them and neutralise the pressure tactics.
| Oracle Tactic | What Happens | How to Respond |
|---|---|---|
| Win-back discounts | Oracle may offer significant discounts (sometimes 30-50% off support fees) to prevent you from leaving. These are typically one-time offers that revert to standard pricing at the next renewal | Evaluate Oracle's offer genuinely, but calculate the total cost over 3-5 years including uplift reversion. Short-term Oracle discounts rarely match long-term third-party savings. Get any discount commitment in writing with multi-year guarantees |
| Audit initiation | Oracle may initiate a licence audit shortly before or after you leave support. This is a common pressure tactic designed to create compliance fear and financial exposure | This is why pre-transition compliance review is essential. If your licensing is clean, an audit has no leverage. Maintain detailed documentation and respond professionally. See: Oracle Licence Audit Strategic Guide |
| FUD campaign | Oracle's sales and support teams may raise fear, uncertainty, and doubt about third-party support: security risks, legal exposure, service quality concerns | Evaluate these claims objectively. Courts have affirmed the legality of third-party support. Reputable providers have robust security methodologies. Request specific evidence for any Oracle claim, not just assertions |
| Matching Service Levels policy | Oracle's 2022 policy change claims you cannot split support for the same product set between Oracle and a third party. Oracle may assert you must drop all support or keep all of it | This is a policy position, not a contractual obligation (unless your specific contract says otherwise). Review your contract for any bundling language. See: Oracle Support Policy vs Contract Rights |
| Reinstatement penalty threats | Oracle reminds you that returning to Oracle support requires payment of 150% of all fees that would have been due during the lapse period | Factor reinstatement costs into your long-term planning. However, in practice, reinstatement fees are negotiable, especially if Oracle wants to sell you new products or cloud services. The threat is designed to deter, not to be an absolute barrier |
Do not be caught off guard. Before you notify Oracle of your decision, prepare responses to each of these scenarios. Brief your executive stakeholders so they are not surprised by Oracle outreach. Oracle's account team will often contact executives directly to express concern. If your leadership team is aligned and prepared, these conversations are manageable. The organisations that stumble are those that make the transition decision at the procurement level without briefing leadership on Oracle's likely response.
Use this checklist to manage the transition from Oracle support to a third-party provider. Each step is designed to protect your operations, compliance posture, and commercial interests.
| # | Action | Detail | Timeline |
|---|---|---|---|
| 1 | Audit your Oracle estate | Inventory all Oracle products, active licences, customisations, and current support costs. Identify stable "run and maintain" systems that are prime candidates for third-party support. Resolve any licence compliance gaps before proceeding | 6-9 months before Oracle support renewal date |
| 2 | Evaluate multiple providers | Engage Rimini Street, Spinnaker Support, and at least one regional provider. Compare proposals on price, SLAs, technical depth, and contract flexibility. Check references from similar-scale organisations in your industry | 4-6 months before renewal |
| 3 | Negotiate aggressively on price and terms | Use 50% as a starting point, not an end point. Push for 60-70% savings through multi-year commitments, volume bundling, and competitive bidding. Lock in price caps and strong SLAs with service credit remedies | 3-4 months before renewal |
| 4 | Secure compliance protections | Ensure the contract includes explicit IP compliance guarantees from the provider. Archive all Oracle patches and documentation before cancelling Oracle support. Prepare your audit defence posture | 2-3 months before renewal |
| 5 | Archive Oracle resources | Download all patches, documentation, Metalink notes, and technical resources while you still have My Oracle Support portal access. Once support lapses, you lose access permanently | 30-60 days before renewal |
| 6 | Brief executive stakeholders | Prepare leadership for Oracle's likely response (win-back offers, audit threats, executive outreach). Ensure alignment across procurement, IT, legal, and the C-suite | Before notifying Oracle |
| 7 | Notify Oracle | Formally notify Oracle that you will not be renewing support. Check your contract for required notice periods (typically 30-90 days before renewal date). Document the notification in writing | Per contract notice period |
| 8 | Manage the transition | Time the switch to your Oracle support renewal date to avoid overlapping payments. Onboard with your new provider. Train internal IT teams on new support processes and escalation paths | At renewal date |
Third-party support offers significant cost savings (typically 50-70% below Oracle's fees), more flexible service terms tailored to your specific environment, extended support for older Oracle systems that Oracle no longer patches, and dedicated senior engineers who support your customisations. For organisations running stable, mature Oracle deployments, third-party support is one of the highest-ROI cost optimisation strategies available.
A 50% discount off Oracle's support price is the standard industry baseline, not an aggressive target. Most providers start their proposals at roughly half of your Oracle support bill. From there, well-prepared buyers push for 60-70% or more through multi-year commitments, volume bundling, competitive bidding between providers, and scope optimisation. The key is never accepting the first offer.
Yes. Courts have affirmed that Oracle licensees have the legal right to choose independent support providers. Oracle cannot force you to stay on its support programme. Your perpetual licences remain valid even after you stop paying Oracle for support. The legal requirements are that your provider does not infringe Oracle's IP (no unauthorised copying of Oracle code) and that you maintain compliance with your licence terms. Reputable providers have robust processes to ensure full compliance. See: Is Oracle Third-Party Support Legal?.
Oracle can audit any customer at any time, regardless of support status. In practice, audits are driven by business triggers (no recent purchases, mergers, renewals) rather than specifically by switching to third-party support. The best mitigation is being fully licence-compliant. Conduct a thorough internal compliance review before switching, resolve any gaps, and maintain detailed documentation. If your licensing is clean, an audit threat has no leverage. See: Oracle Licence Audit Strategic Guide.
Yes, but Oracle typically requires back payment of support fees for the lapsed period plus a reinstatement fee of 150% of the fees that would have been due. In practice, however, these fees are negotiable, especially if Oracle wants to win back your business or sell you new products. Returning is treated as a new deal, which can actually improve your leverage. Some organisations use a hybrid approach: keeping Oracle support on certain critical systems while moving stable environments to third-party support.
You lose access to Oracle's quarterly Critical Patch Updates (CPUs) and new patches once support lapses. You retain the right to use any patches you downloaded while on support, but no new patches will be available from Oracle. Third-party providers address security vulnerabilities through custom patches, virtual patching, and workarounds. Archive all available patches from My Oracle Support before your support renewal date lapses.
Reputable providers monitor Oracle's security advisories and vulnerability databases continuously. When a critical vulnerability is identified, they develop custom fixes, virtual patches, or configuration-level workarounds specific to your environment. Response times for critical vulnerabilities should be defined in your SLA. Some providers offer faster vulnerability response than Oracle because they can develop targeted fixes for your specific configuration rather than creating universal patches for all customers.
In practice, many organisations maintain a hybrid approach: keeping Oracle support on systems where they plan upgrades or need Oracle's latest features, while moving stable "run and maintain" environments to third-party support. However, Oracle's Matching Service Levels policy (updated in 2022) claims you cannot split support for the same product within a "licence set." Whether this is enforceable depends on your specific contract language. See: Oracle Support Policy vs Contract Rights.
The primary risks are: losing access to Oracle's official patches (mitigated by the provider's security methodology), compliance exposure if your licensing is not clean before switching (mitigated by pre-transition compliance review), provider dependency on a single company for all Oracle support (mitigated by evaluating provider stability and financial health), and the cost of returning to Oracle support if your strategy changes (mitigated by factoring reinstatement costs into long-term planning). All of these risks are manageable with proper preparation.
For organisations with Oracle support spend exceeding $300K annually, independent advisory is strongly recommended. An independent adviser helps you evaluate providers objectively (without the bias of provider sales teams), negotiate better pricing using market benchmarking data, ensure your licence compliance is clean before transition, and manage Oracle's response tactics. The cost of advisory is typically a fraction of the additional savings achieved through expert negotiation. See: Redress Compliance Third-Party Support Advisory.
We advise enterprises on third-party support evaluation, provider negotiation, licence compliance review, transition planning, and Oracle response management. Fully independent. No ties to Oracle or any third-party support provider. Fixed-fee engagement.
Third-Party Support AdvisoryIndependent third-party support advisory. Provider evaluation. Contract negotiation. Compliance review. Transition management. 100% vendor-independent, fixed-fee engagement.