Third-party Oracle support can cut maintenance costs by 50% or more — but it comes with trade-offs. This playbook provides a comprehensive analysis of the differences, product coverage, pros and cons, Oracle's retention tactics, cost comparisons, fit assessment, negotiation strategies, and a 10-step action plan to help you make an informed decision.
Third-party Oracle support refers to maintenance and technical support for Oracle software provided by an external vendor rather than Oracle Corporation. You continue to use your valid Oracle licences but rely on a third-party provider for help desk support, bug fixes, and regulatory updates — instead of paying Oracle's annual support fees. Crucially, these providers operate independently of Oracle and do not have access to Oracle's proprietary support portal or source code.
| Dimension | Oracle Premier Support | Third-Party Support |
|---|---|---|
| Annual Cost | ~22% of licence cost per year, with 3–5% annual increases | ~50% lower than Oracle's fees, with flat/fixed pricing |
| Patches & Updates | Official Oracle patches, quarterly Critical Patch Updates, security fixes | No Oracle patches after contract ends; provider creates "virtual patches" and workarounds for bugs and security vulnerabilities |
| Upgrade Rights | Included — upgrade to newer software releases without purchasing new licences | Not included — you "freeze" on your current version; must return to Oracle support (with backdated fees) for future upgrades |
| Customisation Support | Not supported — Oracle only assists with vanilla, unmodified software | Fully supported — engineers troubleshoot your entire environment including custom extensions, integrations, and custom code |
| Knowledge Base | My Oracle Support (MOS) — Oracle's proprietary portal, patch downloads, support notes | Provider's own support portal and knowledge repository; staffed by former Oracle support engineers |
| Service Model | Severity-based ticketing; generic troubleshooting scripts; may recommend "apply patch" or "upgrade" | Direct access to senior engineers; named support leads; aggressive SLAs (e.g., 15-minute critical response, 24/7 coverage) |
| Support Duration | Tied to Oracle's support lifecycle — Premier → Extended → Sustaining (with declining coverage) | Indefinite — provider supports your version as long as you need it, with no end-of-support deadlines |
In summary, third-party support replaces Oracle's support for licensed customers, delivering help and fixes with a more customer-focused approach. You trade the steady stream of official Oracle patches and upgrade rights for lower cost, personalised service, customisation support, and extended support life for older software. For detailed analysis, see our Third-Party Oracle Support: Savings or a Trap? guide.
Evaluating third-party support options? Get independent advice from former Oracle licensing specialists.
Third-Party Advisory Service →Third-party support spans a wide range of Oracle's on-premise software portfolio. Leading providers such as Rimini Street and Spinnaker Support cover Oracle's major product lines.
All major modules — Financials, HR, Supply Chain, Manufacturing — including older releases (12.1, 11i) that Oracle has placed in Sustaining Support. Third-party providers deliver tax and regulatory updates, bug fixes, and customisation support long after Oracle has stopped issuing patches. See our Oracle EBS Licensing Guide.
HCM, Financials, Campus Solutions and more. Third-party support maintains legacy PeopleSoft systems indefinitely — providing payroll tax compliance updates, regulatory fixes, and customisation support. See our PeopleSoft Licensing Guide.
EnterpriseOne and World — helping JDE customers avoid forced upgrades to newer releases or Oracle Cloud ERP by providing bug fixes and localisations on existing versions. Particularly valuable for manufacturing and distribution companies. See our JD Edwards Licensing Guide.
Oracle Database (all versions, 10g through 19c and beyond) plus WebLogic, Fusion Middleware, and OBIEE. Companies running stable database versions receive third-party security updates and performance tuning, avoiding expensive Oracle Extended Support fees. See our Oracle Database Licensing Guide.
Full Siebel CRM support for telecom, finance, and other industries — including custom components, browser/OS compatibility updates, well beyond Oracle's support timeline.
EPM/financial planning tools, Oracle Retail, Exadata software, and other niche on-premises products. Any on-premises Oracle software for which you hold a perpetual licence can potentially be maintained by a third-party vendor.
The primary motivator: Oracle's annual support fees are ~22% of licence cost, increasing 3–5% per year. Third-party support charges roughly half of Oracle's fee with no automatic annual increases. Over five years, savings on a $1M licence estate can exceed $650K — budget freed for digital transformation, cloud migration, or new initiatives. See our Oracle Support Cost Reduction Strategies.
Third-party vendors continue to support older Oracle versions indefinitely — eliminating end-of-support deadlines imposed by Oracle. No forced upgrades just because Oracle's calendar says support is ending. Keep running EBS 11i, PeopleSoft 9.1, or Database 12.1 as long as it serves the business, with full bug fixes, security patches, and tax/regulatory updates.
Direct access to senior engineers (often former Oracle experts) who handle issues from start to finish. Contractual SLAs include 15–30 minute critical response times and 24/7 coverage. No more being told to "apply the latest patch" or "upgrade to the next release." Named support engineers familiar with your environment result in faster turnaround and higher satisfaction.
Oracle's standard support won't troubleshoot custom code — they require you to reproduce problems in an unmodified environment. Third-party providers support both standard Oracle code and all customisations, extensions, and integrations. They'll even write fixes for custom code. One-stop support for the real-world state of your software.
Oracle's 3–4% annual increases compound significantly over time. Third-party providers offer flat or fixed fees for the contract duration — eliminating "budget creep" and making financial planning straightforward.
Named account managers become intimately familiar with your environment. Regular check-ins, health reports on Oracle systems, and proactive problem-solving. Feels like "having an extension of our IT team" rather than dealing with a faceless ticketing system.
One company cut its Oracle support bill by 60% by switching to a third-party provider, freeing hundreds of thousands of dollars redirected into analytics and digital transformation projects. Over five years, savings from third-party support can easily run into the millions for large Oracle estates.
Once you leave Oracle support, you stop receiving Oracle's official patches, fixes, and security updates. Third-party providers develop "virtual patches" to address bugs and vulnerabilities — but they reverse-engineer solutions without access to Oracle's source code. Leading providers have strong security methodologies, and no widely reported breaches have been attributed to third-party support customers (including banks and government agencies). However, the risk exists: you're betting an independent firm can match Oracle's security vigilance. Mitigation: Ensure the provider has strong security credentials (ISO 27001), and augment with firewalls and intrusion detection.
You "freeze" on your current version. No new features, modules, or performance enhancements from future Oracle releases. If your business later requires a new Oracle capability, you'd need to return to Oracle support (with backdated fees) or find a workaround. Mitigation: Complete any necessary upgrades while still on Oracle support, then switch to third-party for the stable period thereafter.
Oracle retains the right to audit your software use even after you leave support. Industry observers note Oracle sometimes increases audit activity on customers who drop support. If you want to return later, Oracle typically charges backdated fees plus a reinstatement fee — potentially erasing savings. Mitigation: Conduct an internal licence audit before switching, maintain documentation of entitlements and usage, and archive all Oracle patches while you still have access. See our Oracle Audit Defence Service.
Oracle's contracts often require you cannot drop support on a subset of licences — it's all or nothing for that product family. For example, if you have 100 Oracle Database licences, Oracle may require all 100 stay on support or you terminate all. You can't keep 50 on Oracle and 50 on third-party. Mitigation: Review contracts carefully, identify which licences are tied together, and structure your transition so you only drop support in allowed ways. See our Oracle Support Agreements Guide.
Oracle sales reps often react poorly — expect more aggressive sales tactics, less friendly terms on other deals, and potential audit triggers. You lose My Oracle Support (MOS) access, patch downloads, and knowledge base. Mitigation: Keep the relationship professional, maintain product documentation before switching, and be prepared for Oracle's pushback.
The Oracle vs. Rimini Street case established that third-party support is legal for customers, but providers must operate within the law. Courts found Rimini had improperly accessed Oracle's materials — resulting in injunctions on their operating methods. Reputable providers have adjusted accordingly. Mitigation: Vet your provider's legal history, ask how they obtain updates, and confirm no active court restrictions on their operations.
Oracle is well aware that third-party support siphons its lucrative maintenance revenue. If you're considering a switch, be prepared for Oracle to respond in one or more of these ways:
Oracle reps may imply third-party support is "illegal" (which is false — courts have affirmed customers' rights), reference the Rimini Street lawsuit as a scare tactic, or suggest your systems will become instantly vulnerable. They may hint that you'll be "first in line for an audit." Counter: Know the legal facts, talk to reference customers, and evaluate security objectively. Many large enterprises including government agencies have used third-party support for years without issue.
Oracle may remind you that dropping support triggers matching service-level repricing — the cost of supporting remaining products could increase to recoup Oracle's revenue. If you terminate support on a subset of licences, Oracle can raise the fee percentage on remaining licences. Counter: Time moves to coincide with natural contract expirations, or negotiate written waivers for repricing during a partial drop.
Despite Oracle's official "no discount" stance on support, they have been known to offer one-time discounts, free support years, or credits tied to other Oracle purchases. Oracle might bundle: "Buy a cloud subscription and we'll waive the support penalty." Counter: Leverage third-party quotes to push Oracle for a better deal — but be aware any short-term concession may be recouped later. See our Oracle Contract Negotiation Service.
Customers who drop support are widely believed to be placed in a higher-risk pool for audits. Oracle knows it can only generate additional revenue through an audit true-up. Counter: If you're fully compliant, Oracle's audit tactic loses its bite. Ensure you're clean on licensing before switching. See our Oracle Audit Defence Service.
Oracle may escalate to VPs or legal counsel — letters reminding you of contractual obligations, calls urging you to reconsider. This is high-pressure retention. Counter: Stay firm, involve your legal team, and remember: Oracle cannot terminate your existing perpetual licences just because you left support. Any legal posturing is largely a bluff.
Many organisations use the option of third-party support as leverage: by showing Oracle you have a credible Plan B, you may extract a better support deal. However, be prepared to follow through — if Oracle calls the bluff and you stay, the leverage is lost. For negotiation frameworks, see our Oracle Support Negotiation Tactics guide.
Oracle pushing back on your third-party support plans? Our negotiation team has decades of Oracle experience.
Oracle Contract Negotiation →| Cost Element | Oracle Premier Support | Third-Party Support |
|---|---|---|
| Annual Support Fee (Year 1) | ~22% of licence = $220,000 | ~50% lower = $110,000 |
| Annual Increase | Typically 3–5% per year (automatic) | 0% (fees usually fixed during contract) |
| Support Coverage | Standard (vendor patches, basic SLA, no custom code) | Comprehensive (custom fixes, tailored SLA, no new Oracle patches) |
| Upgrade Rights to New Versions | Yes — included with support | No — need to re-licence or resume Oracle support |
| 5-Year Cumulative Cost | ~$1.2M (with yearly uplifts) | ~$550K (flat fee) |
| Estimated 5-Year Savings | — | ~$650K (≈55% savings) |
If your Oracle product enters Extended Support, Oracle may charge an additional 10%+ uplift on top of the 22%. Third-party support avoids these escalating costs entirely — you get a simple, predictable fee regardless of Oracle's lifecycle designations.
If you attempt to drop some licences, Oracle's matching service-level repricing could push the cost percentage of remaining ones even higher than 22%. Third-party support for your entire product family eliminates this risk.
Avoiding forced upgrades saves project dollars. Better support responsiveness reduces downtime and operational losses. Not having to re-implement customisations in a new version for several years saves significant development effort. These indirect savings can match or exceed the direct fee reduction.
Your Oracle applications or databases are in steady-state — running the current version for a while, meeting business requirements, no pressing need for new features. An Oracle EBS R12 instance with extensive customisations, or a stable Oracle Database supporting core operations. These organisations prioritise stability and cost control over adopting the latest technology. For them, third-party support is a straightforward win.
Oracle products reaching end of Premier Support (or already in Sustaining Support). Rather than paying Oracle Extended Support surcharges or being pressured to upgrade, switch to third-party support and continue running "out-of-date" versions with full coverage. Buy time until a replacement is planned.
IT budget pressure demands savings. Oracle maintenance fees are a prime target — immediate 50%+ reduction is a "quick win" for meeting budget goals. Freed-up capital funds cloud migration, digital transformation, or other strategic initiatives.
Your organisation is migrating to a SaaS ERP (Workday, SAP), open-source database, or cloud-native architecture. Third-party support serves as a cost-effective bridge during the multi-year transition — keep the old Oracle system supported at a fraction of the cost while investing in the replacement.
If your IT roadmap requires staying current on Oracle tech — a planned EBS 12.2 upgrade, adopting Oracle Cloud modules, or implementing new database features — you need Oracle support for upgrade rights. Rule: Don't switch if a major Oracle upgrade is in progress or planned soon. Finish the project first.
If you're tightly aligned with Oracle's roadmap — participating in customer advisory boards, eagerly anticipating quarterly updates, or needing new Oracle features for competitive advantage. Third-party support is best for "frozen" environments, not those requiring continuous vendor innovation.
If most of your Oracle estate is already in the cloud (Fusion Cloud, Autonomous Database), third-party support only applies to the remaining on-premises portion. A hybrid approach may work — third-party for on-prem EBS, Oracle support for cloud — but assess complexity and contractual restrictions.
Systems requiring constant updates for compliance or competitive edge — a trading platform needing every performance patch, or payroll with very frequent tax changes beyond what a third party might cover promptly. While third parties do deliver tax/regulatory updates, organisations with extremely low risk tolerance may prefer Oracle's direct patches.
Assess each Oracle system individually — some may be ready to switch while others should remain under Oracle support. A phased approach can maximise savings on stable systems while maintaining Oracle support for strategic ones. For help categorising your Oracle portfolio, see our Oracle Licence Management Services.
Even if you plan to switch, the way you handle negotiations with Oracle is critical. There's an opportunity to negotiate better terms — or at minimum, ensure you exit properly.
Calmly let Oracle know you're exploring alternatives due to budget constraints and lack of need for upgrades. If they believe you are serious, Oracle might bend its "no discount" rule. Having a quote from Rimini Street or Spinnaker in hand — and a business case approved by your CFO — strengthens your position. You're introducing competition into what is normally a monopoly. Key: Only use this tactic if you're genuinely prepared to leave.
Be precise: "Oracle, if you can match 50% of our current support cost or freeze increases for three years, we will sign." Ask for flexibility to drop a subset of licences without penalty. Bundle discussions: "We'll buy X product, but only if you reduce support fees on Y legacy product." Oracle can justify support concessions internally as part of a larger deal.
This allows Oracle time to escalate and seek internal approvals. Involve procurement and executive sponsors early — CIO-to-Oracle VP conversations break logjams. Allow time to evaluate Oracle's counter-offer against the third-party proposal. An early start prevents auto-renewal because time ran out.
Understand termination clauses, repricing provisions, reinstatement fees, and matching service-level policies. If dropping a certain module triggers a penalty, negotiate around it or plan to drop everything. Consider negotiating audit immunity terms if you decide to stay. See our Oracle Support Agreements Guide.
Oracle's official policy charges backdated support fees plus reinstatement penalties to return. Try negotiating a "safety net" clause: if you return within X years, Oracle will waive or cap reinstatement fees. This makes management more comfortable trying third-party support with an agreed path back.
Ensure you provide proper written notice within required periods (typically 30–90 days) to avoid auto-renewals. If you strike a deal to stay, get all terms in contract amendments — verbal promises and emails from sales reps are insufficient. Document every interaction, especially if Oracle makes troubling statements.
Need experienced negotiators on your side when dealing with Oracle? We've sat on both sides of the table.
Oracle Contract Negotiation →Whether you ultimately switch or use the option as leverage, here are actionable steps to guide your decision and execution.
Reconcile what you own versus what's deployed. Identify compliance risks (unlicensed options enabled, user count overages) and remediate proactively. Being clean on licensing removes Oracle's audit leverage. Engage Oracle licensing experts if needed.
Target stable systems for third-party support — older ERP, CRM, or database systems not slated for new features. Keep Oracle support for strategic systems requiring upgrades or cloud integration. This segmentation maximises savings while minimising risk. A hybrid approach works if contract rules allow it.
Get detailed proposals from leading providers. Compare costs, scope of services, and SLA commitments. Ask for customer references in your industry. Verify credentials: years in business, Oracle client count, security certifications (ISO 27001), and legal history with Oracle.
Quantify 5-year cost savings, IT impacts (pros and cons), risk mitigations, and potential reinstatement costs. Get executive buy-in with a clear narrative: "We save $X million over five years, reinvest in Y initiatives, and mitigate risks with Z strategies."
Align with support renewal cycles — avoid mid-term changes that invoke Oracle penalties. Time the cutover to coincide exactly with Oracle support expiration. Consider Oracle's fiscal year timing — reps may be more flexible near end of quarter. Complete any needed upgrades on Oracle support first.
Communicate with IT ops, security (CISO), application owners, procurement, finance, and executive sponsors. Ensure the CISO's team is comfortable with the third-party security approach. Educate application owners that they won't receive new features but will get improved support for what they have.
Even if you fully intend to switch, engage in dialogue. Oracle might make a retention offer that changes the math. Enter with a clear ask — if Oracle meets it, weigh against the third-party option. If they don't, proceed with documented justification. See our Oracle Contract Negotiation Service.
Coordinate cutover date and procedures with the new provider. Download all patches, updates, and knowledge base articles from My Oracle Support before access ends. Set up support channels with the provider. Update systems to point to new update sources. Inform helpdesk and end-users of new support processes.
Work with your provider to understand their security update process and timeline. Augment with increased network monitoring, up-to-date firewalls, and virtual patching at the network layer. Review Oracle's public security bulletins regularly. Maintain compliance documentation for future audits.
Review support performance and business impact annually. Are issues resolved promptly? Have cost savings held? Have emerging needs for an upgrade appeared? If Oracle releases a highly attractive new version, revisit Oracle support or hybrid models. Stay vigilant to ensure you continue getting intended value.
Third-party support for Oracle can save money and improve support quality — but it requires ensuring licence compliance, accepting a "no-upgrades" period, and mitigating security risks. Ideal candidates are organisations with stable Oracle systems looking to reduce costs. With proper due diligence and execution, third-party support is a powerful tool for CIOs to regain control of Oracle costs and support on their own terms.
Whether you're evaluating third-party support, negotiating a better deal with Oracle, or preparing for an audit after switching — Redress Compliance provides independent advisory from former Oracle licensing specialists who've sat on both sides of the table.
Explore our complete Oracle licensing knowledge hub — playbooks, guides, and case studies.
Oracle Knowledge Hub →Also managing SAP, IBM, Microsoft, or Salesforce licence costs? We cover all major vendors.
All Advisory Services →