SAP Licence Conversion Options
For on-premise SAP customers transitioning to S/4HANA, SAP has provided three main conversion routes. Each carries different implications for cost, flexibility, and long-term licensing structure.
| Conversion Path | How It Works | Advantages | Disadvantages |
|---|---|---|---|
| Product Conversion | Line-by-line conversion of current ECC licences to S/4HANA equivalents; allows phased migration with some parts converted while ECC licences remain for others | Least disruptive; carries forward existing contract structure and discounts; allows phased approach | Largely discontinued since 2023 — SAP removed the primary product conversion SKU from its price list; unavailable for customers who did not act early |
| Contract Conversion | Terminate or sunset old ECC licence agreements and purchase new S/4HANA licences; SAP calculates credit for existing licence value to offset new costs | Clean slate — simplifies complex legacy contracts; opportunity to eliminate shelfware; restructure licensing completely | Credit percentages diminishing (90% → 70–80% → lower); requires careful analysis to ensure functional coverage; forces renegotiation of all terms |
| RISE with SAP (Cloud) | Subscription bundle including S/4HANA software, cloud infrastructure, and services; shifts from perpetual licences + maintenance to term-based subscription | OPEX model; SAP manages infrastructure; includes credits/incentives for existing investments; aligns with cloud-first strategy | Cedes infrastructure control; subscription resets licensing entirely; different metrics (consumption, user bands); periodic renewal required |
Product conversion, when available, was the least disruptive path and protected historic discounts. Contract conversion provides the opportunity for a fresh start but requires maximising credit value before percentages drop further. RISE aligns with cloud strategy but fundamentally changes the licensing and operational model. See S/4HANA Cloud vs On-Premise Licensing.
Key Challenges in Licence Migration
| Challenge | Why It Matters | Risk if Unmanaged |
|---|---|---|
| Diminishing credit value | SAP reduces the percentage of existing licence value that can be credited toward S/4HANA each year | Delaying to 2027 may result in only 50–60% credit, leaving significant existing investment unrecovered |
| Functional coverage gaps | S/4HANA is not a one-to-one match with ECC — modules are merged, split, or new; licence mapping requires meticulous analysis | Missing a component during conversion means purchasing new licences later at unfavourable pricing |
| Dual environment costs | Running ECC and S/4HANA in parallel during testing, phased rollouts, or extended migration periods | Paying maintenance on both ECC and S/4HANA simultaneously without negotiated transition rights |
| New licence metrics | S/4HANA and RISE introduce updated user definitions, subscription metrics, and consumption-based models | Unexpected cost increases if new metrics count users or usage differently than the legacy contract |
| Shelfware carry-over | Converting unused ECC licences to S/4HANA equivalents perpetuates waste instead of eliminating it | Continued maintenance payments on products that provide no value in the new environment |
| SAP sales pressure | SAP reps push RISE or contract conversion aggressively with end-of-quarter urgency and diminishing incentive warnings | Rushing into a multi-year commitment without thorough analysis; locking in unfavourable terms for years |
Need Expert SAP Licensing Guidance?
Redress Compliance provides independent SAP licensing advisory services — fixed-fee, no vendor affiliations. Our specialists have helped enterprises save millions through strategic licence optimization, Digital Access negotiation, and contract restructuring.
Explore SAP Advisory Services →Migration Timing: The Cost of Delay
Maximise Credit Value
Converting licences well before 2027 locks in higher credit percentages (currently 70–80%, previously 90%). Some enterprises convert licences to S/4HANA before the technical migration is complete — holding S/4 licences while still running ECC — to capture a better financial deal. This requires coordinating maintenance on both during the overlap.
Balance Timing and Value
Converting 2–3 years before 2027 balances credit value against technical readiness. The credit percentage will be lower than early movers achieved, but the gap between licence conversion and technical migration is shorter, reducing dual-maintenance costs.
Diminished Returns
Waiting until 2026–2027 risks credits dropping to 50–60% or lower. Combined with time pressure, negotiating leverage diminishes significantly. SAP’s account teams know deadline-driven customers have limited alternatives, resulting in less favourable terms across pricing, flexibility, and contractual protections.
Best Practices for a Smooth Licence Migration
1. Start with a thorough inventory and usage analysis. Catalogue all existing SAP licences: type, count, maintenance cost, and actual usage. Identify shelfware that should be eliminated rather than converted. Project future needs — S/4HANA may introduce new capabilities you want licences for, or make certain legacy components unnecessary. See SAP Licence Optimisation Services.
2. Request formal conversion proposals early. Ask SAP for a licence conversion proposal: “If we convert now, what would our new S/4 entitlement look like, and what credits would we get?” This establishes a baseline for evaluation. If the first offer is not favourable, you have time to negotiate or explore alternatives.
3. Evaluate all paths side by side. Request proposals for contract conversion, RISE subscription, and (if still available) product conversion. Compare total cost of ownership over the migration period, including new licence costs, one-time fees, ongoing maintenance or subscription, and implementation services. Do not accept SAP’s preferred path without comparing alternatives.
4. Negotiate transition rights for dual environments. Secure written rights to run ECC and S/4HANA concurrently for a defined period without paying duplicate licences. Include fallback provisions if the S/4 project is delayed. Transition rights should cover testing, phased rollouts, and any extended parallel-run scenarios.
5. Maximise credit for existing investments. Drop unused licences (shelfware) before conversion so their value can be credited rather than carried forward as waste. Push for the highest offset SAP will allow. Demonstrate which licences are unused to strengthen the case for maximum credit.
6. Clarify maintenance on new licences. New contract maintenance is typically 22% of net licence price. Ensure this is calculated on the discounted licence value, not list price. If you negotiated heavy discounts on new S/4 licences, confirm the maintenance base reflects those discounts.
7. Build flexibility into the new contract. Include provisions for business changes: divestiture rights (reallocating licences if you sell a division), true-down capability after each migration phase, and the ability to adjust licence counts if needs change. Long-term agreements without flexibility become costly constraints. See SAP Contract Negotiation Service.
Recommendations for CIOs
1. Treat licence migration as a project, not an afterthought. Assign dedicated ownership with a clear timeline. Licence decisions during S/4HANA migration can lock in costs for 5–10 years — they deserve the same rigour as the technical migration.
2. Convert early to capture maximum credit value. If your organisation is committed to S/4HANA, there is a financial argument for converting licences now rather than waiting. Every year of delay reduces the credit percentage SAP offers for existing investments.
3. Eliminate shelfware before converting. Audit current usage and identify unused licences, modules, and user types. Remove them from your contract before conversion — converting shelfware to S/4HANA equivalents perpetuates unnecessary cost in the new environment.
4. Do not accept SAP’s first offer. SAP’s initial conversion proposals are starting positions, not final terms. Negotiate credit percentages, pricing, transition rights, contract flexibility, and maintenance terms. Market benchmarks and competitive alternatives strengthen your position.
5. Secure transition rights in writing. Dual-environment periods are inevitable during migration. Without negotiated transition rights, you risk paying double maintenance. Ensure the new contract explicitly permits continued ECC use for a defined period.
6. Involve all stakeholders. Procurement, ITAM, finance, and functional department leads must be engaged. Procurement drives negotiation; ITAM validates licence mapping; finance approves the business case; functional leads verify that the new licences cover all required capabilities. Missing any stakeholder risks gaps or overspend. See SAP Contract Negotiation Playbook.
7. Document the mapping from old to new. Maintain a clear record of how new S/4HANA entitlements map to former ECC licences. This documentation supports operational teams in understanding the new licensing rules, helps with future audits, and demonstrates good-faith conversion if SAP questions entitlements later.
8. Engage independent expertise for high-value migrations. SAP licence conversions involve millions of dollars over multi-year terms. Independent advisors bring market benchmarks, conversion programme expertise, and negotiation leverage that SAP’s own account teams will never provide. The ROI on advisory engagement during migration typically exceeds 10× the cost. See SAP Licence Optimisation Services.
“SAP licence migration is one of the most consequential financial decisions in the S/4HANA journey — yet it is consistently treated as a secondary workstream behind the technical migration. In our experience advising enterprises through these transitions, the difference between a well-prepared licence conversion and a rushed one is typically seven figures over the contract term. The organisations that achieve the best outcomes convert early, eliminate shelfware first, evaluate all paths comparatively, and negotiate every term. The organisations that accept SAP’s default proposal without independent analysis consistently overpay.”