What SAP Conversion Credits Are
SAP conversion credits represent a mechanism that allows customers holding on-premise perpetual or subscription licences to "convert" the recognised value of those licences toward cloud subscriptions. This is not a discount applied to a fixed list price. Rather, it is a credit generated against the net licence fee value of your existing on-premise portfolio — typically positioned as a form of trade-in or migration incentive.
In practice, conversion credits function as a form of cloud subscription prepayment. SAP calculates a credit value based on your existing licence estate, which is then applied against your RISE, SuccessFactors, BTP, SAC, or other cloud product subscriptions. The credit reduces the effective cost of your cloud footprint for a defined period (usually 12–36 months), after which standard list pricing applies.
How Conversion Credit Value Is Calculated
SAP uses a conversion formula that typically yields 50–75% of your net annual licence fee value, though this varies by product line and customer segment. For example, a customer paying £3M annually in on-premise SAP ERP software maintenance might be offered £1.5M to £2.25M in annual conversion credits over a 3-year RISE contract. This appears generous on paper; in reality, it requires scrutiny.
The calculation is based on:
- Net licence fee value: What you actually paid for SAP software, not list price
- Conversion percentage: Typically 50–75% depending on product and negotiation leverage
- Time window: Credits are usually applied over 3 years; after that, you pay list price
- Product eligibility: Not all on-premise licences convert equally; some lines are restricted
The critical issue is that SAP's calculation often overstates economic benefit. Converting a licence portfolio worth £3M does not mean you gain £3M in value; it means you gain a credit that reduces subscription invoices by that amount for a limited period. Once the credit expires, you face full-price cloud subscriptions.
The Credit-to-Subscription Economics
Consider a real scenario: A mid-market customer with £3M in annual on-premise SAP ERP maintenance receives an offer of £1.8M in annual RISE conversion credits over 36 months. SAP's sales deck will emphasize the "£1.8M savings"; what it will not emphasize is what happens in year four.
Under the old model, annual costs were £3M (licence + maintenance). Under the RISE model with credits, costs might be structured as follows:
| Year | RISE List Price | Conversion Credit Applied | Net Annual Cost | vs On-Prem Cost |
|---|---|---|---|---|
| Year 1–3 | £2.4M | £1.8M | £600K | £2.4M savings |
| Year 4–5 | £2.4M | £0 | £2.4M | 20% increase vs on-prem |
This scenario illustrates the trap: years 1–3 appear excellent; years 4 onwards reveal a significantly higher cost structure. Many customers have discovered this only when credits were depleted and renewal negotiations began.
RISE Migration Credits: Mechanics & Negotiation
SAP's RISE with SAP programme includes dedicated conversion credits designed specifically for cloud ERP migration. These credits recognise on-premise ERP licence value (S/4HANA, Business Suite, etc.) and convert that value into RISE subscription credits over the contract term.
RISE credits are structured around use cases and professional services costs as much as software. A typical RISE conversion might include:
- Software conversion credit (40–60% of on-prem licence value)
- Professional services allowance (20–40% of on-prem licence value)
- Cloud infrastructure allowance (if RISE Managed Services is included)
The time window is critical. SAP typically requires that RISE conversion credits be consumed over 24–36 months. Any credits not consumed within that window are forfeited. This creates pressure to accelerate cloud adoption before business and technical readiness is validated.
BTP Conversion Credits and Technology Licensing
Beyond RISE, SAP offers conversion credits for on-premise technology licences converting to BTP (Business Technology Platform). Customers holding NetWeaver, SAP Basis, SAP Content Server, and similar technology licences can convert those values into BTP capacity credits.
BTP credit valuation is often opaque. SAP lists conversion rates (e.g., a NetWeaver license converts to X BTP service units), but the value of those units varies sharply depending on actual BTP consumption patterns. A customer offered "£500K in BTP credits" may find those credits depleted far faster than anticipated if cloud adoption requires higher database or integration throughput than planned.
The Credit Expiry Problem
One of the most destructive elements of conversion credit structures is the expiration cliff. Credits that cannot be used within the defined window (typically 24–36 months) evaporate completely. For customers whose migrations encounter technical delays, organisational resistance, or business disruption, this represents pure value destruction.
A £2M credit window expiring unused is equivalent to a £2M cost increase in year four. Yet many organisations discover this only when renewal discussions begin, at which point negotiating extended credit windows is significantly harder.
Negotiation strategies must address credit expiry explicitly:
- Push for extended credit windows (48–60 months rather than 36)
- Build in grace periods or rolling windows that extend if migration milestones are delayed
- Secure written commitment that unused credits can be applied to related cloud services (e.g., BTP) if primary products are not consuming credits at projected rates
- Tie credit expirations to business milestones rather than calendar dates
When Conversion Credits Make Commercial Sense
Conversion credits are genuinely valuable under specific conditions:
Strong on-premise portfolio with high maintenance costs: Customers with large, ageing ERP estates paying premium maintenance fees on perpetual licences gain real TCO reduction from cloud migration, even after credits expire. The credit accelerates the business case but is not the entire justification.
Genuine readiness for cloud adoption: Organisations with validated cloud strategies, skilled cloud teams, and defined application roadmaps can consume credits efficiently within timeframes. This is a minority of customers.
Subscription-first cloud approach: Customers committed to consuming a high volume of cloud services (not just ERP but also analytics, cloud platforms, or SaaS tools) can use credits across multiple products, extending their effective value.
Conversion credits become commercially dangerous when they are the primary driver of cloud migration timing. If you are moving to RISE primarily because of conversion credits, not because cloud is strategically justified, you risk accelerating a transition before your organisation is ready — resulting in project failure, poor adoption, or higher-than-expected transformation costs.
Negotiation Strategy: Fighting for Real Value
Effective negotiation of conversion credits requires independence from SAP's framing:
- Demand alternative structures: Propose cash-equivalent discounts rather than time-limited credits. A 20% discount on year 1–3 RISE pricing is often more valuable than a conversion credit equivalent because it does not expire.
- Challenge valuation: Have independent advisors calculate the fair value of your on-premise licence portfolio. SAP's offer may significantly undervalue your estate, particularly if licences are under-deployed.
- Negotiate extended windows: Push credit expiry dates to 48–60 months, tie them to business milestones, and secure guarantees that unused credits can be applied to other SAP cloud products.
- Include scope flexibility: Ensure that credits can be applied across RISE, BTP, SuccessFactors, and Analytics Cloud. A credit tied only to RISE creates a locked-in dependency.
- Secure rollover provisions: Negotiate that credits unexpended due to delayed business decisions can roll to the next contract period rather than expiring.
- Get claw-back protection: Ensure that if you terminate or exit a RISE contract early, any credits you have already received are not clawed back.
Why Redress Compliance is your strongest ally here: Conversion credit valuations require deep understanding of SAP's pricing mechanics, negotiation leverage analysis, and independent technical assessment of what your actual cloud costs will be post-credit. We value your portfolio independently, model true post-credit TCO, and negotiate credit structures that align with your real business and technical readiness — not SAP's timeline. We've recovered millions in underclaimed credits and blocked premature migrations driven by expiring credit windows.
The Negotiation Playbook
When SAP presents conversion credits, follow this sequence:
- Request full valuation detail: Require SAP to break down the credit calculation line-by-line, showing which licences qualify and at what percentage.
- Commission independent valuation: Have an external advisor (not SAP or a SAP partner) calculate your actual licence value and what a fair conversion percentage should be.
- Model cash equivalents: Ask SAP what % discount they would offer for the same economic benefit as the proposed credit. The answer often reveals that credits are priced lower than they appear.
- Push back on expiry: Negotiate extended windows and milestone-based expirations. Most SAP negotiators will move on expiry terms if you have leverage.
- Separate pricing from credits: Negotiate base RISE pricing independent of credits. Do not allow SAP to bundle them in ways that obscure the true cost.
- Document in contract: Ensure all credit terms are fully documented: the total credit value, how it is applied (monthly, quarterly, etc.), the expiry mechanism, what happens if you exit early, and whether unused credits convert to other products.
Closing Perspective
SAP conversion credits are valuable tools, but they function as commercial management instruments first and cost-reduction mechanics second. SAP uses them to accelerate cloud adoption, smooth the perceived pain of migration costs, and lock customers into long-term commitments. This is not malice; it is how software licensing works at enterprise scale.
Your role is to extract maximum value from credits while ensuring that credit structures do not dictate your migration timeline or cloud strategy. Credits should accelerate a migration that is already justified on strategic and financial grounds, not be the primary justification for a migration.