RISE with SAP, public versus private cloud, and what each means for your data

RISE with SAP is the managed-cloud route, and it splits into two very different destinations. Public Cloud standardizes you. Private Cloud keeps your complexity. The choice shapes the data and code work.

RISE with SAP is how SAP wants you to move: one subscription that bundles the S/4HANA Cloud license, the infrastructure, and the migration services. It re-platforms the commercial model as well as the system. The part buyers miss is that RISE splits into two very different destinations, and the one you pick changes the data and custom-code work in front of you.

What RISE with SAP actually is

It is an all-in-one managed-cloud subscription. Instead of buying licenses, hosting, and services separately, you buy them as a package and SAP runs the environment. The commercial shift is real, but it does not remove the readiness work. The data still has to be fit to move before any subscription helps you.

• Dec 31, 2027 ECC 6 mainstream maintenance ends. Paid extended maintenance runs to 2030 at roughly two extra points of fee. Older ECC releases already lost mainstream support in 2025. The date is a planning input, not a cliff.

S/4HANA Public Cloud

Public Cloud is standardized software as a service. SAP manages everything, releases run on SAP's schedule, and custom code is heavily limited. The model is fit-to-standard, which means the bespoke ABAP you accumulated over years on ECC has to be retired, replaced with approved extension points, or rethought as a process change. The upside is a clean, current, lower-maintenance core. The work is adopting standard processes and cleansing your data into standard structures.

The six dimensions of SAP data readiness

Score each from zero to five before you commit to a date. A low total means an early start invites overruns.

• Master data quality. Duplicates and completeness across customers, vendors, and materials. Usually one of the two lowest scores.
• Data quality. Consistency and validity of values: units of measure, classifications, mandatory fields.
• Custom code. What breaks against the simplified data model, and how much of it is actually used.
• Reporting dependencies. Which BW models and dashboards go dark when the data structure changes.
• Scope decisions. Whether keep, drop, and redesign were decided deliberately or left open.
• Program ownership. Who owns the data outcome, and how senior they are.

Source: Thinklytics SAP data readiness practice, 2026.

S/4HANA Private Cloud

Private Cloud is a dedicated environment on a hyperscaler such as AWS, Azure, or Google Cloud. It keeps room for customization, which is why complex pharma, energy, and manufacturing operators choose it: they need their specialized and regulated workflows intact. The trade is that you carry more of your existing complexity forward, including the custom code and the data debt that came with it.

• 40% of the migration timeline is discovery and data cleansing. Pre-move cleansing with validation rules cuts post-migration defects by about 60% and post-go-live performance issues by about 25%. The work you skip up front returns as production incidents.

How the choice changes the data work

Public Cloud forces your data into standard structures, so the mapping and cleansing to the standard model is heavier and the custom-code retirement is unavoidable. Private Cloud preserves more of your shape but moves more of your legacy condition with it. In both cases the data has to be profiled, cleaned, and reconciled first. The destination differs. The readiness work does not. Don't move the mess. Clean it first.

Frequently asked questions

What is RISE with SAP?

RISE with SAP is an all-in-one subscription that moves you off on-premises ECC into an SAP-managed cloud, bundling the S/4HANA Cloud license, infrastructure, and migration services into one commercial package. It re-platforms the commercial model as well as the system.

What is the difference between Public and Private Cloud?

Public Cloud is standardized software as a service where SAP manages everything and custom code is heavily limited, so you adopt standard processes. Private Cloud is a dedicated, customizable environment on a hyperscaler such as AWS, Azure, or Google Cloud, which keeps room for specialized and regulated workflows.

Which one is right for us?

Public Cloud fits companies willing to adopt standard processes and retire most custom code. Private Cloud fits complex operators in pharma, energy, and manufacturing who need to keep regulated or specialized workflows. The deciding factor is how much of your current configuration must survive.

Does Public Cloud really allow almost no custom code?

It allows very limited extension, by design. The model is fit-to-standard, so heavy custom ABAP from your ECC years has to be retired, replaced with approved extension points, or rethought as a process change. That code review is a major part of a Public Cloud move.

How does the choice change the data work?

Public Cloud forces your data into standard structures, so cleansing and mapping to the standard model is heavier. Private Cloud keeps more of your shape but carries more of your legacy complexity forward. Either way the data has to be profiled, cleaned, and reconciled before it moves.

Is RISE the only way to S/4HANA?

No. You can still run S/4HANA on-premises or on your own hyperscaler contract outside RISE. RISE is the bundled, SAP-managed commercial route, and it is the one SAP is pushing hardest, but the data readiness work is the same regardless of how you buy.