SAP S/4HANA Cloud (RISE) vs On-Premise Licensing: Key Differences and How to Choose

Why This Decision Matters More Than Any Other SAP Commercial Choice

SAP's transition from perpetual on-premise licensing to subscription-based cloud models is not a product upgrade — it is a fundamental restructuring of how SAP monetises its installed base. For customers, this means the commercial implications of choosing between RISE with SAP and on-premise S/4HANA extend far beyond the first year's bill. They reshape your cost trajectory, your negotiation leverage, and your exit options for the next ten to fifteen years.

I have advised on over eighty indirect access disputes and hundreds of SAP contract negotiations. The organisations that make this decision well — who understand what they are actually buying, what they are giving up, and where SAP's commercial interests diverge from their own — consistently achieve outcomes that are materially better than those who simply respond to SAP's sales cycle. This guide gives you the analytical framework to be in the first group.

The Fundamental Licensing Model Difference

On-premise S/4HANA licences are perpetual. Once purchased, you own the right to use that version of the software indefinitely, regardless of whether you continue paying SAP annual support. SAP annual support is approximately 22% of your net licence value per year — so a $5 million licence investment carries $1.1 million in annual support costs from day one. That support fee covers access to patches, updates, legal change packages, and SAP's support infrastructure. You are not paying for the right to use the software; you are paying for support services.

RISE with SAP operates on a fundamentally different basis. You do not purchase a licence — you subscribe to a service. RISE is a bundled subscription that combines S/4HANA Cloud Private Edition software, infrastructure hosting on a hyperscaler of your choice (AWS, Azure, or Google Cloud), application management services, and access to a defined set of SAP Business Technology Platform (BTP) capabilities. The contract is typically a minimum three-year term with annual payments expressed as a total cost covering all bundled components.

What RISE with SAP Actually Includes — and What It Does Not

SAP's sales material for RISE with SAP is deliberately comprehensive in how it describes what is included, without always being precise about what falls outside the bundle. Based on our contract reviews, RISE with SAP genuinely includes: S/4HANA Cloud Private Edition software, infrastructure hosting (SAP manages the SLA, the hyperscaler provides the servers), SAP Enterprise Support, a defined allocation of BTP CPEA credits for platform consumption, migration tooling and methodology access, and basic application lifecycle management.

What RISE with SAP does not include — despite frequently being positioned as included in sales conversations — is: SAP SuccessFactors, SAP Ariba, SAP Concur, SAP Fieldglass, SAP Analytics Cloud beyond minimal embedded access, additional BTP consumption beyond the contracted CPEA credit allocation, and any line-of-business cloud applications that were not part of the original deal. Each of these is a separate subscription requiring separate negotiation.

The Cost Structure Comparison

On-premise S/4HANA licensing creates a capital expenditure profile: a large upfront licence purchase, followed by predictable annual support payments at 22% of net licence value. For a 2,000-user deployment, a realistic licence investment is $8 million to $15 million at negotiated rates (SAP's list pricing is never the starting point for a serious negotiation), followed by $1.76 million to $3.3 million in annual support costs. Infrastructure, hardware, and internal IT operations are separate costs borne entirely by the customer.

RISE with SAP converts this to an operational expenditure model. Pricing is typically expressed per Full User Equivalent (FUE) per month. SAP uses the FUE metric in cloud contracts, where users are classified by role: a Professional (Advanced) user equals 1.0 FUE, a Core user equals approximately 0.2 FUE, and a Self-Service user equals approximately 0.033 FUE. Published list pricing for RISE Private Edition runs approximately $170 to $180 per FUE per month, but contracted pricing with proper negotiation typically lands 25% to 45% below list for engagements above 100 FUEs.

The S/4HANA Migration Changes Your Licence Baseline — Always

One of the most commercially significant and least discussed aspects of migrating to S/4HANA is that the migration invariably changes your licence baseline. This is true whether you are migrating on-premise or going to RISE.

In SAP ECC, user classification uses a different and far more complex taxonomy than S/4HANA. Migrating to S/4HANA requires a licence conversion exercise — a process SAP calls a licence measurement service — that reclassifies your existing users against S/4HANA user types. The reclassification almost always results in SAP identifying additional licence requirements, because S/4HANA's user metric is applied more broadly and the access patterns of your workforce are compared against a cleaner, more strictly enforced user type hierarchy.

Additionally, S/4HANA introduces Digital Access licensing — a document-based charging model for indirect access via third-party systems. Under Digital Access, SAP counts specific document types created by external applications (e.g., a CRM system creating a Sales Order in S/4HANA). This is measured using the Digital Documents Licence Compliance (DDLC) metric. Organisations with complex integration landscapes — which includes most enterprises — need to conduct a DDLC impact assessment before signing any S/4HANA migration contract, whether on-premise or RISE. Failing to do so regularly results in Digital Access claims of six to eight figures at audit.

Infrastructure, Operations, and Control

Under on-premise deployment, the organisation controls every layer of the technology stack below the application. Hardware procurement, network architecture, disaster recovery configuration, backup scheduling, patching cadence, and security posture are all owned by the customer. This delivers maximum control and flexibility. It also means that your IT operations team carries the full burden of managing an enterprise ERP infrastructure, and your capital budget must absorb hardware refresh cycles every four to six years.

RISE with SAP transfers infrastructure responsibility to SAP and its hyperscaler partners. SAP defines and manages the hosting SLA, the technical upgrade schedule, and the application management scope. The customer retains control over business configuration, data, and application customisation. The trade-off is that the customer loses direct control over infrastructure decisions, is subject to SAP's release cadence for updates and upgrades, and must accept SAP's choice of management processes within the contracted scope.

For organisations with mature internal IT operations teams and complex, highly customised SAP landscapes, the loss of control that comes with RISE is frequently underestimated. SAP's managed service quality varies significantly across geographies and client sizes, and the RISE contract's SLA structure leaves material gaps in accountability that experienced advisors can identify and address during contract negotiation.

Customisation and Clean Core

On-premise S/4HANA provides full access to the ABAP development environment. Customers can write custom code, build Z-objects, create custom transactions, and modify the system extensively. This flexibility is the primary technical reason why some organisations — particularly those in heavily regulated or operationally complex industries — continue to prefer on-premise deployment despite SAP's commercial pressure toward RISE.

RISE with SAP Private Edition supports ABAP development and custom code, giving it a significant advantage over S/4HANA Cloud Public Edition (which restricts modifications to SAP's approved extensibility framework). However, SAP's commercial pressure in RISE contracts increasingly includes "clean core" commitments — effectively contractual constraints on the extent of customisation SAP will support under the managed service. The clean core narrative serves SAP's operational interests (fewer custom landscapes are cheaper to manage) but may not align with your business requirements.

Negotiation Leverage: Where Each Model Creates and Destroys Optionality

On-premise perpetual licensing creates negotiation leverage at renewal time because your support costs are fixed as a percentage of a static licence value. The leverage comes from potential third-party maintenance providers — companies like Rimini Street or Spinnaker Support — who offer support services for on-premise SAP licences at approximately 50% of SAP's support rate. This optionality constrains SAP's ability to raise support costs and gives buyers genuine leverage in support renewal negotiations.

RISE with SAP eliminates this leverage. Support is embedded in the subscription fee, and third-party maintenance is not an option for RISE deployments. At renewal, your negotiation leverage depends almost entirely on the alternatives available to you — migration cost, switching cost to a competing ERP, and the quality of your relationship with SAP's account team. Organisations that have not cultivated these alternatives typically face aggressive renewal pricing at the end of their first RISE term.

The best commercial outcomes in RISE negotiations come from organisations that have done three things: completed an honest total cost of ownership model covering the full contract term and renewal scenarios, identified credible competitive alternatives and made SAP aware of them, and engaged an independent advisor with current SAP deal desk benchmarking data before entering the negotiation. SAP's published list pricing is the ceiling, not the floor.

How to Choose: A Decision Framework

The choice between RISE and on-premise is not primarily a technology decision — it is a commercial and operational one. The following considerations, drawn from advisory experience across more than eighty SAP migration engagements, should anchor your analysis.

• Customisation depth: If your S/4HANA landscape requires extensive ABAP customisation or industry-specific modifications, on-premise or RISE Private Edition (with carefully negotiated clean core commitments) is appropriate. Public Cloud is not.
• Integration complexity: If you have a high volume of third-party systems creating documents in SAP, conduct a DDLC assessment before any migration decision. The Digital Access liability can be the largest single cost item in the migration — and it exists regardless of whether you choose RISE or on-premise.
• Internal IT capability: If your IT organisation lacks the capacity to manage enterprise ERP infrastructure reliably, the managed service component of RISE has genuine operational value. If your IT team is strong, you are paying a premium for a service you can perform more cheaply.
• Total cost of ownership horizon: Run a seven-year TCO model, not a three-year one. RISE pricing typically escalates at renewal, and the escalation rate is rarely contractually capped in initial agreements. On-premise support costs are more predictable over a long horizon.
• Exit optionality: RISE contracts are notoriously difficult to exit early. Model the exit costs before signing, and negotiate contractual protections — data portability, exit assistance, and reasonable termination rights — as part of the initial deal.

The Role of Independent Advice

SAP's deal structure for RISE is sophisticated and designed to accelerate decision-making under commercial pressure. The 2027 ECC maintenance deadline is a real commercial constraint, but SAP's account teams routinely present it as more urgent and less flexible than it actually is. Independent advisors with no SAP partner affiliation and current deal benchmarking data consistently help clients achieve 25% to 45% better commercial outcomes than those negotiating directly — and the advisory investment is typically recovered in the first year of improved pricing.

Redress Compliance is 100% buyer-side, has no SAP reseller or implementation partner relationships, and has completed over 500 SAP advisory engagements. Our RISE advisory practice specifically covers deal structuring, pricing benchmarking, DDLC assessment, and contract negotiation support. If you are evaluating this decision, we welcome a confidential conversation.