Executive Clarity · Decision 3 of 8

RISE vs GROW

Not two products — two delivery models for the same S/4HANA core. Your legacy, not SAP's marketing, decides which one is yours.

The question

Which commercial and delivery package fits your S/4HANA move: RISE with SAP — the private-cloud edition bundled with managed infrastructure and migration support — or GROW with SAP — the public-cloud, multi-tenant edition built for fast, standardised deployments?

Decision factors

The documented facts

  • RISE is SAP's private-cloud offering: a dedicated environment that permits controlled ABAP custom code, custom transactions and brownfield conversion of existing ECC landscapes.
  • GROW is SAP's public-cloud edition: multi-tenant, clean-core by contract — no core modifications — implemented greenfield against SAP's best-practice processes.
  • Since 2025 SAP positions both under the "SAP Cloud ERP" umbrella: one HANA core, two delivery models. The deployment mechanics are those of SAP Public Cloud vs Private Cloud.
  • Industry analyses consistently report lower entry pricing and faster time-to-live for GROW's multi-tenant model, and a premium for RISE's dedicated environment. Exact deltas vary by deal — treat any single percentage as a negotiating anecdote, not a constant.

Inference

  • The real selector is your legacy: a landscape with hundreds of custom transactions that the business still depends on effectively rules out GROW — not because GROW is worse, but because its clean-core contract is incompatible with carrying that code.
  • A useful field heuristic: an ECC with 50+ living custom transactions usually points to RISE; a greenfield with none makes GROW workable. The heuristic's job is to start the audit, not to replace it.
  • GROW's constraint is also its benefit: the enforced clean core removes an entire class of future upgrade cost. Organisations that could fit GROW but choose RISE "to keep options open" are often buying optionality they will pay for annually.

Point of view

Frame RISE vs GROW to the board as strategic delivery models, not technical flavours. The decision is really about how much of your past you intend to carry into the next fifteen years. Choose RISE because your complexity is genuinely value-bearing — never because auditing the custom code felt like too much work this quarter.

Conditional, not ideological — the recommendation grid

If

Large enterprise, deep ECC legacy, regulated

RISE: brownfield conversion, controlled custom code, dedicated environment. Pair it with a clean-core programme so the legacy shrinks instead of fossilising.

If

Mid-market or first-time SAP, minimal legacy

GROW: fastest standardised path, lower entry cost, clean core by contract. Invest the saved money in adoption, not in re-creating old reports.

If

Greenfield ambition inside a legacy organisation

Consider GROW for new entities or spin-offs while the core migrates via RISE — two-tier is a strategy, not a compromise.

If

You cannot yet count your living custom code

Neither, yet. Run the custom-code audit first — signing a delivery model before knowing your legacy is how transformations start stalled.

The commercial sequence — baseline before signature

The delivery-model choice is also a contract choice, and the order of work decides your negotiating position. Three steps, in sequence:

  • 1 · Baseline. A full analysis of the current SAP contract position — on-premise and cloud — against the actual landscape, processes and in-house know-how. You cannot price a move you have not measured; shelf-ware, unused engines and legacy maintenance terms all change the arithmetic.
  • 2 · Cloud business case. A company-specific commercial assessment of the cloud model against that baseline — the subscription's cost profile over five-plus years, not its first-year discount. This is where the business case & TCO discipline does its work, and where the July 2026 EU commitments on shelf-ware termination and segmentation strengthen the customer's hand.
  • 3 · Contract. Only then the negotiation: contractual optimisation potential identified from the baseline, a deliberate RISE or GROW negotiation strategy, and technical requirements derived from the cloud contract framework — not the other way around.

Signing the model before the baseline exists reverses the leverage: the vendor knows your renewal date, and you don't yet know your own consumption.

Monday-morning questions

  • How many custom transactions were actually executed in production in the last year — and who can name their business owners?
  • Which of our processes are genuinely differentiating, and which are merely different?
  • What does each model cost over five years for us — including the operating model around it, not just the subscription?
  • If we chose GROW, what would we have to give up on day one — and would anyone outside IT notice?

Where this sits in the decision chain

This is decision 3 of 8 in the Executive Clarity decision library. It builds on SAP Public Cloud vs Private Cloud and leads into the discipline that keeps either choice healthy: SAP Clean Core strategy. The commercial mechanics beneath this choice — FUEs, role-based user types and Digital Access — are examined in the licensing decision inside RISE vs GROW.

Sources

  • SAP's published RISE with SAP and GROW with SAP offering descriptions.
  • Independent licensing and compliance analyses of the two models (e.g. Redress Compliance).
  • SAP partner implementation guides on delivery-model selection.

Editorial standard: facts, inference and point of view are kept separate above. Published 2026-08-02 · By Andreas BORN.