The single most consequential moment in an SAP S/4HANA migration, from a licensing perspective, is the named user conversion clause in the migration paperwork. The clause maps each ECC named user type the customer currently holds to one or more S/4HANA Full Use Equivalent (FUE) categories, with a defined conversion ratio per category. The default conversion ratios on the SAP migration price list are the most expensive outcome possible for the customer. Each ratio is negotiable, and the difference between the default and the negotiated position is typically twenty to forty per cent of the total S/4HANA user-licence cost over the first five contract years.
Most procurement teams treat the conversion as a back-office exercise managed by the SAP administrator. By the time they understand the financial implications, the migration paperwork has been countersigned and the conversion is locked in. This article walks through the structure of the FUE conversion, where the negotiable points are, and the diagnostic exercise every procurement team should run before the migration paperwork lands.
How FUE conversion actually works
S/4HANA replaced the legacy named user types (Professional, Functional, Limited Professional, Developer, etc.) with a new metric called Full Use Equivalent. The FUE is a normalised licensing unit that allows different user categories to be expressed in a common denominator. The new categories are Advanced Use, Core Use, Self-Service Use, and several specialised types for analytics and developer access.
Each S/4HANA category carries an FUE conversion factor relative to the Advanced Use base. The current standard factors are approximately 1.0 for Advanced Use, 0.2 for Core Use, and 0.05 for Self-Service Use. The customer’s ECC named user population is mapped into these categories using a published conversion table, and the total FUE entitlement is calculated.
The conversion default table
The default migration table maps ECC Professional users to S/4HANA Advanced Use on a 1:1 basis, ECC Functional users to S/4HANA Core Use on a 1:1 basis, and ECC Limited Professional users to S/4HANA Self-Service Use on a 1:1 basis. On paper, the customer’s total user count is preserved. The trap is in the FUE arithmetic that follows.
Where the cost emerges
Under the default mapping, a customer with 1,000 ECC Professional users, 3,000 Functional users, and 5,000 Limited Professional users converts to 1,000 Advanced Use, 3,000 Core Use, and 5,000 Self-Service Use — a total FUE of 1,850 (1000 + 600 + 250). At the current Advanced Use list price of approximately $4,800 per FUE per year, that is $8.88M of annual entitlement. The same customer’s ECC contract typically licensed the underlying population at approximately $5.2M annually. The conversion alone produces a $3.68M annual increase before any usage growth.
The four negotiation points that move conversion cost
Four levers move the converted cost. They are stacked rather than alternative — a well-prepared migration negotiation engages all four.
1. Category re-mapping
The default mapping treats every ECC Professional user as a Advanced Use S/4HANA user. In reality, a substantial portion of the ECC Professional population only uses functionality that falls within the Core Use scope under the S/4HANA definitions. A pre-migration usage analysis, run from ECC transaction logs, typically identifies twenty to forty per cent of Professional users who can credibly be mapped to Core Use rather than Advanced Use. The FUE saving is the difference between the 1.0 and 0.2 conversion factors applied to the re-mapped population.
2. FUE conversion ratio
The published conversion ratios are not contractually fixed — they are the SAP price-list defaults. Negotiating a 0.15 Core Use factor instead of 0.2, or a 0.04 Self-Service Use factor instead of 0.05, produces meaningful savings on populations of any reasonable size. SAP’s migration desk has discretion to offer favourable conversion ratios as part of the broader S/4HANA commitment.
3. Grandfathering of pricing
The most powerful single lever. A grandfathering clause that applies the customer’s existing ECC weighted-average discount to the converted FUE population for a defined period (typically three to five years) effectively preserves the existing economic position while the technical migration completes. The clause is routinely conceded by SAP when the customer commits to a defined S/4HANA implementation milestone.
4. Future-growth caps
The migration commercial agreement should include a defined per-FUE price ceiling for the first three to five years, protecting the customer against SAP’s annual list-price uplift. Without the ceiling, the converted population is exposed to whatever pricing changes SAP introduces in subsequent years.
The diagnostic exercise every procurement team should run
Before the migration paperwork lands, four questions need a written answer. Procurement teams who can produce the answers walk into the conversion discussion from a position of strength.
- What is the current ECC named user population, by license type, by business unit, and by usage profile? The data is in SUIM and the USMM extract; the analysis is the discipline.
- What is the current FUE-equivalent under the default conversion, and what is the resulting S/4HANA annual cost at list price?
- What proportion of the ECC Professional population credibly maps to S/4HANA Core Use under a documented usage analysis? This is the population that drives the highest-impact re-mapping savings.
- What is the existing ECC weighted-average discount, and what would the S/4HANA cost be if that discount were applied to the converted FUE population?
Timing the negotiation against the broader migration
The named user conversion is one of several commercial items in the broader S/4HANA migration agreement. The others include database conversion (Oracle to HANA), engine conversion (see our companion piece on engine metrics in S/4HANA conversion), and any RISE or GROW deployment-model commitments. The negotiation sequence matters: anchoring the user conversion early, before the broader deal economics are agreed, prevents the user-licence cost from being used as a "give" to close other line items.
The strongest negotiation position is one where the customer has documented the ECC baseline, calculated the default conversion outcome, and prepared a counter-proposal with specific re-mapping, conversion-ratio, and grandfathering terms. That document, presented to SAP at the start of the migration commercial discussion, reframes the conversation from "what does the default conversion produce" to "what variance from the default will SAP accept".
The RISE wrinkle
Where the migration includes a RISE deployment model, the user conversion is bundled with infrastructure and managed-service fees in a single per-FUE rate. The bundled rate obscures the underlying conversion arithmetic, making it harder for the customer to evaluate whether the conversion ratios are competitive. Demand a line-item breakdown of the per-FUE rate showing the user-licence component, the infrastructure component, and the managed-service component separately. SAP will resist this; the resistance is itself an indicator of where the margin is.
For the broader RISE structural analysis, see our SAP RISE topic page and the RISE economics white paper. The SAP S/4HANA Migration Compliance service covers the broader migration commercial structure. For real-world conversion outcomes, see our global utility S/4HANA migration case file, which documents a conversion where the default position would have produced a $14.2M annual user-licence cost and the negotiated outcome closed at $8.6M. For the adjacent named-user discipline, see our license pool rebalancing piece.
The post-signature compliance posture
Even where the conversion has been negotiated favourably, the post-signature compliance posture in S/4HANA is materially different from ECC. The FUE consumption is measured continuously through native S/4HANA telemetry rather than annually through USMM, which means the customer’s license position is visible to SAP in near-real-time. Three operational disciplines protect the negotiated economic position: monthly FUE consumption review against entitled volume, quarterly role-content drift analysis to prevent silent reclassification of Core Use users to Advanced Use, and an annual post-conversion audit-readiness review aligned to the migration anniversary date.