Noel D'Costa
Contents
RISE with SAP public cloud suits companies whose processes are standard and need no very specific configuration. Private cloud suits companies with industry-specific processes, deep configuration or an ECC system they want to convert rather than rebuild.
The public edition gives you SAP's best practices, SAP-managed upgrades twice a year and no changes to SAP code. The private edition keeps full configuration, all industries and the brownfield path.
Short answer: if you can run on SAP's standard, go public. If you cannot, or you are not sure, look hard at private before you sign.
This article is one spoke of my ECC to S/4HANA migration guide. For what a RISE contract bundles, read my RISE with SAP overview. Here I only cover the edition decision.
The names changed in 2025 and the old ones still dominate search. This is where they stand in October 2026:
- SAP Cloud ERP is SAP's marketing name for its cloud ERP. Its core application is still called SAP S/4HANA Cloud Public Edition, and SAP's own blogs now write "SAP Cloud ERP Public Edition".
- SAP Cloud ERP Private is the private cloud product, which most people still search for as SAP S/4HANA Cloud Private Edition.
- RISE with SAP is the transformation offer for existing SAP customers.
- SAP GROW, which most people still call GROW with SAP, is the offer for companies new to SAP.
The point most articles get wrong: RISE is not a synonym for private cloud. On its SAP GROW page, SAP says RISE with SAP can have SAP Cloud ERP or SAP Cloud ERP Private at the core. GROW is built on the public edition.
So "RISE public or private" is a real choice. The commercial wrapper and the edition are two separate decisions, and you should make the edition decision first.
SAP publishes an offering comparison for the public, private and on-premise editions on the SAP Help Portal. This table summarises the parts that decide most cases, checked in October 2026:
| Area | Public edition (SAP Cloud ERP) | Private edition (SAP Cloud ERP Private) |
|---|---|---|
| How you get there | New implementation only | New implementation, system conversion, selective data transition, or lift and shift |
| Configuration | SAP Central Business Configuration | Full access to Customizing |
| Extensibility | Key user (in-app), developer extensibility with ABAP Cloud, side-by-side on SAP BTP | All extensibility options |
| Changes to SAP code | Not possible | Possible, though SAP does not recommend them |
| Upgrades | Two a year, February and August, managed by SAP | New release every two years, feature packs every six months in its first two years, installed by SAP when you ask |
| Maintenance | You always run the current release | Seven years per release; you must plan upgrades to stay in maintenance |
| Industries | Consumer products, discrete manufacturing, energy and natural resources, financial services, public services, service industries | All industries |
| Add-ons | Only add-ons qualified for the public edition | Add-ons qualified for S/4HANA |
| Hosting | SAP data centres or hyperscalers | Hyperscaler, SAP data centre, private data centre or sovereign cloud |
Three rows decide most cases: configuration, industries and how you get there.
Central Business Configuration works by scoping SAP's best practices, then adjusting settings within them. You do not get the full Customizing tree that ECC teams know. If your finance, pricing or logistics design depends on settings deep in that tree, the public edition will not have them.
The industry row is a scope statement, not a marketing list. If your core process belongs to an industry outside the public edition's list, you are into private edition territory before any other question.
The upgrade row is the one CFOs underestimate. The SAP upgrade schedule for the public edition put the 2608 production upgrade for three-system landscape customers on 15 and 16 August 2026. SAP set that date, not the customer.
My rule is short. Standard processes that do not need very specific configuration can go to public cloud.
Everything else needs a harder look. I'd check these signals before anyone signs for public cloud:
- Industry fit. Your core business sits outside the public edition's supported industries.
- Configuration depth. Pricing, revenue, costing or settlement logic relies on configuration a fit-to-standard workshop cannot map to SAP's best practices.
- Add-ons. You depend on an SAP or partner add-on that is not qualified for the public edition.
- Process ownership. The business is not willing to change a process to match the standard, and nobody with authority will make it.
- History. You want to convert ECC with its history and configuration, rather than reimplement and load data.
One signal on its own is a conversation. Two or more and I would expect private edition to be the answer.
I have seen a company in the entertainment industry choose public cloud and regret it. Its needs were not standard, and public cloud was the wrong fit for them.
The lesson is not that public cloud is weak. It works well for the businesses it was built for. The lesson is that the fit check has to happen before the contract, not during Explore.
Watch for the opposite mistake as well. A company with largely standard processes picks private cloud because it feels safer, then rebuilds ECC habits in it. They pay for flexibility they did not need and carry custom code they will defend at every upgrade.
Public or private cloud under RISE with SAP?
Standard processes that need no very specific configuration
Public edition (SAP Cloud ERP)
Industry-specific processes or deep configuration
Private edition (SAP Cloud ERP Private)
An ECC system you want to convert, not rebuild
Private edition, system conversion
A complex group core with simple subsidiaries
Private at the core, public in subsidiaries (two-tier)
Clean core means keeping customisations to a minimum and governing them well. The edition decides who enforces it.
In the public edition, the system enforces it. New developments use ABAP Cloud and released interfaces only, and you cannot modify SAP code. My SAP clean core guide explains the extension levels in detail.
In the private edition, clean core is a governance decision. You can still modify the core, and every modification is a cost you carry into each upgrade.
That is why I'd put a design authority of business and IT in charge of every exception, whichever edition you pick. IT alone will approve anything that is technically possible. The business alone will ask for its old process back.
The most common clean core mistake I see is trying to make SAP work like Oracle. Teams rebuild another system's logic in custom code instead of adopting SAP's standard process. In the public edition that fails at design, which is the cheaper place to find it.
The upgrade trade-off follows the same logic.
- Public edition. You always run the current release and get new features twice a year. You also test twice a year, on SAP's calendar, whether or not your business is in the middle of a year-end close.
- Private edition. You choose when to upgrade within the maintenance window. That freedom is only worth something if you use it, because a private edition system that never upgrades is an ECC system with a cloud invoice.
Standard processes that do not need very specific configuration can go to public cloud. Everything else needs a harder look.
For an ECC customer, the edition decides the migration path. The public edition is always a new implementation: configuration and processes are rebuilt on SAP's best practices, and only business data moves. The private edition supports the system conversion and selective data transition paths described in my migration guide.
In my experience a GROW with SAP project on the public edition takes about 6 to 9 months. A RISE with SAP programme takes 9 to 18 months, depending mostly on the path and the custom code. My S/4HANA migration timeline and project plan breaks that down phase by phase.
A two-tier model is a valid middle route. SAP publishes customer stories where the parent runs private edition and subsidiaries run the public edition, integrated. It works when the subsidiaries really are standard, and it adds integration work you have to own.
The edition also changes the commercial conversation. Subscription metrics, full user equivalent (FUE) sizing and what each package includes differ, and the traps I see most in RISE deals are renewal terms, FUE sizing and AI credits. My guide to RISE with SAP contract and pricing covers what to negotiate.
Before you sign, I'd put these questions to SAP and to your partner:
- Which of our end-to-end processes does the public edition's scope cover today, and which are on the roadmap only?
- Which of our add-ons are qualified for the edition you propose?
- Which of our current configurations have no equivalent in Central Business Configuration?
- What does the upgrade calendar look like against our year-end close and peak season?
- If we start on the public edition and outgrow it, what is the route, and is it a new project?
- Show us the high-level design for our business, not a generic edition comparison.
The last question matters most. A partner who answers with generic information is not ready to advise you on this choice. My guide to choosing an S/4HANA migration partner covers the rest of that conversation.
Take your top 20 business processes and mark each one standard, standard with configuration, or specific. Do it with the process owners in the room, not from a slide.
If almost everything is standard, ask for a public edition proposal and a fit-to-standard workshop on your real data. If several core processes are specific, or you want to convert ECC, ask for private edition and plan clean core governance from day one. My free greenfield vs brownfield migration assessment helps with the path question.
I help organisations make this call before the contract fixes it. If you want an independent view, get in touch.
Is RISE with SAP public cloud or private cloud?
It can be either. SAP says RISE with SAP can have SAP Cloud ERP, the public edition, or SAP Cloud ERP Private at its core. Most ECC customers with complex processes choose private, but RISE itself does not decide the edition.
What is the difference between S/4HANA Cloud public and private edition?
The public edition is SaaS with SAP's best practices, SAP Central Business Configuration, two SAP-managed upgrades a year and no changes to SAP code. The private edition gives full access to Customizing, all industries, all extensibility options and system conversion from ECC. It gets a new release every two years, with seven years of maintenance per release.
Is SAP Cloud ERP the same as S/4HANA Cloud Public Edition?
Yes, in practice. SAP markets its cloud ERP as SAP Cloud ERP, and SAP S/4HANA Cloud Public Edition is its core application. The private product is now called SAP Cloud ERP Private, which most people still know as S/4HANA Cloud Private Edition.
Can I convert SAP ECC to S/4HANA Cloud Public Edition?
No. The public edition only supports a new implementation, so you rebuild processes on SAP's best practices and migrate business data. System conversion and selective data transition from ECC are only available for the private edition and on-premise.
Can you modify SAP code in S/4HANA Cloud Private Edition?
Yes. SAP lists modifications as possible but not recommended in the private edition. Every modification adds effort to future upgrades, so I'd send each one through a design authority of business and IT and record why it exists.
Which companies should choose SAP public cloud ERP?
Companies whose processes are standard and need no very specific configuration, in an industry the public edition supports, and willing to adopt SAP's best practices. Companies with industry-specific processes, deep configuration or an ECC system they want to convert usually fit the private edition better.
Written by
Noel D'Costa
ECC to S/4HANA migration: paths, steps and SAP ECC deadlines
What SAP ECC is, what changes in S/4HANA, how to choose between greenfield, brownfield and selective data transition, and the steps, tools and deadlines that matter.
How to choose an S/4HANA migration partner
SAP's partner badges narrow the field. They do not pick your partner. Here is how I would test references and high-level design, and keep the scope in your own hands.
RISE with SAP pricing: what is in the contract
RISE with SAP is priced as a quoted subscription, mostly on Full Use Equivalents. Here is what the contract covers, what it leaves out, the three traps I see most and what I always negotiate.
S/4HANA migration cost: what drives it by path
What an ECC to S/4HANA migration costs by company size, why brownfield vs greenfield cost depends on your system, and the drivers that move the bill: custom code, data, mock conversions, dual running and the contract conversion.
Next step
Running an ERP programme right now?
If this article touched on a programme you are live in right now, a 30-minute conversation usually gets further than another week of internal analysis.