SAP's push toward cloud ERP has evolved from RISE with SAP (2021) toward broader SAP ERP Cloud packaging (2025). This transition fundamentally changes how SAP software is licensed, contracted, and consumed. This guide examines the licensing structure changes, FUE metrics, transition credit programmes, enterprise contract risks, pricing considerations, and strategic recommendations.
Part of the SAP RISE content series. See also: SAP ERP Private Cloud Licensing | RISE vs Own Infrastructure | RISE Negotiations Guide.
| 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 is 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, services contracted separately |
| User metric | Full User Equivalents (FUEs): pooled capacity | FUEs continue with possible refinements | Named Users (Professional, Limited Professional, ESS): rigid per-type counts |
| 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 through new purchases |
| FUE Aspect | Detail |
|---|---|
| How FUEs work | Contract for a number of FUEs instead of specific named user counts. 1 Advanced user = 1 FUE (power user). 1 Core user = 0.2 FUE (5 Core users per FUE). 1 Self-Service user = 0.033 FUE (30 per FUE). 1 Developer = 0.5 FUE. Pooled model eliminates predicting exact user type counts. Reallocate within pool as needed |
| Mapping legacy users | ECC Professional user = 1 Advanced (1 FUE). ECC Limited Professional = approximately 1 Core (0.2 FUE). ECC Employee Self-Service = 1 Self-Service (0.033 FUE). Many casual users count minimally, potentially lowering cost. Conduct internal usage analysis before negotiation: categorise by actual transaction patterns, not job titles |
| FUE monitoring and true-up | Requires ongoing consumption monitoring. Exceeding contracted FUEs triggers true-up purchase. Negotiate: 10-15% headroom buffer, pre-negotiated tiered pricing for additional FUEs, visibility into SAP measurement methodology to avoid disputes |
| Digital Access in the cloud | Indirect/digital access handled via separate document-based metric. Do not assume cloud = all you can eat. If contract does not explicitly cover digital access for known integrations (CRM, e-commerce, IoT, portals), SAP can claim additional fees. Proactively negotiate inclusion before signing |
| Period | Credit Level | Detail |
|---|---|---|
| 2021-2022 (early adopter) | Up to 90% maintenance credit | $1M annual maintenance = $900K annual credit. Nearly cost-neutral cloud subscription. Most generous terms SAP has offered. Multi-year offsets against subscription fees |
| 2023-2024 (migration programme) | 60-70% credits | SAP Migration and Modernisation Program: existing S/4HANA to cloud received approximately 60% of annual subscription in credits; ECC received approximately 45% of contract value. Some mid-sized customers offered up to 100% for limited time. Significant room to negotiate before programme deadlines |
| 2025-2027 (declining window) | 50-60% or less | Credits declining approximately 10% per year. Customer paying $5M maintenance: 2021 = $4.5M credits; 2026 = $2.5-3M. $1.5-2M annual difference. Over 5-year contract = $7.5-10M in forgone savings. Do not rush solely for incentives. A failed migration costs more than any credit savings |
Use declining credits as one input to your decision, not the sole driver. A customer paying $5M in annual maintenance who delays from 2021 to 2026 loses approximately $1.5-2M in annual credit value, or $7.5-10M over a 5-year contract. However, a failed or hasty migration costs far more than any credit savings. Lock in terms now with a ramp-up deployment schedule aligned with your actual migration timeline.
| Risk | Detail | Mitigation |
|---|---|---|
| Loss of perpetual rights and vendor lock-in | If you stop paying, you lose all access. No perpetual fallback. Exiting RISE after 5 years requires renewing at whatever SAP offers or migrating to a different ERP (massive multi-year undertaking) | Negotiate exit provisions upfront. Some customers have attempted to secure conversion rights to perpetual licences if they do not renew. At minimum, secure favourable renewal terms while you have pre-signature leverage |
| Renewal pricing and escalator risk | Most common contract mistake: focusing only on initial term price. Cloud subscriptions give SAP more leeway at renewal unless restricted | Cap renewal increases (3-5% maximum), lock pricing for at least one renewal term beyond initial period, clarify renewal notification timeline, secure ability to adjust FUE counts at renewal |
| Inability to scale down | Standard RISE contracts are rigid. Commit to set FUEs and system size for full term. Can pay more to scale up but cannot reduce mid-term. Spin off a division = still paying for those FUEs | Negotiate one-time adjustment rights for divestiture/restructuring, contractual clause allowing 10-15% FUE reduction at annual anniversary, carefully size initial subscription |
| Scope gaps and hidden costs | Not everything automatically included. Common additional costs: disaster recovery, advanced security, additional storage, integration services, archiving, high-availability configurations | Review contract line by line. If not listed, not provided. Verify environments (dev/test/prod), DR systems, backup retention, storage, overage costs, network connectivity. Every sales promise must be in the contract |
| 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 = approximately $1.3M/yr | Approximately $1.5M/yr subscription (all-inclusive) | RISE approximately $200K/yr higher but includes infrastructure and automatic upgrades |
| 5-year TCO (same scenario) | Approximately $6.5M + potential hardware refresh $500K-$1M | Approximately $7.5M + one-time migration $1.5-2M | Within plus/minus 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 = approximately $216K/yr = approximately $430/user/yr all-inclusive |
| Public edition | N/A | Approximately $150/FUE/month (less flexibility) | Lower per-FUE cost but less customisation and control |
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 within plus/minus 10% of staying on-premises. But they gain improved capability, avoid technical obsolescence, and eliminate massive upgrade projects. Do not accept SAP's vague "20% TCO saving" claim at face value. Ask SAP to demonstrate it based on your specific numbers. Build 5-year and 10-year TCO comparisons with your actual cost data.
| Recommendation | Detail |
|---|---|
| Model the full TCO before committing | Build 5-year and 10-year comparisons including licence/subscription, infrastructure, internal staff reallocation, migration costs, decommissioning, and growth projections. Do not rely on SAP's TCO calculators. Use independent modelling with actual cost data |
| Lock in transition credits before they decline | Credits declining approximately 10% per year. If committed, lock terms now. Negotiate phased commitment: lock pricing and credits now with ramp-up deployment aligned with actual timeline. Do not sign a contract you are not prepared to execute |
| Negotiate renewal protections aggressively | Cap increases (3-5% maximum), lock pricing for at least one renewal term, secure FUE adjustment rights, clarify notification timelines. Far easier before signing than at renewal when SAP holds leverage |
| Right-size FUEs through usage analysis | Categorise every user by actual transaction patterns (not job titles). Map to FUE categories. Many casual users count minimally. Pre-negotiate tiered pricing for additional FUEs |
| Address digital access explicitly | Ensure contract includes digital access document allocation for all known integrations (CRM, e-commerce, IoT, portals, RPA). If silent on indirect access, SAP can claim additional fees. Next major audit battleground in cloud model |
| Negotiate scale-down provisions | Standard contracts do not allow mid-term reductions. Request adjustment rights for divestitures, restructuring, or annual true-down windows. Even 10-15% reduction at anniversary prevents paying for unneeded capacity |
| Verify scope completeness line by line | Review every component: environments, SLAs, storage, backup, migration services, integration support. If not in the contract, not included. Engage independent advisory to review for gaps. Advisory fee is a fraction of discovering missing components post-signature |
| Plan exit strategy before signing | Understand what happens if you do not renew: perpetual conversion? Data extraction? Notice period? SAP does not offer perpetual conversion by default. Raising the question and documenting the answer creates a reference point |
| Consider the 2027/2030/2033 timeline | ECC support ends 2027 (extended to 2030 at +2%/yr premium). ECC-in-cloud bridge option through 2033 at premium cost. Every year past 2027 increases costs. Use third-party maintenance as negotiation leverage if timeline extends |
RISE (launched 2021) is an all-in-one subscription bundle: S/4HANA Cloud + infrastructure + support + BTP + Signavio + Business Network in one contract. SAP ERP Cloud (evolving 2024-2025) refers to broader cloud ERP offerings that may be packaged more modularly. Both are subscription-based with FUE user metrics. The key question: what exactly is included? Review the bill of materials line by line.
FUEs are SAP's unified user metric. Instead of separate counts of Professional, Limited Professional, and ESS, you purchase a pool: 1 Advanced user = 1 FUE, 1 Core user = 0.2 FUE (5 per FUE), 1 Self-Service user = 0.033 FUE (30 per FUE), 1 Developer = 0.5 FUE. Reallocate between user types without purchasing new categories. SAP monitors consumption and requires true-up if exceeded. Negotiate headroom (10-15% buffer) and pre-agreed pricing for additional FUEs.
Perpetual licences are typically terminated or shelved. You stop paying maintenance but give up usage rights after a migration transition period. If RISE contract ends, you cannot reactivate old licences by default. Negotiate: explicit dual-use during migration, defined migration period, and clarify what happens if you do not renew. This underscores the irreversibility of the cloud commitment.
Yes, but at reduced levels. Credits have declined from up to 90% (2021) to approximately 50-60% by 2025-2026. SAP periodically launches special programmes with enhanced credits tied to fiscal quarter-end deadlines. The declining credits create urgency but should not be the sole driver. A failed migration costs more than any credit savings. Use credits as one input, not the sole decision factor.
Not by default. Standard contracts commit to fixed FUEs for the full 3-5 year term. You can add capacity but cannot reduce mid-term. Negotiate: one-time adjustment rights for divestitures or major organisational changes, annual true-down windows (10-15% reduction), and careful initial sizing since you cannot remove capacity once committed.
Not entirely. Traditional named user audits are replaced by FUE consumption monitoring. SAP checks active accounts, types, and whether they align with purchased FUEs. The biggest cloud compliance risk is digital access/indirect use: if the contract does not cover documents from external systems, SAP can claim additional fees. Cloud does not equal "all you can eat." Clarify integration coverage and measurement methodology.
ECC support ends 2027, with extended maintenance to 2030 at +2%/year premium. SAP's "ERP Private Edition Transition Option" runs ECC on SAP's private cloud through 2033 at premium cost. Only available to customers who migrated ECC to HANA and SAP's private cloud by 2030. It is a last resort, not a long-term strategy. Every year past 2027 increases costs through maintenance premiums or expensive bridge contracts.
Redress Compliance provides independent SAP advisory: TCO modelling, RISE and Cloud ERP contract negotiation, transition credit maximisation, renewal protection, and informed licensing decisions with no vendor conflicts of interest. 100% vendor-independent. Fixed-fee engagement.
SAP RISE Advisory ServicesIndependent SAP advisory. RISE evaluation. Cloud ERP contract negotiation. FUE optimisation. Transition credits. 100% vendor-independent, fixed-fee engagement.