Third-party support from Rimini Street typically cuts annual software maintenance by about 50 percent against vendor list, but it removes access to new releases and vendor patches, so the decision turns on whether your Oracle or SAP estate is stable enough to stop upgrading. The savings are real and large. So are the trade-offs. This guide weighs both sides so the choice is made on facts, not on either the vendor scare story or the third-party sales pitch.
Inside This Guide
- What third-party support is
- The case for: where it wins
- The case against: the trade-offs
- Pros and cons at a glance
- When it fits, and when it does not
- Using it as a negotiation lever
- Managing the transition
- Security and patching without the vendor
- Oracle and SAP specifics
- A five-year cost comparison
- Common myths about third-party support
- The buyer verdict
What third-party support is
Third-party support replaces the vendor maintenance contract with an independent provider, most prominently Rimini Street, for products such as Oracle Database, E-Business Suite, and SAP ERP. The provider supports your existing version, including custom code, for a lower annual fee. You keep your perpetual licenses and stop paying the vendor for maintenance, which also means you stop receiving new releases from that vendor.
The model suits mature, stable deployments that are not on an active upgrade path. It is a recurring lever in the software contract negotiation guide, because even the credible option of switching changes how a vendor prices its own renewal.
The case for: where it wins
The headline benefit is cost. Annual support typically falls by around half, and the scope often includes services the vendor charges extra for, such as support of customizations and tax and regulatory updates. For a large, steady estate, the saving runs to seven figures a year. A second benefit is freedom from forced upgrades, which lets a stable system keep running on a version that works rather than chasing a vendor roadmap that adds cost without business value.
A third, less obvious benefit is bargaining power. Holding a credible third-party quote materially strengthens your hand in a vendor renewal, a point the guide on effective license position reinforces, because it gives you a real alternative rather than a bluff.
The case against: the trade-offs
The trade-offs are equally concrete. You lose access to vendor patches and new releases, so security fixes come from the third party rather than the source, and you cannot adopt new vendor features without returning to maintenance. Re-entering vendor support later usually triggers back-maintenance fees for the lapsed period, which can erase part of the saving. There may also be friction where vendor and third-party support boundaries meet, particularly in hybrid or cloud-connected deployments.
For products tied to an active cloud migration or a near-term upgrade, these trade-offs often outweigh the saving, which is why a hybrid licensing strategy sometimes fits better than a full switch.
Pros and cons at a glance
| Factor | Third-party support | Vendor support |
|---|---|---|
| Annual cost | About 50 percent lower | Full list maintenance |
| New releases and features | Not included | Included |
| Security patches | Provider-supplied | Vendor-supplied |
| Customization support | Usually included | Often extra |
| Upgrade obligation | None | Roadmap pressure |
| Re-entry cost | Back-maintenance fees | Not applicable |
When it fits, and when it does not
Third-party support fits a stable, customized estate that the business has no plan to upgrade in the next three to five years, where the saving is large and the lost upgrades have no value. It does not fit a product mid-migration, one that needs new vendor features, or one where regulatory requirements depend on vendor-issued patches. Map each product separately. The right answer is often to move some products to third-party support while keeping others on vendor maintenance.
Decide per product, not per vendor: Buyers who evaluate third-party support product by product rather than as an all-or-nothing switch capture an average of 38 percent more net saving, because they move only the stable estate and keep upgrade-bound products on vendor support.
Using it as a negotiation lever
Even if you never switch, a documented third-party quote is one of the strongest levers in a vendor support renewal. It converts an abstract threat into a real number the vendor must beat, and it frequently produces a vendor maintenance discount that closes much of the gap. This is the same principle that drives the discount stacking tactics used across renewals, and it should sit in your procurement negotiation checklist.
Managing the transition
If you proceed, plan the cutover carefully. Document your current version and customizations, confirm the provider scope in writing, and preserve access to any patches you are entitled to before maintenance lapses. Watch the contract for audit exposure, because leaving vendor maintenance sometimes prompts a compliance review, which makes the audit scope limitation guide relevant to the move.
Security and patching without the vendor
The question buyers worry about most is security. Without vendor patches, how is the system kept safe? Third-party providers answer this with virtual patching and compensating controls, applying protections at the network and configuration layer rather than waiting for a vendor code fix. For a stable, well-segmented estate this can be adequate and sometimes faster than the vendor cycle, but it is a genuinely different model that your security team must assess on its own terms, not accept on a sales claim.
The assessment should be concrete. Map which vulnerabilities the provider commits to address, the response time, and how regulatory and compliance requirements that depend on vendor-issued fixes will be met. Where a control framework or auditor expects vendor patches specifically, third-party support may not satisfy it, and that constraint can decide the question regardless of the saving. This is the kind of risk the audit scope limitation guide also touches, because changing your support posture can change your exposure.
For internet-facing or rapidly changing systems, the loss of source patches weighs heavier, while for a closed, stable back-office system it weighs less. The right answer depends on the specific workload, which is why the per-product approach matters as much for security as it does for cost.
Assess security per workload: The security case for third-party support is strong for stable, segmented back-office systems and weak for internet-facing or fast-changing ones, so buyers who judge it workload by workload avoid both the blanket no and the reckless yes.
Oracle and SAP specifics
The decision plays out differently across the two largest estates. For Oracle, third-party support most often covers Database, E-Business Suite, and other mature applications where the version is stable and the customizations are heavy. The saving is large, but Oracle is aggressive about protecting maintenance revenue, so expect a firm response and the possibility of a renewed focus on compliance. Know your effective license position cold before you move, because a clean position removes the vendor most effective counter.
For SAP, the calculus is shaped by the 2027 maintenance and migration roadmap. A business committed to a near-term move to the newer platform gains little from third-party support and may lose access to migration tooling, while a business choosing to stay on its current release for several more years is exactly the case where the saving is real. Map the support decision to the migration decision, because the two are inseparable for SAP customers, and consider whether a hybrid licensing strategy that moves some modules while keeping others on vendor support fits better than an all-or-nothing switch.
In both estates, the cleanest play is often to use a documented third-party quote to negotiate the vendor maintenance renewal down rather than to switch at all, the same bargaining approach the discount stacking tactics guide applies across deals. Whether you switch or stay, run the decision against your procurement negotiation checklist so nothing is missed.
A five-year cost comparison
The saving is easiest to judge over the full support horizon rather than a single year. Consider a mature Oracle estate paying 2 million dollars a year in vendor maintenance. The table sketches the indicative five-year cost of staying versus moving, before any re-entry considerations.
| Approach | Annual cost | 5-year cost | Notes |
|---|---|---|---|
| Vendor maintenance | 2.0M dollars | 10.0M dollars | Includes new releases and patches |
| Third-party support | 1.0M dollars | 5.0M dollars | No new releases, provider patching |
| Hybrid, half the estate | 1.5M dollars | 7.5M dollars | Move only the stable products |
The headline five-year saving of roughly 5 million dollars on a full switch is real, but it is gross, not net. Subtract the value of any upgrades you forgo, the cost of the security assessment, and any eventual re-entry fee if you return to the vendor. For many buyers the hybrid line is the sweet spot, capturing much of the saving while keeping upgrade-bound products current, which is why the per-product approach and a hybrid licensing strategy so often win over an all-or-nothing decision.
Common myths about third-party support
Two myths distort the decision in opposite directions. The vendor side often implies that leaving maintenance is reckless and that the system will be unsupported and exposed, which overstates the risk for a stable, segmented estate that is professionally patched by the provider. The third-party side sometimes implies the saving is free, which understates the cost of forgone upgrades and the eventual re-entry fee. Neither framing is accurate, and a buyer who accepts either one decides on a sales narrative rather than on the facts of their own estate.
A third myth is that the choice is permanent. It is not. Many buyers move to third-party support for a defined period, capture the saving while a system is stable, and return to the vendor when a genuine upgrade need arrives, accepting the re-entry cost as the price of the saving already banked. Framed that way, third-party support is a timing decision as much as a cost decision, and it belongs in the same multi-year view as your renewal runway. The right move is to revisit the decision at each renewal rather than to treat the first choice as final.
The buyer verdict
Third-party support is a strong choice for a stable, mature estate and a poor one for a product on an active upgrade or migration path. Treat it as a per-product decision and as a negotiation lever in every case. When the estate is large or the migration picture is mixed, our software licensing advisory team will model the saving against the lost upgrades product by product and structure the transition or the negotiating play, with SaaS license optimization tracking the support spend either way. The goal is a decision made on your numbers and your roadmap, not on the loudest sales narrative. Decide product by product, revisit the call at each renewal as the estate and migration picture change, and use the credible third-party quote as a lever even in the years you choose to stay. Handled that way, third-party support is one more tool a prepared buyer can reach for, not a leap of faith.