Bluefield — Selective Data Transition to S/4HANA
As of 2026-09-30
What is Bluefield?
Bluefield (SAP: Selective Data Transition) keeps the ECC processes and history that still pay, redesigns the rest and moves data selectively into S/4HANA. Rarely declared (2% of employers, Whitehall 2026) but widely practised (15% run hybrid multi-phase programmes).
What it is
Bluefield is the name the market gives to the third S/4HANA migration path — the one SAP itself calls Selective Data Transition (SDT). Greenfield rebuilds the system from SAP best-practice content and migrates only open items and master data; brownfield converts the ECC system in place with SUM/DMO and carries every process, customisation and year of history forward. Bluefield sits between them: the organisation keeps the processes, organisational structures and history that still earn their keep, redesigns what does not, and moves the data selectively — by company code, by time slice, by process area — into a target S/4HANA system.
Why it matters
- Picking brownfield or greenfield by label when the programme is in fact selective hides the real cost centre — data design, transformation rules and reconciliation — until the first month-end close breaks the reporting baseline.
Key points
- SAP names three paths: new implementation (greenfield), system conversion (brownfield), Selective Data Transition (bluefield).
- Typical mechanism: shell conversion of an empty ECC copy, redesign, then selective data load with transformation rules.
- Variants: Mix & Match, client / company-code transfer, carve-out, merger consolidation.
- Delivered by SAP DMLT services and SDT partners (SNP — BLUEFIELD trademark —, cbs, Natuvion…); tooling is vendor-specific.
- Whitehall 2026 (n≈800): 2% of employers declare bluefield, 15% run hybrid multi-phase, brownfield 21%, greenfield 17%.
- Wins on sound processes + bad data, harmonisation needs, phased go-lives, tight downtime.
- Loses when the process model is the problem (greenfield) or the landscape is small and clean (brownfield).
- Cost moves from technical conversion to data design, transformation rules and reporting reconciliation.
Terms used on this page
- Selective Data Transition (SDT)
- SAP's name for the bluefield path: selective transfer of configuration and data into S/4HANA.
- Shell conversion
- Convert an ECC copy stripped of master and transactional data, then load data selectively.
- Mix & Match
- New greenfield configuration receiving selected historical data from ECC.
- DMLT
- SAP Data Management and Landscape Transformation — SAP's service line for selective and landscape transformations.
- Time slice
- Migrating only a bounded range of fiscal years of history.
- Company-code transfer
- Moving selected legal entities into a target system, e.g. for a carve-out or consolidation.
- Legacy translator
- Consultant who reads ECC customising and historical dependencies and maps them to the S/4HANA target.
- Reporting reconciliation
- Proving that analytics totals match before and after the transition, across re-mapped structures.
Sources
- Whitehall Resources — The Pragmatic Middle: The Bluefield Shift (2026 SAP Talent Survey, Sept. 2026)
- Whitehall Resources — Choosing the right SAP S/4HANA migration talent model (May 2026)
- SAP Support — Data Management and Landscape Transformation (DMLT)
- SNP — Greenfield, brownfield and BLUEFIELD: the approaches to SAP S/4HANA migration
- SNP — SAP S/4HANA Selective Data Transition Engagement
- cbs Corporate Business Solutions — Selective Data Transition
Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.