RISE with SAP: contract review, migration advice and readiness checks

RISE with SAP is SAP's offer for existing SAP customers to move their on-premise ERP to the cloud under one subscription. It bundles a cloud ERP (usually SAP Cloud ERP Private, formerly SAP S/4HANA Cloud Private Edition), SAP-managed technical operations, transformation tools and the RISE with SAP Methodology.

I help companies with three parts of it: reviewing the RISE contract before they sign, advising on the migration, and checking whether their system and teams are ready. This page explains what RISE is in October 2026, what SAP runs and what stays with you, and where my detailed guides go deeper.

SAP describes RISE with SAP as a route to modernise on-premise ERP using "a proven methodology, expert guidance, and an agent-led toolchain" (from the RISE with SAP product page). It is a commercial and delivery package. It is not a separate ERP product.

The names changed in 2025, and searches still use the old ones. This is where they stand now:

1. SAP Cloud ERP Private is the private cloud ERP at the core of most RISE deals. Most people still search for it as SAP S/4HANA Cloud Private Edition, or "rise with sap s/4hana cloud".
2. SAP Cloud ERP is SAP's cloud ERP name, and its public edition is what people mean by "rise with sap public cloud". RISE can be built on either edition.
3. SAP GROW (still widely called GROW with SAP) is the offer for companies new to SAP, built on the public edition.
4. SAP RISE and RISE with SAP are the same thing. "SAP RISE" is just the shorter search.

The edition choice is the decision most companies get wrong, because they assume RISE means private cloud. My guide to RISE with SAP public vs private cloud covers what each edition allows on configuration, upgrades, industries and migration paths. My rule there: standard processes that do not need very specific configuration can go to public cloud.

"SAP runs it" is the phrase that causes most budget surprises. SAP's managed cloud services page says the service goes beyond infrastructure to include management of the operating system, the SAP HANA database and the SAP Cloud ERP Private application. That is technical operations.

Your business processes, master data and month-end close are still yours. So is the implementation itself. This is the short version of the split:

Area	SAP runs it under RISE	Stays with you or your partner
Hosting	Infrastructure on a hyperscaler or in SAP data centres	Choosing the provider and region that fit your data residency rules
Technical operations	Operating system, SAP HANA database, application operations, monitoring and security	Deciding when to take upgrades in private edition, and testing them
Business processes	Standard SAP content and best practices	Process design, configuration decisions and functional support
Data	The database it sits in	Cleansing, mapping, migration and ownership of master data
Custom code	The platform for extensions	Remediating, retiring or rebuilding your custom objects
Programme	Onboarding, the methodology and quality gates	Partner selection, governance, testing, training and cutover

The SAP Help Portal publishes a full offering comparison of the public, private and on-premise editions if you need the detailed rows. Optional extras such as a higher availability SLA and disaster recovery are separate line items. I cover those in my RISE with SAP contract and pricing guide.

People often search for a "RISE with SAP adoption framework". SAP's own name for it is the RISE with SAP Methodology. It replaced the loose mix of onboarding material that earlier RISE customers received.

On SAP's RISE with SAP Methodology page, the methodology has three working parts:

1. SAP Activate roadmaps in SAP Cloud ALM. The project runs through the familiar phases: discover, prepare, explore, realise, deploy and run.
2. Quality gates. A checkpoint at the end of each phase where you complete a questionnaire, so SAP and your partner see the same status.
3. Onboarding and preparation. Onboarding sessions, a digital discovery assessment toolkit in the discover phase, and a transformation preparation service that SAP says is an entitlement in the SAP Cloud ERP Private package.

SAP's 2026 description of RISE also names the transformation tools in the toolchain: SAP Signavio, SAP LeanIX and WalkMe. SAP also now describes AI assistants for migration and modernisation as part of that toolchain. What you are actually entitled to depends on your order form, so check each tool by name.

The methodology is useful structure. It does not make the hard decisions for you. Quality gates confirm that a phase is complete; they do not tell you whether your scope, edition or data plan was right in the first place.

Sometimes I lead from the start. Other times, I'm brought in to steady the ship when things go sideways. Across the 21 SAP programmes I have led or rescued, the RISE work I do falls into three services.

Each one has a clear output, so you know what you are paying for.

Service	When it helps most	What you get
Contract review	Before you sign the first RISE order form, or before a renewal	A line-by-line read of the order form against your design, and a list of terms to negotiate
Migration advice	When you are choosing the path, the edition or the partner	A recommendation on edition and migration path, with the reasoning written down
Readiness checks	Before you commit to a timeline or a partner quote	A reading of the SAP Readiness Check and your own system, and the open questions that set the scope

1. RISE contract review

Most RISE overspend is decided in the first order form, not at renewal. The three traps I see most are renewal terms, FUE sizing and AI credits. Full Use Equivalents (FUEs) are the usage metric SAP prices the ERP subscription on.

I always negotiate two things into a RISE deal: the modules that are included, by name, and phase-wise pricing, so you pay as phases go live rather than for the full scope from day one. On a programme that runs 9 to 18 months before the first go-live, paying for users who will not touch the system yet is real money.

What you get from the review:

1. A scope check. Every module, add-on and cloud service in the order form compared with what your design needs.
2. A sizing check. Your FUE count tested against how people will actually use the system, not their job titles.
3. A negotiation list. Renewal terms, AI credit terms, included modules and phase-wise pricing, written as points procurement can take to SAP.

How FUEs are counted, what the subscription includes and excludes, and the questions to put to SAP are all in my RISE with SAP pricing guide. It is practical guidance from programme work, not legal advice. Your contract counsel should still read the order form.

2. RISE migration advice

RISE is the wrapper. Underneath it is still an ERP migration with three possible paths: greenfield (new implementation), brownfield (system conversion) or selective data transition. The public edition is a new implementation only, so the edition choice and the path choice have to be made together.

My path rule: greenfield when you are moving from other systems or new processes must be defined. Brownfield when processes are defined and working. Selective when the processes of some areas need to be redefined.

What you get from migration advice:

1. An edition recommendation. Public or private, based on how standard your processes are and which industries you operate in.
2. A path recommendation. Greenfield, brownfield or selective, tied to your process and data findings.
3. A realistic timeline. For RISE programmes I plan on 9 to 18 months; GROW programmes on the public edition usually take 6 to 9 months.
4. A partner brief. The scope written in your words, so partners quote against your design rather than theirs.

The full step-by-step, the tools and the SAP ECC maintenance deadlines are in my ECC to S/4HANA migration guide. For what drives the budget by path, read my guide to S/4HANA migration cost.

3. RISE readiness checks

The SAP Readiness Check tells you what in your ECC system collides with S/4HANA. It does not tell you what to do about it. A readiness check turns those results into decisions you can fund.

What you get from a readiness check:

1. A reading of the SAP Readiness Check. Simplification items, add-ons, custom code impact, interfaces and financial data quality, explained for the people who have to decide.
2. A custom code view. Which objects break, and which you should retire rather than fix.
3. An interface and data view. Both ends of each interface, and where your data needs cleansing before it moves.
4. The open questions. The list of decisions the check cannot answer, which becomes the scope of your migration assessment.

What the Readiness Check covers, how to run it and where it falls short are in my guide to the SAP Readiness Check and S/4HANA migration assessment. If you are new to SAP rather than moving from ECC, my GROW with SAP page is the better starting point.

RISE fits best when you are an existing SAP customer, your ECC or on-premise S/4HANA system is the core of the business, and you want SAP rather than your own team or a hosting provider to run the technical stack. It fits less well when you have no appetite for standard processes, or when nobody inside the business can own decisions on scope, data and custom code.

Ask these questions before you sign:

1. Have we decided between the public and private edition, or are we assuming private?
2. Do we know which of our custom objects are still used?
3. Is our FUE count based on how people will use the system, or on job titles?
4. Does the contract price follow our rollout phases?
5. Who owns post-go-live functional support, given that SAP runs only the technical layer?

If two or more of those have no clear answer, sort them out before the order form, not after.

What is RISE with SAP?

RISE with SAP is SAP's offer for existing SAP customers to move their on-premise ERP to the cloud under one subscription. It bundles a cloud ERP, usually SAP Cloud ERP Private, with SAP-managed technical operations, transformation tools and the RISE with SAP Methodology.

What is the difference between SAP RISE and S/4HANA Cloud?

S/4HANA Cloud is the ERP software, now sold as SAP Cloud ERP (public edition) and SAP Cloud ERP Private. RISE with SAP is the package around it: the subscription, the managed cloud operations, the tools and the methodology. SAP RISE and RISE with SAP are the same offer.

What do RISE with SAP managed services include?

SAP manages the infrastructure, operating system, SAP HANA database and the SAP Cloud ERP Private application. Functional support of your business processes, data migration, custom code and the implementation itself are not included unless you buy them separately.

Is RISE with SAP available on public cloud?

Yes. RISE can be built on SAP Cloud ERP, the public edition, or on SAP Cloud ERP Private. The public edition suits standard processes that do not need very specific configuration, and it is a new implementation only, so you cannot convert an ECC system into it.

What is the RISE with SAP adoption framework?

SAP calls it the RISE with SAP Methodology. It runs SAP Activate roadmaps in SAP Cloud ALM, adds a quality gate at the end of each phase, and includes onboarding sessions and, for SAP Cloud ERP Private, a transformation preparation service.

How long does a RISE with SAP implementation take?

I plan on 9 to 18 months for a RISE programme, against 6 to 9 months for GROW with SAP on the public edition. The range depends on the migration path, custom code volume, data quality and how many entities go live in each phase.

If you are about to sign a RISE order form, choose a migration path or commit to a partner's timeline, get an independent view first. Get in touch and tell me where you are in the process.