SAP support is the largest recurring line item most SAP customers never renegotiate: Enterprise Support bills at 22% of net license value every year, applied to a license base set years ago, regardless of what you actually still run. In our 340+ engagements the firms that treat support as fixed overhead pay it forever; the firms that treat it as negotiable cut 20–40% by rebasing the license value, capping uplifts, and putting a credible third-party support quote on the table. With ECC mainstream maintenance ending 31 December 2027, that conversation is now time-boxed. This pillar maps the levers, the benchmark percentages, and the sequence that works.
You cut SAP support cost by attacking the four things SAP prefers you treat as fixed. The percentage — 22% for Enterprise Support, 19% for Standard — is mostly policy, but the base it applies to is not: retiring shelfware licenses before a renewal rebases them lowers the fee permanently. The annual uplift, tied to a price index, is contractually cappable. The 2027 ECC maintenance deadline is being used as leverage to push you onto RISE, but it is also your leverage, because a credible third-party support route (Rimini Street, Spinnaker Support) prices at roughly half of SAP's fee and resets the entire negotiation. Worked together, the combined reduction across our SAP support engagements runs 20–40% of annual support spend — and it holds, because it is structural rather than a one-time discount.
The practitioner rule: rebase the license value first, then cap the uplift, then time the renewal to the 2027 deadline with a third-party quote in hand. Negotiate the percentage in isolation and SAP will not move; change what the percentage is applied to and the whole number drops.
This guide is the pillar for our SAP support-strategy cluster. It links down to three deep-dive sub-guides — SAP third-party support, SAP support fee negotiation, and the 2027 maintenance deadline — and sits alongside our SAP vendor practice and SAP audit defence service. Start here, then go deep where your spend hurts most.
SAP sells two mainstream support tiers. Enterprise Support, the default for most ERP customers, is 22% of net license value per year; Standard Support, where still available, is 19%. The fee is not metered to incidents or usage — it is a flat percentage of the contractual license value, so a customer who has decommissioned half their licensed users still pays support on the full historical base. That decoupling is the entire reason support is the most over-paid SAP line item. The table below shows how the tiers compare and where each bites.
| Support tier | Annual fee | Basis | What it covers | Reducible by |
|---|---|---|---|---|
| SAP Standard Support | 19% | % of net license value | Core fixes, patches, online tools | Rebasing + uplift cap |
| SAP Enterprise Support | 22% | % of net license value | Standard + mission-critical SLAs, advisory | Rebasing + uplift cap + tier review |
| ECC extended maintenance (2028–2030) | 24% | 22% + 2pt uplift | Enterprise Support, no new innovation | Third-party support route |
| Third-party support | ~11% | ~50% of SAP fee | Break/fix, tax/legal, custom code | n/a — already the floor |
The pattern that matters: the headline percentage is the least movable thing in the table, and the license base it is applied to is the most movable. Most enterprises argue about the 22% and never touch the base — which is exactly backwards. We unpack the mechanics in how SAP support fees work.
The support base you carry into that event is the base you pay on for years. We model the rebased number with you before it locks.
Mainstream maintenance for SAP ECC 6.0 and Business Suite 7 ends on 31 December 2027. SAP offers extended maintenance through the end of 2030 at a 2-percentage-point uplift — 24% instead of 22% — and after that, only customer-specific maintenance, which is more expensive and narrower in scope. SAP presents this as a forcing function for S/4HANA and RISE adoption. It is. But it is also the single largest leverage event in the SAP relationship for the next four years, because every customer who has not yet committed to a destination is, by definition, a contestable account.
The reason the deadline matters for cost rather than just compliance is timing. A customer who renews support for another three-year cycle in 2026 without a deadline strategy locks in the 22% on an un-rebased license base, then faces the extended-maintenance uplift on top. A customer who sequences the deadline — rebasing first, then deciding between RISE, S/4HANA on-premises, and staying on ECC with third-party support — negotiates from leverage rather than under it. The full timeline and the destination decision tree are in the 2027 deadline deep-dive and our analysis of SAP ECC end-of-life options.
| Milestone | Date | What changes | Cost impact |
|---|---|---|---|
| Mainstream maintenance ends | 31 Dec 2027 | ECC 6.0 / Business Suite 7 leave standard support | Decision forced |
| Extended maintenance | 2028–2030 | Support continues, no new innovation | +2pt (24%) |
| Customer-specific maintenance | 2031+ | Narrowed scope, bespoke pricing | Higher, less value |
| Third-party support | Any time | Independent provider, frozen release | ~50% lower |
"SAP set the 2027 date to create urgency for RISE. Used correctly, the same date is the strongest negotiating position you will have this decade."
Yes, materially. Independent third-party support providers — Rimini Street and Spinnaker Support being the largest — price at roughly 50% of SAP's annual maintenance fee, and once avoided forced-upgrade and self-service costs are included, customers report total savings of 50–90%. Their model is a fixed service envelope rather than a percentage of license value, so it does not inflate as your estate grows, and it typically includes support for custom code and tax/legal/regulatory updates that SAP scopes separately.
The catch is real and must be priced honestly: while on third-party support you lose access to new SAP releases, enhancement packs, and patches. For a stable ECC estate with no near-term innovation roadmap, that is often a non-issue for years; for a customer mid-S/4HANA, it is disqualifying. The decision is rarely "switch forever" — it is "use the switchability as leverage, and switch if SAP will not meet a benchmarked number." We model both the standalone economics and the negotiation use in the third-party support deep-dive.
| Dimension | SAP Enterprise Support | Third-party support |
|---|---|---|
| Annual cost | 22% of license value | ~50% lower |
| Pricing basis | % of license value (rises) | Fixed service envelope |
| New releases & enhancement packs | Included | Not available |
| Custom-code support | Out of scope | Included |
| Tax / legal / regulatory updates | Standard scope | Included |
| Best fit | Active S/4HANA roadmap | Stable ECC, deferred migration |
The full benchmark percentages, the rebasing model, the third-party savings math, and the 2027 deadline timeline — in one research paper.
By changing the inputs SAP applies the percentage to, and by capping the things SAP would otherwise escalate automatically. Four levers do almost all the work. First, rebase: identify and retire shelfware licenses before the renewal, so the percentage applies to a smaller base. Second, cap the annual support uplift — SAP's standard contracts allow index-linked increases that compound, and a negotiated cap (or a freeze) is worth more over a five-year horizon than most one-time discounts. Third, freeze the support fee through an S/4HANA conversion so the migration does not become a repricing event. Fourth, hold a credible third-party quote so the renewal is competitive rather than a rubber stamp.
The reason these compound is that each addresses a different mechanism. Rebasing lowers the principal; the cap lowers the growth rate; the conversion freeze removes a step-up; the third-party quote supplies the market alternative SAP's deal desk responds to. The negotiation scripts and the rebasing checklist are in the support fee negotiation deep-dive, and the broader renewal play in SAP renewal negotiation.
| Lever | What it changes | Typical impact | Best timed |
|---|---|---|---|
| License rebasing | The base the % applies to | 10–25% of support | Before renewal |
| Uplift cap / freeze | Annual increase rate | 3–8% per year compounding | At renewal |
| S/4HANA support freeze | Removes conversion step-up | Avoids 10–20% jump | At conversion |
| Third-party quote leverage | Supplies market alternative | 5–15% of support | Before 2027 |
We start with a free support-spend triage — your support contract in, a rebased reduction model out, typically inside two weeks.
No — it relocates it. RISE with SAP folds support into the per-FUE subscription, so the visible 22% line disappears from the invoice, but the equivalent cost is recovered inside the subscription price. Treating RISE as the end of maintenance cost is one of the most expensive misreadings we see, because it removes the line item buyers know how to challenge and replaces it with a bundled price that is harder to decompose. RISE should be evaluated as a repricing of support — and benchmarked against the alternative of staying on-premises with third-party support — not as its elimination.
The honest comparison puts three destinations side by side over a five-year horizon: RISE (support embedded), S/4HANA on-premises (22% continues on the converted base), and ECC on third-party support (≈50% lower, no new innovation). The right answer depends on your innovation roadmap, not on which line item is most visible. We unpack the RISE economics in RISE with SAP explained and the conversion mechanics in S/4HANA migration before 2027.
| Destination | Support cost | New innovation | Leverage profile |
|---|---|---|---|
| RISE with SAP | Embedded in subscription | Included | Lowest after signing |
| S/4HANA on-premises | 22% on converted base | Included | Moderate |
| ECC + third-party support | ~50% lower | Frozen | Highest |
Twelve to eighteen months before the support renewal or the 2027 deadline, whichever is sooner. The reason is mechanical: rebasing requires a usage audit and a shelfware retirement that SAP must accept before the renewal locks the base, and that process takes months. A rebasing completed two months before signing barely registers; the same work completed twelve months out reshapes the entire renewal. The firms that start late renew on an inflated base and then discover the extended-maintenance uplift on top. The firms that start early walk in with a rebased number, a capped uplift, and a third-party quote — negotiating against a market price they control.
For SAP estates above roughly $5M in annual support spend, independent buyer-side advisory across the support base, the uplift, and the deadline strategy typically captures reduction equal to several times the advisory fee — and the reduction recurs every year, because it is built into the contract rather than discounted once. Our SAP vendor practice sets out the full engagement model.
$1.8B+ in documented client savings across 340+ engagements. Buyer-side only since 2016. Gartner recognised.
Weekly compliance intelligence for IT leaders.