Moving to RISE means your perpetual SAP licences are shelved, your maintenance stops, and your ownership rights disappear. This guide explains exactly what happens to your installed base, how to maximise conversion credits, negotiate dual-use periods, protect against lock-in, and avoid the most expensive mistakes enterprises make during the transition.
This article is part of the RISE with SAP vs. Traditional Licensing pillar series. Related guides include RISE vs. BYOL Contractual Differences, RISE vs. Own Infrastructure Cost Comparison, and RISE Negotiation Guide for CIOs.
Under traditional SAP licensing, your organisation owns perpetual rights to use SAP software indefinitely. Even if you stop paying maintenance. You made a capital investment, and that asset sits on your balance sheet. You can drop support, run unsupported, switch to third-party maintenance, or simply leave the software installed while you migrate at your own pace. The licence is yours.
RISE with SAP replaces this model entirely. You no longer own anything. You pay a recurring subscription for access to S/4HANA Cloud, infrastructure, and support, bundled into a single annual fee measured in Full User Equivalents (FUEs). When the subscription ends, so does your access. There is no residual perpetual right, no fallback to an unsupported on-premises installation, and no option to run the software without paying.
No return path. Once shelved, reinstating perpetual licences requires a new purchase, typically at current list prices. SAP does not offer automatic reversion from RISE to on-premises.
The single most consequential decision in a RISE migration is not the infrastructure choice or the FUE sizing. It is the decision to surrender perpetual licence rights. Every other element of the deal can be renegotiated at renewal. Perpetual rights, once surrendered, are gone permanently. CIOs must understand this before signing.
When you execute a RISE contract, the existing perpetual licences for any SAP products replaced by the RISE subscription are formally shelved. This is not optional. SAP requires licence termination for products whose functionality is now delivered through RISE.
SAP offers conversion credits, discounts applied to the RISE subscription price, to incentivise migration. These credits partially compensate for the perpetual licences and pre-paid maintenance you are surrendering. However, the credit amount varies enormously based on timing, deal size, and negotiation skill.
| Credit Type | Description | Typical Range |
|---|---|---|
| Maintenance pro-rata credit | Refund for unused portion of pre-paid annual maintenance at the time RISE begins | Pro-rata of remaining months. Negotiate to align RISE start with maintenance renewal to maximise this. |
| Licence trade-in credit | Discount applied to RISE subscription reflecting the value of surrendered perpetual licences | 20-60% of original licence value (varies by timing and deal size) |
| Shelfware credit | Additional credit for unused/over-purchased licences that were never deployed | Highly variable: 0% to 30% of shelfware value. Must be explicitly negotiated. SAP does not offer this proactively. |
| Early-mover incentive | Additional discount for enterprises migrating before the 2027 ECC support deadline | Declining over time: generous in 2021-2023, moderate in 2024-2025, minimal from 2026 onwards |
Credits are applied as a reduction to the annual RISE subscription fee, typically for the initial contract term (3 to 5 years). They do not carry over to renewal terms. Renewal pricing resets to SAP's standard rates unless explicitly negotiated.
Case study: Global manufacturer, $4.5M credit on $5M maintenance base (2021 early mover). A large manufacturer paying $5M annually in SAP maintenance negotiated a RISE deal in 2021. The company held $10M in shelfware and was an early adopter of the RISE programme. SAP offered a credit package equivalent to approximately 90% of one year's maintenance ($4.5M) plus partial recognition of the shelfware value. The first-year RISE subscription was nearly cost-neutral. Over the 5-year contract term, the manufacturer's total RISE cost was approximately 15% higher than the legacy maintenance-only cost, but included S/4HANA Cloud, infrastructure, and managed services that would have cost significantly more if procured separately.
Timing matters enormously. A comparable company approaching SAP in 2025 with a similar profile received credits equivalent to only 55% of annual maintenance and zero shelfware recognition, resulting in a first-year cost increase of $2.2M. The credit differential alone can amount to millions over the contract term.
Come to the negotiation with a complete inventory of every perpetual licence you hold, including shelfware. Document the original purchase price, current maintenance cost, and deployment status (active, partially used, unused). SAP's commercial team has flexibility to offer credits within approval limits, but they will not volunteer maximum discounts without pressure.
Present your sunk investment as a concrete number and make it clear that a RISE deal without meaningful credit recognition is not commercially viable. The strongest leverage exists when you have credible alternatives: staying on-premises with third-party support, migrating to a competing ERP, or deploying S/4HANA on your own infrastructure under traditional licensing.
Many SAP customers carry significant shelfware, licences purchased years ago that were never fully deployed. Under traditional licensing, shelfware was an annoyance (you paid maintenance on unused software) but not a crisis. You could drop maintenance on unused licences to reduce costs, or redeploy them when needs changed.
Under RISE, shelfware becomes a total loss. Unused licences are shelved alongside active ones, with no residual value. The maintenance you paid on shelfware for years disappears with no compensation unless you explicitly negotiate shelfware credits into the RISE deal.
High risk: Large shelfware + late migration. Enterprises with substantial shelfware that migrate to RISE after 2025 face the worst economics: high sunk costs, declining SAP credit generosity, and no residual value from unused licences. The shelfware investment is entirely written off.
Medium risk: Moderate shelfware + good timing. Enterprises that migrated in 2022-2024 and had moderate shelfware typically negotiated partial recognition. Some credit was applied, but the full historical investment was not recovered.
Pre-negotiation strategy. Before approaching SAP for a RISE deal, conduct a thorough licence reconciliation. Identify every licence that is unused or underutilised. Drop maintenance on genuine shelfware before the RISE negotiation. This reduces your annual maintenance baseline, which SAP uses as a reference point for pricing the subscription. A lower baseline means a lower RISE price target, and the savings from dropping shelfware maintenance compound immediately while you prepare for the transition.
The loss of perpetual rights is the most significant strategic risk of RISE. Under traditional licensing, dissatisfied SAP customers could drop maintenance, freeze their systems, and migrate away at their own pace, sometimes over years. Under RISE, when the subscription ends, everything stops.
| Risk | Description | Mitigation |
|---|---|---|
| Renewal price escalation | SAP holds maximum leverage at renewal. You cannot walk away without losing your ERP. | Negotiate renewal price caps (e.g., max 3-5% annual increase) in the initial contract |
| No downsize flexibility | Standard RISE contracts prohibit reducing FUE counts mid-term | Negotiate mid-term flex-down rights (e.g., 10-15% reduction allowed after year 2) |
| No conversion to perpetual | SAP does not offer automatic reversion from RISE to on-premises licensing | Negotiate a conversion-to-perpetual option. Even if priced, having the right documented creates leverage. |
| Data extraction complexity | Exiting RISE requires extracting all data from SAP's managed cloud environment | Include explicit data portability rights and a minimum 6-month transition period in the contract |
| M&A scenarios | Divestitures and acquisitions can change your FUE requirements dramatically | Include M&A clauses allowing subscription adjustments (up and down) upon corporate restructuring |
Plan for the exit even if you never intend to leave. The protections you negotiate at signing, renewal caps, flex-down rights, conversion options, data portability, are the only leverage you will have at renewal. Once you are live on RISE with no perpetual fallback, SAP's negotiating position is structurally stronger than yours. The time to address this imbalance is before you sign, not when the renewal notice arrives.
During the migration from ECC or on-premises S/4HANA to RISE, most enterprises require a period of parallel operation, running both the legacy system and the new RISE environment simultaneously for data validation, user acceptance testing, and phased cutover.
SAP typically permits a dual-use period, but the default offer is often too short for complex enterprise migrations. A 3-month dual-use window is standard in SAP's initial proposal. Enterprises with large, customised ECC landscapes routinely need 6 to 12 months for a safe transition.
Key provisions to negotiate for the dual-use period:
The financial case for RISE is often presented by SAP as maintenance-cost-neutral. Your existing annual maintenance payment simply redirects to the RISE subscription. In practice, the economics are more complex.
| Cost Element | Traditional (On-Prem) | RISE with SAP |
|---|---|---|
| Licence ownership | Perpetual: sunk cost already paid | None: subscription only |
| Annual maintenance | 20-22% of licence value | Eliminated (included in subscription) |
| Infrastructure | Separate cost (on-prem or IaaS) | Included in subscription |
| Basis support / operations | Internal staff or outsourced | Included in subscription (managed service) |
| Upgrade costs | Major project every 5-7 years | Included (continuous updates) |
| Typical Year-1 net impact | Baseline | +10% to +40% above maintenance-only cost (offset by infrastructure and operations savings) |
The honest analysis must compare total run-rate cost (maintenance + infrastructure + operations + periodic upgrades) against the RISE subscription, not just maintenance alone. When infrastructure and operations savings are included, RISE can be cost-neutral or even cost-positive for enterprises with high on-premises operations costs. Conversely, enterprises with efficient, low-cost infrastructure (e.g., well-optimised hyperscaler deployments) often find RISE 15-30% more expensive on a like-for-like basis. Model both scenarios with your actual cost data before committing.
Perpetual licences for SAP products replaced by the RISE subscription are formally shelved, deactivated and removed from productive use. Maintenance payments on those licences stop immediately. You lose the perpetual right to use the software. After the dual-use grace period expires, you cannot run the legacy system in production. Licences for SAP products not covered by RISE (e.g., standalone BW, BusinessObjects) remain unaffected and continue under their existing maintenance agreements.
SAP typically offers conversion credits, discounts applied to the RISE subscription to partially compensate for surrendered perpetual licences and pre-paid maintenance. The credit amount varies widely: early movers (2021-2023) received credits covering 70-100% of first-year maintenance cost. Enterprises migrating in 2025-2026 typically see 30-55%. Shelfware credits are not offered proactively but can be negotiated. Come prepared with a complete inventory of licences, purchase prices, and maintenance history to maximise your credit position.
Yes. SAP permits a dual-use grace period for parallel operation during migration. However, the default offer is often only 3 months. Enterprises with complex landscapes should negotiate 6 to 12 months, with extension clauses if migration encounters delays. Ensure the contract states explicitly that no additional licence or maintenance fees apply during the dual-use period, and include rollback rights in case the RISE deployment does not meet acceptance criteria.
Shelfware is shelved alongside active licences, with no residual value unless you negotiate shelfware credits into the RISE deal. The maintenance you paid on shelfware for years is a sunk cost. To mitigate this: drop maintenance on genuine shelfware before negotiating RISE (reducing your baseline cost), and present the historical shelfware investment as explicit leverage for credit negotiation.
Not automatically. Once perpetual licences are shelved under a RISE contract, they cannot be reactivated. If you choose not to renew RISE, you would need to purchase new on-premises licences at current list prices, a significant capital expenditure. Some enterprises negotiate a conversion-to-perpetual option in the initial RISE contract, giving them the contractual right (though typically at a cost) to convert to on-premises licensing at the end of the term. This option must be explicitly negotiated. SAP does not offer it by default.
Align the RISE subscription start date with the end of your SAP maintenance renewal cycle. If your maintenance renews in January and you sign RISE in March, you have paid for 10 months of unused maintenance. Negotiate a pro-rata credit for the remaining maintenance period, or time the RISE start to coincide with the maintenance expiry. Also ensure the dual-use period is covered within the existing maintenance term so you are not paying maintenance and RISE subscription simultaneously for the parallel run.
Generally, earlier migration secures better credits. SAP's incentive programmes have become less generous over time as the 2027 ECC support deadline approaches and SAP's urgency to attract new RISE customers diminishes. Enterprises that delay until 2026-2027 will face reduced credit offers, higher subscription pricing, and the pressure of the ECC end-of-support deadline. If you are committed to SAP long-term, modelling the economics of migrating now versus waiting almost always favours earlier action. The credit differential alone can amount to millions over the contract term.