Editorial photograph of an Oracle support contract review meeting with database licensing reports on the conference table
Article · Oracle · Support Strategy

Oracle third party support. When to leave. When to stay.

Oracle Premier and Sustaining Support runs at 22 percent of net license per year. Third party providers price the same support at 50 percent less. This framework decides which Oracle estates qualify, what to test, and how to exit if the move does not deliver.

Read the Briefing Oracle Knowledge Hub
50%Typical annual support saving
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Oracle Premier Support sits at 22 percent of net license per year with an annual uplift typically running 3 to 8 percent. Third party providers cover the same patches and fixes at 9 to 12 percent of net license. The decision is not just financial.

The mistake pattern is consistent across every engagement. Customers either move every Oracle workload and trigger audit exposure, or never move and overpay by millions annually.

Key Takeaways

The seven decisions that govern an Oracle support move

  • The financial case is large. 45 to 60 percent annual saving against the Oracle Premier line.
  • The patch path is the first risk. Future Oracle Critical Patch Updates are not accessible after termination.
  • The reinstatement fee is 150 percent. Plus the prospective rate uplift if the customer returns to Oracle support.
  • Stable estates qualify. Custom or pre upgrade estates do not.
  • The exit clause matters. The third party contract must permit return to Oracle support without penalty.
  • The audit position must be baselined. Before, not after, the move.
  • Run a pilot. One product family for 12 months before the full estate transition.

1. What Oracle support actually delivers

The Oracle support contract bundles four services into a single 22 percent fee. The customer that wants to evaluate third party support must understand what each service is worth in isolation.

Patch and Critical Patch Update access

Oracle releases Critical Patch Updates quarterly across the Database, Middleware, and Application stacks. Active support customers can download these patches from the Oracle support portal. CPUs include security fixes, regulatory updates, and engineering corrections.

Service request and break fix

Active support customers can log a service request with Oracle Support. The published Oracle SLA varies by severity. Severity 1 production down issues target a one hour response. The actual mean time to resolution varies materially by product and by region.

Version upgrades and roadmap access

Active support customers can move to any future version of the licensed product. A customer on Database 12c can upgrade to 19c or 23c without buying a new license. Loss of support freezes the version at the last patch level held at termination.

The audit defense indirect benefit

Oracle audit teams treat active support as a positive signal. A customer that pays full Premier support is statistically less likely to be the subject of an aggressive audit motion than a customer that has lapsed support. The signal is informal but real.

2. What third party support delivers

Third party support providers offer the same break fix, security fix, and engineering response services that Oracle Support delivers, sourced from their own engineering staff and patch archive.

The fix stream

Third party providers maintain their own patch archive sourced from the period when the customer was an active Oracle support customer. Security fixes that match published CVEs are issued from the provider's own engineering team. Critical Patch Update equivalents are released on the provider's own schedule.

The service level position

Most third party providers commit to 15 to 30 minute response times for Severity 1 incidents and a named engineer for the customer account. Customer satisfaction surveys consistently show third party provider scores well above Oracle's own support scores for the same product set.

What is not in scope

  • New Oracle releases. A customer on Database 19c stays on Database 19c. Future Oracle releases require return to Oracle support to access.
  • Oracle issued certifications. Some Oracle hardware and OS certifications require active Oracle support. Third party providers issue their own certification stack.
  • Oracle Cloud entitlements. BYOL to Oracle Cloud Infrastructure is restricted while on third party support for some product families.

3. The financial case

The Oracle Premier Support fee is calculated as a percentage of net license. The customer can extract the exact figure from the Oracle ordering documents. Most enterprises have between 4 and 12 separate Oracle ordering documents that aggregate to the total support line.

The Oracle baseline

Oracle productNet licensePremier annualPremier 5 year cost
Database EE4.5M USD990K USD5.5M USD with 3 percent uplift
WebLogic Suite1.2M USD264K USD1.5M USD with 3 percent uplift
EBS Financials2.8M USD616K USD3.4M USD with 3 percent uplift
Total8.5M USD1.87M USD10.4M USD across 5 years

The third party position

Third party providers price at 9 to 12 percent of the same net license base, with the rate typically held flat for 3 to 5 years. The same 8.5M USD net license base costs the customer 765K to 1.02M USD per year on third party support, against 1.87M USD on Oracle Premier.

The 5 year net

The 5 year saving on the example above is 5.5M to 6.6M USD before accounting for any reinstatement risk or pilot costs. The customer that signs a 3 year third party agreement and returns to Oracle in year 4 absorbs the reinstatement fee but still nets 2.5M to 3.5M USD across the 5 year window.

4. Workloads that qualify

Not every Oracle estate is a good candidate for third party support. The workload qualification test is the single most important step in the framework.

The qualification criteria

  1. Stable production status. The workload runs in production with no active major upgrade planned in the next 24 months.
  2. Patched to current. The customer is on the latest Critical Patch Update at the time of the move.
  3. Documented configuration. The deployment, the customisations, the integrations, and the operational runbook are documented.
  4. Known fix backlog. Open Oracle service requests are resolved or accepted as known issues.
  5. No Fusion roadmap inside 12 months. The customer is not in the middle of an EBS to Fusion or PeopleSoft to Fusion migration.
  6. No new Oracle license purchase inside 12 months. Recent purchases have a reinstatement exposure if support lapses on connected licenses.

The classic qualifying workloads

  • Oracle EBS R12.2 on Database 19c. Stable, patched, slow change. The classic third party candidate.
  • Siebel CRM in maintenance mode. Many customers run Siebel for 3 to 5 more years before moving to Salesforce or Dynamics.
  • JD Edwards EnterpriseOne 9.2. Stable application platform with strong third party provider coverage.
  • PeopleSoft HCM and Financials. Stable releases with documented patch path.
  • Standalone Database EE for legacy data warehouse. Stable schema and well understood operational profile.

5. Workloads that do not qualify

The opposite test is equally important. Some Oracle workloads should never move to third party support without significant additional risk acceptance.

The disqualifying patterns

  • Mid major upgrade. Database 12c to 19c, EBS R11 to R12, PeopleSoft 9.0 to 9.2.
  • Live Fusion migration. EBS to Fusion ERP, HCM to Fusion HCM, Siebel to Service Cloud.
  • Custom application stack heavily dependent on Oracle patching. Custom forms, custom database extensions.
  • Engineered Systems on the current Oracle hardware refresh. Exadata customers in active hardware engagement.
  • Oracle Cloud Infrastructure BYOL workloads. Some BYOL paths require active Oracle support.
  • Workloads under live audit. Audit activity should resolve before any support strategy change.

6. The risk matrix

The risk matrix is a structured way to score each Oracle workload against the qualification criteria. The matrix produces a green, amber, or red rating for each product line.

Risk dimensionGreenAmberRed
Version statusLatest CPU1 to 2 CPUs behindMultiple CPUs behind
Major upgrade horizonNo upgrade in 24 monthsUpgrade in 12 to 24 monthsActive upgrade
Fusion migrationNo migration plannedStrategy phaseActive migration
Customisation levelStandard plus reportsModerate customisationHeavy custom forms
Audit statusNo active auditRecent audit closedActive audit
New license intentNone in 12 monthsMaybe in 6 to 12 monthsActive purchase

7. The pilot plan

The pilot is the move that protects against the financial and operational risk of a full estate transition. A well designed pilot covers 12 months of one product family before any broader move.

Pilot scope

  • One product family. Typically EBS or Database EE on a defined cluster.
  • One geographic region. Easier to roll back if the pilot fails.
  • Defined SLA targets. Response and resolution times that match or exceed Oracle's published SLA.
  • Defined patch cadence. Critical Patch Update equivalents on a documented quarterly schedule.
  • 12 month evaluation window. Long enough to test through several patch cycles and a full year end close.

Pilot success criteria

  1. Zero Severity 1 escalation failures. The provider's named engineer handles all production down incidents.
  2. Patch cadence matched. Provider issued Critical Patch Update equivalents on the documented schedule.
  3. No audit triggered. Oracle audit activity does not increase during the pilot period.
  4. Customer satisfaction baseline. Internal IT and business satisfaction scores match or exceed the Oracle support baseline.
  5. Financial saving captured. The actual saving matches the modeled saving within 5 percent.

8. The exit option

The third party support contract must permit the customer to return to Oracle support without commercial penalty from the third party provider. The Oracle reinstatement fee is a separate matter.

Required contractual provisions

  • Termination for convenience with 90 days notice. Allows the customer to exit if Oracle issues a reinstatement amnesty.
  • Patch archive access at termination. The customer retains a complete copy of all patches issued during the support period.
  • Knowledge transfer at termination. 90 days of post termination knowledge transfer to the customer or to a successor provider.
  • Data return clause. All support cases, fix engineering, and configuration documentation returned at termination.

The Oracle reinstatement defense

The customer that returns to Oracle support pays the published reinstatement fee of 150 percent of lapsed support. The negotiation move is to time the return into a larger Oracle transaction, such as a ULA renewal or a new Oracle Cloud Infrastructure commit, where Oracle has commercial flexibility to waive or reduce the reinstatement fee.

What to do next

The checklist takes the Oracle buyer from where they are today to a qualified, piloted, contracted third party support transition.

  1. Pull every Oracle ordering document. Net license and support line by ordering document. Multi year history.
  2. Run the risk matrix per product family. Green, amber, red ratings.
  3. Baseline the deployed license position. Internal license review for every product family at green or amber.
  4. Model the 5 year saving. Oracle baseline against the third party baseline. Include reinstatement scenarios.
  5. Scope the pilot. One product family, one region, 12 months.
  6. Negotiate the third party contract. Exit clauses, patch archive, knowledge transfer.
  7. Time the Oracle exit. Avoid the 30 days before Oracle fiscal year end. Document the support termination notice.
  8. Run the deal through Vendor Shield. Independent buyer side review before signature.

Frequently asked questions

What is the typical annual saving when moving Oracle Database support to a third party provider?

Oracle Premier Support runs at 22 percent of net license per year. Third party providers price the same support coverage at 9 to 12 percent of net license per year. The customer with 5M USD of Oracle Database net license pays 1.1M USD to Oracle Premier and 450K to 600K to a third party provider.

Across 35 transitions, the median annual saving was 52 percent of the Oracle Premier line. Larger estates above 10M USD of net license achieved savings of 55 to 60 percent against the Oracle rate.

Does the customer lose access to Oracle patches and security fixes?

Yes. The terms of Oracle support require the customer to download patches while under active Oracle support. Once the customer terminates Oracle support, future patches and Critical Patch Updates are not accessible from the Oracle support portal.

Third party providers issue equivalent fixes from their own engineering staff. The defense pattern is that the customer downloads and archives all patches and CPUs while still under Oracle support, then transitions to the third party fix stream.

Can a customer move to third party support and still buy new Oracle licenses?

Yes. The Oracle Master Agreement permits the customer to buy new licenses regardless of support status on existing licenses. The customer that terminates support on a subset of licenses can still purchase new licenses for new projects.

The traps are the reinstatement fee and the matching service level rule. A customer that later wants to return a subset of licenses to Oracle support pays 150 percent of lapsed fees as reinstatement and must keep all licenses on the same support level.

Which Oracle workloads are good candidates for third party support?

Stable production estates that have completed the major version upgrade and are running known and patched workloads are good candidates. Examples include EBS R12 on Oracle Database 19c, mature Siebel deployments, and JD Edwards EnterpriseOne 9.2.

Custom application stacks, environments that depend on frequent Oracle patching, and roadmaps that include near term migrations to Oracle Cloud Infrastructure are poor candidates. The customer that plans to move to Fusion SaaS within 12 months should stay on Oracle support during the migration.

How does the customer protect against the Oracle audit risk after moving to third party support?

Oracle audits do not change frequency based on support status. The audit risk is constant whether the customer pays Oracle Premier or third party support. The defense is the same as for any Oracle customer.

The pre move audit defense work is to baseline the deployed license position, complete an internal license review, and put the Oracle Master Agreement and ordering documents in a single repository accessible to the audit response team.

Can a customer return to Oracle support after a third party period?

Yes. Oracle reserves the right to charge a reinstatement fee of 150 percent of lapsed support fees plus a future support uplift. The customer that lapsed 1M USD of annual Oracle support for two years and wants to return pays 3M USD of back fees plus a higher prospective rate.

The negotiation move is to scope the third party period as a finite assessment. Some customers have negotiated reinstatement waiver clauses at the original signing, particularly inside larger ULA renewals or new Oracle Cloud Infrastructure commits.

How does Redress engage on Oracle third party support decisions?

Redress runs Oracle third party support advisory inside the Vendor Shield subscription and the Renewal Program. The work covers estate qualification, cost modeling, provider scoping, the contractual exit from Oracle support, and the reinstatement defense.

Typical engagements deliver 45 to 60 percent annual support savings against the Oracle Premier baseline while protecting the audit position, the new license purchase right, and the option to return to Oracle support if the workload changes.

How Redress engages

Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the Oracle Knowledge Hub, and the Software Spend Assessment.

Read the related Oracle ULA Decision Framework, the Oracle Hub, the case studies, the benchmarking service, the management team page, the about us page, and the contact page.

Model the Oracle support savings against your specific estate with the third party support savings calculator.
Open the Calculator →
White Paper · Oracle

Download the Oracle ULA Decision Framework.

The companion playbook covers the Oracle Unlimited License Agreement decision tree, certification mechanics, and the negotiation moves that protect the customer at exit.

Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.

Oracle ULA Decision Framework

Open the playbook in your browser. Corporate email only.

Open the Paper →
50%
Median support saving versus Oracle
22%
Oracle Premier annual rate
500+
Enterprise Clients
$2B+
Under advisory
100%
Buyer side

Third party support is not a discount. It is a different contract, a different support model, and a different relationship with the publisher. Treat it that way.

Former Oracle Support Director
Now on the buyer side, 35 third party transitions reviewed
More Reading

More from this practice.

Oracle Knowledge Hub →
Oracle support strategy overview
Oracle · Support
Oracle Support Strategy
Premier, Sustaining, third party, hybrid.
11 min read
Oracle ULA decision framework white paper
Oracle · White Paper
Oracle ULA Decision Framework
Certify, exit, or extend.
16 min read
Oracle audit defense guide
Oracle · Audit
Oracle Audit Defense Guide
The first 14 days set the outcome.
13 min read
Oracle knowledge hub
Oracle · Hub
Oracle Knowledge Hub
All Oracle research in one place.
8 min read
Oracle advisory services
Oracle · Services
Oracle Advisory Services
Buyer side advisory across Oracle.
9 min read
Editorial photograph of an Oracle support strategy review with the CIO and CFO at the boardroom table

Cut the support bill. Protect the workload.

We have advised on 35 third party support transitions across Oracle Database, EBS, Siebel, JD Edwards, and PeopleSoft. Every engagement starts with one conversation.

Oracle intelligence, monthly.

Support pricing benchmarks, third party transition patterns, ULA decision data, and the moves that worked. Written for buyer side teams running active Oracle decisions.