SAP ECC to Cloud Conversion Credits: How to Maximise the Value of Your Existing Perpetual Licences

How SAP Conversion Credits Work

When a perpetual ECC customer moves to S/4HANA Cloud (via RISE or GROW), SAP offers to "convert" existing licence value. The credit is applied against the new cloud subscription fee. SAP's marketing calls this "protecting your investment" — the reality is more complex.

Credits are typically applied as a discount on Year 1–3 subscription fees, not as transferable cash. This means the credit value is locked into the cloud deal structure. Unlike a cash discount that could be applied flexibly, conversion credits must be consumed within specific time windows and across specific product lines.

Understanding how SAP structures this can mean the difference between recovering 75% of your perpetual licence investment or watching 25% evaporate. Our S/4HANA Migration Licensing advisory team has reviewed over 300 conversion credit proposals, and the pattern is consistent: early negotiations are critical.

What Qualifies for Conversion Credit?

Not all perpetual licences qualify for conversion. SAP explicitly excludes third-party components, expired maintenance modules, and certain legacy products. The criteria are not always published — you must negotiate qualification explicitly during the deal phase.

• Named User licences: typically qualify at higher rates (60-90% of paid value)
• Engine-based licences: SAP EWM, TM, APO often qualify at reduced rates (40-65% of paid value)
• Add-on products: CRM, SRM, MES modules often qualify at separate, negotiated rates
• Database licences: SAP HANA database — complex. May be bundled in the new subscription or treated as separate credit
• Maintenance and support: typically do not qualify for conversion credit
• Training and implementation costs: never qualify

SAP's Default Conversion Rate — and Why It's Wrong

SAP's initial offer typically credits perpetual licences at 50–70% of their original list price value. This is SAP's starting position, not market rate. Many enterprises treat this as a fixed offer and accept it without challenge.

Independent benchmarks suggest 75–90% is achievable for core ECC Named User licences. Engine-based licences (SAP EWM, TM, etc.) often convert at lower rates — negotiate separately. The "list price" base SAP uses for calculation is often inflated vs. what you actually paid.

Here's what we've observed: enterprises that negotiate early and separate conversion credits from the cloud deal structure recover 20–30 percentage points more value on average. This isn't theoretical. A customer with £8M in perpetual licence value who accepts a 60% conversion rate leaves £3.2M on the table.

The "Credit Burn" Problem

Conversion credits are time-limited. Typically, they must be applied within 12–36 months. If your cloud subscription fee is lower than expected (e.g., you optimized the licensing model), credits can expire unused. SAP structures credit burn rates to benefit SAP, not the customer.

Some credits are front-loaded — applied to Year 1 only — eliminating flexibility. Others are "use-it-or-lose-it" within a fixed window. We've seen customers with £2–3M in conversion credits lose half their value because the cloud deal was delayed six months and the credit application window closed.

Key risks to watch for:

• Credits applied to inflated list price, not actual transaction price (front-loads the benefit to SAP)
• Front-loaded credits that can't be deferred if go-live is delayed
• No flexibility to apply credits across multiple cloud product lines
• Expiry clauses that don't account for phased implementations
• Credits that can't be carried forward if annual subscription fees are lower than expected

Negotiating a Better Conversion

Conversion credit negotiation is a high-leverage moment. Negotiate before you commit to the migration pathway — once you've chosen RISE or GROW, your negotiating position weakens. SAP knows the switching cost at that point.

Push for these terms:

• Higher conversion rate: 75%+ of paid licence value, not list price
• Explicit qualifying licence list: named individually with per-licence conversion rates
• Longer application window: 36–48 months minimum, with carry-forward rights
• Cross-product flexibility: ability to apply credits to HANA Cloud Platform, BTP, Datasphere, or other SAP cloud offerings if ERP subscription is optimized
• HANA database handling: negotiate whether HANA credits are bundled into S/4HANA subscription or available separately as BTP credits
• Staggered application control: you control when credits are applied each year, not SAP

The conversion credit negotiation phase typically takes 2–4 weeks. This is time well invested. We've seen customers recover 15–25% additional credit value through focused negotiation on these points alone.

Our SAP licence optimisation service includes a full audit of your perpetual licence portfolio and conversion credit entitlements.

RISE vs GROW: Different Credit Frameworks

The cloud deployment model you choose affects how conversion credits work. RISE with SAP and GROW with SAP have fundamentally different commercial structures, and conversion credit mechanics differ accordingly.

RISE with SAP (S/4HANA Private Cloud / Cloud ERP Private): More complex credit negotiation because infrastructure costs are bundled. You're paying for managed services, not just software. Conversion credits are typically larger, but the underlying subscription cost is also higher. Negotiate aggressively on the credit base and application window — RISE deals are more negotiable because the infrastructure component is flexible.

GROW with SAP (S/4HANA Public Cloud): Simpler conversion but lower maximum credit rates. Public cloud licensing is more standardized, so SAP has less flexibility on credit negotiation. GROW does not support brownfield conversion for legacy systems — credits apply differently for greenfield public cloud customers. If you're running a complex ECC landscape, you may not qualify for full GROW conversion credits.

Hyperscaler credits: If RISE is deployed on AWS, Azure, or GCP, negotiate hyperscaler marketplace credits alongside SAP conversion credits. These are separate mechanisms and often overlooked. AWS credits, Azure credits, and GCP credits can be substantial — and they stack on top of SAP conversion credits.

For a detailed comparison of both models and their licensing implications, see our GROW vs Cloud ERP Private comparison.

Common Traps to Avoid

• Accepting list-price basis for conversion rate calculation: Always push back. SAP should convert at a percentage of what you actually paid, not what it would cost to buy new. Demand paid-value basis.
• Not securing a minimum credit floor in the contract: If SAP underestimates your cloud subscription cost, credits can expire unused. Negotiate a minimum floor — if credits exceed subscription fees in a given year, they must carry forward.
• Allowing SAP to define which licences qualify unilaterally: This is a negotiating point. If a licence was licensed and maintained in good standing, it qualifies. Don't let SAP exclude products without documented justification.
• Missing the credit application window without an extension clause: If your go-live slips, ensure the contract allows for credit application window extension. Standard 12–month windows are too tight for enterprise implementations.
• Not aligning credit burn with your actual go-live timeline: Front-loaded credits expire if implementation is delayed. Negotiate staggered credit application aligned to your phased implementation plan.
• Treating conversion credits as guaranteed savings before validating the calculation: Always ask SAP to show you the arithmetic. Recalculate. Have an independent advisor verify the numbers before the deal closes.

What to Demand in Your Contract

This is the non-negotiable contract language for conversion credit protection:

• Written conversion rate schedule: Not a verbal commitment. Define an explicit table of qualified products and individual conversion rates, signed by both parties.
• Explicit list of qualifying licences with individual conversion rates: Name the products, the quantity, the paid licence cost, and the conversion rate for each. This prevents future disputes.
• Credit application flexibility: Ability to allocate credits across product lines. If ERP subscription is lower than expected, credits must be usable for HANA, BTP, or other SAP cloud products.
• 48-month minimum credit application window: Shorter windows (12–24 months) are too restrictive for enterprise implementations.
• Floor protection: If credits exceed subscription value in any year, carry forward rather than expire. This protects you if cloud optimization reduces Year 2 costs.
• Conversion credit audit rights: You should have the right to audit SAP's conversion credit calculation (similar to standard audit rights). SAP is known to overstate cloud subscription costs to consume credits.