SAP's mainstream support for ECC ends in 2027, with extended support (at a premium) through 2030. Roughly 63% of ECC customers had not yet licensed S/4HANA by mid-2024, and full migrations take 18 to 36 months. This playbook covers timeline urgency, migration approaches, licensing conversion strategies, RISE with SAP evaluation, SAP incentive programmes, negotiation tactics, common pitfalls, and a governance checklist to help CIOs navigate this monumental transition.
SAP's mainstream maintenance for ECC ends in 2027, with optional extended support (at a +2% premium fee) available through 2030. SAP has recently offered select customers support until 2033 if they commit to a future cloud migration (essentially a RISE with SAP deal). It is widely believed SAP will not delay these end-of-support dates again.
63% of ECC customers still had not licensed S/4HANA by mid-2024. Given that a full migration takes 18 to 36 months for large enterprises, time is perilously short. Waiting until 2026 to start is a recipe for schedule pressure, cost overruns, and depleted resources. As 2027 nears, demand for experienced S/4HANA consultants will far outstrip supply. SAP's conversion credit percentage typically declines as 2027 approaches. If budget allows and your project is firm, converting sooner locks in higher credits. Use the time you have now to negotiate from a position of choice rather than last-minute desperation.
| Approach | Description | Timeline | Best For |
|---|---|---|---|
| Greenfield | Brand-new S/4HANA from scratch. Full process redesign. Clean core, no custom code baggage. | 18 to 36+ months | Heavily customised ECC, fragmented multi-instance, business seeking transformation |
| Brownfield | In-place technical conversion of ECC. Preserves processes, custom code, historical data. | 12 to 18 months | Relatively standard ECC, tight timeline, working processes worth preserving |
| Bluefield (Hybrid) | New S/4HANA instance with selective migration from ECC. Preserve what works, reengineer what does not. | 15 to 24 months | Large enterprises wanting phased approach, mixed process quality across ECC |
Many large enterprises pursue hybrid strategies: converting core finance via brownfield methods but implementing new S/4 modules (TM, EWM) from scratch. A common pattern is "brownfield then optimise," performing the technical conversion first, then embarking on continuous improvement projects post-migration. Requires ECC 6.0 EHP 6 or above for brownfield. Older versions need interim upgrades before conversion.
SAP does not automatically carry over your ECC licences to S/4HANA. S/4HANA is a new product line, so new licences are required. Enterprises must acquire S/4HANA licences through SAP's conversion programmes or by purchasing outright.
In S/4HANA, SAP streamlined licence definitions. Common S/4 types are Professional Use, Functional Use, and Productivity Use, roughly corresponding to the older Professional, Limited Professional, and Employee categories. Map old licence types to the new model correctly during migration. See FUE Licensing in S/4HANA.
Many SAP customers only utilise around 70 to 75% of their existing licence entitlements on ECC. In negotiations, SAP has been willing to let customers terminate that shelfware as part of the conversion, which lowers the ongoing maintenance base. Use the migration as a chance to right-size. There is no sense converting and paying maintenance on 1,000 licences if you only need 700 in S/4HANA.
S/4HANA introduces the Digital Access licensing model for indirect/automated usage. New S/4HANA contracts default to Digital Access for indirect use. If indirect access is a significant concern (many interfaces to S/4), consider negotiating a conversion to the document model with SAP. They often offer substantial discounts to encourage adoption.
SAP offers conversion programmes to "trade in" your existing ECC licences for S/4 licences. SAP assigns a credit value to your current licences (often equal to what you originally paid, if you move early). That credit can offset the cost of the new S/4HANA licences.
| Aspect | Product Conversion (Legacy) | Contract Conversion (Current) |
|---|---|---|
| Approach | Direct swap of ECC licences for S/4HANA equivalents. Maintains original contract terms. | Replace the entire contract. Sign new S/4HANA licence contract with credit for licences previously owned. |
| Status | Largely retired / phased out. Removed from SAP's price list in mid-2023. | The primary method today. Available for perpetual on-prem and RISE/subscription. |
| Dual-use rights | Explicitly permitted: run ECC and S/4HANA in parallel during transition. | Must be negotiated: typically 6 to 12 months of ECC read-only usage after S/4 go-live. |
| Shelfware | Does not reduce licence footprint. Shelfware remains. | Opportunity to eliminate shelfware. SAP willing to terminate unused licences as part of conversion. |
| Discounts | Preserves original negotiated discounts. | Credit value typically decreases the longer you wait. Early movers get higher credits (up to 100%). |
An enterprise with $5M in ECC licences might receive a $5M credit applied to an S/4HANA contract if they migrate within the next year or two. However, that incentive could decrease to 50% credit if they wait longer. Engage your SAP account team immediately to understand your conversion credit eligibility and get promises in writing. See S/4HANA Licensing Migration Paths.
RISE with SAP is SAP's flagship subscription bundle designed to simplify the move to S/4HANA in the cloud. It consolidates S/4HANA Cloud (public or private edition), cloud infrastructure (via AWS, Azure, GCP, or SAP data centres), and business transformation tools into a single contract.
| Aspect | RISE Public Cloud | RISE Private Cloud |
|---|---|---|
| Model | Multi-tenant SaaS. Standardised processes. Quarterly automatic updates. | Single-tenant managed instance. Customisation supported. Customer-controlled updates. |
| Customisation | Limited: must use SAP best practices. Extensions via BTP only. | Extensive: can bring existing ECC custom code and ABAP modifications. |
| Best for | Organisations with standardised processes. Cloud-native mindset. | Heavily customised ECC. Complex integrations. Need to migrate as-is first. |
| Migration path | Greenfield only. Complete process redesign. | Brownfield or Hybrid. Preserves existing configurations and data. |
Instead of purchasing specific named user licences, RISE uses Full User Equivalents (FUE) to measure usage. Different user types are weighted differently: an "Advanced" user counts as 1.0 FUE, a "Core" user as a fraction. This provides flexibility but requires careful modelling to avoid overcommitting.
SAP's initial RISE proposals often come in at roughly 3x the customer's current annual maintenance spend. Treat it as an opening offer with significant room to negotiate. Many large SAP customers use the threat of staying on perpetual licences (or even third-party support for ECC) as leverage to get a better RISE deal. See RISE: Private vs Public Cloud.
SAP offers credits that can offset migration costs. Customers moving ECC to S/4HANA Cloud via RISE could get credits equal to 45% of their current annual contract value. Those moving an existing on-prem S/4HANA to cloud could get 60%, with some smaller customers even 100% for one year. These credits can also purchase BTP services or LoB solutions.
Customers who show commitment by signing S/4 contracts could avoid the +2% extended maintenance fee for 2028 to 2030. SAP account executives have latitude to waive this fee or provide support through 2030 free of charge if a firm migration project is in place. Ask explicitly: "If we move forward with S/4HANA licensing now, can SAP guarantee support on ECC until our go-live without extra charge?"
Hyperscalers (AWS, Azure, GCP) and systems integrators often offer funding programmes to co-sponsor migrations: cloud credits, professional services funding, or fixed-fee packages. Large SIs may reduce rates to capture market share as 2027 approaches. Orchestrate these to reduce total migration cost: get cloud credits from an IaaS provider, SAP licence discounts, and SI fixed fees simultaneously.
SAP often provides better conversion discounts or credits at year-end or right before support milestones. Plan your migration to coincide with SAP's incentive programmes at their peak. SAP's fiscal year ends December 31. The strongest discount authority occurs in Q4 (October to December).
Make it clear you are evaluating other paths: staying on ECC with extended support, third-party maintenance, or migrating to S/4HANA using a BYOL (bring your own licence) private cloud approach. Some enterprises use the possibility of deferring the S/4HANA move altogether as a bargaining chip. Compare proposals from hyperscalers to show you could run S/4HANA without RISE.
Conversion credit percentages decline as 2027 approaches. If budget allows and your project is firm, converting sooner locks in higher credits. Some companies buy S/4HANA licences ahead of go-live to maximise credits, accepting overlapping maintenance for a short period.
Ensure you can run ECC and S/4HANA in parallel during transition (typically 6 to 12 months) without duplicate costs. Define clearly: duration, capacity (production vs read-only), and whether additional licences are needed. Get this in writing as a contractual provision.
In cloud contracts, negotiate a cap on price increases for renewals (e.g., no more than 3% per year). For perpetual licences, agree on a fixed price for future purchases. Include a "right-size" clause allowing you to reclassify or swap licence types as needs evolve.
Ensure contracts address what happens if you leave RISE. Do you regain on-prem licence rights? Negotiate provisions for scaling usage up and down. Clarify pricing for future growth. Build safeguards against unexpected price hikes to keep costs predictable.
Use the migration as an opportunity to right-size. SAP has been willing to let customers terminate unused licences as part of conversion. If you only need 700 of 1,000 licences in S/4HANA, ensure you receive credit for the rest and stop paying maintenance on the surplus immediately.
SAP may bundle or discount consulting, training credits, or migration tools as part of an overall migration package. If SAP's desire to secure a RISE contract is strong, they may offer significant value-added services at no additional cost. Never accept the first offer. SAP expects savvy customers to push back and has room to manoeuvre.
Treating RISE as a turnkey solution and then struggling with data and process changes. Plan for 18 to 36 months. Run a phased or pilot migration before Big Bang. Test with a smaller division first to uncover issues before full-scale rollout.
Buying more users or services than needed, leading to wasted spend. Conduct thorough licence inventory and usage analysis before committing. Use SAP's LAW tool to measure actual usage. Only convert what you need. Right-size the 25 to 30% average shelfware.
Getting a nasty shock at renewal when costs jump due to auto-renewal clauses or escalators (e.g., 5% annual price increase after initial term). Negotiate caps on renewal increases. Review all fine print around renewal terms, pricing escalators, and flexibility constraints before signing.
Discovering later that some features (advanced analytics, extra environments, email integration) need separate licences under S/4HANA. Map every ECC capability to its S/4HANA equivalent. Verify what is included in core S/4HANA vs what requires add-on licences. Get clarity on BTP, analytics, and embedded features.
Being exposed to double payment risk during the transition period when both ECC and S/4HANA are running. Negotiate explicit dual-use clauses allowing 6 to 12 months of parallel operation. Define capacity and mode (production vs read-only) in the contract.
A rushed, last-minute migration drives up costs, depletes consultant availability, and leaves no room for strategic negotiation. Start now. Even if full migration by 2027 is not feasible, secure interim support (extended maintenance or third-party) and use that time wisely to execute your roadmap.
Yes. S/4HANA is a new product line, so new licences are required. SAP offers conversion credits to help offset the cost, but it is not a free upgrade. Without a negotiated conversion deal, you would buy S/4HANA licences from scratch. The credit value depends on your current licence base, how early you convert, and the negotiated terms with SAP.
SAP's mainstream maintenance ends in 2027. You can purchase extended support through 2030 at a +2% annual premium. Some customers have negotiated support until 2033 by committing to a future RISE contract. Third-party support providers (Rimini Street, Spinnaker) can cut support costs by ~50% but come with trade-offs: no new SAP upgrades or patches, and SAP may view this as grounds for an audit. Running ECC beyond support windows without a plan exposes you to security risks and compliance concerns.
Product conversion was an older programme allowing a direct swap of ECC licences for S/4HANA equivalents while maintaining original contract terms. It is mostly phased out. Contract conversion is the modern approach where you sign a completely new S/4HANA licence contract and terminate or convert the old one, ideally with credit for the licences you previously owned. Contract conversion also offers the opportunity to eliminate shelfware and right-size your licence estate. See S/4HANA Licensing Migration Paths.
It depends on your priorities. RISE simplifies infrastructure management and shifts costs to OpEx, but locks you into SAP's platform. On-premises S/4HANA preserves the CapEx model and maximum control but requires you to manage infrastructure. Many enterprises use a hybrid approach or leverage RISE Private Edition for heavily customised environments. Model TCO for each path over 5+ years and consider exit flexibility, not just Year 1 costs. See RISE: Private vs Public Cloud.
For large enterprises, a full migration typically takes 18 to 36 months, or longer for complex multi-instance environments. Brownfield conversions are generally faster (12 to 18 months) than greenfield reimplementations (18 to 36+ months). Hybrid/Bluefield approaches fall in between. These timelines include planning, licence conversion, technical migration, custom code remediation, testing, training, and go-live. Start planning immediately if you have not already.
SAP offers credits that can offset migration costs. Customers moving ECC to S/4HANA Cloud via RISE could get credits equal to 45% of their current annual contract value. Those moving an existing on-prem S/4HANA to cloud could get 60%, with some smaller customers even 100% for one year. These credits can also purchase BTP services or LoB solutions. Credit values and eligibility change over time, so engage your SAP account team immediately to understand your specific entitlement.
Redress Compliance provides independent SAP advisory: licence optimisation assessments, conversion strategy planning, RISE vs on-premises TCO modelling, contract negotiation support, and audit defence. We help enterprises negotiate from strength and avoid the common pitfalls that cost millions. Complete vendor independence. No SAP partnerships, no resale commissions.
SAP Advisory ServicesIndependent SAP advisory helping enterprises plan ECC to S/4HANA migrations, maximise conversion credits, negotiate RISE contracts, and avoid common pitfalls. Fixed-fee engagement models.