How to Negotiate SAP S/4HANA Licensing: Conversions, Discounts, and Migration Credits

The Negotiating Context in 2026

SAP's commercial position in S/4HANA migration conversations is driven by one overriding constraint: the company has committed to migrating the majority of its 35,000 ECC customer base to S/4HANA Cloud by 2027. With Gartner projecting 17,000 companies not yet ready by that deadline, SAP's internal quota pressure is substantial. ECC mainstream maintenance for EHP 0–5 ended December 31, 2025 — that deadline has already passed. EHP 6–8 support ends December 31, 2027, with extended maintenance available at approximately 24% of licence value (versus the standard 22%) through 2030.

This creates a structural buyers' market. SAP needs these migrations more than any individual customer needs to migrate on SAP's preferred timeline. Customers who understand this dynamic and are willing to credibly signal alternatives — third-party support providers like Rimini Street, which can deliver equivalent support at up to 50% below SAP maintenance costs, or simply continued ECC operation with extended maintenance — negotiate meaningfully better outcomes than those who accept SAP's urgency framing at face value.

The fact SAP would prefer buyers not know: migration credits decrease approximately 10% per year. A migration finalised in 2025 receives 70 to 80% credit against existing licence value. The same migration in 2027 will receive 50 to 60%. SAP's account teams rarely communicate this decay curve unless buyers ask specifically — and the urgency messaging SAP deploys obscures the credit decline rather than highlighting it as a reason to act.

The Three Conversion Paths Explained

SAP offers three distinct mechanisms for converting ECC licences to S/4HANA. Each has different commercial implications, and the right choice depends on your existing contract structure, the degree of alignment between your current licence metrics and S/4HANA's user type model, and whether you are converting to on-premise, Private Cloud, or Public Cloud.

Path 1: Product Conversion

Product conversion replaces existing ECC licence types with their S/4HANA equivalents on a like-for-like basis. The commercial benefit is simplicity and continuity — existing discount positions and maintenance terms are preserved wherever possible. The limitation is that product conversion assumes a reasonable mapping between what you currently licence and what S/4HANA offers. Organisations with legacy licence types, particularly those acquired through M&A rather than directly from SAP, may find that product conversion produces a less favourable metric mapping than contract conversion.

Product conversion is typically the right path for organisations with a clean, recently purchased ECC licence base and a moderate to low level of customisation who want the simplest possible commercial transition.

Path 2: Contract Conversion

Contract conversion is a more comprehensive negotiation that restructures the entire commercial relationship — not just the product licences but also user type mapping, metric alignment, maintenance terms, and potentially digital access provisions. It offers more flexibility to reshape the licence baseline but requires more commercial sophistication to execute effectively.

Contract conversion is the right mechanism for organisations that need to rationalise an overly complex or poorly structured ECC licence base, those with significant legacy licence types acquired through M&A that do not map cleanly to S/4HANA metrics, and those with strong negotiating leverage who want to restructure the commercial terms, not just the product names. The risk with contract conversion is scope creep — SAP can use the restructuring process to increase your overall licence obligation if your team does not control the mapping process rigorously.

Path 3: Compatibility Packs

Compatibility packs allow organisations to continue using ECC-based licence entitlements in an S/4HANA environment for a defined period — effectively bridging the gap between the old and new licence models during a phased migration. They are a transitional mechanism, not a long-term solution, and SAP has progressively tightened their availability and duration.

Important: many compatibility pack provisions that covered indirect access and specific legacy transactions expired December 31, 2025. Organisations relying on compatibility pack coverage for their integration landscape should have verified whether those provisions carried forward into their S/4HANA contract. If not, new DDLC exposure may have materialised from January 1, 2026.

Migration Credit Mechanics

SAP's migration credit programme allows existing ECC licence value to be applied against S/4HANA subscription or licence fees, reducing the net new investment required to move to S/4HANA. Understanding how credits are calculated, the timeline decay, and what they can be applied against is essential for maximising their value in a conversion negotiation.

How Credit Is Calculated

Migration credits are calculated as a percentage of your existing ECC licence value — specifically the perpetual licence fees paid, not the annual maintenance. A customer with €5 million in ECC perpetual licence value who migrates in 2025 at an 80% credit rate receives €4 million in credit applicable to S/4HANA fees. The same migration in 2027 at a 60% credit rate produces €3 million in credit — a €1 million difference driven entirely by timing.

The credit is typically applicable against subscription fees, implementation services from SAP, and BTP credits — depending on how the negotiation is structured. Credits applied against subscription fees reduce the Year 1 cash requirement most visibly, but credits applied against BTP allocations can deliver ongoing operational value if BTP consumption is significant.

What Drives Credit Percentage

Three factors influence the credit percentage your team can negotiate. First, timing — as noted, credits decay approximately 10% per year approaching the 2027 EHP 6–8 deadline. Second, deal size — larger conversions involving significant new S/4HANA spend attract higher credit percentages as SAP prioritises high-value conversions for preferential treatment. Third, conversion path — moving to RISE with SAP (Private Cloud) typically attracts stronger credits than on-premise S/4HANA conversion, because RISE generates ongoing subscription revenue for SAP rather than a one-time licence fee.

Discount Benchmarks

SAP's published list prices for S/4HANA are a commercial fiction — no major enterprise pays them. The negotiating question is not whether you will receive a discount but how large that discount should be and what the right basis for measuring it is.

Industry benchmarks for S/4HANA licence discounts off list price: standard enterprise deals at 35 to 45% discount; large, strategically important accounts at 45 to 55%; deals with credible competitive alternatives (Rimini Street, Oracle ERP, Microsoft Dynamics) at 50 to 60% or higher. These ranges assume a well-prepared negotiation with data, competitive positioning, and independent advisory support. Buyers who engage SAP without this preparation typically achieve 20 to 30% discounts — a 25 to 45% worse outcome than buyers who negotiate from a position of knowledge.

The mechanics of how discounts are measured matters as much as the percentage. SAP's initial proposals typically present discounts against a grossly inflated baseline — the Estimated List Price that bears limited relationship to what any comparable customer actually pays. Insist on benchmarking your deal against actual peer transaction data, not SAP's internal list pricing model. Independent SAP commercial advisory specialists maintain peer transaction databases that can validate whether SAP's proposed pricing represents a genuine market discount.

Dual-Use Rights: The Most Valuable Protection Most Buyers Forget

Dual-use rights are contractual provisions that allow you to run your existing ECC system in parallel with S/4HANA during the migration period without incurring additional licence fees for the ECC environment. They are among the highest-value negotiating points in any S/4HANA conversion — and they are among the most frequently overlooked by buyers who focus on the headline subscription price rather than the total contract structure.

Without dual-use rights, running ECC and S/4HANA in parallel — which is operationally necessary for data migration, user acceptance testing, cutover planning, and contingency — creates double licence obligations. For a large enterprise paying €2 million per year in ECC maintenance, an 18-month parallel run period without dual-use rights adds €3 million in avoidable licence costs.

SAP typically grants dual-use rights for 12 to 18 months when explicitly negotiated. The key is asking for them before signature — dual-use rights added after the contract is signed command a separate fee. In our experience, buyers who request dual-use rights during the initial negotiation receive them in the vast majority of cases. Buyers who discover they need them after go-live find SAP significantly less accommodating.

A Client Pattern: The Timing Mistake

A global industrial manufacturer with approximately 3,200 SAP users entered the S/4HANA conversion conversation in mid-2024, driven by the EHP 6 maintenance deadline. SAP's account team delivered a well-orchestrated urgency narrative — migration must begin immediately, credits are being reduced, RISE is the only viable path forward. The company's procurement team, under deadline pressure and without independent advisory support, accepted SAP's initial proposal with minor modifications.

The negotiated credit was 68% of ECC licence value — below the 75 to 80% that was achievable in 2024 for a deal of that size. The subscription discount was 38%, against a benchmark of 48 to 52% for comparable deals at that user count and term length. Dual-use rights were not requested and not included. The parallel run period of 14 months cost the company an additional €1.8 million in ECC maintenance fees that should have been zero-cost under a properly negotiated dual-use provision.

The total negotiating shortfall versus an achievable outcome was approximately €4.2 million over the initial 5-year term — entirely avoidable with preparation, data, and independent advisory support.

Six Actions That Determine Your Outcome

1. Calculate Your Migration Credit Entitlement Before SAP Names a Number. Know your ECC perpetual licence value, the applicable credit percentage for your migration timeline, and the maximum credit value you can negotiate. SAP should not be the first party to name a credit number — that anchors the conversation at their preferred starting point.

2. Request Dual-Use Rights as a Non-Negotiable Requirement. Include dual-use rights for 18 months as a stated requirement in your initial commercial conversation. If SAP raises this as an issue, the appropriate response is that a conversion that includes genuine transition support includes dual-use provisions — this is a market standard, not a special concession.

3. Build Competitive Leverage Before the Negotiation Begins. Rimini Street's third-party support can maintain your existing ECC environment at up to 50% below SAP maintenance costs while you complete the migration on your own timeline. Having a credible alternative to SAP's urgency-driven schedule gives you the ability to walk away from a bad deal — the single most powerful negotiating tool available.

4. Benchmark the Discount Against Peer Transactions, Not SAP's List Price. Demand that your pricing be benchmarked against actual peer transaction data at equivalent user counts, industry verticals, and contract terms. SAP's list price is not a legitimate benchmark for discount negotiation.

5. Negotiate BTP Credits and DDLC Coverage as Part of the Conversion. Migration is the moment of maximum leverage for every ancillary commercial term. BTP credit allocations, digital access coverage, digital access document volumes, and API access terms are all more negotiable at conversion than at any subsequent annual review.

6. Time the Deal for SAP's Q4 if Possible. SAP's fiscal year ends September 30. The July to September Q4 window is when quota pressure peaks and discount authority is most liberally applied. For deals where timing is flexible, Q4 engagement consistently produces better outcomes than mid-year conversations.