RISE and GROW with SAP: The 2026 Buyer's Guide.

RISE with SAP and GROW with SAP are SAP's two cloud ERP commercial bundles, and the choice between them is the defining SAP buyer question of 2026. RISE is the private-cloud route — S/4HANA Cloud Private Edition for existing customers carrying configured ECC estates and custom code. GROW is the public-cloud route — S/4HANA Cloud Public Edition for net-new or greenfield adopters who can run standardised processes. Both are subscriptions priced in Full User Equivalents (FUE), not perpetual named users plus 22% maintenance, and both bundle software, infrastructure and support into a single opaque number. This guide breaks down what each includes, how FUE pricing actually works, and where the negotiable value sits before you sign.

What is the difference between RISE with SAP and GROW with SAP?

RISE and GROW are both subscription routes to S/4HANA in the cloud, but they target opposite ends of the customer base. RISE with SAP is built on S/4HANA Cloud Private Edition and is engineered for organisations migrating an existing, heavily configured SAP estate — it preserves custom code (the ABAP layer), supports a brownfield or selective-data-transition migration, and carries conversion credits for retired ECC licences. GROW with SAP is built on S/4HANA Cloud Public Edition and is engineered for net-new adopters and greenfield deployments who can adopt SAP's standardised, best-practice process scope in exchange for a faster, lower-entry, fully-managed multi-tenant service. For a deeper walk through the two cloud tiers, see our breakdown of RISE with SAP and the standalone GROW with SAP guide.

Indicative comparison from buyer-side SAP engagements. Package scope and entry points vary by region and SAP commercial cycle.

The practical decision rule we apply with clients: if your differentiation lives in customised SAP processes and you have material custom code, RISE is the realistic path; if you are replacing a legacy non-SAP system or standing up a new entity, GROW is usually faster and cheaper to enter. The grey zone — a mid-size ECC customer willing to re-engineer toward standard — is where the two-speed strategy and the hardest negotiation live. We unpack that decision in full in our RISE vs GROW vs on-prem comparison.

How is RISE and GROW priced — what is an FUE?

Both bundles are priced in Full User Equivalents (FUE), the consumption metric that replaced perpetual named users in SAP's cloud model. Every user authorisation is mapped to one of three categories — Advanced Use, Core Use or Self-Service Use — and each category converts to FUEs at a fixed ratio. You buy a pool of FUEs, so the category mix you negotiate, not your raw headcount, determines the bill. The conversion ratios below are the public-cloud benchmark; the full mechanics are covered in our SAP FUE explained guide.

Public-cloud (GROW) FUE conversion ratios. Private-edition (RISE) mappings follow the same three-tier logic with deal-specific adjustments.

The trap is the same one that plagues the perpetual named-user model: over-classification. In our 340+ engagements we routinely find estates where 30–45% of users are mapped to Advanced Use when their actual transaction profile is Core or Self-Service. Because an Advanced user costs five times a Core user and thirty times a Self-Service user in FUE terms, mis-mapping a few hundred users can inflate the subscription by seven figures over a typical five-year term. The category mapping is the FUE equivalent of named-user reclassification — and it is fully negotiable at signature.

On absolute price, FUEs are sold against published package scopes (for GROW, a Base and a Premium package). Indicative benchmarks we see place public-cloud FUE list pricing in the low-to-mid hundreds of dollars per FUE per month before discount, with private-edition RISE priced as a blended subscription that folds in infrastructure and managed services. Treat any single per-FUE figure with suspicion — the bundle composition, not the unit rate, is where SAP holds margin.

What does the RISE with SAP bundle actually include?

RISE is sold as a single subscription, but it is really four commercial layers stacked into one line item. Understanding the layers is the prerequisite to benchmarking them, because SAP does not price them separately on the order form. The table below shows the standard composition.

The four layers of a RISE subscription. None are separately priced on the SAP order form — which is precisely why they need separate benchmarks.

The bundling is the commercial risk. Because the hyperscaler and managed-service layers are wrapped inside the per-FUE number, a buyer cannot tell whether the infrastructure markup is 15% or 60% over a direct cloud commitment. Our approach is to model each layer against an external reference — a direct hyperscaler enterprise discount, a third-party managed-services quote, and standalone support — and then ask SAP to defend the spread. The bundle frequently survives that test for mid-size estates; for large, infrastructure-heavy estates it often does not.

When should you choose GROW, RISE, or stay on-prem?

The right answer depends on three variables: how customised your processes are, whether you are migrating an estate or starting fresh, and how much leverage your ECC maintenance stream still gives you. The decision matrix below reflects how we steer clients, and it deliberately keeps on-premise (or third-party-supported ECC) on the table — because the credible alternative is what makes a RISE or GROW negotiation work.

Decision matrix from buyer-side engagements. The on-prem rows exist because the alternative is leverage, not because we discourage the cloud.

Note the timing dimension. SAP mainstream maintenance for ECC 6.0 runs to the end of 2027, with extended maintenance available at a premium to 2030. That deadline is real leverage — but it is leverage SAP also uses against you, framing the cloud move as urgent. Buyers who treat the 2027 date as a negotiation clock rather than a panic trigger consistently sign better terms. Our S/4HANA migration 2027 guide covers the runway in detail.

How do ECC conversion credits work in a RISE move?

When an existing perpetual customer moves to RISE, SAP applies a conversion credit — a value attributed to the retired on-premise licences — against the new subscription. The credit reduces the effective subscription cost, but two things determine whether you capture its full value: the baseline used (your licensed entitlement versus your actual deployment) and how the credit is amortised across the subscription term. Account teams routinely set the baseline against your full licensed estate, which sounds generous but quietly rolls shelfware into the subscription you then pay for indefinitely.

The single largest lever in a RISE deal is therefore baseline hygiene before conversion: reclassify over-licensed users, retire genuine shelfware, and quantify indirect/digital access exposure so it is priced correctly rather than discovered later. Get the baseline right and the conversion credit works for you; get it wrong and you subscribe to your own historical over-buying. This is the same discipline that drives our SAP cost benchmarks — see SAP license cost in 2026 for the underlying per-user numbers.

What are the biggest negotiation traps in a RISE or GROW deal?

RISE and GROW contracts share a recurring set of pressure points. The five below account for most of the value we recover on these deals, and each is negotiable at signature even though the standard paper presents them as fixed.

• FUE over-classification — users mapped to Advanced Use when Core or Self-Service fits; the fastest cost lever on the subscription line.
• Shelfware in the conversion baseline — retired-licence credit calculated on entitlement rather than deployment, rolling dead spend into the subscription.
• Uncapped renewal uplift — subscriptions default to open-ended price escalators; cap year-over-year increases at signature.
• No downscale rights — RISE/GROW proposals assume only growth; negotiate a documented right to reduce FUEs at renewal.
• Indirect / digital access drift — third-party systems creating SAP documents can surface as a separate charge; quantify and cap exposure before SAP raises it.

Across our SAP practice, the buyers who pay closest to list treat the RISE proposal as a procurement formality; those who treat it as a benchmarked negotiation — with a credible on-prem or third-party-support alternative documented — consistently land materially lower. For the audit-side exposure that often runs in parallel, see our SAP audit defence work, and for the broader commercial sequence, contract negotiation.

Frequently asked questions.

Related reading.

← Back to all insights