Skip to content

170 practical guides on SAP, cybersecurity and AI, $9.99 each. Shop all books ›

0

Blog›SAP

What Is RISE with SAP? What It Includes, Who Secures What and the 2027 Deadline

RISE with SAP bundles S/4HANA Cloud Private Edition, hyperscaler infrastructure and SAP-run technical operations into one subscription. Here is what it includes, how it compares with other options and what stays your responsibility.

Somewhere in most large SAP customers there’s a slide with a countdown to December 31, 2027, the end of mainstream maintenance for SAP ECC 6.0. On the next slide, almost always, is the phrase “RISE with SAP.” It shows up in board updates, renewal negotiations and job ads, and people use it to mean slightly different things. This guide sorts that out.

RISE with SAP is SAP’s program and commercial offering for moving companies to its cloud ERP. At its core is SAP S/4HANA Cloud Private Edition, run by SAP on a hyperscaler such as AWS, Microsoft Azure or Google Cloud, sold as one subscription together with infrastructure, technical operations and a set of extra cloud services and tools.

In one sentence: RISE with SAP is a subscription bundle that moves your SAP ERP to S/4HANA Cloud Private Edition, with SAP running the infrastructure and technical operations and you keeping control of your business processes, data and user access.

Key takeaways

  • RISE launched in January 2021 and is built around S/4HANA Cloud Private Edition.
  • SAP runs the infrastructure, database and technical operations; the customer still owns users, roles, data, custom code and business configuration.
  • Package names and contents have changed over time, so read the current contract rather than an old slide.
  • The ECC deadline matters: SAP mainstream maintenance for ECC 6.0 on enhancement packages 6 to 8 ends at the end of 2027.
  • Security work doesn’t disappear in RISE. Access, segregation of duties and monitoring still sit with you.

What does RISE with SAP include?

RISE started in January 2021 as a single contract that combined several things companies used to buy separately. The exact content depends on the package and the deal, and SAP has reshaped the packaging more than once. In 2025, for example, SAP started describing RISE as the overall transformation journey and selling the cloud service itself under the “SAP Cloud ERP Private” name. Broadly, the bundle covers:

Part What it is
S/4HANA Cloud Private Edition The ERP software itself, single-tenant, with room for your own configuration and custom code
Infrastructure Servers, storage and network on a hyperscaler (AWS, Azure or Google Cloud), provisioned and paid for through SAP
Technical managed services Operating the database and SAP technical stack, patching, backups and technical lifecycle tasks, as defined in SAP’s roles and responsibilities document
SAP Business Technology Platform (BTP) A credit allocation for integration, extensions and analytics on SAP BTP, with the size depending on the package
Process and transformation tools Depending on the package, tools such as SAP Signavio for process analysis, SAP Build and access to SAP Business Network
Support SAP’s enterprise support for the bundled software

The point of the bundle is one contract and one throat to choke. Instead of separate deals for licenses, hosting, a managed service provider and add-on tools, a company signs one subscription with SAP. Whether that is cheaper or simpler for a given company is a negotiation question. Independent licensing advisors regularly point out that add-ons beyond the included allocation, such as extra BTP consumption, cost more, so model your real needs before signing.

RISE vs on-premise vs public cloud: what’s the difference?

RISE is one of several ways to run SAP’s ERP. The differences come down to who runs what and how much you can customize.

Option Who runs the infrastructure and technical stack? Customization Typical fit
On-premise S/4HANA You or your hosting partner Full Companies that want full control or have specific hosting requirements
S/4HANA on your own hyperscaler account You or a partner, on AWS, Azure or Google Cloud Full Cloud-first companies that want to keep operations in house
RISE with SAP (Private Edition) SAP High: own configuration, custom code within SAP’s rules Large companies moving from ECC with complex processes
S/4HANA Cloud Public Edition (often via GROW with SAP) SAP, shared multi-tenant service Limited: standard processes and approved extensions Smaller and mid-size companies that can adopt standard processes

The Public Edition updates on SAP’s schedule and keeps customers close to the standard. Private Edition is closer to the on-premise world: you can bring custom code and decide more about upgrades, but you also carry more of the complexity. For an introduction to the ERP itself, see our guide to SAP S/4HANA.

Why are companies moving to RISE now?

The biggest driver is the end of ECC mainstream maintenance. SAP has stated that mainstream maintenance for SAP Business Suite 7 core applications, including SAP ERP 6.0 on enhancement packages 6, 7 and 8, runs until the end of 2027. Optional extended maintenance runs from 2028 to the end of 2030 for an additional fee. Systems on older enhancement packages already left mainstream maintenance at the end of 2025.

SAP has also announced a transition option for customers who move to a private cloud edition of SAP ERP, which can extend maintenance for ECC-based systems up to 2033 under specific conditions. It is narrow and conditional, so it’s a bridge for some customers, not a reason to delay planning.

Other reasons companies give: they want to stop running data centers and SAP technical operations, they want predictable subscription costs, and they want access to SAP’s newer cloud services and AI features, which SAP increasingly delivers to cloud customers first. The counter-arguments are cost, contract lock-in over long subscription terms and less direct control over the technical environment.

Who is responsible for what in RISE?

This is where projects get into trouble. Many business leaders hear “SAP runs it” and assume security is now SAP’s job. It isn’t, at least not all of it. SAP publishes a roles and responsibilities document for RISE that is part of the contract, and SAP describes a shared security responsibility model.

Area Usually SAP Usually the customer
Data center, hyperscaler setup and network inside the SAP environment Yes
Operating system and database operations, technical patching Yes Agree maintenance windows
Backups Yes, as defined in the contract Check retention meets your needs
Disaster recovery Only if contracted as an additional service Decide whether you need it and buy it
Users, roles and authorizations Yes
Segregation of duties and access reviews Yes
Custom code and its security Yes
Business configuration and data Yes
Connections to your other systems, identity provider and network Shared Yes, on your side

The short version, which SAP’s own security people have also said publicly: SAP takes over much of the infrastructure work, while the administration, security and compliance of the ERP application, including roles and authorizations, stay with the customer. In practice that means everything in our guides to segregation of duties and SAP GRC still applies after you move. Your SAP security team doesn’t go away. It focuses on the application layer instead of the servers.

What does a RISE project look like?

A RISE contract doesn’t migrate your system by itself. Companies still choose a migration approach and run a project, usually with a systems integrator. The main approaches are the same as for any S/4HANA move:

  • System conversion (brownfield). Convert the existing ECC system, keeping history and most custom code. Faster to plan, but it carries old problems forward unless you clean up along the way.
  • New implementation (greenfield). Start fresh with standard processes and migrate selected data. More redesign work, but a cleaner result.
  • Selective data transition. A middle path that moves selected parts of the old system, often with specialist tools.

Typical steps include assessing custom code (much of it is often unused), cleaning master data, planning the security redesign, testing integrations and rehearsing the cutover. Tools such as SAP Signavio, when included, help analyze current processes before you decide what to keep.

The security redesign deserves its own line in the plan. S/4HANA changes the user interface toward SAP Fiori apps, changes some transactions and authorization objects, and merges vendors and customers into business partners. Copying old ECC roles into the new system usually brings old segregation of duties conflicts with it. Teams that redesign roles during the move tend to finish with fewer audit findings.

What changes for SAP Basis and security teams?

A common worry in SAP teams is “what will we do once SAP runs the system?” The honest answer is that the work shifts rather than vanishes.

SAP Basis administrators lose most of the server, operating system and database work: installing patches at the operating system level, managing storage, running backups. What remains is the application side. Someone still has to plan and test SAP software updates with the business, manage transports between development, test and production, watch performance from the business point of view, handle interfaces and work with SAP’s operations team when something breaks. Many Basis people move into roles that combine this application management with cloud integration on BTP.

Security teams keep almost everything they had at the application layer and gain some new tasks. They still design roles, run access requests and reviews, manage emergency access and check custom code. On top of that they need to understand how the RISE environment connects to the company network, how single sign-on works with the corporate identity provider, which logs SAP makes available and how to bring them into the company’s security monitoring. They also become the people who read the roles and responsibilities document closely and push back when a gap appears.

Auditors notice the difference too. They will ask for evidence from SAP, such as certifications and service reports, alongside the company’s own evidence for access control and change management. Agree early who collects what.

What should you check before signing a RISE contract?

RISE contracts are long and detailed. Questions that save trouble later:

  1. Sizing and metrics. How are users counted, and does the contracted volume match your real usage over the full term?
  2. Service scope. Which tasks are standard in the roles and responsibilities document, which are optional, and which cost extra? Disaster recovery is a common surprise.
  3. BTP and add-ons. How many BTP credits are included, and what happens when you run out? Which tools are in your package and which are not?
  4. Service levels. What availability is promised, how are maintenance windows agreed and what happens if SAP misses the target?
  5. Security and compliance. What certifications and reports will SAP provide for your auditors? How do you get logs into your own security monitoring?
  6. Exit. How do you get your data out if you leave, and in what format?

None of this is unusual for a large cloud contract. RISE is a big commitment, often over several years, and the details decide whether it works for you.

Frequently asked questions

Is RISE with SAP the same as S/4HANA Cloud?

Not exactly. RISE is the program and commercial bundle. Its core is S/4HANA Cloud Private Edition, plus infrastructure, technical operations and extra services. S/4HANA Cloud Public Edition is a different, multi-tenant product.

Does SAP handle security in RISE?

SAP handles much of the infrastructure and technical security, as described in its roles and responsibilities document. The customer remains responsible for users, roles, authorizations, segregation of duties, custom code, data and connected systems.

Can I keep my custom code in RISE?

Yes, Private Edition allows custom code and customer-specific configuration within SAP’s rules. Most projects use the move to remove unused code and reduce changes to the standard.

Do I have to move to RISE before 2027?

No. 2027 is when ECC mainstream maintenance ends, and extended maintenance is available through 2030 for an extra fee. RISE is one of several paths to S/4HANA, alongside on-premise and other cloud options.

The bottom line

RISE with SAP packages S/4HANA Cloud Private Edition, hyperscaler infrastructure, SAP-run technical operations and a set of cloud services into one subscription. It can take a lot of infrastructure work off your plate, especially with the ECC 2027 deadline approaching. Read the roles and responsibilities document closely, size the contract for real usage, and plan the security redesign, because users, roles, data and custom code stay your job in the cloud.

Sources: SAPinsider: SAP support deadlines 2027, 2030 and 2033; SAP Office of the CSO on customer responsibilities in RISE; SAPinsider: security for SAP RISE; SC Media: where SAP’s responsibility ends in RISE.

Go deeper with these books