The brownfield route to S/4HANA — the in-place conversion of an existing ECC environment to S/4HANA — is the path most large SAP estates take. It preserves the configuration, the custom code, and the historical data. It also preserves the licence position. Every over-classification, every under-managed role-collection, every undocumented engine over-consumption that existed in the ECC environment carries into the S/4HANA estate at the conversion event. The conversion is the moment at which the legacy position is committed to the new contract structure, typically for the term of a multi-year subscription or perpetual agreement. This article sets out the five recurring licence-exposure categories specific to brownfield conversions and the buyer-side preparation that converts the legacy position into a clean baseline before the conversion locks it in. It is one of the engagement patterns inside our S/4HANA migration compliance service.
Why brownfield carries the legacy
The brownfield conversion is technically an in-place upgrade. The database, the configuration, the master data, the custom code, and the user-master data all migrate forward. SAP’s perspective on the licence position at the conversion event is that the converted estate’s licence requirement is whatever the legacy estate was generating immediately before the conversion. The contracted FUE quantity, the named-user counts, and the engine-metric entitlements are derived from the legacy USMM and LAW outputs. The conversion is therefore the moment at which the legacy measurement becomes the new contracted position, and the legacy measurement’s flaws become contractual obligations.
The greenfield alternative re-implements the SAP environment from scratch. The licence baseline is constructed at the implementation point rather than carried over. The brownfield route has many advantages — speed, cost, continuity — but the legacy-licence-position carryover is a meaningful disadvantage that buyers commonly underestimate.
Risk one — classification drift
The first and largest exposure is accumulated classification drift in the source ECC environment. Most ECC environments have ten to twenty years of role-collection assignments, organisational moves, and project-trial roles that were never deactivated. The USMM at the moment of conversion reflects all of this accumulated drift. The configured-entitlement classification carries over, the over-classification carries over, and the inflated user count becomes the contracted FUE baseline.
The mitigation is the classification rebuild before the conversion event. A buyer-side reclassification pass applied to the source ECC USMM produces the cleaned position. The cleaned position becomes the conversion baseline, and the cleaned baseline becomes the contracted FUE quantity. The economic value of this work is the cost differential applied across the contract life. The pattern is documented in the pharma S/4HANA case file.
Risk two — the FUE conversion ratio
S/4HANA introduces the Full Use Equivalent (FUE) metric. FUE consolidates named-user counts across user types into a single weighted metric, with different user types contributing different FUE values per the contract’s ratio table. The brownfield conversion applies an FUE ratio table to convert the ECC named-user counts into an FUE-equivalent quantity. The ratio table is a commercial negotiation point at the conversion event and is consequential: a small adjustment to a ratio applied across thousands of users moves the contracted FUE quantity materially.
The recurring buyer-side error is treating the FUE ratio table as a given rather than as a negotiation surface. Ratios vary across contract generations and across negotiation rounds; the buyer-side leverage at the conversion event includes the ratio table. The S/4HANA topic page covers the FUE mechanics in more detail.
Risk three — engine consumption
The ECC engine metrics — HR-PA, payroll, materials management documents, and so on — carry over to S/4HANA in a generally one-to-one mapping. The recurring exposure is that the ECC engine consumption may itself be over-reported, either because the measurement methodology counted internal traffic, or because the consumption included gross numbers rather than the contractually permitted net of carve-outs. The over-reported engine consumption becomes the contracted entitlement requirement under S/4HANA at conversion.
The mitigation is the engine measurement audit applied to the ECC environment before the conversion. The audit reproduces the ECC engine measurement under the validated methodology, compares the result to the SAP-reported number, and documents the gap. The cleaned engine position becomes the conversion baseline. See the engine metrics pillar for the broader engine-measurement frame.
Risk four — custom-code residue
The brownfield conversion preserves custom code, which is one of its principal advantages. But custom code in the ECC environment may invoke integration patterns that trigger digital-access exposure under the S/4HANA Digital Access framework. The exposure persists into the S/4HANA estate unchanged. Custom code that called SAP via batch interface from a third-party system, custom RFC consumers, custom IDoc processors — each of these is a candidate for digital-access measurement under the new framework.
The mitigation is the integration-topology review applied at conversion time. The review documents every active integration in the source ECC environment, classifies each as direct human use or indirect, and produces the inventory that supports the digital-access negotiation at the conversion event. The conversion is often the moment at which the digital-access position is first formally established, and the position at conversion sets the baseline for ongoing measurement. See the digital access pillar for the framework detail.
Risk five — the baseline trap
The brownfield conversion typically settles a multi-year subscription or perpetual entitlement based on the position established at the conversion event. The baseline trap is that the contracted quantity is then locked in for the contract term. Subsequent licence-optimisation work in the post-conversion environment releases unused capacity but the contracted minimum may continue to bind. The economic benefit of optimisation work that should reduce cost instead accumulates as un-utilised entitlement.
The mitigation is the structural one: the baseline negotiation at the conversion event should include flexibility to draw down the contracted quantity if usage proves materially below the baseline. Most SAP contracts include limited flexibility in this dimension and the buyer-side leverage at conversion includes the ability to enhance it. The RISE topic page covers the contractual mechanics where the conversion goes through the RISE structure; the RISE contracts pillar covers the broader frame.
The conversion event is the single largest commercial event in most SAP estates’ lifetimes. The legacy licence position carried into that event becomes the contracted baseline for the next five to ten years. The two months of preparation work that cleans the position has multi-million-pound consequences over the contract life.
The preparation sequence
The brownfield licence preparation has four parallel workstreams that should run in the six months before the conversion event. The classification rebuild, applied to the source ECC USMM. The engine measurement audit, applied to the source ECC engine consumption. The integration topology review, applied to the source ECC interface inventory. And the FUE ratio review, applied to the proposed conversion ratio table. Each workstream produces a cleaned baseline input to the conversion negotiation. The combined output is a defensible conversion baseline that is materially below the as-is ECC measurement and that becomes the contracted position for the S/4HANA estate.
How the three routes compare
The brownfield route preserves the legacy position. The greenfield route constructs a fresh position. The hybrid route — the selective re-implementation of high-value processes inside an otherwise brownfield migration — sits between the two on every dimension including licence-position implications. The selection between the three routes is principally a technical and process decision, but the licence-position consequences should be quantified before the route is chosen. In our 500+ engagements we have seen estates choose the brownfield route principally to preserve customisation, only to discover at the conversion event that the licence-position cost of preservation outweighs the customisation value. The S/4HANA conversion blueprint covers the route-comparison framework.
What good looks like
A well-executed brownfield licence preparation reduces the conversion baseline by between fifteen and thirty per cent against the unprepared position. The reduction comes principally from the classification rebuild (the largest component in most estates), the engine measurement cleanup (the second component), and the FUE ratio negotiation (the third). The economic value of the preparation runs into the millions on most large-estate conversions. The work is calendar-bounded and predictable, the methodology is well-established, and the dependency is on buyer-side execution discipline rather than on commercial negotiation skill. See the pharma case file for the pattern in practice.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
Before the conversion event, run a full licence-baseline review of the source ECC environment. Reclassify, clean the role-collections, document the engine consumption. The baseline carried into the conversion is the contracted position for the post-conversion structure. See the S/4HANA migration compliance service brief.