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

For existing SAP ECC customers, the path to S/4HANA typically begins with a licence conversion — a mechanism that gives you credit for your existing SAP investments when moving to S/4HANA. Understanding how conversions work is foundational to any negotiation.

1. The Conversion Principle:

SAP's conversion programme allows existing SAP ERP/ECC licence holders to convert their on-premise licences to S/4HANA equivalents. The basic concept: you surrender your existing SAP ERP licences (and associated support), and SAP provides S/4HANA licences at a reduced cost — recognising the value of what you've already paid for. In SAP's terminology, this is called a "conversion" or sometimes a "migration" — though the commercial mechanics differ depending on whether you're converting to on-premise S/4HANA, S/4HANA Cloud (private edition), or RISE with SAP.

2. Conversion Ratios — What Credit Do You Actually Get?

SAP's standard conversion ratios determine how much of your existing licence value is credited toward S/4HANA. These ratios are not fixed — they're negotiable, and they vary by product, customer size, and deal context. However, here are the typical starting ranges:

3. Net Licence Value vs List Price — A Critical Distinction:

SAP calculates conversion credits based on net licence value (NLV) — the amount you actually paid after discounts, not the SAP list price. If you purchased SAP ERP licences 10 years ago at a 55% discount to list, your NLV is 45% of list. SAP applies the conversion ratio to this NLV, not to the higher list price. This means enterprises that negotiated aggressive discounts on their original licences receive proportionally less conversion credit — a frustrating but important reality to factor into your financial modelling.

For example: If your SAP ERP licences have a list value of $10M but you paid $4.5M (55% discount), and SAP offers a 60% conversion ratio, your credit toward S/4HANA is $2.7M (60% × $4.5M) — not $6M (60% × $10M).

4. Conversion to RISE vs On-Premise S/4HANA:

The conversion mechanics differ significantly depending on your target deployment:

On-premise S/4HANA: You convert your existing perpetual licences to new S/4HANA perpetual licences. The conversion credit reduces the net new licence fee you pay. Your ongoing support continues at SAP's standard 22% annual rate on the new licence value (minus the conversion credit offset). This is the most straightforward conversion and generally yields the highest credit percentages.

RISE with SAP (cloud subscription): Conversion credits are applied differently — they reduce your annual RISE subscription fee rather than a one-time licence purchase. SAP calculates a "credit" based on your existing NLV and amortises it across the RISE contract term (typically 3–5 years). The practical effect is a reduced annual subscription, but the total credit applied over the full term may be lower than what you'd receive in an on-premise conversion. Critically, your existing perpetual licences are typically surrendered when you move to RISE — you're trading an asset you own for a subscription you rent.

SAP's list prices for S/4HANA are well-documented, but they bear little relationship to what enterprises actually pay. Understanding realistic discount ranges is essential for setting negotiation targets and evaluating SAP's proposals.

1. List Prices vs Street Prices:

SAP's published list prices for S/4HANA user licences serve as a starting point. For on-premise perpetual licensing, list prices for Professional Users typically range from $3,200 to $4,500 per user, Limited Professional Users from $1,200 to $1,700, and Self-Service Users from $200 to $350. However, virtually no enterprise pays list price. The actual transaction price — what we call the "street price" — depends on volume, competitive pressure, existing relationship value, and negotiation skill.

2. What Drives Discount Depth?

Discount levels aren't arbitrary — they're influenced by specific, identifiable factors:

Volume: The single most important driver. An enterprise licensing 5,000 S/4HANA users has significantly more negotiating power than one licensing 500. SAP's discount tiers step up meaningfully at ~500, ~1,000, ~2,500, and ~5,000+ user thresholds. The largest deals (10,000+ users) can achieve 50–55% discounts on the core user licences.

Competitive alternatives: SAP discounts more aggressively when they believe you're genuinely evaluating Oracle Cloud ERP, Microsoft Dynamics 365, Workday, or Infor. Having a credible alternative — even a preliminary RFP or proof-of-concept — shifts SAP's internal approvals for deeper discounts. A well-documented competitive evaluation can add 5–15% to your discount level.

Fiscal year timing: SAP's fiscal year ends December 31. Q4 (October–December) consistently yields the deepest discounts, with the final two weeks of December offering concessions that are simply unavailable earlier in the year. Aligning your negotiation to close in Q4 is one of the easiest, most reliable tactics available — typically worth 5–15% additional discount.

Existing relationship value: Enterprises with large existing SAP estates ($10M+ annual spend) have more leverage because SAP wants to protect the total relationship. Your S/4HANA migration is an opportunity to consolidate and potentially grow SAP's share of your IT spend — SAP's account team knows this and will go further to secure the deal.

3. RISE with SAP Subscription Pricing:

For RISE with SAP deals, pricing is structured as annual subscription fees rather than one-time licence purchases. RISE list prices are typically quoted per user per month, with the total including S/4HANA Cloud, HANA database, infrastructure, and base BTP credits. Discounts on RISE follow similar dynamics but tend to be slightly lower than on-premise perpetual deals because SAP is providing infrastructure and ongoing services.

Typical RISE discounts range from 20–40% off list for the subscription component, with additional negotiation possible on the infrastructure sizing, BTP credit allocation, and included services. The key difference: RISE discounts compound annually (you save every year), whereas on-premise discounts are one-time (but you own the licence perpetually). Model both scenarios over 5+ years to compare total cost of ownership.

4. The "Waterfall" Discount Structure:

SAP's pricing in large deals often follows a waterfall structure: the base licence discount is applied first, then conversion credits are deducted, then any migration incentives or promotional credits are applied. Understanding the order of operations matters because each layer applies to a reduced base. For example: 40% discount on list price → conversion credit on the discounted amount → migration credits on the post-conversion amount. Getting the order wrong in your financial model can create a false impression of the total savings.

Beyond licence conversion credits and volume discounts, SAP offers various migration credits and incentive programmes designed to accelerate S/4HANA adoption. These represent significant additional value — but only if you know to ask for them and understand how they work.

1. SAP's S/4HANA Migration Credit Programme:

SAP periodically runs migration credit programmes that provide existing customers with financial incentives to move to S/4HANA. These credits can take several forms: direct subscription credits (reducing your RISE or cloud subscription for the first 1–3 years), implementation funding (SAP contributes to your system integrator's fees), or free BTP credits and add-on entitlements. The availability and generosity of these programmes fluctuates with SAP's strategic priorities and cloud adoption targets.

As of mid-2025, SAP's migration incentives are particularly aggressive because SAP has publicly committed to migrating a significant portion of its installed base to S/4HANA Cloud by 2027. This creates internal pressure on SAP's sales teams to close migration deals — which translates directly into your negotiation leverage. Every SAP account executive has S/4HANA migration targets, and missing those targets has career consequences.

2. Types of Migration Incentives Available:

3. BTP Credits — The Most Under-Negotiated Element:

BTP (Business Technology Platform) credits are increasingly central to SAP's S/4HANA ecosystem. BTP provides integration services, analytics (SAP Datasphere, SAP Analytics Cloud), AI capabilities, workflow automation, and extension development tools. Most RISE deals include a base allocation of BTP credits, but the default amount is almost always insufficient for enterprise-scale usage.

The negotiation opportunity: BTP credits have relatively low marginal cost to SAP (they're cloud compute resources), but high perceived value to customers. This asymmetry means SAP is often willing to increase BTP credit allocations as a deal sweetener — especially when the alternative is reducing the core S/4HANA licence price. Push for 2–3× the default BTP allocation as part of your deal. A typical RISE contract might default to 3,000 credits/year; negotiate for 8,000–10,000, particularly if you plan to use Datasphere, SAC, or integration services.

4. Extended ECC Support — Bridging the Gap:

Many enterprises need to run ECC and S/4HANA in parallel during migration — which can take 18–36 months for complex deployments. During this period, you're paying both ECC support/maintenance and the new S/4HANA subscription. SAP's standard approach is to continue charging full ECC support during the migration window, which effectively means double-paying for the same functional capability.

The negotiation lever: demand that SAP provide extended ECC support at a reduced rate (or freeze it at current levels with no uplift) for the duration of the migration. Some enterprises have successfully negotiated 50–100% ECC support discounts during the agreed migration window, conditional on committing to a defined S/4HANA go-live date. This can save $500K–$3M depending on your ECC support base.

One of the most expensive mistakes in S/4HANA migration is converting your existing SAP user count one-to-one to S/4HANA without analysing whether the same users — and user types — are actually needed. SAP's conversion process defaults to mapping your current licence quantities to the equivalent S/4HANA user types, but this rarely reflects actual requirements.

1. The One-to-One Mapping Trap:

If you have 3,000 SAP ECC Professional Users today, SAP's default conversion will propose 3,000 S/4HANA Professional Users. But in most enterprises, a significant portion of those users are over-licensed. Mapping legacy licences to S/4HANA user roles properly requires analysing what each user actually does in the system — not simply replicating the existing licence structure.

Common findings from user-role analysis in migration projects:

20–35% of "Professional" users only view reports or approve workflows — they could be reclassified as Limited Professional or Self-Service users in S/4HANA, at 30–60% lower licence cost per user.

10–15% of licensed users haven't logged into SAP in the past 12 months — these are pure shelfware that shouldn't be converted at all.

5–10% of users access only one or two transactions — they may qualify for Self-Service user status or could be served through embedded analytics or Fiori apps that don't require individual SAP licences.

2. Quantifying the Savings Opportunity:

For an enterprise with 3,000 ECC Professional Users, a proper user-role analysis typically reveals that only 1,800–2,100 genuinely need S/4HANA Professional licences. The remainder can be right-sized to cheaper tiers or eliminated entirely. On a 3,000-user estate at list prices, this optimisation can reduce the S/4HANA licence cost by $2M–$5M — before any discounts or conversion credits are applied.

This analysis should be completed before you engage SAP on pricing. If you approach SAP with a request for 3,000 Professional Users and later try to reduce to 2,000, SAP will resist — they've already sized the deal and set internal expectations. But if your initial ask is 2,000 Professional + 600 Limited + 200 Self-Service, based on documented usage data, SAP has little ground to challenge it.

3. S/4HANA's Changed User Definitions:

S/4HANA introduces subtle but financially significant changes in how user types are defined compared to ECC. The Professional User in S/4HANA covers a broader range of Fiori applications and embedded analytics than the ECC equivalent. However, some functions that required a Professional User in ECC can now be performed by a Limited Professional user in S/4HANA — particularly around approvals, simple data entry, and standard reporting. Conversely, some S/4HANA-specific features (advanced planning, embedded AI, certain Fiori analytical apps) may require a Professional licence where the equivalent ECC function didn't.

The implication: don't assume a direct equivalence between ECC and S/4HANA user types. Conduct a fresh user-role mapping exercise specific to S/4HANA's licence definitions, not based on ECC historical assignments.

S/4HANA migration isn't just about acquiring new licences — it's also an opportunity to retire legacy SAP components that are absorbed into or replaced by S/4HANA's architecture. Every retired component represents support savings that can be redirected to fund the S/4HANA investment.

1. What S/4HANA Replaces:

S/4HANA consolidates several previously separate SAP products into its core. Enterprises that previously licensed these products separately can retire them during migration and eliminate their associated support costs:

2. Timing Legacy Retirement to Maximise Savings:

The key challenge is timing. You can't retire ECC support until S/4HANA is live and your users have migrated. This creates a parallel-run period where you're paying for both systems. However, you can retire auxiliary components (SRM, on-premise CRM, SCM/APO) earlier if you've already adopted their cloud replacements (Ariba, Sales Cloud, IBP) — the retirement doesn't have to wait for the core S/4HANA cutover.

Build a phased retirement timeline that maximises overlap between new system go-live and old system support termination. Every month of parallel support is a month of unnecessary cost. Aggressive enterprises target a 3–6 month parallel-run period before terminating legacy support; conservative ones allow 12 months. The difference on a $5M annual ECC support bill is $2.5M–$4.6M in unnecessary overlap cost.

3. Support Savings as S/4HANA Funding:

A powerful negotiation tactic: frame the S/4HANA investment as funded by legacy support savings. If retiring ECC, BW, SRM, and CRM support will save $3M/year, present this to your CFO and SAP as the economic justification for the S/4HANA deal. This reframes the S/4HANA investment from "new cost" to "cost-neutral modernisation" — making internal approval easier and giving SAP a compelling narrative for their deal approval process.

In some cases, enterprises have negotiated with SAP to explicitly link legacy retirement to S/4HANA pricing: "We'll commit to S/4HANA at $X/year, contingent on being able to terminate ECC support within 12 months of go-live, with no reinstatement penalty." This creates a contractual connection between the new and old systems that protects both sides.

Price is only one dimension of an S/4HANA deal. The structural contract terms you negotiate will determine your cost trajectory, flexibility, and leverage for the next 3–7 years. These terms often have a greater cumulative financial impact than the headline discount.

1. Annual Escalation Caps:

SAP cloud subscriptions (RISE, BTP, analytics) typically include annual price escalation clauses of 3–5%. On-premise support follows SAP's standard 22% of licence value with potential annual uplifts. Over a 5-year RISE contract, an uncapped 5% annual escalation adds 27.6% to your total cost compared to flat pricing. Negotiate explicit caps: either flat pricing for the full term, or a maximum increase of CPI or 3%, whichever is lower. For deals above $5M/year, SAP will often agree to price locks in exchange for multi-year commitments.

2. Flex-Down Rights (True-Down Clauses):

One of the most valuable — and most commonly overlooked — contract protections is the right to reduce your licensed quantities at defined intervals. If your business contracts, restructures, or divests a division, you may need fewer S/4HANA users than originally licensed. Without flex-down rights, you're paying for unused licences until the contract ends.

Negotiate annual or bi-annual adjustment rights allowing you to reduce user count by 10–20% without penalty. SAP will resist (they prefer guaranteed minimums), but the clause is achievable — particularly when bundled with other commitments. SAP termination and downsize rights are contractual protections that every S/4HANA buyer should pursue.

3. Pre-Agreed Expansion Pricing:

If your business grows during the contract term and you need additional S/4HANA users, you'll want the ability to add them at your negotiated rate — not at SAP's list price. Lock in expansion pricing as part of the original deal: "Any additional users added during the term will be priced at the same per-user rate as the initial order." Without this, SAP can charge a premium for mid-term additions when they know you need capacity urgently.

S/4HANA negotiations shouldn't be compressed into a few weeks. The most successful outcomes come from structured preparation over 9–12 months. Here is a practical timeline based on enterprise best practice.

Why 12 Months?

Each phase builds leverage for the next. The internal assessment (Phase 1) produces data that enables effective competitive positioning (Phase 2), which creates credible alternatives to present during SAP engagement (Phase 3). Active negotiation (Phase 4) benefits from time — SAP's concessions deepen as their fiscal year-end approaches. Finalisation (Phase 5) aligns with SAP's Q4 targets for maximum discount potential.

Enterprises that compress this into 3–4 months consistently get worse outcomes. They lack usage data for user optimisation, have no competitive alternatives to cite, and face time pressure that SAP exploits. The extra 6 months of preparation typically yields 15–25% better total deal value — on a $10M deal, that's $1.5M–$2.5M in additional savings for a relatively modest investment of time.

Common Timing Mistakes:

Starting negotiation in Q3 for a Q4 close: This gives SAP only one quarter to make concessions. Start in Q1 or Q2 so you have multiple negotiation rounds before the year-end push. The goal is to arrive at Q4 with a near-final proposal that just needs SAP's year-end sweetener to close.

Accepting SAP's urgency framing: SAP's account team will create artificial urgency — "this pricing is only available until end of quarter" or "the migration credit programme expires soon." These are sales tactics, not genuine constraints. SAP migration programmes have been extended repeatedly. Don't let artificial deadlines compress your preparation.

Negotiating in isolation from other SAP renewals: If you have SAP contracts renewing within 12 months of your S/4HANA deal (SuccessFactors, Ariba, BTP, analytics), align them. Negotiating everything together creates maximum leverage — SAP's account team is evaluated on total customer spend, and a consolidated renewal gives them more room to make concessions.

To illustrate how these negotiation elements combine, consider a realistic scenario for a mid-large enterprise moving to S/4HANA.

Enterprise Profile:

A $3B revenue manufacturing company with 4,500 SAP ECC users. Current SAP annual spend: $8M (comprising $3.2M licence support + $4.8M in various SAP cloud subscriptions and services). Existing NLV across ECC, BW, CRM, and SRM: $14.5M. Migration target: S/4HANA Cloud Private Edition via RISE with SAP.

Total 5-Year Impact:

SAP's initial proposal: 5-year cost of approximately $30.2M (licence + subscription + ongoing ECC support during migration).

Optimised outcome: 5-year cost of approximately $17.4M — a $12.8M improvement (42% reduction) achieved through user right-sizing, deeper discounts, aggressive conversion credits, migration incentives, and legacy retirement.

Key point: The $12.8M savings isn't one big concession — it's the cumulative result of multiple optimisation layers: user analysis ($4.2M), deeper discount ($940K), improved conversion credit ($5.05M), reduced subscription ($7M over 5 years), and legacy retirement ($4M avoided). Each layer is individually achievable; together they transform the deal economics.

Every S/4HANA negotiation is unique, but the fundamental principles apply universally. Here is a consolidated checklist distilling this guide's recommendations into actionable steps.

The Bottom Line:

S/4HANA is a strategic investment — but it should be a well-negotiated strategic investment. The difference between an unprepared and fully optimised S/4HANA deal is typically 30–45% of total contract value. For a $15M deal, that's $4.5M–$6.75M in savings — achievable through preparation, data, competitive leverage, and structured negotiation.

The preparation effort — user analysis, NLV calculation, legacy inventory, competitive evaluation, TCO modelling — typically requires 200–400 hours of internal work spread over 3–4 months. The return on that investment is measured in millions. No other procurement activity in most enterprises delivers comparable ROI.