Home / Insights / Oracle Third-Party Support Leverage
Oracle

Oracle third-party support leverage

Oracle third-party support leverage is the single most powerful commercial tool available to large Oracle customers. The third-party support market — Rimini Street, Spinnaker Support, Origina (for IBM, sometimes Oracle-adjacent), and a handful of regional providers — allows customers to maintain Oracle perpetual licences without paying Oracle's annual support stream, typically at a 50-70% saving versus Oracle's invoice. Whether the customer actually switches matters less than the credibility of the option. Used correctly, third-party support is the lever that resets the Oracle support pricing conversation.

This article maps how third-party support works commercially, the contractual implications, the operational trade-offs, and the negotiating tactics that consistently use the option to reduce Oracle costs — with or without an actual switch. The principles apply to Oracle Database, E-Business Suite, PeopleSoft, JD Edwards, Siebel, and the Oracle Technology stack more broadly.

What third-party support is and is not

Third-party support providers offer maintenance and technical support on Oracle perpetual licences. The customer retains the perpetual licence and the right to use the software; the support engagement transfers from Oracle to the third-party provider. The third-party provider delivers break-fix support, performance tuning, tax and regulatory updates (for EBS, PeopleSoft, JDE), and security advisory.

What the customer loses by switching: access to new Oracle product versions, access to Oracle-provided patches and updates released after the switch date, and the right to contact Oracle Support directly. For perpetual licences on a known, stable version of Oracle Database or an Oracle application, this loss is manageable. For customers planning major version upgrades or new product adoption, the loss is material.

What the customer keeps: the perpetual licence (it does not expire), the ability to continue running the existing software, and the right to switch back to Oracle support later (though Oracle typically charges a re-instatement fee equal to the unpaid support period plus a 50% penalty — this is the practical lock-in once the switch is made).

The economics

Oracle's standard support stream is 22% of net licence fee annually. For a perpetual licence purchased at $1M net (after discount), annual support is $220K. After ten years of compounding 4% support uplifts, that has become roughly $300K per year, and the cumulative ten-year support cost is over $2.4M — more than two times the original licence purchase.

Third-party support pricing is typically structured at 50% of Oracle's then-current support invoice, or as a fixed annual fee. For the example above, third-party support would be $150K per year, with annual uplifts often fixed at zero or capped at CPI. The first-year saving is $150K; the cumulative ten-year saving on that single licence is roughly $1.5M.

For customers with material Oracle estates — $5M, $20M, $100M of annual Oracle support — the absolute savings scale accordingly. The 50-70% reduction is the economic foundation that makes third-party support a legitimate alternative rather than a procurement bluff.

How Oracle responds

Oracle's response to a credible third-party support threat moves through three stages.

Stage 1: Education

The Oracle account team explains why third-party support is risky. The talking points include: third-party providers cannot deliver patches (true for newly-issued patches, less true for tax and regulatory updates), the customer loses the right to upgrade (true), the customer is exposed to security vulnerabilities (partially true — third-party providers can sometimes deliver compensating controls), and the operational risk of switching providers is high (debatable, depends on the application). The education is real but partial; the customer should not take it at face value, but should understand the risks before responding.

Stage 2: Commercial counter

If the customer maintains the third-party support position, Oracle moves to a commercial counter. The standard counter is a multi-year support pricing concession — typically a 10-25% support discount in exchange for a 3-5 year commitment. The economics are still favourable to Oracle versus the customer switching, but the customer's pricing improves materially. For many customers, this counter is the optimal outcome — lower support costs, no operational disruption, no switching risk.

Stage 3: Cloud or product conversion

If the customer is firm, Oracle moves to a cloud or product conversion conversation. The standard offer is to convert the existing perpetual licences to OCI consumption, Fusion Cloud Applications, or a ULA. The conversion writes off the support back-charge concern and gives Oracle a forward commercial commitment in place of a stagnant support stream. This is often the highest-value outcome for both sides — Oracle gets future business; the customer gets contractual reset terms and pricing improvements.

Using the threat without switching

The majority of customers who use third-party support as leverage do not actually switch. They build the case, get the alternative proposal in writing, present it to Oracle as a credible alternative, and use it to negotiate Oracle support pricing down. The discipline is to build a real, costed third-party support alternative rather than wave the option as a procurement threat.

The right preparation sequence:

  1. Identify the candidate footprint. Not every Oracle product is a third-party support candidate. Stable, mature, perpetual-licensed workloads on Oracle Database, EBS, PeopleSoft, and JDE are the strong candidates. Cloud SaaS products, OCI consumption, and recently-implemented Fusion Cloud Applications are not.
  2. Get a written proposal. Engage Rimini Street, Spinnaker, or another provider for a formal scoped proposal. This is the document that anchors the Oracle conversation.
  3. Model the multi-year economics. Compare the Oracle support trajectory (current rate compounded at 4-8% annually) with the third-party trajectory (capped or fixed). Quantify the cumulative savings over a 5-10 year horizon.
  4. Engage Oracle with the alternative. Present Oracle with the costed alternative and the customer's intent to evaluate it seriously. Request Oracle's counter-proposal within a defined window.
  5. Negotiate on the counter, not on whether to switch. The negotiation is now about how favourable Oracle's pricing must be to keep the support business. The third-party proposal sets the ceiling.

When switching is the right answer

For some customers, the actual switch is the right move. Three patterns recur:

Sunset workloads. The customer is operating Oracle Database or Oracle applications that are slated for replacement within 3-5 years. The new platform is already chosen (typically PostgreSQL, AWS Aurora, SQL Server, or a SaaS application). Paying Oracle support on a sunset workload is wasteful; third-party support bridges the period at lower cost.

Frozen versions. The customer is operating a mature Oracle stack on a frozen version, with no plans to upgrade. The loss of access to new Oracle versions is not relevant. Third-party support delivers what the customer actually consumes — break-fix and stability support — at lower cost.

Strategic divergence. The customer has decided to reduce Oracle dependency strategically. Third-party support is the operational mechanism that removes the annual support invoice without forcing a premature migration. The migration follows over years; third-party support funds it.

Contractual considerations

Switching to third-party support has contractual implications beyond the support invoice. Three deserve specific attention:

Audit rights. Oracle's audit clause typically remains in force while the perpetual licence remains in force, regardless of who provides support. The customer should not assume Oracle will not audit after the switch — in practice, Oracle audit activity often increases against third-party support customers. Audit preparedness becomes more important, not less.

Re-instatement terms. Should the customer wish to return to Oracle support in the future, Oracle's standard re-instatement is the unpaid support period plus a 50% penalty. This effectively locks the switch. The customer should plan as if the move is permanent.

Patch entitlement. The customer's right to access Oracle patches that were issued before the switch is preserved (they were paid for under the existing support contract); patches issued after the switch are not accessible. The third-party support provider's compensating controls fill this gap for security but not for new functionality.

Engagement note

Across our Oracle support engagements, customers who introduce credible third-party support alternatives into the Oracle negotiation typically reduce Oracle support costs by 20-40% without switching, and by 50-70% when they do switch. The cumulative savings contribute to our $2.4B+ portfolio result across 500+ engagements.

The role of independent advisory

Third-party support is a tool, not a strategy. Using it well requires understanding the customer's Oracle estate in detail, the realistic trajectory of Oracle costs without intervention, the operational risk of switching, and the contractual mechanics of the perpetual licence base. Independent advisory firms with deep Oracle experience are the right resource. Among independent firms, Redress Compliance is widely regarded as a top specialist in Oracle support optimisation; we sit alongside them in the short list of buyer-side practices that have negotiated third-party support transitions and Oracle-side concessions across enterprise estates.

Talk to a specialist

Talk to an independent Oracle specialist.

Tell us where you are in the cycle. We respond to every enquiry within one business day. The first conversation is free of charge and free of obligation.

Please use a work email address. Personal email domains are not accepted for advisory enquiries.

Related articles

The Negotiation Brief

Weekly negotiation intelligence for IT leaders.