The third S/4HANA migration approach — positioned between the greenfield rebuild and the brownfield system conversion — is the bluefield or selective data transition. Bluefield deploys a new S/4HANA system architecture from scratch, then selectively migrates data and configuration from the ECC source, leaving behind the historical complexity, unused customisation, and legacy data structures that would otherwise be carried forward into the new system. As an architectural pattern bluefield offers real advantages: a clean technical foundation, controlled scope of data migration, and the opportunity to redesign business processes during the move. As a licensing event bluefield carries a hybrid position that is neither greenfield nor brownfield, and the entitlement cost depends on a small number of decisions made during the migration design. Across our S/4HANA migration compliance engagements we work through five decision points that determine the licensing outcome.
How SAP categorises bluefield deployments
The first practical question is which conversion programme applies to the bluefield deployment. SAP’s contract conversion programme treats brownfield and greenfield as separately named paths; bluefield is not consistently named in the conversion templates. In practice the bluefield deployment is normally negotiated as a greenfield event with conversion credit allowed for the source ECC entitlement that the buyer chooses to surrender.
The conversion credit treatment is the principal economic lever. A bluefield deployment that conserves the full ECC entitlement (because the ECC system continues to operate during a transition period) carries different economics from a bluefield deployment that surrenders the ECC entitlement at cutover. The negotiation should resolve the treatment at sign rather than at execution. The RISE conversion economics piece covers the credit mechanics in detail.
Decision one — scope of data migration
The first migration design decision is the scope of data brought across. A narrow scope (current open documents, current master data, current period activity) supports a clean go-live and a small new-system footprint. A broad scope (multi-year transaction history, historical master data, archived activity) approaches the brownfield position and surrenders many of the bluefield advantages.
Why the scope decision affects licensing
Data scope affects licensing through two channels. The first is engine consumption: engines licensed on data volumes (document volumes, processed records) consume against the data brought forward, not the data left behind. A narrow scope produces a lower engine consumption position. The second is user activity: users with substantial historical data in the source system may be classified differently in the destination system depending on the migrated transaction history. The engine metrics topic page covers the engine consumption mechanics.
Decision two — scope of configuration migration
The second design decision is the scope of configuration migration. Configuration that is brought across (customer-namespace ABAP, modified standard objects, custom tables) carries the same compliance position into the destination system that it had in the source. Configuration that is rebuilt from scratch in the new system carries the destination’s compliance position.
The relevance is to custom-code obligations and to indirect access. Custom code carried forward inherits the source-system audit risk; custom code rebuilt to S/4HANA standards reduces the audit risk but introduces remediation cost. The custom code remediation piece covers the rebuild-vs-carry decision.
Decision three — transition-period architecture
The third decision is whether the source ECC system continues to operate during a transition period and, if so, for how long. The transition-period architecture has direct licensing implications: during the transition, both systems carry their own licensing footprint, both systems are subject to USMM measurement, and both systems contribute to the compliance position.
Decision points inside the transition
Three sub-decisions sit inside the transition architecture. First, the duration: how long both systems will operate in parallel. Second, the user assignment: whether users are licensed on both systems during the transition or solely on the destination. Third, the data synchronisation: whether ongoing transactions in the source are replicated to the destination, with the audit implications that synchronisation carries. The S/4HANA topic page covers the transition-period framework.
Bluefield is sold as the best-of-both-worlds migration pattern. The pattern works architecturally; the licensing position needs to be designed deliberately or the buyer ends up paying for the source system, the destination system, and the migration overhead at the same time.
Decision four — FUE sizing
The destination S/4HANA system requires FUE sizing in the standard manner. The bluefield position offers an opportunity that brownfield does not: the destination user population can be sized against the redesigned role catalogue rather than against the inherited authorisation profile of the source. The result is typically a lower FUE count than a brownfield conversion would produce, provided the redesign discipline is applied.
The discipline involves: mapping each destination role to the underlying business activity rather than to the source-system role from which it descends; sizing each user against the minimum required role for their actual activity; cross-checking the role-based size against the documented FUE conversion table. The FUE conversion math piece sets out the conversion calculation.
Decision five — residual source-system position
The fifth decision concerns what happens to the source ECC system after the transition completes. The options are: full decommissioning (entitlement surrendered, source system retired); read-only retention (entitlement reduced, source system retained for historical access); operational retention (entitlement maintained, source system continues to operate for legacy processes that did not migrate).
Each option carries different long-term cost. Full decommissioning produces the cleanest economic position but requires that all data and process needs are met by the destination system. Read-only retention is the most common compromise but requires the buyer to negotiate a read-only entitlement that SAP’s standard catalogue does not cleanly provide. Operational retention is rarely chosen deliberately but is sometimes the result of incomplete migration scope. The brownfield licensing risks piece covers the dual-system position.
The negotiation implications
Bluefield’s licensing position should be negotiated as a single integrated programme rather than as a series of separate transactions. The integrated negotiation captures: the conversion credit treatment for surrendered ECC entitlement; the FUE sizing for the destination system; the transition-period dual-licensing arrangement; the read-only entitlement (if applicable) for the retained source; and the support cost for both systems during transition. Each item negotiated separately produces a worse total than the same items negotiated together. The S/4HANA migration license strategy white paper sets out the integrated negotiation framework. The pharma S/4HANA migration case file documents an estate that negotiated the integrated programme.
— 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.
The follow-through
Bluefield is a workable migration pattern for buyers whose source-system complexity argues against pure brownfield and whose timeline argues against pure greenfield. The licensing position is workable but is not the default; the buyer must design the licensing outcome deliberately or it will resolve in SAP’s favour by default. The five decisions above produce a defensible position when worked through systematically. The greenfield license baseline piece covers the alternative pattern that bluefield is compared against.