RISE with SAP is the path for existing customers — not the ERP, not GROW
For companies already running SAP ERP Central Component or SAP S/4HANA on premises, RISE with SAP is the guided path onto SAP Cloud ERP Private — methodology, expert guidance, and an agent-led toolchain. Cloud ERP Private is what you land on. Autonomous Enterprise is what the landing is supposed to unlock.
The mix-up that actually happens is treating RISE as a synonym for the ERP, or as the same door as SAP GROW. GROW is the entry for companies new to SAP, on SAP S/4HANA Cloud Public Edition. Different buyer, different core. RISE is how existing customers get onto Cloud ERP Private without throwing away the business logic they already paid for.
The useful question on a live program is narrower: is this still a hosting and migration motion, or is the agent-led toolchain in the statement of work?
Why the path exists
On-premises ECC is an excellent system of record. It was not built as a system of context, execution, and engagement for agents. On-premises SAP S/4HANA closed part of the data-architecture gap; the operational gap remains. Agents need live process context, governed APIs, and a shared engagement layer. Those sit in the cloud stack — SAP Business Data Cloud, SAP Knowledge Graph, Joule Work — on top of Cloud ERP Private. RISE is how existing customers lift that ceiling. Waiting does not freeze the AI story. Cloud ERP Private keeps receiving agents without a classic upgrade project, and the gap compounds.
Clean Core rides along for a practical reason. Custom code that blocks upgrades also blocks the AI SAP will keep shipping in the cloud. The Custom Code assistant on the RISE page is aimed at that pile. The method is older than agents. The agents are new leverage on the same constraint.
The move, and what the move is for
RISE now sells two connected jobs. They collapse in conversation. They should not collapse in a statement of work.
The first is the move: agent-led transformation. Seven named assistants sit in the migration process. In practice the painful parts of a conversion are supposed to be assisted work, not a second factory of spreadsheets.
- System Analysis builds a trusted baseline of what is in the landscape.
- Custom Code sorts Z-code and enhancements: replace with standard, remediate, or keep.
- Data Management prepares and migrates data in a governed cockpit.
- Configuration, Test Management, Rollout, and Project Management cover settings, test scope, global template versus local requirement, and the running picture of the program.
After go-live the same class of agents is meant to keep running: code hygiene, regression, data quality, change and release. The conversion becomes a cycle, not a one-time cutover.
The second job is what the move is for: a fast path to agentic AI on Cloud ERP Private. FC Bayern Munich’s 2026 migration is still the first job — 9.5 million fan and member records, 25,000 product masters, a 99.9% SLA, EU residency — then a clean-core foundation for Joule later. Salling Group starting an AI phase after RISE go-live is the same sequence: land, then agents. Finishing a RISE migration is not the same sentence as “agents run finance.”
SAP GROW sits beside this path. GROW is not a smaller RISE, and RISE is not the public-cloud product. Signing RISE does not purchase Autonomous Enterprise. It lands the landscape on Cloud ERP Private with a method and a toolchain.
What is live, and what is named
The methodology, the expert guidance, and Cloud ERP Private as the target are the live offer. Customer stories in 2026 are still mostly that move.
The seven assistants are named on the product page as newly announced and embedded. Training material still marks them planned for later in 2026. Prefer the product page for what exists as named tools. Do not invent a GA month the page does not state. Named is not the same as live in the statement of work.
Eligible customers — training says those who have converted at least half of current maintenance to cloud — may activate a limited set of Joule assistants on remaining on-premises ERP. Confirm it on the current contract. It is not universal.
Which program is this
If the real objective is to leave the data center, a hosting-shaped RISE can still be the right first motion, with AI as a later phase. If the objective is agents in a live process this year, ask whether the toolchain and the activation services are in the statement of work, or only the move.
Keep RISE and GROW on different slides. Keep Clean Core on the table: agents on a heavily modified core are how programs buy a second migration. Migration assistants help you get there. Domain agents in Joule Work run after.
What is not settled
Exact GA timing for the seven assistants is not on the product page. Until Help or a dated news piece states GA, brief them as named, not live. On-premises Joule activation is eligibility-bound, and may need the underlying application, not only the ERP. Customer RISE stories are still mostly the move, not the toolchain. That lag will date the live-versus-named section first.