SAP third-party support is independent maintenance from a non-SAP provider — most commonly Rimini Street or Spinnaker Support — priced at roughly half of SAP's annual maintenance fee. For a stable ECC estate it can cut support cost 50% or more; the trade is that you stop receiving new SAP releases and enhancement packs while you are on it. Even if you never switch, a credible third-party quote is the single most effective lever for resetting an SAP support renewal.
Third-party support is enterprise maintenance for SAP software delivered by an independent firm rather than by SAP itself. The two largest providers, Rimini Street and Spinnaker Support, price at approximately 50% of SAP's annual maintenance fee, and customers report total savings of 50–90% once avoided forced upgrades and self-managed costs are factored in. Their model is a fixed service envelope, not a percentage of license value, so the bill does not inflate as your estate grows, and it typically includes support for custom code, interfaces, and tax/legal/regulatory updates that SAP scopes separately.
The core trade-off: while on third-party support you keep your existing, perpetually licensed SAP software and get full break/fix and regulatory support — but you lose access to new SAP releases, enhancement packs, and patches. For a frozen ECC estate that is often a non-issue; mid-migration it is disqualifying.
This is a sub-guide in our SAP support strategy pillar. It pairs with SAP support fee negotiation and the 2027 maintenance deadline, and sits under our SAP vendor practice and SAP audit defence service.
On a five-year horizon the gap compounds, because SAP's fee is a percentage of license value that rises with index-linked uplifts while a third-party envelope is fixed. Take an estate with $40M of net license value: SAP Enterprise Support at 22% is $8.8M a year before uplifts; a third-party provider at roughly half is around $4.4M, flat. Over five years, even before SAP's annual increases, the difference is well over $20M.
| Line | SAP Enterprise Support | Third-party support | Five-year delta |
|---|---|---|---|
| Annual fee ($40M license base) | $8.8M (22%) | ~$4.4M | — |
| Annual uplift | Index-linked, compounding | Flat / capped | Widens gap |
| Five-year cost (no uplift) | $44M | ~$22M | ~$22M saved |
| New releases / patches | Included | Not available | Roadmap cost |
Send us your support line and license base; we return a side-by-side five-year model — typically inside two weeks.
Both deliver the core value — roughly half SAP's fee, fixed envelope, custom-code and regulatory support — but they differ in posture. Rimini Street is the largest and most litigation-tested provider, with the deepest bench and a global footprint; Spinnaker Support offers SAP and Oracle support plus managed services and is often positioned as the more consultative, hybrid option. The right choice depends on estate size, geographic spread, and whether you also want managed-services scope alongside break/fix.
| Dimension | Rimini Street | Spinnaker Support |
|---|---|---|
| Typical pricing vs SAP | ~50% | ~50% |
| Scope | Break/fix, custom code, tax/legal | Break/fix + managed services option |
| Footprint | Global, largest provider | Global, hybrid/consultative |
| Best fit | Large, stable estates | Mid-market, managed-services need |
"The quote you never intend to accept is still the most valuable document in the renewal. SAP's deal desk reprices the moment a credible alternative is in the room."
The full benchmark percentages, the third-party savings math, the rebasing model, and the 2027 deadline timeline — in one research paper.
Three things, and they must be priced honestly rather than dismissed. First, new SAP innovation — releases, enhancement packs, and feature patches stop while you are on third-party support. Second, the direct SAP support relationship and its escalation path, replaced by the provider's. Third, the simplicity of being able to switch back: returning to SAP support generally requires paying back-maintenance for the lapsed period, so the move is not frictionless to reverse. None of these is fatal for a stable estate, but each is a real cost that belongs in the model.
The decision therefore hinges on your roadmap. If you intend to stay on ECC through and beyond 2027 with no near-term S/4HANA plan, the lost innovation has little value and the saving is close to pure. If you are actively converting, the lost releases are the whole point and third-party support is the wrong tool — though the quote still has negotiating value. See the destination logic in the 2027 deadline guide and the broader ECC end-of-life options.
| What you give up | Matters if… | Doesn't matter if… |
|---|---|---|
| New releases / enhancement packs | Active S/4HANA roadmap | Frozen ECC estate |
| Direct SAP escalation | Mission-critical SAP-only path | Provider SLA is sufficient |
| Frictionless switch-back | Likely to return within 1–2 yrs | Long-term decision made |
Most of our SAP support engagements use third-party support as a negotiating instrument rather than a destination. The play is to run a genuine evaluation — a real RFP to Rimini and Spinnaker producing a costed, deliverable quote — and bring that number into the SAP renewal. Because SAP's deal desk knows the alternative is executable, the support fee, the uplift cap, and even the license-base rebasing all become negotiable in a way they never are when the renewal is uncontested. The credibility of the quote is everything: a hypothetical does nothing, a signed-ready proposal moves eight figures.
The full negotiation sequence — when to run the RFP, how to time it against the renewal, and how to combine it with rebasing — is in SAP support fee negotiation and our SAP renewal negotiation guide. The principle: never renew SAP support without a live alternative on the table.
$1.8B+ in documented client savings across 340+ engagements. Buyer-side only since 2016. Gartner recognised.
Weekly compliance intelligence for IT leaders.