SAP Conversion Credits give existing ECC perpetual license value against future S/4HANA subscription, on premise license, or RISE bundle. Published credit ratios start at 50 to 70 percent of historical net license fee. Advisor led negotiations regularly reach 80 to 95 percent. The credit applies during the conversion window, typically the first three subscription years for RISE, or as direct license value offset for on premise. Three conversion paths drive credit value: brownfield, greenfield, and bluefield. The wrong path destroys 30 to 60 percent of available credit. For a Fortune 1000 ECC estate the credit difference between best and worst path execution exceeds $14M. This page documents the three conversion paths, the credit calculation, the timeline, and the common mistakes that destroy credit value.
The three conversion paths
SAP defines three conversion paths from ECC to S/4HANA, each with different scope, effort, and Conversion Credit treatment.
| Path | Scope | Effort window | Credit treatment |
|---|---|---|---|
| Brownfield (System Conversion) | In place technical upgrade of existing ECC to S/4HANA, preserving custom code, configuration, and data | 14 to 24 months | Full Conversion Credit available against future S/4HANA license or RISE subscription |
| Greenfield (New Implementation) | Fresh S/4HANA implementation with redesigned processes, selective data migration | 18 to 30 months | Conversion Credit available but credit conversion ratio often lower |
| Bluefield (Selective Data Transition) | New S/4HANA implementation with selective data and configuration migration from ECC | 20 to 36 months | Credit available, treatment varies by selective scope |
The path selection has implications beyond the implementation method. Brownfield preserves the historical commercial relationship: existing ECC perpetual licenses convert directly to S/4HANA equivalents at the highest credit ratio. Greenfield restarts the commercial relationship: the customer is treated closer to a new SAP customer, with credit available but at lower conversion ratios.
How Conversion Credit is calculated
SAP Conversion Credit calculation has three primary inputs: the historical net license fee paid for the ECC perpetual license, the user equivalent mapping from ECC named user types to S/4HANA FUE types, and the conversion ratio negotiated for the deal.
| Input | Source | Typical value |
|---|---|---|
| Historical net license fee | Original ECC license agreement, net of any historical discount | Sum across all ECC engines and named user purchases |
| User equivalent mapping | SAP's published ECC to S/4HANA user type mapping table | 1 ECC Professional User typically maps to 1 S/4HANA Advanced FUE |
| Conversion ratio (published) | SAP standard offer document | 50 to 70 percent of historical net license fee |
| Conversion ratio (negotiated) | Advisor led negotiation | 80 to 95 percent of historical net license fee |
| Credit application window | Conversion agreement term | First 3 subscription years for RISE, or perpetual offset for on premise |
For a customer with $18M of historical ECC perpetual license fee, the published 50 to 70 percent ratio produces a Conversion Credit of $9M to $12.6M. A negotiated 85 percent ratio produces $15.3M. The $3M to $6M gap is the negotiation lever.
Conversion Credit rule: the published credit ratio is the starting position, not the final value. Conversion Credit is negotiable on the same basis as any other major commercial term. Customers who accept SAP's first offer without independent benchmarking leave 15 to 40 percent of available credit on the table.
Brownfield path mechanics
Brownfield is the most common path for enterprise ECC customers with substantial custom code and active business operations. The path preserves the technical estate (custom code, configuration, master data, transactional history) and upgrades the underlying technology layer to S/4HANA. SAP supplies the technical tools (Software Update Manager, Maintenance Planner, Simplification Item Catalog).
The commercial treatment of brownfield is the simplest of the three paths. Existing ECC perpetual licenses convert to S/4HANA equivalents through the SAP Conversion Credit framework. The user mapping is direct: ECC Professional User maps to S/4HANA Advanced FUE, ECC Limited Professional maps to Core FUE, and so on. Conversion Credit applies at the highest available ratio because the customer is preserving the commercial relationship with continuous use of the SAP estate.
The brownfield trap is custom code remediation cost. Simplification Items (changes between ECC and S/4HANA that affect custom code) require code remediation effort that scales with custom code volume. A 15,000 object ECC estate typically requires 4,000 to 7,000 hours of custom code remediation during brownfield conversion. The remediation effort is technical work, not Conversion Credit impact.
Greenfield path mechanics
Greenfield is the path for customers who want to restart with standard S/4HANA processes, abandoning historical custom code and historical process customisation. The implementation is treated as a new SAP project: fresh blueprint, fresh build, fresh configuration, with selective data migration from ECC for master data and open transactional data.
The commercial treatment of greenfield is more complex. Conversion Credit is available but the conversion ratio is typically 10 to 25 percent lower than brownfield because SAP treats greenfield as closer to a net new customer relationship. The user mapping is still anchored on historical ECC users, but the implementation is treated as a fresh S/4HANA contract with full RISE or GROW or on premise subscription pricing.
The greenfield value case is process simplification. Customers who have heavily customised ECC over 15 to 20 years often find that 30 to 50 percent of the customisation no longer reflects current business process, and the standard S/4HANA functionality has caught up to or exceeded the customised behaviour. Greenfield surfaces this simplification, and the multi year operating cost reduction often exceeds the Conversion Credit ratio gap.
Bluefield path mechanics
Bluefield is the selective migration path: a new S/4HANA implementation with selective data and configuration migration from ECC, typically using specialised migration tools from SNP, Datavard, or other partners. Bluefield is the right path for customers who want most of the greenfield benefits (clean S/4HANA estate, modern configuration) with some preservation of historical data and selected custom code.
The commercial treatment of bluefield varies by selective scope. Conversion Credit ratios fall between greenfield and brownfield, depending on what proportion of the ECC estate is preserved. The user mapping follows the standard SAP framework. The implementation timeline is the longest of the three (20 to 36 months) because the selective migration adds complexity to a fresh S/4HANA build.
What destroys Conversion Credit value
Six common mistakes destroy Conversion Credit value during the conversion negotiation:
- Accepting the published ratio. The 50 to 70 percent published ratio is the starting position. Advisor led negotiations regularly reach 80 to 95 percent. Accepting the published ratio without benchmarking leaves $3M to $6M on the table on a $18M historical license base.
- Greenfield without explicit credit preservation. Greenfield contracts that do not explicitly reference Conversion Credit eligibility are sometimes processed as net new contracts, losing credit value entirely.
- Letting historical license fee discount the calculation base. SAP commercial teams sometimes propose calculating Conversion Credit against the discounted license fee (net) rather than the list license fee. The right base is the historical net fee, not list, but the calculation method should be agreed explicitly.
- Surrendering Maintenance prepayments. Multi year Maintenance prepayments on the ECC estate carry value at conversion. Maintenance prepayments typically convert at 100 percent against future RISE subscription or on premise Maintenance, but only when explicitly preserved in the conversion agreement.
- Accepting credit window compression. SAP defaults to applying Conversion Credit across the first 3 RISE subscription years. Negotiating extension to 5 years preserves more credit value against multi year commitment.
- Conversion without Digital Access reset. The conversion moment is the right time to reset Digital Access exposure. Accepting SAP's inflated Digital Access volumes during conversion is the most common cost driver outside the per FUE rate. See SAP Digital Access Pricing.
The 12 to 18 month conversion calendar
The conversion calendar covers commercial negotiation, technical preparation, and execution. The commercial negotiation runs in parallel with the technical preparation, which compresses the calendar but increases coordination complexity.
| Month from cut over | Commercial activity | Technical activity |
|---|---|---|
| T-18 months | Path selection (brownfield, greenfield, bluefield). Conversion Credit modelling. Initial SAP commercial conversation. | Custom code analysis. Simplification Item review. SI partner selection. |
| T-12 months | FUE methodology validation. Digital Access reset modelling. Tier and bundle decisions. | Conversion sandbox built. First end to end test cycle planned. |
| T-9 months | Conversion Credit ratio negotiation. Multi year price hold negotiation. | First conversion test cycle complete. Issue triage. |
| T-6 months | Contract execution. Final term negotiation. | Second conversion cycle. Pre production environment built. |
| T-3 months | Post signature commercial close out. | Cut over rehearsal cycles. |
| T-0 | Conversion live, subscription begins, credit applied. | Production cut over. |
Worked example: 1,700 FUE estate
An enterprise ECC customer with $18M historical net ECC perpetual license fee, converting to RISE Private Cloud Premium tier at $250 per FUE per month for 1,700 FUEs ($5.1M per year subscription). Two outcomes:
| Outcome | Credit ratio | Conversion Credit value | Subscription cost net of credit (3 years) |
|---|---|---|---|
| SAP first offer (published ratio) | 60% | $10.8M | $15.3M - $10.8M = $4.5M |
| Advisor led negotiation | 88% | $15.8M | $15.3M - $15.8M = $0 (credit exhausted, surplus rolls to year 4) |
The $5M difference in three year subscription cost is driven entirely by the Conversion Credit ratio. Both outcomes reflect the same underlying ECC license history, the same FUE count, and the same per FUE subscription rate. The negotiated ratio is the variable.
User mapping from ECC to S/4HANA FUE
The user mapping from ECC named users to S/4HANA FUE classifications is the second largest credit value lever after the conversion ratio. SAP publishes a standard mapping table, but customer side validation routinely produces a different mix that affects both the Conversion Credit calculation and the future per FUE subscription cost.
| ECC named user type | SAP standard mapping | Customer side validated mapping |
|---|---|---|
| Professional User | 1.0 Advanced FUE | 1.0 Advanced FUE for active power users, 0.2 Core FUE for inactive or limited use |
| Limited Professional User | 0.2 Core FUE | 0.2 Core FUE confirmed, with 0.033 Self Service for users below activity threshold |
| Employee User | 0.033 Self Service FUE | 0.033 Self Service FUE for active users, 0 for inactive |
| ESS User | 0.033 Self Service FUE | 0.033 confirmed |
| Test User | 0 (not counted) | 0 confirmed, with documentation requirement |
| Developer User | 0.2 Core FUE | Separate Developer Use entitlement preferred over FUE counting |
A 5,000 named user enterprise ECC estate under SAP standard mapping typically produces 2,100 to 2,600 FUEs. Under customer side validated mapping with activity filtering, the same estate produces 1,400 to 1,800 FUEs. The 25 to 40 percent gap affects both the Conversion Credit calculation (lower FUE count produces lower future subscription, which means a smaller portion of the credit is consumed) and the ongoing subscription cost (lower FUE count produces lower annual subscription).
Where to start
The Conversion Credit work begins in the commercial planning phase, 18 months before cut over. The first step is a complete inventory of historical ECC license value, including all engines, named user purchases, industry add ons, and maintenance prepayments. The second step is the user mapping from ECC named users to S/4HANA FUE classifications. The third step is the negotiation against the published credit ratio with benchmarking from comparable conversions.
For the broader conversion path framework see SAP Conversion Credits Overview. For the underlying S/4HANA edition decision see S/4HANA Public vs Private Cloud vs On Premise. For RISE specific commercial guidance see RISE with SAP Negotiation and RISE vs GROW vs HEC. For the SAP commercial framework see SAP Licensing Complete Guide and the SAP vendor intelligence hub. For active commercial work see Software Licensing Advisory and Cloud Contract Negotiation. For the deadline driving the conversion timeline see SAP ECC 2027 End of Life Strategy.