RISE With SAP vs SAP ERP Cloud — Licensing Structure Comparison
| Dimension | RISE With SAP (2021+) | SAP ERP Cloud (2025+) | Traditional On-Premises |
|---|---|---|---|
| Model | All-in-one subscription bundle | Subscription — potentially more modular packaging | Perpetual licence + 22 % annual maintenance |
| What's included | S/4HANA Cloud + infrastructure + support + BTP starter + Signavio + Business Network | S/4HANA Cloud + infrastructure + support — additional components may be modular | Software licence only — infrastructure, support, and services contracted separately |
| User metric | Full User Equivalents (FUEs) — pooled capacity | FUEs continue — possible refinements in packaging | Named Users (Professional, Limited Professional, ESS) — rigid per-type counts |
| Infrastructure | SAP-managed (hyperscaler or SAP DC) | SAP-managed or customer-managed options emerging | Customer-managed — hardware, DC, and admin costs |
| Budget treatment | OpEx — recurring annual subscription | OpEx — recurring subscription | CapEx (licence) + OpEx (maintenance + infrastructure) |
| Perpetual rights | None — usage rights end when subscription ends | None — subscription model | Yes — indefinite right to use purchased version |
| Scalability | Scale up: yes (add FUEs). Scale down: no mid-term reduction | TBD — SAP may introduce more flexibility | Fixed — owned licences; adjustments only through new purchases |
Full User Equivalents (FUEs) — The New User Metric
How FUEs Work
Under RISE and S/4HANA Cloud licensing, you contract for a number of Full User Equivalents (FUEs) instead of specific named user counts. Different user types consume different fractions: 1 Advanced user = 1 FUE (power user, equivalent to old Professional), 1 Core user = 0.2 FUE (5 Core users per FUE), 1 Self-Service user = 0.033 FUE (30 Self-Service users per FUE), 1 Developer = 0.5 FUE. This pooled capacity model eliminates the need to predict exact user type counts upfront. You purchase a pool and allocate across user roles as needed — if a department needs fewer Advanced users but more Core users, you simply reallocate within the pool without purchasing new licence types.
Mapping Legacy Users to FUEs
Companies transitioning from ECC must map old named user licences to FUE categories. SAP guidance: one ECC Professional user → one Advanced user (1 FUE), one ECC Limited Professional → approximately one Core user (0.2 FUE), one Employee Self-Service user → one Self-Service user (0.033 FUE). This mapping can dramatically change the number of "units" required. Many casual ECC users count very minimally in FUE terms — potentially lowering cost. However, if not optimised, heavy-user organisations may find FUE consumption higher than expected. Conduct internal usage analysis before negotiation — categorise every user by actual transaction patterns (not job title) to determine the optimal FUE mix.
FUE Monitoring and True-Up
The FUE model requires ongoing consumption monitoring. If your actual user mix exceeds contracted FUEs (e.g., 110 FUEs consumed against 100 purchased), you must true-up by purchasing additional capacity. SAP monitors usage — this replaces traditional named user audits but introduces its own compliance requirement. Negotiate: (a) headroom buffer — 10–15 % above expected usage to accommodate growth, (b) pre-negotiated tiered pricing for additional FUEs (so you know the cost of growth before it happens), and (c) visibility into SAP's measurement methodology — understand exactly how SAP calculates FUE consumption to avoid disputes.
Digital Access in the Cloud
Indirect/digital access — where external systems create SAP transactions — is handled via a separate document-based metric in S/4HANA Cloud. SAP often offers to include a volume of document licences or a conversion to the digital access model as part of RISE contracts. Do not assume "cloud = all you can eat" — if your contract does not explicitly cover digital access for known integrations (CRM, e-commerce, IoT, portals), SAP can claim additional fees for documents created by non-SAP systems. Proactively negotiate inclusion of digital access for all identified integration points before signing.
Transition Credits and Conversion Programmes
Up to 90 % Maintenance Credit
When RISE launched, SAP offered up to 90 % of annual maintenance fees as credit toward the RISE subscription. A customer paying $1M in annual maintenance could receive $900K in annual credit — making the cloud subscription nearly cost-neutral compared to maintenance. These were the most generous terms SAP has offered. Customers who locked in during this window secured the best financial position for cloud transition. The credits were designed as multi-year offsets against subscription fees, effectively eliminating the "double payment" problem during migration.
60–70 % Credits — Special Programmes
By 2024, standard maintenance credits had declined to approximately 60–70 %. SAP's "Rise with SAP Migration and Modernisation Program" offered special incentives through end of 2024: organisations moving existing S/4HANA on-premises to cloud received ~60 % of annual subscription value in credits; those moving from ECC received ~45 % of contract value. Some mid-sized customers were offered up to 100 % credit for a limited time (effectively a free first year). These credits could offset both subscription fees and migration services. The takeaway: there was significant room to negotiate, especially before published programme deadlines.
50–60 % or Less — Urgency Increases
Credits continue to decline at approximately 10 % per year. By 2025–2026, standard maintenance credits may be 50–60 % or lower. A customer paying $5M in annual maintenance who moved in 2021 might have received $4.5M in credits; the same customer waiting until 2026 might receive only $2.5–3M — a $1.5–2M annual difference. Multiplied over a 5-year contract, the cost of delay is $7.5–10M. SAP's strategy is deliberate: front-load rewards for early movers. However, don't rush solely for incentives — a failed or hasty migration costs more than any credit savings. Use the declining credits as one input to your decision, not the sole driver.
Enterprise Contract Risks in the Cloud Model
Loss of Perpetual Rights and Vendor Lock-In
In the on-premises model, a perpetual licence gives you indefinite usage rights — even without support payments. In the subscription model, if you stop paying, you lose all access. No perpetual fallback exists. This dramatically raises vendor lock-in: exiting RISE after 5 years requires either renewing (at whatever terms SAP offers) or migrating to an entirely different ERP (a massive, multi-year undertaking). SAP is betting on lifetime subscriptions. Mitigation: negotiate exit provisions upfront — some customers have attempted to secure conversion rights to perpetual licences if they do not renew. SAP does not offer this by default, but the discussion is worth having. At minimum, secure favourable renewal terms while you have pre-signature leverage.
Renewal Pricing and Escalator Risk
The most common contract mistake: focusing only on the initial term price. Traditional maintenance increased at predictable rates (CPI or fixed percentage). Cloud subscriptions give SAP more leeway at renewal unless the contract restricts it. Always negotiate price protections: (a) cap renewal increases (3–5 % maximum per year), (b) lock pricing for at least one renewal term beyond the initial period, (c) clarify the renewal notification timeline and your rights if you choose not to renew, (d) secure the ability to adjust (reduce) FUE counts at renewal for known scenarios (divestitures, downsising). Without these protections, you could face a 20 %+ price increase in Year 4 with no alternative but to pay or begin a multi-year migration away from SAP. Treat renewal as part of the deal you are making now — lock in what you can while you hold negotiating leverage.
Inability to Scale Down
Unlike elastic cloud services, standard RISE contracts are "rigid up and down". You commit to a set number of FUEs and system size for the full term. You can pay more to scale up (add FUEs, storage), but you cannot reduce commitments mid-term. If you spin off a division that had 20 % of SAP users, you are still paying for those FUEs for the remainder of the term. Negotiate: (a) one-time adjustment rights for divestiture or organisational restructuring, (b) a contractual clause allowing FUE reduction at annual anniversary points (even if limited to 10–15 %), and (c) carefully size the initial subscription — do not overbuy "just in case" because you cannot trim later. Start with actual need and pre-negotiate tiered pricing for growth.
Scope Gaps and Hidden Costs
A RISE contract is complex — not everything is automatically included. Common items that require additional cost: disaster recovery environments, advanced security/compliance features, additional storage beyond baseline allocation, specific integration services, archiving solutions, and high-availability configurations (99.9 % SLA vs standard 99.7 %). Review the contract line by line and confirm every component. If it is not listed, it is not provided. Verify: number of environments (dev, test, prod), DR systems, backup retention, included storage, overage costs, network connectivity responsibilities, and any migration services. Ensure every promise made during sales ("we'll help migrate your data," "that extra sandbox is possible") is written into the contract. Post-signature change requests for missing pieces are extremely expensive.
Pricing Considerations and TCO Modelling
| Scenario | On-Premises (Status Quo) | RISE With SAP | Key Difference |
|---|---|---|---|
| Mid-sized enterprise (500 users) | $5M licence (sunk) + $1.1M/yr maintenance + $200K/yr infrastructure = ~$1.3M/yr | ~$1.5M/yr subscription (all-inclusive) | RISE ~$200K/yr higher, but includes infrastructure and automatic upgrades |
| 5-year TCO (same scenario) | ~$6.5M + potential hardware refresh $500K–$1M | ~$7.5M + one-time migration $1.5–2M | Within ±10 % when all factors included; RISE avoids hardware refresh |
| Per-FUE monthly cost | N/A (named user model) | $170–$200/FUE/month (private edition enterprise) | 100 FUEs covering 500 users ≈ $216K/yr ≈ $430/user/yr all-inclusive |
| Large enterprise (thousands of users) | $5M+/yr maintenance | $5–10M+/yr subscription | Higher absolute cost; offset by eliminated infrastructure and upgrade projects |
| Public edition | N/A | ~$150/FUE/month (less flexibility) | Lower per-FUE cost but less customisation and control |
"Cloud ERP is not automatically a cheaper ERP. It shifts costs around — expect higher software subscription spending offset by lower infrastructure and internal support costs. Over a 5–10 year horizon, many enterprises find the total cost difference is within ±10 % of staying on-premises. But they gain improved capability, avoid technical obsolescence, and eliminate the massive upgrade projects that ECC requires every 5–7 years. Don't accept SAP's vague '20 % TCO saving' claim at face value — ask SAP to demonstrate it based on your specific numbers." — Redress Compliance Advisory
Strategic Recommendations
✅ Independent CIO Recommendations for SAP Cloud Transition
- Model the full TCO before committing: Build a 5-year and 10-year Total Cost of Ownership comparison including licence/subscription fees, infrastructure costs, internal staff reallocation, migration project costs, decommissioning expenses, and growth projections. Do not rely on SAP's TCO calculators — they are designed to favour the RISE outcome. Use independent modelling with your actual cost data
- Lock in transition credits before they decline further: Credits are declining approximately 10 % per year. If you are committed to moving, locking in terms now secures better financial positioning. However, do not sign a contract you are not prepared to execute — credits are worthless if the migration fails. Negotiate a phased commitment: lock pricing and credits now with a ramp-up deployment schedule that aligns with your actual migration timeline
- Negotiate renewal protections aggressively: Cap renewal price increases (3–5 % maximum), lock pricing for at least one renewal term, secure FUE adjustment rights at renewal, and clarify notification timelines. These protections are far easier to obtain before signing than at renewal when SAP holds the leverage
- Right-size FUEs through usage analysis: Conduct internal analysis to categorise every user by actual transaction patterns (not job titles). Map to FUE categories to determine the optimal mix before negotiation. Many organisations discover that casual users count minimally in FUE terms — potentially reducing the required FUE count significantly. Pre-negotiate tiered pricing for additional FUEs to manage growth cost-effectively
- Address digital access explicitly: Ensure the RISE or Cloud ERP contract includes digital access document allocation for all known integrations (CRM, e-commerce, IoT, portals, RPA). If the contract is silent on indirect access, SAP can claim additional fees for documents created by non-SAP systems. This is the next major audit battleground in the cloud model
- Negotiate scale-down provisions: Standard RISE contracts do not allow mid-term reductions. Request adjustment rights for divestitures, organisational restructuring, or annual true-down windows. Even limited flexibility (10–15 % reduction at annual anniversary) prevents paying for capacity you no longer need
- Verify scope completeness line by line: Review every contract component: environments (dev, test, prod, DR), SLAs (99.7 % vs 99.9 %), storage allocation, backup retention, migration services, and integration support. If something is not in the contract, it is not included. Engage independent SAP licensing advisory to review the contract for gaps and omissions — the advisory fee is a fraction of the cost of discovering missing components post-signature
- Plan exit strategy before signing: Understand what happens if you do not renew: can you convert to perpetual licences? Can you extract your data in a standard format? What is the contractual notice period? SAP does not offer perpetual conversion by default — but raising the question and documenting the answer creates a reference point for future negotiations
- Consider the 2027/2030/2033 timeline: ECC support ends 2027 (extended maintenance to 2030 at +2 %/year premium). SAP's ECC-in-cloud bridge option runs through 2033 at premium cost. Factor these hard deadlines into your roadmap — every year past 2027 increases costs. Use third-party maintenance as negotiation leverage if your timeline extends beyond 2027