Migrating from SAP ECC to S/4HANA is not just a technical upgrade. It is a strategic business decision with significant licensing implications. Three core migration paths exist: perpetual on-premise conversion, RISE with SAP subscription, and hybrid models that combine both. Each affects IT budgets, risk, and agility differently. The licensing path you choose locks in your cost structure, your negotiating position, and your operational flexibility for the next 5 to 10 years. This guide provides the strategic framework for choosing the right path.
Migrating from SAP ECC to S/4HANA requires a licensing decision that is as consequential as the technical migration itself. The licensing path you select determines whether your ERP spend follows a capital expenditure or operating expenditure model, whether you retain control over infrastructure and customisation, and whether SAP or your organisation sets the pace of change.
Three core migration paths exist, each with distinct cost models, risk profiles, and strategic implications.
Convert existing ECC licences to S/4HANA on-premise equivalents. Preserves your existing entitlements and contract terms. Maintains a CapEx model with ongoing annual maintenance (typically 17 to 22% of licence value). Full control over infrastructure, customisations, and upgrade timing. Leverages prior licence investments. Best for organisations that want continuity, full control, and a stable cost structure.
Subscription cloud service bundling S/4HANA, infrastructure, and managed services under a single contract. Shifts ERP spend from CapEx to OpEx. Accelerates innovation cycles with SAP-managed updates. Reduces in-house IT overhead. Multi-year commitment (typically 3 to 5 years). Available in private cloud (single-tenant, full customisation) or public cloud (multi-tenant, clean core) editions. Best for organisations prioritising agility and cloud-first strategy.
Combination of on-premises licences and RISE subscriptions. Core systems stay on-premises under perpetual licences while new capabilities or regions deploy via RISE. Flexibility for phased rollouts. Regulatory compliance for sensitive data that must remain on-premises. Cloud benefits where they fit. Requires careful governance to avoid duplicate licensing. Best for phased migrations and regulated industries.
A thorough upfront assessment ensures your migration path aligns with both your financial strategy and transformation roadmap. The decision is not purely about cost. It is about the operating model you want for the next decade: full control with higher internal responsibility (perpetual), vendor-managed simplicity with less flexibility (RISE), or a carefully governed combination of both (hybrid).
When converting legacy ECC licences to S/4HANA, SAP offers two approaches. Each has different impacts on cost, continuity, and contract structure. Understanding the distinction is critical because it determines whether you preserve your existing commercial terms or start fresh under SAP's current (and typically less favourable) licensing rules.
Replaces existing ECC licences with equivalent S/4HANA licences while maintaining your original contract terms intact. You retain negotiated discounts and replace ECC products with S/4HANA versions. Dual-use rights allow you to run ECC and S/4HANA in parallel without duplicate costs, which is ideal for phased rollouts. The limitation: product conversion does not reduce your licence footprint. Shelfware (unused licences you are paying maintenance on) remains, and maintenance continues on those unused licences.
Replaces the entire contract. You terminate the ECC agreement and sign a new S/4HANA contract. SAP grants licence conversion credits valued at your existing licences. This is a one-time reset: you can redesign your licence portfolio, drop obsolete modules, right-size user counts, and adopt new S/4HANA metrics like FUE (Full Use Equivalents). The risk: contract conversion moves you to SAP's latest licensing rules, and you lose legacy perks from your old contract (negotiated discounts, favourable terms, grandfathered pricing).
SAP's conversion credit incentives are gradually shrinking. Early movers historically received the highest credits, while late movers receive less. Acting sooner maximises credit value and avoids double payment for overlapping ECC and S/4HANA usage. With ECC mainstream support ending in 2027, every quarter of delay reduces your negotiating leverage and the financial incentive SAP offers for conversion. See Migrating from ECC: Licensing and Cost Implications.
| Conversion Type | Contract Terms | Licence Flexibility | Dual-Use Rights | Key Risk |
|---|---|---|---|---|
| Product conversion | Preserved from ECC contract | Low (1:1 replacement) | Yes, parallel operation | Shelfware and maintenance on unused licences persist |
| Contract conversion | New S/4HANA terms | High (redesign portfolio) | Negotiate explicitly | Lose legacy discounts and grandfathered terms |
RISE with SAP is a subscription-based cloud offering designed to streamline S/4HANA adoption. Instead of buying software outright, you pay a subscription fee that bundles S/4HANA software, cloud infrastructure, and basic technical services (maintenance, updates, monitoring) under one contract. This fundamentally changes the financial relationship with SAP.
RISE shifts ERP spending from capital expense to operating expense. The subscription eliminates upfront licence costs and can accelerate deployment since infrastructure and upgrades are handled by SAP. For CFOs, this converts a large capital outlay into a predictable monthly or annual payment. For CIOs, it reduces internal infrastructure management burden. The trade-off: over a 10-year horizon, cumulative subscription costs typically exceed the total cost of perpetual licensing plus maintenance, which is why TCO modelling is essential before committing.
RISE is available in two editions. Private cloud (single-tenant, dedicated infrastructure, full ABAP customisation, customer-controlled upgrades) costs 20 to 40% more per FUE but preserves your customisation landscape. Public cloud (multi-tenant SaaS, clean core, quarterly automatic updates) costs less per FUE but restricts customisations to BTP extensions. The choice depends on your customisation reality and change management capacity.
Both RISE editions use Full Use Equivalents (FUE) as the unified user metric. FUE replaces the traditional SAP named user model (Professional, Limited Professional, Employee) with a single metric that weights users by their access level. Right-sizing FUE allocations before contract negotiation is critical. Over-provisioning FUEs at contract signing locks in higher costs for the entire commitment term.
Commit to larger volumes or bundle additional SAP cloud services (BTP credits, Analytics Cloud, SuccessFactors) to win discounts. Include flexibility for adjusting user counts or swapping services as needs change. Seek migration assistance from SAP as part of the package (implementation credits, data migration support, technical conversion services). Negotiate the contract term strategically: longer commitments give SAP more revenue certainty and should translate into better per-FUE pricing. With careful negotiation, the subscription path can deliver strong value. See RISE with SAP vs Traditional On-Premise Licensing.
A hybrid SAP licensing model blends on-premise and cloud deployment strategies. Core systems stay on-premises under perpetual licences while new capabilities or regions deploy via RISE. This is particularly suitable for phased rollouts or when certain systems must remain on-premises due to regulatory requirements.
Hybrid models work best for organisations that cannot migrate everything at once. Common scenarios: regulated industries where certain data must remain on-premises, phased geographic rollouts where some regions move to RISE while others remain on-premise, organisations with complex customisation landscapes that need time to rationalise before committing to RISE, and enterprises with significant remaining value in existing perpetual licences that does not justify abandoning them prematurely.
Hybrid gives you cloud benefits where they make sense and keeps sensitive workloads in-house. You can test RISE with a specific business unit or geography before committing the entire organisation. This phased approach manages risk better than a big-bang migration. The challenge: managing dual licence models requires vigilance to avoid inefficiencies and duplicate costs.
The primary risk of hybrid models is inadvertently paying for the same users or processes twice: once under the perpetual on-premise licence and once under the RISE subscription. Negotiate dual-use rights or transition clauses with SAP so you can run both old and new systems in parallel without duplicate charges. Strong governance and clear contract terms are essential to prevent overlap. Map every user and every workload to a single licensing regime before go-live.
The right migration path depends on your organisation's financial strategy, risk appetite, customisation complexity, and transformation timeline. No single path is universally superior.
| Dimension | Perpetual On-Prem | RISE Subscription | Hybrid |
|---|---|---|---|
| Cost model | CapEx + annual maintenance | OpEx (ongoing subscription) | Mixed CapEx + OpEx |
| Control | Full (infrastructure, customisations, timing) | Vendor-managed cloud | Split by workload |
| Flexibility | Lower (locked to own infrastructure) | Higher (scale users/modules) | Highest (choose per workload) |
| Innovation speed | Self-managed upgrade cycles | Always on latest version | Varies by component |
| Long-term cost (10 yr) | Lower cumulative (if stable) | Higher cumulative over time | Depends on split |
| Licensing complexity | Low (single model) | Low (single model) | High (two regimes) |
| Vendor dependency | Lower | Higher (SAP platform + pricing) | Moderate |
| Customisation support | Full ABAP, any modifications | Private: full; Public: BTP only | Full for on-prem portion |
| Best for | Stable orgs wanting control | Agility-first, cloud-ready orgs | Phased migrations, regulated industries |
Score your organisation against each dimension. If you prioritise control and cost predictability, perpetual on-premise is the strongest fit. If you prioritise agility and reduced IT overhead, RISE subscription is the strongest fit. If you need to manage a phased transition or face regulatory constraints, hybrid is the pragmatic middle ground. The framework should inform your starting position, but the final decision should be validated by a detailed 5 to 10 year TCO model specific to your organisation.
Do not let SAP's sales team choose your migration path. They will push whichever model generates the most revenue for SAP, which is typically RISE with the longest possible commitment. Your path should balance cost optimisation with the agility and control your business requires. An independent assessment ensures the decision is driven by your interests, not SAP's.
Executing a smooth and cost-effective S/4HANA licence migration requires diligent planning and negotiation. These four steps form the foundation of every successful migration.
Begin with a full inventory of ECC licences and users. Identify unused or underutilised licences (shelfware) and note maintenance costs. This baseline shows the true value of your entitlements and informs how much credit you can carry into S/4HANA. Typical enterprises find 15 to 25% of their SAP licences are unused or significantly underutilised. Cleaning up shelfware before conversion ensures you do not carry dead cost into the new contract.
Compare the multi-year total cost of ownership for staying on-premise, moving to RISE, or a hybrid mix. Include all costs: licence/subscription fees, maintenance, infrastructure, implementation, internal labour, BTP development (for RISE), integration rework, training, and change management. A 5 to 10 year projection highlights which option delivers better long-term value. Do not rely on SAP's TCO comparison. Build your own model with your own numbers. See How to Budget for SAP Private Cloud: 5-Year TCO.
Plan migration to coincide with SAP's incentive programmes and deadlines. SAP often provides better conversion discounts at fiscal year-end or before support milestones. Lock in higher credit values and secure extras like migration service funding. SAP's fiscal year ends December 31. The strongest discount authority and deal flexibility occur in Q4 (October to December), when SAP's account teams are motivated to close commitments against annual targets. Aligning your negotiation timeline to SAP's fiscal calendar is one of the simplest ways to improve your commercial outcome.
Build flexibility into S/4HANA agreements. Ensure dual-use rights for parallel ECC/S/4HANA operation during transition. If opting for RISE, negotiate provisions to scale usage up or down, swap services, and clarify pricing for future growth. Aim for safeguards against unexpected price hikes at renewal: negotiate a cap on annual escalation (3 to 5% maximum), include the right to adjust FUE volumes at the anniversary, and secure a clear exit path if RISE does not deliver the expected value.
With SAP's ECC mainstream support ending in 2027 and conversion incentives declining each year, now is the time to solidify your migration path. A proactive licensing strategy ensures that when your organisation goes live on S/4HANA, it has the right entitlements at the right cost. Organisations that wait until 2027 to negotiate will face the weakest conversion credits, the least commercial flexibility, and the highest pressure to accept SAP's terms as presented.
SAP's initial conversion credit offer is a starting position, not a final number. Enterprises that accept the first offer typically leave 15 to 30% of potential credit value on the table. Benchmark the conversion credit against peer organisations and your own entitlement value. Push back with data: what you paid for the licences, what maintenance you have paid over the years, and what the fair market value of the conversion should be.
If you convert 1,000 ECC user licences to S/4HANA but only 750 are actively used, you are carrying 250 unused licences (and their associated maintenance cost) into the new contract. Conduct a thorough licence audit before conversion. Drop or right-size unused entitlements. Every unused licence you eliminate before conversion reduces your ongoing cost for the next 5 to 10 years.
During migration, you will run ECC and S/4HANA in parallel for 6 to 18 months. Without explicit dual-use rights in your contract, SAP could argue that parallel operation requires separate licences for both systems, effectively doubling your licence cost during the transition period. Dual-use rights must be negotiated explicitly and documented in the contract.
RISE subscription costs are attractive in Year 1 because they eliminate the upfront licence purchase. Over 10 years, cumulative subscription payments typically exceed the total cost of perpetual licensing plus maintenance. This does not make RISE a bad choice (the operational benefits may justify the premium), but organisations that choose RISE based on Year 1 cost without modelling the long-term trajectory often experience budget shock at renewal.
S/4HANA migration often changes how third-party systems interact with SAP, potentially creating new Digital Access licensing obligations. Map your integration landscape and indirect usage footprint before signing the migration contract. Negotiate Digital Access terms explicitly as part of the conversion agreement rather than discovering compliance gaps after go-live.
Product conversion replaces ECC licences with S/4HANA equivalents while preserving your original contract terms, negotiated discounts, and commercial structure. Contract conversion terminates the ECC agreement entirely and creates a new S/4HANA contract with SAP's current licensing terms. Product conversion preserves continuity but does not allow you to right-size. Contract conversion gives you a fresh start to redesign your portfolio but risks losing legacy commercial advantages.
Score your organisation against five dimensions: cost model preference (CapEx vs OpEx), control requirements (full vs vendor-managed), customisation complexity (heavy ABAP/Z-code vs standard processes), change management capacity (annual vs quarterly update cycles), and regulatory constraints (on-premise mandates vs cloud-acceptable). Model the 5 to 10 year total cost of ownership for each path with your specific numbers before deciding. Do not rely on SAP's comparison.
Yes, but they are declining. SAP's conversion credit programmes were most generous for early adopters and have been gradually reducing in value. The closer you get to the 2027 ECC support deadline, the less incentive SAP has to offer generous credits because the urgency to migrate shifts the negotiating leverage toward SAP. Acting sooner maximises credit value. Benchmark the offered credits against peer organisations to ensure you receive a fair conversion.
Yes, but only if you have explicit dual-use rights in your contract. SAP offers dual-use rights as part of product conversion, allowing parallel operation of ECC and S/4HANA without duplicate licence costs. For contract conversion and RISE, dual-use rights must be negotiated explicitly. Without documented dual-use rights, parallel operation could create compliance exposure.
In most scenarios, yes. RISE subscription payments over 10 years typically exceed the total cost of perpetual licence acquisition plus annual maintenance. However, RISE includes infrastructure and managed services that perpetual licensing does not, making the comparison more nuanced than licence-to-licence. The operational benefits (reduced IT overhead, faster innovation, vendor-managed infrastructure) may justify the premium for organisations that value agility over cost minimisation. Build a detailed TCO model with all costs included before deciding.
When moving to RISE, your existing perpetual ECC licences are typically credited against the RISE subscription. SAP assigns a conversion credit value to your existing licences, which reduces the RISE subscription cost for an initial period. After the credit period expires, the full subscription rate applies. The credit value, the duration of the credit period, and the post-credit pricing are all negotiable. Do not accept the first credit offer without benchmarking and negotiation.
Users who access both on-premise and RISE systems require licensing for both environments unless dual-use or cross-system access rights are explicitly negotiated. This is the double licensing risk that makes hybrid models complex. Map every user to their primary licensing regime and negotiate explicit terms for users who need access to both. Document these terms in the contract to prevent compliance disputes during audits.
Redress Compliance provides independent advisory on SAP licensing optimisation, conversion strategies, RISE negotiations, and audit defence. We help enterprises maximise conversion credit value, right-size licence portfolios, model true TCO, and negotiate contract terms that protect your interests. Complete vendor independence. No SAP partnerships, no resale commissions.
SAP Advisory ServicesIndependent SAP advisory helping enterprises navigate S/4HANA migration paths, maximise conversion credits, and negotiate optimal RISE or perpetual contract terms. Fixed-fee engagement models.