How SAP Migration Credits Work
When an enterprise customer with existing perpetual ECC licences commits to purchasing S/4HANA (either on-premises or via RISE), SAP applies a "migration credit" that reduces the cost of the new S/4HANA licence purchase. This credit is calculated as a percentage of the perpetual ECC licence value being replaced. The migration credit is SAP's commercial incentive for customers to migrate from ECC to S/4HANA rather than extend ECC with third-party support or other alternatives.
The mechanics are straightforward but opaque. A customer with 25,000 perpetual ECC named user licences at a blended cost of $300 per user per year ($7.5 million annual list value) receives a migration credit when purchasing S/4HANA. If the credit is 60% of the ECC licence value being replaced, the credit is $4.5 million, applied against the S/4HANA purchase price. S/4HANA subscription pricing for the same 25,000 users on RISE is approximately $7.5–8 million annually, so the $4.5 million credit effectively reduces year-one S/4HANA cost to $3–3.5 million — appearing to deliver massive savings in year one.
However, this credit is applied only once, when the customer first commits to S/4HANA. The credit cannot be carried forward, stockpiled, or transferred. Additionally, the credit is applied against new S/4HANA subscription fees, not against implementation services or other migration costs. Most importantly, the credit percentage itself — that 60% figure — declines each year as SAP's negotiating position strengthens and migration timelines become compressed.
The Declining Credit Schedule
SAP does not publish official migration credit schedules; they are negotiated customer-by-customer. However, based on customer implementations and Gartner research, the pattern is consistent: migration credits start at approximately 60% of licence value in 2025, decline to approximately 50% in 2026, and are projected to decline to 40–45% in 2027 and beyond. This represents approximately 10% annual decline in the credit percentage.
The implications are severe. For a customer with $7.5 million in annual perpetual ECC licence value:
2025 Migration Credit: 60% of $7.5M = $4.5M in S/4HANA credit
2026 Migration Credit: 50% of $7.5M = $3.75M in S/4HANA credit (loss of $750,000)
2027 Migration Credit: 45% of $7.5M = $3.375M in S/4HANA credit (additional loss of $375,000)
A customer delaying migration from 2025 to 2027 loses $1.125 million in available credits. If migration costs $8–10 million total, this $1.125 million loss represents approximately 11–14% of the total migration cost. This is not a small amount; this is significant financial penalty for delay.
Furthermore, these are approximate numbers based on current market data. SAP's actual migration credit schedule could decline faster than 10% annually if migration volumes surge (SAP's incentive to offer credits decreases when demand is high) or could decline slower if fewer customers migrate than SAP expects (SAP increases credits to drive migration). The key uncertainty is timing — waiting until 2027 when you could commit in 2025 is a high-risk bet that assumes migration credits will remain stable, which historical trends suggest they will not.
The Cost of a One-Year Delay (Worked Example with Numbers)
Let's model the real financial impact of a one-year delay for an enterprise organisation. Assumptions: 25,000 perpetual ECC named user licences, blended cost of $300 per user per year ($7.5 million in licence value), S/4HANA RISE pricing of $7.5 million annually, implementation services cost of $4 million, total migration cost of $8 million.
Migration in 2025 Path: Year-one cost (2025): Implementation $4M + S/4HANA licensing with 60% credit ($4.5M credit applied, net cost $3M) = $7M total year-one cost. Perpetual ECC licence cost continues for 2025 ($7.5M). Total 2025 cost: $14.5M. After year one (2026 onwards): S/4HANA RISE cost $7.5M annually, ECC cost eliminated. Five-year total (2025-2029): $14.5M + (4 x $7.5M) = $44.5M.
Migration in 2026 Path (One-Year Delay): Year one (2025): Continue ECC perpetual licences $7.5M. Year two (2026): Implementation $4M + S/4HANA with 50% credit ($3.75M credit, net cost $3.75M) + ECC cost for 2026 ($7.5M) = $15.25M. Total 2025-2026 cost: $7.5M + $15.25M = $22.75M. After year two (2027 onwards): S/4HANA cost $7.5M annually, ECC cost eliminated. Five-year total: $22.75M + (3 x $7.5M) = $45.25M.
Financial Impact of One-Year Delay: Delay cost = $45.25M - $44.5M = $750,000 additional cost. This is the exact $750,000 credit loss we calculated above. Delaying migration from 2025 to 2026 costs approximately $750,000 in incremental spending compared to proceeding in 2025.
Now extend this to a two-year delay: Migration in 2027 at 45% credit means the credit is $3.375M instead of $4.5M. Two-year delay cost = $1.125M additional spending. For a customer with $10M in ECC licence value, this calculation produces $1.5M–$1.875M in sunk cost from delaying migration.
What SAP Doesn't Tell You About Credits
First, migration credits are applied once and cannot be reactivated. If a customer receives a 60% credit in 2025 but decides to delay implementation until 2026, they cannot reapply the credit; they are locked into that 60% rate for their 2026 implementation. However, if they wait to negotiate until 2026, SAP will offer 50% credit. This is why early commitment and documentation are critical — securing the credit in writing before delaying implementation is essential.
Second, migration credits are applied against S/4HANA subscription fees only. They are not applied against implementation services, BTP credits, add-on modules, or any other cost component. If S/4HANA implementation services increase from $4M to $5M (which is common as scopes expand), the customer absorbs the full $1M increase; the migration credit does not scale up to cover larger implementation costs.
Third, migration credits can be forfeited or partially forfeited if the customer fails to migrate by specific deadlines or changes their migration scope. Some SAP contracts include clauses stating that if the customer does not complete S/4HANA deployment within 36 months of receiving the credit, the credit is reclaimed or reduced. This creates pressure to execute migration on SAP's timeline, not the customer's timeline.
Fourth, migration credits are not contractually protected in most cases. SAP reserves the right to recalculate or reduce migration credits if the customer's licence count decreases, if the customer's scope changes, or if SAP believes the customer has violated any contract terms. A customer who downsizes from 25,000 ECC licences to 20,000 licences may find that their migration credit is recalculated downward based on the new (smaller) licence count.
Maximising Your Credit Before the Cliff
First, negotiate your migration credit now, before the 2027 deadline creates panic. Document your 2025 credit rate in writing as part of an S/4HANA pilot, proof-of-concept, or pre-implementation agreement. Do not wait until you are 12 months from the 2027 deadline to negotiate; by then, SAP's negotiating position will be much stronger and credits will be minimal.
Second, lock in your credit amount by committing to a specific S/4HANA contract start date early. If you commit to a 36-month S/4HANA contract starting January 2026, lock in the 2026 credit rate (approximately 50%) in writing before the negotiation closes. Do not assume you can renegotiate the credit during implementation; SAP will not renegotiate once the contract is signed.
Third, understand whether your migration credit applies to on-premises S/4HANA, RISE with SAP, or both. Some credits are restricted to RISE only; others apply to both. Verify this explicitly before signing, because the choice between on-premises and RISE will affect your S/4HANA cost structure and the value of your credit.
Fourth, model your migration cost with and without the credit. A customer with a declining credit schedule should migrate sooner if the credit decrease is larger than the implementation cost savings from deferral (typically, deferral does not produce savings, because implementation costs tend to increase over time as complexity builds).
Should You Act Now? Decision Framework
Migrate now (2025-2026) if: You have a clear S/4HANA business case, your implementation team is ready to execute, you can absorb $4–5M in implementation cost, and you want to maximize your migration credit before decline. Early migration also provides two full years of S/4HANA operation before the 2027 deadline, reducing post-deadline panic.
Defer but commit to 2027 (with written credit guarantee) if: Your S/4HANA business case is still developing, you need 2025-2026 to finalize scope and approach, but you can document your migration credit commitment (50%) in writing before year-end 2025. This captures credit value while allowing you implementation timeline flexibility.
Choose extended maintenance or third-party support if: Your S/4HANA business case is weak, your ECC system is stable with infrequent change, and your primary goal is cost reduction. In this case, migration credits are irrelevant; focus on extended maintenance costs (24% of licence value) versus third-party support (12%) instead.
Recommendations
First, engage SAP or a qualified advisor immediately to understand your current migration credit eligibility and the projected credit decline for your specific situation. Do not assume you understand migration credit mechanics without professional review.
Second, run a financial model comparing migration now (with current 60% credit) versus deferral to 2027 (with projected 40–45% credit). Quantify the credit loss from deferral and compare it against any savings from deferring implementation cost. In most cases, the credit loss will exceed implementation cost savings.
Third, if you are leaning toward migration, commit to a specific S/4HANA contract start date in 2025 or early 2026 and lock in your migration credit in writing. Do not enter into preliminary discussions without documenting the credit terms.
Finally, if you choose extended maintenance or third-party support instead of migration, ignore migration credits entirely and focus on maintenance cost optimization. Migration credits are only relevant for customers committed to S/4HANA migration; they are sunk cost for customers choosing other paths.
Need Credit Analysis?