Migrate, hybrid, or stay on SAP: decide RISE on the FUE math and the five year cost, not the brochure. The 2027 deadline is your leverage, not SAP's.
SAP mainstream maintenance for ECC ends on 31 December 2027, with extended support to 2030 at a 2 point uplift. In a representative 8,000 user estate, an uncorrected FUE classification turns a 1,900 FUE need into a 3,350 FUE bill, roughly 4.35 million US dollars of avoidable annual cost.
Prepared by Redress Compliance · June 2026 · Representative SAP estate scenario (benchmark scenario, not a quote).
Executive summary
RISE with SAP is not a product. It is a contractual repackaging of S/4HANA, infrastructure, and base managed services into one subscription priced on a single metric, the Full Use Equivalent, or FUE. The decision is not cloud versus on premise. It is which paper you sign and at what count.
The metric is where the money moves. SAP maps your users into Advanced, Core, and Self Service bands that convert to FUE at 1 to 1, 5 to 1, and 30 to 1. The opening classification is generous to SAP. Correcting it to real usage is the single largest lever on the bill.
In the representative 8,000 user estate modeled here, SAP's opening classification lands at 3,350 FUE. Reclassification to recorded usage takes it to 1,900 FUE, a 43 percent reduction worth about 4.35 million US dollars a year at benchmark FUE list.
On a five year horizon, RISE and a brownfield on premise S/4HANA path land within 0.3 percent of each other in this model, roughly 29.5 million versus 29.4 million US dollars. Cost is not the deciding factor. Flexibility, operating model, and exit terms are.
This paper gives you the FUE conversion math, the five year TCO read, the indirect and digital access reset, the hybrid pattern that wins most often, the flexibility clauses that make RISE worth signing, and SAP's counter moves. The deadline that sets your leverage is 31 December 2027. Start the decision 18 months before, not after the renewal letter.
What are you actually buying when you sign RISE with SAP?
You are buying a bundle and a metric, not a product. RISE with SAP wraps S/4HANA Cloud Private Edition, hyperscaler infrastructure, the HANA database, and a base layer of SAP managed services into one subscription.
In 2025 SAP began retiring the tiered RISE Base, Premium, and Premium Plus labels in favor of SAP Cloud ERP, private edition packaging, but the commercial shape is unchanged.
The single metric is the FUE. Every user is mapped to a band, each band converts to FUE at a fixed ratio, and the FUE total times the negotiated rate sets the subscription. There is a published minimum: the smallest commitment starts at 60 FUE. Below that, RISE is not offered.
Three mechanics inside the bundle are easy to miss and expensive to ignore.
| Bundle mechanic | How it behaves | Why it matters to the buyer |
|---|---|---|
| Committed FUE floor | The contracted FUE count is a floor for the term. You can add above it, but you cannot drop below it without a true down clause. | Sign the floor at corrected usage, never at the opening proposal. |
| Infrastructure pass through | SAP procures the hyperscaler capacity and resells it inside the FUE rate. The markup is invisible and not separately itemized. | Benchmark the all in FUE rate against on premise hosting you price yourself. |
| Anniversary order window | Added FUE prices at the original discount band only if ordered by the contract anniversary. After it, new FUE prices at then current rates. | Forecast growth and pre order at the locked band, or lose the discount. |
How does the 2027 ECC deadline change your negotiating leverage?
The 2027 date is leverage you hold, not pressure SAP holds over you, if you read it correctly. SAP mainstream maintenance for ECC 6.0 enhancement packages 6 to 8 ends on 31 December 2027. That is a real date, and SAP has repeatedly confirmed it will not move.
What softens it is the runway behind it. Extended maintenance runs to 31 December 2030 at a 2 percentage point uplift on the support rate, roughly a 9 percent increase in the annual fee. After 2030, customer specific maintenance and credible third party support options remain.
So the buyer who has a funded plan to 2030 is not cornered in 2027. That runway is the BATNA that lets you negotiate RISE on terms rather than under a clock SAP sets.
Non obvious mechanic. SAP times its sharpest RISE incentives to its own quarter and year end, and frames the 2027 date as if it were your signing deadline. It is not. Your signing deadline is your migration readiness date. Decouple the two and the urgency moves back to SAP's side of the table.
ECC maintenance cost index. Mainstream to 31 December 2027, extended to 2030 at a 2 point uplift, customer specific after. Indicative, not a quote.
Where does FUE conversion inflate your user count?
FUE inflation hides in the band mapping, not in the headcount. The same person can be classified Advanced, Core, or Self Service, and the three convert at very different ratios. SAP's opening proposal tends to map too many users to Advanced, which converts 1 to 1 and carries the full rate.
The correction is a usage based reclassification. You measure what each user actually does, map operational and read only users to Core and Self Service, and reserve Advanced for genuine full scope finance and configuration roles. The table shows the swing in the representative estate.
| User band | FUE weighting | Opening users | Opening FUE | Corrected users | Corrected FUE |
|---|---|---|---|---|---|
| Advanced | 1 : 1 | 2,500 | 2,500 | 1,000 | 1,000 |
| Core | 5 : 1 | 4,000 | 800 | 4,000 | 800 |
| Self Service | 30 : 1 | 1,500 | 50 | 3,000 | 100 |
| Total | 8,000 | 3,350 | 8,000 | 1,900 |
FUE by band, opening classification versus usage corrected. Numbers match the table above. Benchmark scenario, not a quote.
Two FUE mechanics are worth naming. First, the band mix is contractual, so once you sign Advanced heavy, SAP measures against that baseline at renewal. Second, conversion credit from your existing ECC licenses is applied as a discount on the RISE subscription, not as cash, and it expires if unused.
How does RISE reset your indirect and digital access exposure?
RISE signing is the moment to reset indirect access, because the contract is reopened anyway. Indirect or digital access is licensed by counting nine document types created by non SAP systems, each weighted, with most lines counting at 0.2 per document. Left unmanaged, it is the most common audit surprise.
At a RISE transition you have three live options on indirect access. Each carries a different cost and risk profile.
- Convert to digital access: license the measured documents, often via the Digital Access Adoption Program discount, and retire the legacy named user proxy.
- Cap and carve out: negotiate a documented ceiling on counted document types and exclude system to system traffic that should not count.
- Baseline and defer: measure now, fix the entitlement, and time the conversion to the RISE order rather than under a later audit.
The mechanic to exploit is timing. SAP discounts digital access most aggressively when it is bundled into a RISE order it wants to close, far less so when it is raised in an audit. Reset it inside the deal, not after.
Is RISE actually cheaper than on premise S/4HANA over five years?
In this model, no, and that is the point. RISE converts capital cost to operating cost and offloads infrastructure and basic operations, but the five year totals land within a rounding error of each other. The brochure savings claim does not survive a full TCO build.
The table compares a brownfield on premise S/4HANA conversion against RISE for the representative estate over five years. Both carry the same system integration migration cost, because the project work is the same regardless of where it runs.
| Five year cost line | On premise S/4HANA | RISE with SAP |
|---|---|---|
| License or FUE subscription | $4.00M | $20.00M |
| Maintenance, or premium add ons | $4.40M | $2.50M |
| Infrastructure and operations | $15.00M | included |
| Migration project (SI) | $6.00M | $6.00M |
| Exit and egress reserve | included | $1.00M |
| Five year total | $29.40M | $29.50M |
Five year TCO, on premise S/4HANA versus RISE. Totals match the table above. Benchmark scenario, not a quote.
Where the common advice on RISE with SAP is wrong
The standard SAP and partner pitch is that RISE is the obvious, cheaper, lower risk path and that staying on premise is a dead end. We disagree. In the RISE evaluations we ran in 2024 to 2025, the five year totals came out at or near parity once infrastructure, operations, and exit reserves were priced honestly.
The cost case rarely decides it. The buyer side move is to stop arguing price and negotiate the operating model and the exit terms instead. That is where RISE is genuinely better or genuinely worse, and where SAP has the least scripted response.
FUE reduction
Range of FUE removed by reclassifying users off the opening Advanced heavy proposal across the RISE estates we benchmarked.
Recovery on the quote
Range recovered against the opening RISE subscription quote once the FUE baseline was clean and the BATNA was credible.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025.
Why is a hybrid path the most common best outcome?
Hybrid wins most often because few estates are uniformly ready for RISE. The core finance and supply chain that is process stable and integration heavy moves to RISE cleanly. The plants, custom builds, and acquisitions mid integration are cheaper and safer left on premise or on a separate timeline.
A hybrid also preserves leverage. When SAP knows the whole estate must move on one order, the BATNA is weak. When part of the estate can stay or move later, every line item stays contestable. The phased calendar below maps the decision against the 2027 date.
Baseline and model
Build the verified FUE count, model RISE against on premise across five years, and segment the estate into move now, move later, and stay.
Position the three paths
Put RISE, on premise, and hybrid on the table together, with the 2030 extended maintenance runway as the BATNA, and price each path standalone.
Close and lock terms
Settle on the corrected FUE floor and lock the flexibility clauses, with a signed side letter where the order cannot carry them.
Which contractual flexibility provisions make RISE worth signing?
RISE is worth signing only when the clauses make it reversible and re sizable. The subscription form removes the perpetual license you used to own, so the protection has to come from the terms. Five clauses do most of the work.
| Clause | What it secures | Buyer protection |
|---|---|---|
| Annual FUE reclassification | Re measure the band mix to actual usage each year and reset the count. | Stops the opening classification becoming a permanent baseline. |
| FUE true down at anniversary | Reduce the committed FUE floor at the anniversary, not only increase it. | Matches the bill to a shrinking or restructured estate. |
| Renewal uplift cap | Cap the renewal increase at a fixed percentage or a published index. | Removes the renewal shock that follows the first discounted term. |
| Exit and data egress | Guaranteed data export, transition assistance, and no egress penalty on exit. | Breaks the lock in that the subscription model otherwise creates. |
| Conversion credit and dual run | ECC license credit applied to the subscription, plus a parallel run window. | De risks cutover and stops the credit expiring unused. |
What are SAP's counter moves and how do you handle them?
SAP's counter moves are predictable, which makes them manageable. Each one has a clean buyer response that you prepare before the first meeting, not during it. The table pairs the move with the counter.
| SAP move | What it sounds like | Buyer counter |
|---|---|---|
| 2027 urgency | You have to move now or lose support. | Extended maintenance to 2030 plus third party support is the funded runway. Decline the clock. |
| FUE generosity | We will classify the users for you. | Insist on a usage based reclassification and the annual reclassification clause. |
| Bundle pull | Deeper discount if you add BTP and SuccessFactors. | Price every line standalone, then decide. A bundle discount on software you do not need is not a saving. |
| Anniversary deadline | This price expires at our quarter end. | Align the order to your fiscal calendar and your readiness date, not SAP's quarter. |
| Single path framing | It is RISE or nothing. | Present hybrid and on premise as live BATNAs and keep all three on the table to signature. |
The side letter is where these counters become binding. When the standard RISE order cannot carry the reclassification right, the true down, or the uplift cap, put them in a signed side letter referenced by the order. A verbal assurance from an account team does not survive a personnel change.
Recommendation. Decide RISE on the FUE math and the five year cost, not the brochure. Correct the classification to real usage before you sign, and hold the 2027 date as your leverage rather than SAP's. Keep hybrid and on premise live to signature, then lock the five flexibility clauses.
- Before you choose a path: build the verified FUE count and the honest five year TCO across RISE, on premise, and hybrid, so the decision rests on flexibility and operating model, not a savings claim.
- Before signature: lock the annual reclassification, FUE true down, renewal uplift cap, exit and egress, and conversion credit clauses, in the order or a signed side letter.
We are glad to tie a meaningful part of the fee to delivered value.
