RISE or GROW — which SAP cloud path fits
RISE and GROW target different organisations with different trade-offs. What each includes, what neither includes, and how to tell which one you are.
Written by APx Technology
Both are SAP cloud ERP bundles. They are aimed at meaningfully different situations, and choosing by name recognition rather than fit is an expensive mistake.
What they are
RISE with SAP bundles S/4HANA Cloud private edition, hyperscaler infrastructure, technical managed services and a set of transformation tooling. It targets existing SAP customers moving an established landscape, where configuration, history and custom development all matter.
GROW with SAP targets S/4HANA Cloud public edition, typically for mid-market organisations or new SAP customers. Fixed scope, best-practice-first, fast start, and a standardised upgrade cadence you do not control.
The real differentiator
Not company size. Tolerance for standardisation.
Public cloud under GROW means you adopt SAP’s processes and SAP’s upgrade schedule. Extensibility is confined to defined extension points. In exchange you get speed, lower cost and a system that stays current without effort.
Private cloud under RISE preserves far more latitude. You keep more of your configuration, you have more extensibility options, and you have some influence over upgrade timing. In exchange you carry more complexity and more cost.
If your processes are genuinely differentiating — if how you do something is part of why customers choose you — public cloud will constrain you. If your processes are ordinary and you have been telling yourself they are special, public cloud is probably the better deal and the standardisation is a feature.
What neither includes
This causes more budget surprises than anything else in the SAP cloud conversation.
Both bundles cover infrastructure, licence and technical operations. Neither covers the transformation work:
- Fit-to-standard workshops
- Custom code assessment and remediation
- Data migration and reconciliation
- Integration build
- Testing
- Training and change management
- Cutover
That is the bulk of the real effort and cost on any serious programme. A RISE subscription is not a project budget, and treating it as one produces a funding gap discovered at the worst moment.
Questions that actually discriminate
Are your processes differentiating or just familiar? Be honest. Most are familiar.
What is your regulatory position on data residency and control? This can rule out options before anything else is considered.
How much custom code do you have, and how much of it is genuinely required? Heavy, genuinely necessary custom development points to private cloud.
Can you absorb an upgrade on SAP’s schedule? Public cloud upgrades arrive when they arrive.
What is your internal basis capability? If you have a strong team, you give up more by moving to managed infrastructure. If you have no team, you gain more.
The uncomfortable third option
Sometimes the honest answer is neither — not yet.
If your data is poor, your processes are undocumented and your custom code is unmapped, moving to cloud ERP will transfer those problems into an environment where they are harder and more expensive to fix. A year spent on data quality and custom code reduction first will make the eventual move faster and cheaper.
Nobody selling a subscription will tell you this, which is a reasonable argument for getting the advice from someone who is not.