SAP RISE Tiers Explained: How Base, Premium and Cloud ERP Private Changed in 2025

RISE with SAP launched in 2021 as SAP's answer to enterprise cloud adoption — a bundled offer combining S/4HANA, managed infrastructure, and SAP Business Technology Platform into a single subscription. Simple in concept, complex in practice. By 2025, the product had evolved significantly, and in July 2025 SAP executed a formal restructuring of the RISE tier architecture that changed what each tier delivers, how it is priced, and what it is called.

If your organisation is evaluating RISE with SAP for the first time, or managing an existing RISE contract toward renewal, understanding the current tier structure — and how it differs from what came before — is essential for making commercially sound decisions. SAP's public communications around these changes are designed to minimise friction, not to give buyers full visibility of what changed and why. This article provides that visibility.

The Original RISE Tier Structure (2021–2025)

When RISE with SAP launched in January 2021, the commercial framework was intentionally simple: two tiers, one contract structure. SAP's pitch was that enterprises could move from on-premise ECC to cloud S/4HANA without managing multiple vendor contracts for software, infrastructure, and support.

RISE with SAP Base

RISE with SAP Base delivered S/4HANA Cloud Public Edition — SAP's multi-tenant, standardised ERP running on SAP's own data centres. Updates were mandatory and quarterly. Customisation was limited to SAP's approved extension model using SAP BTP side-by-side extensions. Target profile: organisations willing to standardise processes to fit SAP's standard template in exchange for a faster, lower-cost cloud migration.

RISE with SAP Premium

RISE with SAP Premium delivered S/4HANA Private Cloud Edition — single-tenant, full-stack SAP running on a customer-selected hyperscaler (AWS, Azure, or GCP), managed by SAP. Updates were annual rather than quarterly. Existing customisations and ABAP code could be migrated. Target profile: large enterprises with complex customisations, regulatory requirements for data residency, or processes that could not be standardised without material business disruption.

What Changed in July 2025

SAP's July 2025 portfolio restructuring was framed publicly as a "simplification" of the product portfolio. In commercial terms, it was a restructuring with three primary objectives: differentiate the public cloud product under a cleaner brand, restructure the private cloud pricing to recover margin, and create more granular commercial handles for SAP's enterprise sales teams to use.

RISE Base → GROW with SAP

For new customers, the Base tier offering is now sold as GROW with SAP — a distinct brand from RISE with SAP that SAP positions as the "standardised, best-practice cloud ERP" for mid-market and ERP-first deployments. Existing RISE Base customers are not automatically rebranded, but new prospects evaluating the public cloud option will encounter GROW rather than RISE language in SAP's commercial proposals.

The underlying technology — S/4HANA Cloud Public Edition — has not changed. The commercial model is largely consistent. What changed is SAP's go-to-market framing and some adjustments to the included BTP credit allocation and Signavio entitlements.

RISE Premium → SAP Cloud ERP Private

The more significant change was the rebrand and restructuring of RISE with SAP Premium into SAP Cloud ERP Private. This was not a simple rename. SAP restructured the bundle contents, revised the FUE volume tier thresholds, adjusted the BTP credit allocations, and introduced a formal tier-within-a-tier structure for Cloud ERP Private with different inclusions at different volume bands. Read our detailed analysis of what SAP Cloud ERP Private includes and what changed for a complete breakdown.

The Current Tier Structure Explained

As of July 2025, the RISE with SAP / SAP Cloud ERP commercial structure has three primary flavours for new enterprise buyers:

For organisations that already have S/4HANA on-premise licences, SAP also offers a Cloud ERP Private Edition (Transition Option) — a commercial mechanism that allows customers to maintain some elements of their perpetual licence investment while moving to managed cloud infrastructure. This is a distinct commercial vehicle covered in our dedicated article on the ERP Private Edition Transition Option.

GROW with SAP vs SAP Cloud ERP Private: What's the Difference?

The choice between GROW and Cloud ERP Private is one of the most consequential commercial and technical decisions in any SAP cloud migration. The marketing positioning overstates the similarities — in practice, these are substantially different products with different risk profiles, different cost trajectories, and different exit dynamics.

Dimension	GROW with SAP (Public Cloud)	SAP Cloud ERP Private
Deployment model	Multi-tenant public cloud	Single-tenant private cloud on hyperscaler
Update cadence	Quarterly — mandatory, cannot delay	Annual — customer can delay within SAP's window
Custom code (ABAP)	✗ Not permitted — BTP side-by-side only	✓ Supported with standard restrictions
Data residency	SAP-determined data centre locations	Customer-selected hyperscaler region
Infrastructure control	None — fully SAP-managed	Limited — SAP manages BASIS/infrastructure, customer manages data
Go-live timeline	Faster — pre-configured, reduced implementation complexity	Longer — full implementation programme required
Typical cost position	Lower TCO for standardised deployments	Higher TCO, offset by control and customisation
Exit flexibility	More portable — standard processes easier to migrate	More complex — custom code creates additional migration dependency

BTP Credit Allocations by Tier

One of the most material commercial differences between the GROW and Cloud ERP Private tiers — and between the pre- and post-July 2025 structures — is the SAP BTP credit allocation included in the subscription. BTP is the foundation for all S/4HANA extensions, integrations, and AI features. Running out of included BTP credits and purchasing overages at list price is one of the most common sources of unexpected cost in SAP cloud deployments.

SAP does not publicly publish BTP credit allocations by tier — they are subject to commercial negotiation. What we can confirm from client engagements is the following pattern:

The practical implication: negotiate BTP credit allocations explicitly, not as an afterthought. SAP's standard proposals include baseline credits that are almost always insufficient for active production environments with meaningful integration and extension workloads. The gap between included credits and actual consumption — when filled with list-price overages — can add 15–25% to your annual SAP spend. Our SAP cost modelling service includes BTP consumption forecasting as a standard component of any cloud contract analysis.

Impact on Existing RISE Customers

If your organisation signed a RISE with SAP Base or Premium contract between 2021 and July 2025, you are on legacy Order Form terms. You are not automatically moved to the new structure. However, SAP's commercial approach to renewals of legacy RISE contracts in 2025–2027 is systematically oriented toward migrating customers to the new tier structure.

What SAP Will Do at Your Renewal

SAP's account teams are measured on cloud revenue — not on your satisfaction with the existing contract. At renewal, expect SAP to present the new tier structure as an improvement, offer "transition commercials" that appear to offer pricing continuity, and use ECC end-of-maintenance urgency (for hybrid environments) as a prompt for decision acceleration. The renewal proposal will be structured to make the new tier appear commercially neutral or slightly better than your current position, while subtly reducing inclusions or resetting discount structures.

What You Should Do

Before engaging with SAP on any renewal commercial, conduct an independent audit of your current contract: what does your existing Order Form actually include, what are you paying per FUE, what BTP credits are contracted, and what exit rights do you have. Then compare that against what SAP is proposing in the new structure — line by line, not at headline level. Our RISE advisory team does exactly this analysis for enterprises approaching RISE renewal, and consistently identifies commercial disparities that SAP's standard renewal proposals obscure.

Which Tier Is Right for Your Organisation?

The right tier depends on your organisation's customisation legacy, internal infrastructure capability, regulatory environment, and commercial risk appetite. SAP's sales process will push you toward Cloud ERP Private — it generates more revenue per customer and creates stronger lock-in. But that does not make it the right choice for every enterprise.

Choose GROW with SAP if your organisation is genuinely willing and able to standardise processes to SAP's best-practice model, your ERP footprint is relatively uncustomised, and speed-to-cloud and cost efficiency are primary drivers. Be clear-eyed: quarterly mandatory updates mean you will need internal capability to absorb SAP changes at frequency. Test and development environment management under a public cloud model is also more constrained than in private cloud.

Choose SAP Cloud ERP Private if you have significant ABAP customisation that would require a multi-year clean-core remediation programme to eliminate, if your regulatory environment requires specific data residency controls, or if annual update cadence is necessary for your change management capacity. Be equally clear-eyed: the higher cost and longer contract terms need to be justified by genuine need, not by inertia or SAP sales pressure.

The ERP Private Edition Transition Option is a third commercial path worth evaluating if you hold significant perpetual S/4HANA licences and want to retain some of that investment value in your cloud migration structure.

Tier-Specific Negotiation Priorities

For GROW with SAP Negotiations

The most valuable negotiation levers in GROW deals are: FUE count right-sizing (the same systematic challenge as Cloud ERP Private), BTP credit allocation (negotiate explicitly upfront), implementation support inclusions (SAP occasionally bundles activation services — understand the cost and scope clearly), and renewal price caps (lock in escalation limits for years two and three).

For SAP Cloud ERP Private Negotiations

In addition to FUE right-sizing and BTP credits, Cloud ERP Private negotiations must address: exit rights and data portability, SLA terms (SAP's standard 99.7% uptime is negotiable upward for mission-critical environments), hyperscaler choice implications (especially if you have existing AWS, Azure, or GCP commitments that can be used as commercial leverage), and multi-year pricing protection against annual escalators.

See our comprehensive RISE with SAP hidden costs guide for the full catalogue of commercial exposures that require explicit contract protection.