A conversion credit is the financial allowance SAP grants when a customer trades the value of existing on-premise licenses toward S/4HANA, typically covering 90 to 100 percent of the net license value already paid under the contract conversion path. The credit is the mechanism that lets a long-standing ECC customer move to S/4HANA without buying the new estate at full list price. Its size, and the conditions attached to it, decide whether an S/4HANA migration is a modest top-up or a second full purchase.
Two conversion paths, two credit outcomes
SAP offers two routes from ECC to S/4HANA, and they treat the credit very differently. Product conversion exchanges specific old license items for their S/4HANA equivalents, item by item, and preserves the existing contract and metrics. Contract conversion replaces the entire old agreement with a new S/4HANA contract and applies the accumulated license value as a credit against the new license requirement. The path chosen sets the credit value and the negotiating room around it.
| Path | Credit basis | Effect on metrics |
|---|---|---|
| Product conversion | Like-for-like swap of named items | Existing metrics largely retained |
| Contract conversion | Net license value as a credit pool | Re-mapped to S/4HANA FUE metrics |
| New license (no conversion) | No credit, full list purchase | Fresh S/4HANA contract |
Contract conversion usually produces the larger headline credit but exposes the buyer to a full re-mapping of users and engines onto the Full User Equivalent model, which can quietly increase the license requirement even as the credit reduces the price. Product conversion is more conservative and keeps the existing named user structure intact.
How the credit is calculated
The credit is built from the net license value the customer has paid, not the list price of the old licenses. SAP starts from the documented contract value, applies its conversion rules, and offsets the result against the new S/4HANA requirement. Maintenance already paid is generally not credited, and shelfware that was bought but never deployed still counts toward the pool, which is one of the few places unused licenses retain value. The detail of this calculation is set out in our SAP conversion credits analysis and in the S/4HANA versus ECC comparison.
The maintenance base deserves particular attention. When a contract conversion replaces the old agreement, the annual maintenance fee is recalculated against the new S/4HANA license value rather than the old on-premise base. A credit that looks generous on the license line can still raise the recurring maintenance bill if the new subscription or license value sits higher than the old one. Model the maintenance figure across the full term, not only the one-time credit, because the recurring number is what the buyer pays year after year.
Compliance warning: Conversion credits are calculated against the customer's compliant license position, not its deployed position. If an audit finds underlicensed use before conversion, SAP can require the gap to be purchased at list before the credit applies, which removes the discount on exactly the licenses the buyer needs most. Close any compliance exposure on the existing SAP license estate before opening a conversion negotiation, because the order of operations decides the price.
Protecting the credit
The credit is a negotiation, not a formula the buyer must accept. The value SAP offers first is rarely the value available. Buyers protect the credit by baselining the true net license value independently, by timing the conversion away from SAP's quarter and year end pressure unless the timing suits the buyer, and by refusing to let the re-mapping to FUE inflate the new requirement past what the credit covers. A conversion that consumes the entire credit and still requires new spend has usually been mapped against the buyer's interest. The full commercial framework sits in the SAP licensing guide, and engagement support is available through our SAP advisory practice.