The three approaches at a glance
To the point: Greenfield builds SAP S/4HANA from scratch, brownfield converts the existing system, bluefield selects — data, customising and processes are deliberately migrated or rebuilt. SAP calls the methodological path Selective Data Transition; BLUEFIELD® is the registered trademark of the SNP Group for this route.
Greenfield approach means rebuilding SAP S/4HANA on a "green field". Processes are redefined to best practice, the legacy system is replaced, historical data is selectively migrated or archived. For a deeper view of this path see our article on the greenfield approach.
Brownfield approach is the technical conversion of the existing ECC or SAP-ERP system to S/4HANA. Data structures, customising and interfaces are ported; business operations remain close to the familiar state. A deeper treatment is available in our article on the brownfield approach.
Bluefield approach is the hybrid path. Data, processes and customising components are selectively migrated from the legacy system, while other areas are rebuilt. SAP calls this methodological path Selective Data Transition (SDT); BLUEFIELD® is the registered trademark of the SNP Group, operationalised through its SNP Kyano CrystalBridge platform. According to IT-Onlinemagazin on the bluefield approach, the market chooses bluefield when neither a full rebuild nor a pure technical conversion fits the business need.
Three layers must be kept separate to avoid slipping into vendor marketing: the method (selective migration), the tooling (e.g. SNP Kyano CrystalBridge or alternatives) and the commercial vehicle (RISE with SAP, GROW with SAP or classic on-premise). Bluefield as a method can be combined with any of these vehicles — but the recommendation shifts with the constellation.
Our take: Method, tooling and commercial vehicle are three layers — mixing them means buying toolchains instead of making architecture decisions. The profile question decides the path, not the vendor slide.
When the bluefield approach is the right choice
To the point: Bluefield carries the day when you have a productive SAP system that contains structural breaks — for instance after a carve-out, an M&A consolidation, an industry switch or substantial data cleansing needs. Pure brownfield would be too preserving, pure greenfield too radical.
1. Carve-out or M&A consolidation with data selection. A mid-market automation specialist (430 employees, southern Germany) integrated a sister company in 2024 that ran on its own SAP tenant. Pure brownfield would have lifted both tenants including their legacy debt into S/4HANA; greenfield would have meant a 24-month runtime. Bluefield allowed the main tenant to be converted technically and only the business-relevant company codes, open items and master data of the sister to be carried over selectively.
2. Industry or branch switch within SAP. If you need to move from an industry solution to a retail solution, for instance, brownfield is not technically clean — the industry variants differ at depth. Selective migration is often the only economically viable option here because it decouples master and transactional data migration from customising refactoring.
3. Substantial customising load, but with clear refactoring targets. When 40 to 60 per cent of your customisings are still valuable but the rest is technical debt, brownfield lets too much legacy debt flow into S/4HANA. Greenfield costs you the valuable 40 to 60 per cent. Bluefield allows selection — provided that a robust master data and customising inventory has been completed beforehand.
4. Multi-country templates with differing maturity levels. A DACH Mittelstand company with sites in Germany, Austria and Switzerland often runs three tenants with very different customising depth. Bluefield allows the most mature tenant to be used as a template and the others to be migrated selectively into it.
5. Structured path into a RISE with SAP Private Cloud. Bluefield combines with RISE because Private Cloud still permits real customising depth. GROW with SAP (Public Cloud) rarely permits true bluefield selectivity — an important distinction often blurred in vendor slides.
Our take: Five typical indicators, but no automatic rule. Bluefield is the right choice when at least two clearly apply — otherwise brownfield or greenfield is usually more economical.
When greenfield is the right choice
To the point: Greenfield carries when the legacy system is obsolete, the process landscape needs strategic redefinition, or when Public Cloud (GROW with SAP) is the target architecture. From over 30 years of Mittelstand consulting we see four indicators: top-down process redesign, GROW target architecture, end-of-life legacy system, low customising binding. If three apply, greenfield is economically superior.
1. Strategic process redesign with a top-down mandate. When the board has resolved a new business logic — platform economics, data-driven service models or new sales channels — the legacy system is not a viable starting point. More on this in our wiki article on change management.
2. Public Cloud strategy (GROW with SAP). Public Cloud enforces standard processes and fixed half-yearly releases. Selective migrations are limited here. Greenfield is the straight path.
3. Legacy system at end-of-life. An SAP R/3 4.6 or an unmaintainable bespoke ERP is unsuitable as a bluefield source. The conversion effort exceeds the rebuild.
4. Low customising binding and stable standard processes. If your business already operates close to the SAP standard, brownfield or bluefield buys you nothing. Greenfield is cleaner and faster.
Our take: Greenfield is not the radical but the clean variant — when the profile fits. Bluefield only adds complexity in these cases without real benefit.
When brownfield is the right choice
To the point: Brownfield carries when the legacy system is stable, the customising load is documented as a competitive advantage and compliance audit trails must not be broken. Particularly economical when the 2027 maintenance deadline presses and budget is tight. Anyone with stable operations and documented customising depth should not pick bluefield because it is fashionable.
1. High customising depth with documented business value. When 80 to 95 per cent of your customisings are productively used and free of technical debt, conversion is the most economical path.
2. Compliance and audit-trail continuity. Sectors with GoBD, NIS-2 or Supply Chain Act duties require unbroken audit logic. Brownfield preserves it.
3. Limited project budget with a clear 2027 deadline. With the end of mainstream maintenance for SAP ECC on 31 December 2027 (per SAP maintenance strategy), brownfield is the fastest compliance anchor.
4. Stable business processes without strategic redesign need. When order-to-cash, procure-to-pay and finance run robustly, there is no business reason to rethink them.
Our take: Brownfield is the pragmatic anchor — not a compromise but a deliberate architecture decision for continuity. Leaving it for fashion reasons leaves value on the table.
Practical example: bluefield selection at a DACH machinery manufacturer
To the point: A mid-market machinery manufacturer (340 employees, Baden-Württemberg) chose SAP S/4HANA Selective Data Transition in 2025, after two carve-outs from a group structure had to be re-integrated. Result after 14 months: consolidated single tenant, 38 per cent fewer customisings, GoBD audit trail unbroken.
The company ran on SAP ERP 6.0 with three company codes, two of which had come from a carve-out completed in 2023. The customising landscape contained around 180 ABAP enhancements, half of which dated from the group era and no longer carried business value. Pure brownfield would have inherited that debt in S/4HANA; greenfield would have failed against the order-to-cash logic productive-hardened over twelve years.
The bluefield decision enabled three selections in parallel: first, the most mature company code was converted technically; second, the other two company codes were lifted onto the resulting template with selective master and transactional data migration; third, around 70 ABAP enhancements were deliberately not migrated but replaced with standard functionality.
We accompanied the bluefield approach with Selective Data Transition over eight months — the migration-path trade-off saved 32 per cent customising effort against brownfield. From our experience across more than 1,200 Mittelstand ERP projects, this is a typical bluefield profile: a concretely justifiable data-model or customising problem that neither brownfield nor greenfield covers economically.
Our take: The success lay not in the tool but in the upstream profile work. Three company codes, 180 ABAP enhancements with documented value share, a clear carve-out history — without that diagnosis, SDT too would have become a black box.
Decision criteria checklist
To the point: Use these 13 yes/no questions to place your profile quickly. More "yes" answers on the bluefield indicators points to the selective path; many "yes" answers on the brownfield or greenfield side points to the respective pure approach. The profile question decides — not the vendor argument.
Bluefield indicators:
- Have you completed a carve-out, acquisition or M&A consolidation in the past three years?
- Do your valuable customisings sit at 40 to 70 per cent of total customising load (the rest being technical debt)?
- Do you need to switch industry variant within SAP (for instance from industry to retail)?
- Do you operate multiple company codes or tenants with differing customising maturity?
- Are you planning consolidation into a RISE with SAP tenant?
- Do you hold internal SAP data architecture competence — or a reliable external partner for it?
Brownfield indicators:
- Are 80 to 95 per cent of your customisings productive and documented?
- Are you under strict GoBD, NIS-2 or Supply Chain Act audit duties?
- Do you want to reach the 2027 maintenance deadline with minimal risk?
Greenfield indicators:
- Has the board mandated a strategic process redesign?
- Is your target architecture GROW with SAP (Public Cloud)?
- Is your legacy system obsolete (SAP R/3 or older, bespoke, EOL)?
- Is your customising depth close to SAP standard?
Our take: Three "yes" answers or more on one side is a strong signal. If several sides answer with equal strength, an independent diagnosis is the next step — not a vendor workshop.
Frequently Asked Questions
Not automatically. Bluefield is the right choice when you have a concretely justifiable data-model or customising problem that neither brownfield nor greenfield covers economically. Choosing bluefield purely out of risk aversion often costs more than a properly dimensioned greenfield. From more than 1,200 Mittelstand projects: the profile question decides, not the vendor slide.
Bluefield as a method combines well with RISE with SAP (Private Cloud) because customising depth and selective data migration remain possible there. GROW with SAP (Public Cloud) rarely allows true bluefield selectivity because Public Cloud enforces standard processes and fixed releases. According to the DSAG Investment Report 2026, 22 per cent of DACH users plan on RISE and 6 per cent on GROW — a meaningful difference for the path decision.
SAP calls the methodological path Selective Data Transition (SDT). BLUEFIELD® is the registered trademark of the SNP Group, operationalised through SNP Kyano CrystalBridge. Method, tooling and commercial vehicle are three layers — a tool licence is not a migration strategy.
Next steps
The choice between bluefield, brownfield and greenfield is not a tool decision and not a vendor choice but an architecture decision spanning five to ten years of business operation. Our recommendation: start with a profile-based pre-assessment — size, sector, customising depth, M&A history, compliance pressure, cloud strategy. Validate the profile assignment against the checklist in this article. Get an independent diagnosis before commissioning a migration tool or implementation partner. More on our view of on-premise and hybrid systems is available in the linked wiki articles — both belong to the bluefield path decision. Current DACH benchmarks are also documented in the Bitkom Digitalisation Study 2025. An initial conversation is free of charge and leads to an honest assessment — not a proposal wrapped in methodology overhead.
