S/4HANA migration planning">
The S/4HANA conversion is the single largest licensing event most ECC customers will face in the contract's life. The user side of the conversion is well-discussed: the move from Professional, Functional, and Limited Professional named users to the S/4HANA Full Use Equivalent metric, the reclassification of self-service users, the treatment of Solution Manager and BW users. The engine side — the order-to-cash engine, the payroll engine, the FI engine, the BW engine, and the long tail of smaller engines that quietly multiply on a mature ECC estate — is less discussed and frequently more consequential.
This article sets out how SAP converts ECC engine metrics to the S/4HANA commercial framework, where the conversion mechanics most often go against the customer, and how to model the conversion economics before the contract paperwork lands.
The structural change the conversion represents
ECC engines are licensed against a wide variety of metrics: order line counts, payroll runs, document line volumes, master-record counts, FTE counts, message volumes, and a handful of bespoke metrics that exist only for specific industry solutions. The metrics are independent — each engine has its own count, its own price, and its own audit treatment.
S/4HANA reorganises the engine model around a smaller set of headline metrics — principally the Full Use Equivalent count for the core platform, supplemented by specific engine entitlements for high-volume workloads. The reorganisation is not a one-for-one mapping. Some ECC engine entitlements convert cleanly into S/4HANA equivalents; others do not, and the conversion paperwork typically prices the "no-clear-equivalent" engines as separate add-ons or as part of a broader platform tier.
The financial impact of the conversion depends on which engines fall into which category for a particular customer. Customers with order-to-cash and FI engines that map cleanly to S/4HANA equivalents typically see a modest conversion premium. Customers with a long tail of niche engines — industry-specific add-ons, legacy modules, custom-licensed components — can see conversion uplift of forty to seventy per cent over the equivalent ECC position.
The five engine categories and how each converts
1. Core order-to-cash and procurement engines
The cleanest conversion category. ECC's sales order, purchase order, and inventory engines map directly to S/4HANA equivalents, and the conversion mechanics are well-established. The customer's leverage in the conversion is principally on the unit-price and discount-tier inheritance, not on the metric itself. See our order-to-cash engine analysis for the underlying mechanics.
2. Financial engines (FI document line, controlling)
The FI engine converts to the S/4HANA equivalent with some complexity around the document-line definition. ECC's FI document-line metric counts journal entries; S/4HANA's equivalent metric counts the same in principle but with subtly different scope — certain technical line items are included or excluded differently. The conversion can shift the count by five to fifteen per cent depending on the customer's document patterns. See our FI engine document line article.
3. Payroll and HR engines
The payroll engine conversion is increasingly tied to whether the customer is migrating payroll to Employee Central Payroll or retaining SAP HCM Payroll on the S/4HANA platform. The two paths have very different licensing implications. EC Payroll is subscription-based and outside the S/4HANA engine count. SAP HCM Payroll on S/4HANA retains the engine-based metric. See the payroll engine article for the metric definition.
4. BW and analytics engines
The BW engine conversion depends on the customer's analytics strategy: standalone BW on a separate licence, embedded BW inside S/4HANA, or migration to BW/4HANA on the HANA platform. Each path has different conversion mechanics. The detailed mechanics are in our BW engine data volume article.
5. Industry-specific and legacy engines
The most expensive conversion category. Industry-specific engines (IS-Retail, IS-Oil & Gas, IS-Banking, IS-Utilities) and legacy custom-licensed components frequently do not have a clean S/4HANA equivalent, and the conversion paperwork typically prices them as separate add-ons at the current S/4HANA list rates without the historical discount tier. The conversion premium on this category can exceed the customer's entire prior engine spend in some industry verticals.
The conversion paperwork patterns
SAP's S/4HANA conversion contracts come in three principal patterns: the "product conversion" (PCA) model, the "contract conversion" (CCA) model, and the "RISE migration" model. Each has different engine treatment.
The product conversion model maps individual ECC product entitlements to specific S/4HANA equivalents on a line-by-line basis. The mapping is fine-grained, the customer can negotiate each line, but the conversion economics are typically the most punitive because each line is priced independently at current S/4HANA list.
The contract conversion model rolls the entire ECC entitlement into a single S/4HANA contract value at a negotiated conversion ratio. The conversion is simpler, the customer has less line-by-line control, but the headline number is typically more favourable because it reflects a portfolio-level deal.
The RISE migration model converts the ECC entitlement into a RISE-based subscription with the engine entitlements re-expressed as part of the subscription tier. The conversion is the most opaque of the three, but for customers committed to a managed-service path it can produce the lowest total cost of ownership over a five-year horizon.
The four-step engine conversion model
Step 1 — Catalogue the ECC engine entitlement
The starting point is a complete inventory of the ECC engine entitlement: every engine, every metric, every count, every historical discount, every contract amendment. The inventory needs to be exhaustive — missing engines are converted at current list rather than at the historical discount.
Step 2 — Map each engine to the S/4HANA equivalent
For each engine, identify the S/4HANA equivalent (if any) and the conversion mechanic that SAP's standard paperwork applies. The mapping requires reading the current S/4HANA price list against the customer's ECC contract.
Step 3 — Model the three conversion scenarios
Build three financial models: product conversion, contract conversion, RISE migration. Each model should incorporate the conversion ratios, the discount-tier treatment, and the projected engine consumption over the next five years. The variance between the three scenarios is typically twenty to forty per cent of the S/4HANA total cost of ownership.
Step 4 — Negotiate the conversion against the most favourable model
The customer's leverage in the conversion negotiation depends on the alternative paths. A customer with three modelled scenarios can pivot between them in the conversation; a customer with only the path SAP has proposed has materially less leverage. The S/4HANA topic page covers the broader conversion architecture, and the RISE topic page covers the RISE-specific path.
The hidden conversion costs most models miss
Two cost categories are routinely under-modelled in customer-side conversion analysis. The first is the maintenance back-charge on the engines that do not convert cleanly. Some conversion paperwork applies a maintenance true-up against the prior engine entitlement at the conversion date, on the theory that the historical consumption was outside the converted entitlement. The true-up can be material.
The second is the consumption escalation during the parallel-running period. Customers who run ECC and S/4HANA in parallel during the migration see double consumption against both metrics, and SAP's audit position is typically that both should be paid. The negotiated treatment usually allows for a defined parallel-running window with consumption credit, but only if the customer asks. The detail is in the S/4HANA migration compliance service.
The audit position during conversion
SAP's audit activity frequently increases in the twelve months leading up to a conversion conversation. The auditor's pre-conversion audit can establish a baseline that the customer then has to accept as the starting position for the conversion paperwork. The optimal customer-side response is to complete the licence-hygiene work — dormant user cleanup, role-based reclassification, engine consumption cleanup — before the audit cycle opens, so that the baseline reflects the customer's optimised position rather than an inflated pre-cleanup position.
For the worked example, see our case study on a global manufacturer's S/4HANA conversion defence, where a structured pre-conversion cleanup and three-scenario modelling reduced the proposed conversion premium from 47% to 8%. The full methodology is in our S/4HANA conversion economics white paper.
What to ask before signing the conversion paperwork
First: what discount-tier treatment does the conversion paperwork apply to each converted engine? The default is typically the current weighted-average tier; the negotiated position should be the historical engine-specific tier.
Second: what is the parallel-running treatment, and for how long does it apply? Without an explicit parallel-running provision, the customer pays double during the migration window.
Third: what is the audit-rights position post-conversion, and does it permit SAP to back-test the conversion against subsequent consumption? A conversion that locks in the customer's post-conversion position protects against subsequent re-pricing.