SAP's Shift from RISE with SAP to Cloud ERP Licensing: What Has Changed

RISE with SAP to SAP Cloud ERP: The Rebranding Context

SAP launched RISE with SAP in January 2021 as a bundled offering combining S/4HANA Cloud Private Edition, managed infrastructure, and a transformation service. The intent was to simplify SAP's cloud narrative and give enterprises a single commercial package for migrating to S/4HANA in the cloud.

In April 2025, SAP rebranded RISE with SAP as SAP Cloud ERP. The name change reflects SAP's strategic intent to position cloud ERP as the standard offering rather than a differentiated "transformation" programme. SAP also made structural changes to the licensing framework for the Public Cloud edition at the same time, moving from Full User Equivalent (FUE) licensing to Business Suite User Packages — a change with material commercial implications for organisations on or evaluating the Public Cloud path.

For organisations on the Private Cloud Edition (PCE) path — which was the core of the original RISE with SAP offering — the underlying commercial and technical model is largely unchanged. The infrastructure is still hosted on a hyperscaler (AWS, Azure, or Google Cloud), the software licence is still S/4HANA PCE, and the contract structure remains a multi-year subscription with annual escalation clauses. The rebrand does not create new contract terms or new commercial rights for existing RISE customers.

What the Rebranding Changed — and What It Did Not

What Changed

Public Cloud licensing model: The most substantive change accompanying the rebranding is the introduction of Business Suite User Packages for S/4HANA Public Cloud. These packages bundle a set of user licences and module access rights into a per-user-per-month pricing unit, replacing the Full User Equivalent (FUE) metric that was previously used for Public Cloud. For organisations evaluating GROW with SAP (the Public Cloud path), this change means the pricing comparison against previous Public Cloud proposals requires a like-for-like recalculation.

Positioning and sales motion: SAP has shifted its sales motion to lead with SAP Cloud ERP as the default recommendation for all new and renewing customers, rather than offering on-premises, private cloud, and public cloud as equal alternatives. This commercial posture affects the negotiating environment — SAP account teams are more actively incentivised to push cloud ERP than in previous years.

Integration with SAP Business AI: SAP's cloud ERP positioning now more explicitly integrates with SAP Business AI capabilities — including Joule, the AI copilot embedded across SAP applications. Access to the full roadmap of AI capabilities requires cloud deployment on S/4HANA PCE or Public Cloud, which SAP uses as a pull factor in migration conversations.

What Did Not Change

Contract structure and escalation terms: Standard SAP Cloud ERP contracts retain the same escalation provisions as RISE with SAP — typically 3 to 5% annual subscription increases as a contractual right. The rebranding did not introduce new exit rights, data portability protections, or SLA improvements for customers. Existing RISE with SAP contracts were not automatically amended; their original terms continue to govern.

BTP credit bundle: The bundled BTP credits included in SAP Cloud ERP remain at the same level as RISE with SAP — typically insufficient for real enterprise integration and extension requirements. The credit shortfall problem that affected RISE customers continues to affect SAP Cloud ERP customers who accept the standard bundle without negotiating additional credits.

What is not included: SAP Cloud ERP does not include SuccessFactors, Ariba, Concur, Fieldglass, or other line-of-business applications. These remain separate subscription contracts. The rebranding did not expand the scope of the cloud ERP bundle to include the broader SAP portfolio.

S/4HANA migration changes the licence baseline: This fundamental dynamic is unchanged. Migrating from ECC to SAP Cloud ERP triggers a licence baseline reset, with new user type mappings, DDLC reassessment, and BTP credit requirements that must be modelled and negotiated independently of the infrastructure cost.

The Compatibility Pack Expiry — A 2026 Commercial Trigger

One of the most commercially significant events in 2026 for SAP customers is the expiry of Compatibility Pack usage rights in May 2026. The Compatibility Pack allows organisations running S/4HANA to continue using certain legacy ECC processes and interfaces that have not yet been converted to native S/4HANA functionality — a transitional mechanism that SAP provided to ease migration from ECC.

When Compatibility Pack rights expire, organisations that have not completed their conversion to native S/4HANA processes face a compliance exposure. SAP may require a formal extension or impose terms to continue using expired compatibility features. For organisations that have been deferring process conversion in reliance on the Compatibility Pack, the May 2026 expiry is an urgent action item — both a technical compliance matter and a commercial negotiation opportunity.

Enterprises in active SAP Cloud ERP discussions should include Compatibility Pack extension terms as a negotiation lever. SAP's desire to close cloud ERP deals creates an opportunity to negotiate Compatibility Pack extension rights as part of the overall commercial package rather than as a standalone, potentially premium-priced extension.

Business Suite User Packages: The Public Cloud Pricing Change

The shift from FUE (Full User Equivalent) to Business Suite User Packages in SAP S/4HANA Public Cloud has material commercial implications for organisations evaluating the GROW with SAP path.

The Old FUE Model

Under the FUE model, all S/4HANA Public Cloud users were converted to a Full User Equivalent metric based on their access level — professional users counted as 1.0 FUE, limited users as a fraction. Total FUE count determined the subscription price. The model was straightforward to model but became expensive for organisations with large numbers of professional-access users.

The New Business Suite User Package Model

Business Suite User Packages bundle a defined set of user licences with specific module access rights — essentially pre-packaged licence configurations for common business functions. This allows SAP to price the Public Cloud offering in a way that reflects the modules being used, rather than purely the number of users.

The commercial impact depends on the organisation's user distribution and module footprint. For some organisations, the Business Suite packaging will produce a lower per-user cost for common configurations; for others, it will require purchase of packages that include capabilities beyond what is needed, effectively introducing bundling overhead that was not present in the FUE model. Any organisation comparing Public Cloud pricing from before April 2025 to current quotes needs to perform a like-for-like recalculation against the new package structure.

Negotiating SAP Cloud ERP — What Has Changed Commercially

The rebranding to SAP Cloud ERP does not create new negotiating dynamics, but the heightened commercial pressure from SAP to drive cloud adoption does change the leverage calculus. SAP's sales organisation is more motivated to close cloud ERP deals than at any previous point, which creates genuine opportunities for well-prepared buyers.

Leverage Points in the Current Environment

Competition between Private and Public Cloud: SAP's Private Cloud Edition (PCE) and Public Cloud offerings are now positioned as alternative paths within SAP Cloud ERP. Using one as commercial leverage against the other — indicating preference for Public Cloud to drive Private Cloud pricing improvements, or vice versa — is a more viable tactic now than it was when RISE (Private Cloud) was the only cloud narrative.

Third-party maintenance as a timing lever: Indicating credible interest in third-party maintenance support during the evaluation period signals to SAP that the organisation is not committed to SAP's migration timeline. This creates urgency on SAP's side and can unlock migration incentives — including licence credits, reduced implementation fees, or favourable BTP credit bundles — that are not offered to customers who appear committed to the SAP path regardless.

Year-end timing: SAP's fiscal year ends December 31. Structuring SAP Cloud ERP negotiations to target a December close is the most reliable commercial lever available. SAP's account executives and regional leadership have significant incentive to close deals before year-end, and the concessions available in Q4 — on pricing, credit terms, SLA commitments, and contract flexibility — consistently exceed what is available in other quarters.

Contract Terms to Negotiate

Several contract terms in the standard SAP Cloud ERP agreement should be negotiated before signing:

• Annual escalation cap: Negotiate to cap annual subscription increases at a fixed rate (e.g., 3%) or tie to CPI with a stated maximum. Standard contracts allow 3 to 5% increases as SAP's right.
• Exit provisions: Negotiate an explicit right to export data in standard formats, with SAP's migration assistance at no additional cost, upon contract termination.
• BTP credit sufficiency: Model BTP credit consumption for your specific use cases before signing. Negotiate annual credit replenishment terms within the contract rather than purchasing top-ups ad hoc.
• SLA commitments: Secure specific availability SLAs tied to financial penalties. SAP's standard SLAs include credits for downtime, but the thresholds and compensation rates are negotiable.
• Compatibility Pack extension: If Compatibility Pack rights are needed beyond May 2026, negotiate extension terms as part of the cloud ERP commercial package.
• Reversion rights: For Private Cloud Edition, negotiate the right to revert to on-premises licences at a defined price if the business case changes — for example, following a merger or major restructuring.

What Enterprises Should Do Now

Regardless of whether the organisation is currently on RISE with SAP, evaluating SAP Cloud ERP, or still on ECC, the rebranding context creates specific action items:

If currently on RISE with SAP: Review your existing contract terms. The rebranding does not automatically improve your terms, but renewal discussions can be framed around the new commercial environment to negotiate improvements on escalation caps, BTP credits, and SLA commitments. Assess your Compatibility Pack exposure before May 2026.

If evaluating SAP Cloud ERP: Build an independent TCO model that includes the full cost — subscription, BTP credits, line-of-business applications, professional services, and change management — before engaging SAP commercially. Use the FUE-to-Business-Suite-Package transition to force a fresh pricing discussion if previous quotes were based on the old model.

If still on ECC: The rebranding increases the commercial pressure from SAP to commit to SAP Cloud ERP. This is negotiating pressure, not a technical mandate. ECC mainstream support continues through 2027, and third-party maintenance extends the timeline further. Evaluate SAP Cloud ERP on its merits against your specific business requirements, not against SAP's migration urgency narrative.