S/4HANA or RISE, three paths and three cost curves
Enterprises facing the end of ECC support are not choosing between modernization and the status quo: they are choosing among three paths with three full term cost curves, three sets of lock in, and three answers to who pays for the move and when. The SAP account team usually opens with two, and the third is the baseline that keeps the other two honest.
Prepared by Redress Compliance · August 7, 2026 · SAP advisory. Based on 60 to 80 S/4HANA and RISE decisions modeled 2024 to 2025.
Executive summary
The third path is the baseline.
Stay on ECC with extended maintenance, standard support ending at the close of 2027, extended running to 2030 at a two point premium, then customer specific maintenance beyond, is rarely the right end state and almost always the right baseline: without it.
Every RISE quote reads as a price taker negotiation.
It is the cheapest cash path through 2030. It is runway, not a future.
RISE priced 35 to 55 percent above on premise when modeled honestly. Both paths run the same S/4HANA code line; the difference is who operates the platform and how cost shapes across the term.
RISE opens around 12 to 18 percent above the on premise license equivalent in year one and compounds through the annual uplift and the add ons, and after the on premise operating team is honestly added back to the comparison, the full term bundle premium ran 35 to 55 percent across our panel.
Customization depth is the largest swing factor. Heavily modified estates, more than 1,500 user enhancements, faced a Clean Core remediation bill of 18 to 30 percent of the move budget on every path: the modification debt travels with the workload, whoever operates it.
The estates that skipped this line in the model found it again in the program.
Starting early bought the biggest discount.
Buyers who opened the path comparison 18 to 24 months before the ECC support deadline held the realized RISE uplift to 20 to 30 percent above on premise, against the 50 percent default for late starters, because time is what makes the alternative paths credible.
The lock in also deserves its own line: RISE's exit terms, data egress, and the conversion out of FUE are much harder to recover than perpetual on premise rights.
The three paths, and what each really is
| Path | What it is | The honest read |
|---|---|---|
| Stay on ECC to 2030 | Extended maintenance at a two point premium, customer specific beyond | Cheapest near term cash, no future past 2030: runway, and the negotiation baseline |
| S/4HANA on premise | The successor platform on infrastructure you own or lease, your team operating | The middle cost curve, narrow contract surface, control retained |
| RISE with SAP | Application, infrastructure, and basic managed service in one subscription | The widest contract surface, the most lock in, the largest full term bill in our deals |
| GROW with SAP | The public cloud edition for new and mid market estates | Usually not a fit for a large customized ECC estate: scoped out early |
The indexed five year picture. On an illustrative mid market estate with the 2026 ECC base at 100, staying on ECC lands near 122 by 2030, S/4HANA on premise near 140, and RISE near 176.
Stay stays cheapest until standard support runs out, and RISE carries the widest full term gap, which is exactly why the comparison must be full term and like for like: the RISE pitch against the cost of doing nothing is the wrong pair.
The five year math, where the bundle premium hides
RISE looks competitive on the opening slide because the bundle hides the parts the customer used to pay for separately: infrastructure, basis operations, and the managed layer.
The honest comparison adds the equivalent on premise team cost back to the RISE side, and after that adjustment the bundle premium is the actual delta, 35 to 55 percent on like for like scope across our panel, sometimes more.
The year one opening, 12 to 18 percent above the on premise license equivalent, compounds through the annual uplift, the AI add ons, and the services that migrate out of the base bundle as scope grows.
The full pricing decomposition continues in the RISE TCO reality report, and the RISE TCO calculator runs your own numbers in minutes.
The RISE and S/4HANA negotiation recommendations
The ten moves for the path decision: the ECC baseline construction, the FUE conversion, the Clean Core line, the lock in clauses, and the timing that holds the uplift to 20 to 30 percent.
Get the white paper →The swing factors, customization and lock in
Customization depth swings the model more than any pricing line: estates past roughly 1,500 enhancements paid 18 to 30 percent of the move budget in Clean Core remediation on every path, because the modification debt does not care who operates the platform.
Lock in swings the decade: on premise perpetual rights survive the relationship, while RISE's exit terms, data egress costs, and the conversion ratio out of FUE are contractual constructions that only exist if negotiated at signature, the delta running past 100 percent between the paths.
The 2027 deadline strategy works the calendar side, and the embedded features playbook covers the license boundary waiting inside S/4HANA whichever path wins.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across migration decisions, 2024 to 2025
Across roughly 60 to 80 S/4HANA and RISE decisions our team modeled between 2024 and 2025, the path finance approved was rarely the one the SAP account team pitched first:
Opening quotes above the on premise five year total once both carried the same scope.
The early start that held the realized uplift to 20 to 30 percent instead of the 50 percent default.
The numbers read as defensible bands rather than points because SAP estates vary widely, FUE counts, module mix, customization depth, infrastructure age, and a single decimal would imply precision the comparison cannot carry.
What holds across the file: the ECC baseline disciplines every quote, the operating team adjustment is where RISE pitches go to die, and the buyers who modeled all three paths early enough to mean it captured most of the difference regardless of which path they chose.
Your first five moves
- Model all three paths, full term, with the ECC extended maintenance baseline in the deck, because without it every quote is a price taker negotiation.
- Add the operating team back to the RISE side, the adjustment that turns the pitch into the comparison.
- Count the enhancements now: past roughly 1,500, the Clean Core line is 18 to 30 percent of the move budget on every path.
- Negotiate the lock in clauses at signature: exit terms, data egress, and the FUE conversion out, because they only exist if written.
- Start 18 to 24 months before the deadline, where the 20 to 30 percent uplift lives. The SAP practice models the paths with you.
Frequently asked questions
What are the SAP migration options in 2026?
Three real paths: stay on ECC with extended maintenance through 2030 at a two point premium, move to S/4HANA on premise on infrastructure you operate, or move to RISE with SAP, the bundled subscription SAP operates.
GROW with SAP, the public cloud edition, is usually scoped out early for large customized estates.
When does SAP ECC support actually end?
Standard support ends at the close of 2027, extended maintenance runs to the end of 2030 at a published two point premium on the support base, and customer specific maintenance is available beyond at a further premium with shrinking inclusions.
The platform keeps running; new legal change and selected support move out of scope.
Is RISE cheaper than S/4HANA on premise?
Not in our modeling: RISE opening quotes ran 35 to 55 percent above the on premise five year total once both carried the same scope, including adding the equivalent operating team cost back to the RISE side.
The bundle premium opens at 12 to 18 percent in year one and compounds through the uplift and add ons.
What does ECC customization cost in a migration?
Heavily customized estates, past roughly 1,500 user enhancements or modifications, faced Clean Core remediation of 18 to 30 percent of the move budget on every path.
The modification debt travels with the workload regardless of who operates the platform, which is why the enhancement count belongs in the model before any path is chosen.
How much lock in does RISE add?
Materially more than on premise: perpetual rights survive the relationship, while RISE's exit terms, data egress costs, and the conversion ratio out of FUE are contractual constructions that exist only if negotiated at signature.
The lock in delta between the paths ran past 100 percent, and it prices the second term, not the first.
When should the S/4HANA path decision start?
18 to 24 months before the ECC end of standard support: buyers who started there held the realized RISE uplift to 20 to 30 percent above on premise, against the 50 percent default for late starters. Time is what makes the alternative paths credible, and credibility is what moves SAP's number.
