Every CTO evaluating an SAP ECC migration ends up staring at the same three options: brownfield, greenfield, or bluefield. Most sources give you the definitions. A comparison table. A conclusion that basically says “it depends.”
That’s not helpful. That doesn’t help you make a decision.
Here’s the context: ISG‘s 2026 research of 200 senior SAP decision-makers found that 60% of SAP migration projects ran over budget or over time — regardless of which approach they chose. Organisations don’t fail because they picked the wrong approach. They fail because they picked without a framework.
This article gives you that framework. A clear taxonomy of all three approaches, what the ISG outcome data actually shows, the clean core and AI access link most organisations miss when they go brownfield, and an original scoring model you won’t find anywhere else. This guide is part of our complete guide to SAP ECC end of support and what comes next, where we cover the full decision landscape from deadline context through strategic alternatives. If you’re still working out whether migration is the right move at all, start there first.
What are the differences between brownfield, greenfield, and bluefield SAP migration?
The short version: Brownfield converts your existing ECC system in place, keeping all customisations and data. Greenfield rebuilds S/4HANA from scratch. Bluefield — also called Selective Data Transition or SDT — selectively migrates the parts worth keeping.
Brownfield (System Conversion): converting what you have
SAP’s formal name is System Conversion. You take your existing ECC system and convert it to S/4HANA, retaining configurations, historical data, custom ABAP, and existing processes. Your Z-objects come with you. Your inefficient processes come with you too.
34% of organisations chose brownfield per ISG’s 2026 research. It’s the fastest time-to-go-live and causes the least initial disruption. The cost is carried-forward technical debt and a clean core deficit that limits what you can do with AI down the track.
Greenfield (New Implementation): rebuilding from scratch
SAP’s formal name is New Implementation. Processes redesigned from the ground up, customisations replaced by SAP standard functionality, historical data left behind — only master data and open transactions make the move.
18% of organisations chose greenfield. That low adoption reflects the change management burden and the timeline. LeverX estimates greenfield at 12–18 months versus 6–10 months for brownfield. When the 2027 mainstream support deadline is right there in your calendar, that gap matters.
Bluefield / Selective Data Transition (SDT): the hybrid
“Bluefield” is SNP Group‘s trademarked term. SAP’s official label is Selective Data Transition. Both describe selectively migrating chosen data, processes, and configurations from ECC to S/4HANA.
Two sub-variants worth understanding. Shell conversion brings over most ECC configurations selectively, with decisions made during migration — moderate transition speed, moderate clean core attainment. Mix-and-match starts with a new S/4HANA system and selectively integrates ECC elements — higher clean core attainment, suited to organisations that want a modern baseline with selective legacy retention.
48% of organisations chose bluefield/SDT — a plurality. But the aggregate outcome data for the category is murky. Shell conversion and mix-and-match are meaningfully different projects. If you’re evaluating bluefield, compare against the relevant sub-variant, not the category as a whole.
What does the data say about which SAP migration approach performs better?
The short version: The data is sobering. 60% of projects run over budget regardless of approach. Brownfield carries the highest post-migration complexity. Greenfield has the cleanest outcomes but lowest adoption. Bluefield’s aggregate data is muddied by the variance in project types it covers.
The headline from ISG’s 2026 research is not flattering for anyone: nearly 60% of projects delayed and over budget. The causes — underestimated complexity, scope creep, failure to understand internal constraints — are governance failures, not approach failures. ISG principal analyst Michael Dornan put it plainly: “A lot of the delays are caused by people, not necessarily the technology.”
Brownfield gives you the fastest time-to-go-live, but that advantage erodes. LeverX notes the time savings often vanish once you start dealing with legacy complexity. More than half of ISG respondents agreed they had over-customised their ERP to the point where standardisation felt risky. For brownfield organisations, that risk isn’t deferred — it’s imported into the new system. For the full breakdown of why brownfield migrations limit transformation value, the outcome statistics per approach are covered in depth.
Greenfield outcomes on technical debt and AI readiness are consistently the strongest. The 18% adoption reflects the change management burden and timeline cost, not poor long-term results.
Bluefield’s aggregate statistics are genuinely muddied. Shell conversion for a mid-market company and mix-and-match for a multinational are both labelled “bluefield.” Their risk profiles are not comparable. The 60% over-budget figure applies across all three approaches. Approach selection matters — but without Phase Zero governance and an ABAP assessment, no approach prevents failure.
What is SAP clean core and why does your migration path determine your AI access?
The short version: Clean core is SAP’s architectural principle that S/4HANA should remain close to standard, with custom functionality built via SAP BTP rather than direct ABAP modifications. AI capabilities including SAP Joule require clean core to function. Brownfield delivers the lowest clean core attainment by default; greenfield delivers the highest.
SAP’s definition: keep your ERP system as close as possible to its standard state. Handle custom modifications through cloud extensions on SAP Business Technology Platform (BTP) rather than direct ABAP modifications to the core. The core stays clean. Upgrades arrive without you re-validating custom code every time.
Clean core is not just an architectural preference. It’s the gate for AI capability access. The broader implications of how the S/4HANA migration calculus has shifted with AI are covered in our complete SAP ECC end of support guide.
Brownfield migrations carry Z-objects from ECC into S/4HANA. Even the custom code that survives the conversion creates a clean core deficit — it needs post-migration remediation, rebuilt as BTP extensions. That’s a separate project, and it’s routinely underestimated when brownfield is chosen primarily for speed.
SNP Group’s technical summary puts it simply: Brownfield = Low clean core attainment. Shell Conversion = Moderate. Mix-and-Match = High. Greenfield = Very High.
SAP Joule — SAP’s generative AI copilot — requires clean master data and a standard system architecture to function. ISG’s finding: “Fragmented processes, extensive customisations, and legacy data structures often constrain which AI use cases can be effectively deployed after go-live.” Choosing brownfield for speed today may mean paying to remediate customisations later before AI features can be activated. Frame it as optionality risk. It’s real.
How do you audit your ABAP customisation debt before committing to a migration approach?
The short version: Run SAP’s Readiness Check and Custom Code Migration Worklist (CCMW) to inventory your Z-objects before any approach selection discussion. Custom code volume is the first hard constraint — it must be assessed before timeline or budget conversations start.
Z-objects are the custom ABAP code built on top of standard SAP ECC — programmes, reports, function modules, interfaces, and enhancements created to support business-specific processes that SAP standard didn’t cover. Their volume and business criticality determine which migration approaches are feasible for your organisation. Brownfield preserves them. Greenfield replaces them. Bluefield selectively migrates them. If you don’t know what you have, you can’t evaluate which approach fits.
SAP provides the tooling. The SAP Readiness Check analyses your ECC system and flags compatibility issues and custom code requiring remediation. The Custom Code Migration App / CCMW automates the Z-object inventory and identifies what’s compatible, what needs re-coding, and what calls retired tables. Run both before any approach selection conversation.
For each Z-object, assess four things: business criticality (does SAP standard now cover this need?), usage frequency (is this active code or dead code?), remediation effort (how many person-days to replace with a BTP extension?), and S/4HANA compatibility (does it call retired tables?). A significant portion of custom code in mature ECC systems is dead code. Removing it before migration reduces complexity regardless of approach — and is often the first leverage point for brownfield organisations.
Classify your Z-object inventory as Low (mostly standard SAP, few custom objects with S/4HANA equivalents), Medium (moderate custom code, some business-critical Z-objects requiring remediation decisions), or High (extensive Z-object inventory, core processes depend on custom ABAP, many objects call deprecated functionality). This classification feeds directly into the scoring model below. One note: organisations in the 50–500 employee band typically have lower Z-object volumes than the large enterprise benchmarks used in most migration research — smaller organisations may find greenfield more feasible than published analysis implies.
What is Phase Zero in an SAP migration and why does skipping it cause projects to fail?
The short version: Phase Zero is the pre-migration governance stage — data quality, scope definition, stakeholder alignment, success metrics — that must be completed before technical migration begins. ISG identifies governance failures as the primary driver of the 60% over-budget rate. Brownfield projects are the most likely to skip it.
Phase Zero covers five things: who owns data quality decisions and by what date; a data readiness audit to find and fix dirty, duplicate, and incomplete master data before it enters the migration stream (migration tools can move your data — they can’t fix it); a scope lock that freezes which processes and entities are in scope before technical teams begin; executive sponsorship and decision authority confirmation; and agreed success metrics before any vendor is engaged.
Brownfield has a psychological trap. Converting what you already have feels lower risk — less apparent unknown. That perception causes organisations to underinvest in questioning whether what they have is what they actually want to carry forward. Phase Zero is where those questions get answered. Brownfield projects that skip it find the answers during testing, when fixes are expensive and consulting fees spike. The fastest approach to go-live becomes the most delayed project in progress.
How do you choose between brownfield, greenfield, and bluefield? A scoring framework
The short version: Score your organisation on three dimensions — customisation volume, timeline urgency, and transformation ambition — on a 1–3 scale. Total scores of 3–4 point to greenfield; 5–6 to bluefield; 7–9 to brownfield as the pragmatic choice.
Every source on this topic provides criteria. None of them provide a scoring model. That’s the gap this framework addresses.
Dimension 1: Customisation Volume (from your ABAP audit)
- Score 1 — Low: Few Z-objects; most have S/4HANA standard equivalents; processes are largely standard SAP
- Score 2 — Medium: Moderate custom code; some business-critical Z-objects; remediation required but scoped
- Score 3 — High: Extensive Z-object inventory; core processes depend on custom ABAP; many objects call deprecated functionality
Dimension 2: Timeline Urgency (distance to deadline and internal business drivers)
- Score 1 — Flexible: More than three years of runway, no hard internal deadline
- Score 2 — Moderate: 18–36 months; manageable with proper planning
- Score 3 — Urgent: Under 18 months, or a hard business deadline (merger, regulatory requirement) compounding the 2027 pressure
Dimension 3: Transformation Ambition (how much process redesign you want from the migration)
- Score 1 — Maintain: Stay operationally as-is; platform compliance, not process change
- Score 2 — Improve: Targeted modernisation of specific processes
- Score 3 — Transform: Full process redesign, AI-first architecture, clean core as a strategic goal
Total 3–4 → Greenfield. Low customisation, flexible timeline, and high transformation ambition align with clean-core reimplementation.
Total 5–6 → Bluefield / SDT. Moderate customisation, moderate urgency, mixed transformation ambition. Use shell conversion if your starting point leans brownfield; mix-and-match if you want a greenfield baseline with selective legacy retention.
Total 7–9 → Brownfield. High customisation volume and/or urgent timeline constrains your options. Accept the clean core deficit as a known cost and plan explicitly for post-migration remediation before AI features can be activated.
Three caveats to keep in mind. Change management capacity is a fourth dimension that can override numerical results — a transformation ambition score of 3 with no change management budget doesn’t reflect reality. A score of 7–9 doesn’t mean greenfield is impossible — it means the implications need explicit executive acknowledgment. And Phase Zero must be completed before the score is meaningful; scoring ambition without a data readiness audit produces a number that flatters your aspirations rather than reflects your readiness.
When does the data suggest you should not migrate at all?
The short version: When ECC covers a non-core function a SaaS replacement handles better, when you’re in active M&A, when customisation volume makes every approach unviable, or when your transformation ambition is zero. 39% of SAP ECC customers had not migrated as of Q4 2024 — not all of them are paralysed.
Most analysis on this topic assumes migration is the answer and just frames the decision as “which approach.” That assumption deserves scrutiny.
Gartner data shows 39% of SAP’s 35,000 ECC customers worldwide had not migrated as of Q4 2024, nearly a decade after S/4HANA launched. Not uniformly in denial — some have made deliberate choices. And the 2027 cliff isn’t as vertical as it’s often portrayed: mainstream support ends at the end of 2027, but extended support at a 2% premium is available until end of 2030.
Four scenarios where reconsidering migration makes sense. Your ECC system covers a non-core function a modern SaaS tool now handles cheaper. You’re in active M&A and migrating into a system that may be rationalised increases sunk cost risk. Your ABAP audit reveals Z-object volumes so high that every approach is unviable and composable architecture is the better near-term path. Or your transformation ambition is zero and migration is purely a compliance exercise. That last one is a legitimate reason to migrate — just be upfront about it. Organisations that migrate without a transformation thesis are most likely to appear in the next round of ISG over-budget statistics.
For a detailed analysis of when the composable approach is the right call, our companion article covers the alternatives to SAP S/4HANA migration in full. For a complete overview of all aspects of the SAP ECC decision — from deadline mechanics through financial modelling to strategic alternatives — see our complete SAP ECC end of support guide.
Frequently Asked Questions
What is the difference between brownfield and greenfield SAP migration?
Brownfield (System Conversion) converts the existing ECC system in place, retaining all customisations and historical data. Greenfield (New Implementation) builds S/4HANA from scratch, redesigning processes and replacing custom code with SAP standard functionality. Brownfield is faster to go live but carries technical debt forward; greenfield takes longer but delivers a cleaner, AI-ready system. Per ISG 2026 research: brownfield 34%, greenfield 18%.
What is bluefield SAP migration?
Bluefield — also called Selective Data Transition (SDT) — is a hybrid approach that selectively migrates chosen data, processes, and configurations from ECC to S/4HANA. “Bluefield” is SNP Group’s trademarked term; SAP’s official term is Selective Data Transition. Two main sub-variants: shell conversion (closer to brownfield) and mix-and-match (closer to greenfield).
Which SAP migration approach is most common?
Bluefield / SDT is the plurality choice at approximately 48% per ISG 2026 research. Brownfield: 34%. Greenfield: 18%. Most common does not mean best outcomes — 60% of projects run over budget regardless of approach.
What is SAP clean core and do I need it?
Clean core is SAP’s architectural principle that S/4HANA should remain close to standard, with custom functionality built via SAP BTP rather than direct ABAP modifications. It is required to access SAP’s embedded AI features, including SAP Joule. If AI adoption is a strategic priority, clean core is a prerequisite, not an option.
Does a brownfield SAP migration support clean core?
Brownfield migrations can achieve clean core but don’t deliver it by default. Z-objects carried forward from ECC create a clean core deficit requiring separate remediation — rebuilding customisations as BTP extensions post-migration. SNP Group rates brownfield clean core attainment as Low. This cost is routinely underestimated when brownfield is chosen for speed.
How long does each SAP migration approach take?
LeverX’s estimates for single-country standard deployments: brownfield 6–10 months; bluefield/SDT 9–18 months; greenfield 12–18 months. Organisations starting now have feasible timelines for all three. Those starting after mid-2025 may find greenfield tight without phased go-live strategies.
What is SAP Selective Data Transition (SDT) and how does it differ from bluefield?
They are synonymous in practitioner usage. SAP’s official term is Selective Data Transition; “bluefield” is SNP Group’s trademarked label. Both describe selectively migrating data, configurations, and processes from ECC to S/4HANA.
What are Z-objects and why do they matter in SAP migration planning?
Z-objects are custom ABAP code built on top of standard SAP ECC to support business-specific processes. Their volume and criticality are the primary technical variable in migration approach selection. High Z-object volumes make brownfield the default but also the approach most at risk of clean core deficit. SAP’s Readiness Check and CCMW automate the inventory process.
What is Phase Zero in an SAP migration project?
Phase Zero is the pre-migration governance stage — data quality assessment, scope definition, stakeholder alignment, and success metric agreement — completed before technical work begins. ISG identifies governance failures as the primary driver of the 60% over-budget rate. Phase Zero takes six to twelve weeks and is most often skipped in brownfield projects.
Is bluefield better than brownfield for companies with heavy SAP customisation?
Not necessarily. Bluefield offers more selective control, but heavy customisation volumes still require individual Z-object assessment decisions. If your customisation volume is high and most of it is business-critical, the operational advantage of bluefield over brownfield narrows considerably. Complete the ABAP audit first.
What happens to custom SAP code in a greenfield implementation?
In a greenfield implementation, custom ABAP code is not migrated. Each Z-object requires assessment: some will be replaced by SAP standard functionality, some rebuilt as BTP extensions, and some represent processes needing redesign. This assessment is the primary upfront investment that makes greenfield achievable for organisations with moderate customisation volumes.
