The Pre-Read

Independent SAP briefing

RISE with SAP: the guided move for existing customers onto SAP Cloud ERP Private

At a glance

  • What it is: SAP's guided path from SAP ERP Central Component (ECC) or on-premises SAP S/4HANA onto SAP Cloud ERP Private.
  • Available now: the method, the target system, the first custom code migration agent, and activation of up to three Joule Assistants on Cloud ERP Private at no additional cost.
  • Named, with dates still open: most of the other migration assistants.
  • The decision: whether the statement of work buys the move alone, or the move plus the assistants and the AI activation.

The path, and the mix-up

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, SAP's ERP in an SAP-managed cloud, is what you land on. Autonomous Enterprise, SAP's vision of processes run by agents under human direction, is what the landing is supposed to unlock.

The mix-up that happens in programs 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. RISE is how existing customers get onto Cloud ERP Private while keeping the business logic they already paid for.

The useful question on a live program is narrower: is this still a hosting and migration project, or is the agent-led toolchain in the statement of work?

Why the path exists

ECC is an excellent system of record. SAP argues that AI asks three more roles of an ERP: context an agent can reason over, governed workflows it can act in, and one place where people and agents work together. On-premises SAP S/4HANA closes part of that gap. The rest (SAP Business Data Cloud, SAP Knowledge Graph, SAP Company Memory in preview, Joule) runs in SAP's cloud, on top of Cloud ERP Private. In practice that means waiting leaves the gap open: Cloud ERP Private keeps receiving agents without upgrade projects, and the distance compounds.

Clean Core, SAP's practice of keeping the ERP standard and moving customizations into governed extensions, rides along for a practical reason: custom code that blocks upgrades also blocks the AI SAP keeps adding in the cloud. The Custom Code assistant is aimed at that pile.

The move, and what the move is for

RISE now sells two connected jobs. They collapse in conversation. They should stay separate in a statement of work.

The first is the move: agent-led transformation. Seven named assistants sit in the migration process. In practice that means the painful parts of a conversion are supposed to become assisted work instead of a second factory of spreadsheets.

  • System Analysis builds a trusted baseline of what is in the landscape.
  • Custom Code sorts custom ABAP, the Z-code in ECC: 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 and execution, global templates against local requirements, and the running picture of the program.

After go-live the same assistants are meant to keep running as optimization agents for code hygiene, regression tests, and data quality. The conversion becomes a cycle instead of a one-time cutover.

The second job is what the move is for: a fast path to agentic AI on Cloud ERP Private. SAP activates up to three Joule Assistants there at no additional cost, and all of them under the Max Success Plan, its top services contract. FC Bayern Munich's 2026 migration shows the usual order: 9.5 million fan and member records and 25,000 product masters moved first, with a clean-core foundation for Joule later. Salling Group started its AI phase after its RISE go-live. Land, then agents.

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 from the second half of 2026, such as Colombina's 16-country move off ECC and HARTING's newly signed contract, are still mostly the move.

The first piece of the Custom Code assistant is generally available: the SAP S/4HANA custom code migration agent, listed in SAP's Q2 2026 release highlights. It checks custom code packages for SAP S/4HANA readiness, applies high-confidence fixes, and leaves the rest for a developer to review. It runs on SAP Joule for Developers, ABAP AI capabilities, whose free promotion ended in September 2026; use is now billed in AI Units, SAP's meter for AI consumption. Two more custom code agents, one for clean core adoption and one for moving Web Dynpro screens to SAP Fiori, are planned for later in 2026.

The other assistants appear on the RISE page as newly announced, without a general availability date. Brief them as named until SAP publishes one.

Companies still on premises can get selected Joule assistants and agents before they move if they commit at least half of their current maintenance fee to the cloud. SAP says capabilities vary with the system and its customization. Confirm it on the contract.

Which program is this

If the real objective is to leave the data center, a hosting-shaped RISE can still be the right first step, with AI as a later phase. If the objective is agents in a live process this year, ask whether the toolchain, the AI Units, and the assistant activation are in the statement of work, or only the move.

Keep RISE and GROW apart in the steering deck. 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

General availability dates for most of the seven assistants. On-premises Joule activation depends on eligibility and on each system. Customer stories still describe the move more than the toolchain, and that lag will date the live-versus-named section first.

Sources

Already decoded.