Why This Conversation Has Become Urgent

What was once a discussion about transformation ambition has become, for a large portion of the SAP customer base, a time-pressured decision with real commercial stakes.

Mainstream support for SAP ECC ends on 31 December 2027. Optional extended maintenance runs to 2030 at roughly nine percent above standard maintenance fees. As of end-2024, only around 39% of SAP ECC customers had licensed S/4HANA, which means the majority of the installed base is still working out what to do and when.

Full migrations for complex enterprise environments take between 18 and 36 months. Organizations that have not started already need to accelerate their programs.

For SAP consultants, this backlog is an opportunity and a professional risk: demand for migration expertise is rising sharply, and so is the cost of giving clients advice that does not hold up under delivery pressure.

The question of Brownfield, or Greenfield or Bluefield: which approach to recommend, and why, has rarely carried more weight.

The Framework Every Approach Operates Within

There is a prior question worth settling before examining the three approaches: what is the delivery framework they all operate within?

SAP Activate is the methodology SAP requires for all S/4HANA implementations. It runs across six phases: Discover, Prepare, Explore, Realise, Deploy, Run. The methodology is not approach-neutral.

The Explore phase is where it makes its most substantive demand. Fit-to-Standard workshops, run against SAP Best Practices content from the Business Process Navigator, establish which of the client’s processes can be handled by standard SAP functionality and which genuinely require deviation.

The SAP Best Practices library has grown considerably through the S/4HANA Cloud era. Many processes that organisations spent years customising in ECC are now covered by pre-configured standard content, which makes Fit-to-Standard both a methodology principle and a practical cost argument.

SAP’s clean core strategy is the architectural expression of the same thinking: keep the S/4HANA core close to standard, build extensions through SAP Business Technology Platform rather than through direct ABAP modifications, and upgrades stay manageable without re-validating custom code each release cycle.

Fit-to-Standard has its limits in heavily regulated industries and complex manufacturing environments, where some process differentiation is legally required or competitively necessary. The right treatment for it is as a default and a starting point, with documented justification required for each deviation, not as a rule that applies without exception in every context.

Three Approaches, Precisely Defined

Loose use of these terms has consequences for how programs get sold, scoped, and staffed. Precision is a practical professional asset here.

SAP’s official term for what the industry calls Brownfield is System Conversion.

The existing ECC system is converted in place to S/4HANA, carrying forward configurations, historical data, custom ABAP code, and existing processes. SAP Activate’s System Conversion workstream governs delivery, and it is a different engagement from a new implementation. 

Brownfield sits in structural tension with Fit-to-Standard, because its core value proposition is preserving what exists, which pulls against the instruction to adopt what is standard.

The tension is manageable with explicit governance. Brownfield is a legitimate choice for organizations with stable, mature processes where continuity value genuinely exceeds transformation value. The problem is that commercial pressures in most Brownfield engagements work against the Fit-to-Standard discipline that would make the approach sound over the long term.

SAP’s official term for Greenfield is New Implementation.

The S/4HANA system is built from scratch. SAP Best Practices form the starting point. Only master data and open transactions migrate, and historical data stays behind.

SAP Activate’s New Implementation workstream applies in full, with Fit-to-Standard workshops governing process design from a blank canvas. This is the approach SAP’s own methodology is built for, and the one that produces the highest clean core attainment by default.

Bluefield needs a specific clarification that matters professionally: it is a registered trademark of SNP Group, the Heidelberg-based transformation software company. SAP’s neutral term for the same category of work is Selective Data Transition, or SDT.

Both labels are in common use and refer to the same general approach: selectively migrating chosen data, processes, and configurations from ECC to S/4HANA while redesigning others.

Within that category, two sub-variants have meaningfully different delivery profiles.

Shell conversion starts with an ECC system conversion and applies selective data decisions during migration, sitting closer to Brownfield in character.

Mix-and-match starts with a new S/4HANA system and selectively integrates ECC elements, sitting closer to Greenfield. Treating these as interchangeable produces inaccurate scope and timeline estimates at the proposal stage.

The valantic SAP Study 2025 reports that extended Brownfield/Bluefield hybrid strategies now account for 57% of active migrations, with pure Brownfield down from 41% to around 10%. That reflects the market absorbing, slowly, what these approaches actually demand in terms of governance.

Technical Constraints Come Before Approach Preferences

Approach selection is constrained by technical facts that must be assessed before any recommendation is made.

The most important is the volume and business criticality of Z-objects: the custom ABAP code built on top of standard ECC to handle processes that SAP standard did not cover.

Brownfield carries Z-objects forward. Greenfield replaces them. Bluefield/SDT selectively migrates them.

Without knowing what a client has, in what volume, and how much of it is still actively used versus accumulated dead code, no approach recommendation has a solid foundation.

SAP provides two tools that must be run before that conversation starts. The SAP Readiness Check analyses the ECC system and flags compatibility issues and custom code requiring remediation. The Custom Code Migration Workbench automates the Z-object inventory and identifies what is compatible with S/4HANA, what needs recoding, and what calls retired tables.

Running these after an approach has already been agreed reverses the correct sequence and creates the kind of mid-project surprises that lead to overruns. This happens more often than it should. 

Compatibility Pack dependencies add a further layer of urgency: most CP usage rights for on-premise customers expired at end-2025, while customers under RISE with SAP Private Edition retain those rights until 2030, a distinction that affects what is technically viable for clients who have not yet moved.

The Trade-Offs the Market Consistently Underweights

Cost and timeline dominate most approach selection conversations. Both matter. What gets underweighted (and what produces the most damaging long-term surprises) is clean core attainment and its downstream effects on upgrade burden and AI access.

SNP Group’s technical framework rates clean core attainment by approach: Brownfield delivers low attainment by default, shell conversion moderate, mix-and-match high, and Greenfield very high. The mechanism is direct. Z-objects and non-standard configurations carried forward from ECC create a clean core deficit that does not disappear at go-live. Resolving it post-migration means rebuilding those customizations as BTP extensions: a separate program of work that is routinely underestimated when Brownfield is chosen primarily for speed.

The AI access dimension has become the sharpest expression of this cost. SAP Joule’s advanced capabilities (autonomous multi-step agent workflows, BDC-integrated analytics, domain-specific agents across finance, procurement, and supply chain) require S/4HANA Cloud with clean core compliance. This is an architectural dependency documented by SAP.

For any client whose strategic roadmap includes meaningful AI adoption within the next three to five years, clean core attainment belongs in the approach conversation from the start, not as an afterthought once the program is under way. 

Approach selection is necessary, but it is not sufficient. The consultants who understand that distinction, and build governance models accordingly, are the ones clients want in program leadership roles.

Matching the Approach to the Client

The decision sequence that produces the most sound recommendations runs in a specific order. 

First, establish what SAP’s platform direction means for this client’s realistic five-to-ten year horizon: specifically, whether AI capability access and continuous cloud upgrades are genuine strategic priorities or theoretical ones.

Second, run the Readiness Check and CCMW (Customer Code Migration Workbench) to establish the Z-object landscape before any other variable is considered.

Third, evaluate Fit-to-Standard feasibility across the client’s main process areas, because the answer determines how much of what they currently have should actually be preserved.

Fourth, assess organizational change capacity honestly. Greenfield requires C-suite alignment and organization-wide process re-engagement, and programs that underestimate that requirement produce the most painful Explore phases. Only then should the conversation turn to which approaches are technically viable within the available timeline.

Three broad client archetypes emerge from that sequence.

Clients with stable, mature processes, limited near-term AI ambition, and a tight delivery window are typically best served by Brownfield, provided Fit-to-Standard discipline is genuinely enforced during conversion rather than deferred.

Clients with significant legacy inefficiency, a specific transformation mandate, or AI-first strategic objectives are best served by Greenfield, accepting the timeline and change management investment that requires.

Clients navigating M&A activity, carve-outs, multi-instance consolidation, or a selective transformation need are typically the natural fit for Bluefield/SDT, but only with the necessary governance that approach specifically demands.

The deciding question in every case is not which color to choose. It is what Fit-to-Standard analysis reveals about this client’s process landscape, and how much of what they currently run should actually follow them into the new system.

Bluefield Demands the Most Governance Discipline

Bluefield/SDT is frequently sold as the approach that sidesteps the hard decisions of Greenfield and the limitations of Brownfield. In practice it demands the most thorough application of SAP Activate and Fit-to-Standard, because selectivity without methodology discipline produces the exact outcome it is supposed to prevent.

The specific type of failure most liable to occur is that retained process areas never get evaluated against SAP Best Practices, because the commercial logic of the engagement has already framed them as preserved. Fit-to-Standard workshops cover the redesigned areas and skip the retained ones. The result is a system carrying forward legacy complexity under the appearance of a strategic hybrid.

SAP established the Selective Data Transition Engagement group in 2020, comprising SAP, SNP, Natuvion, and cbs, specifically to build best practice governance around this approach and provide a framework for compliant delivery.

Data selection decisions in an SDT project require formal business sign-off, not just IT approval. 

The choices made about which historical data migrates carry audit, compliance, and operational consequences that extend well beyond the go-live date.

The sub-variant is also practically significant here.

Shell conversion and mix-and-match are different program structures with different clean core outcomes, different timelines, and different governance requirements. A consultant advising on Bluefield/SDT who cannot articulate that distinction clearly is not ready to advise on it.

What Cloud and AI Have Changed About the Calculation

Public Cloud under GROW with SAP supports only Greenfield. This is architecturally enforced, which means Fit-to-Standard is structurally mandatory for any client taking that route.

RISE with SAP Private Edition supports all three approaches, but SAP applied direct pressure on implementation partners at Sapphire 2025 to move away from Brownfield as the default and toward clean core-compliant delivery.

Joule Studio Agent Builder reached general availability in Q1 2026, adding custom agent creation, multi-agent orchestration, and integration with SAP and non-SAP data sources, all of which require clean core compliance.

The pace at which SAP is expanding AI capability within the suite means the gap between clean core and non-clean-core deployments will widen across coming upgrade cycles. Consultants whose advisory framework was formed in the on-premise S/4HANA era, before RISE, before Joule, and before SAP Business Data Cloud, are working from an incomplete picture.

What This Means for Your Career

The consultants building the most durable senior careers in this space share one observable characteristic: they engage before the approach decision is made.

The ability to run a credible pre-engagement assessment, facilitate a Fit-to-Standard analysis across a client’s process landscape, and frame clean core and AI access implications for a business audience is where the advisory value currently resides, and where the market is paying for it. 

Bluefield/SDT specialist skills are undersupplied relative to the volume of projects now taking that route. Greenfield demand is growing but requires process design capability rather than configuration depth, a different skill profile that many experienced ECC consultants have not yet developed. From years of watching how SAP programs get staffed, we see that the consultants who get called back into the most senior roles are those who treat these three approaches as strategic decisions with methodology, governance, and long-term architecture consequences. And frankly, the ability to say that clearly to a client who has already been told something different by someone with a stake in a particular answer: that is where the real professional edge is right now.

If you are an SAP professional looking for a new role in the SAP ecosystem our team of dedicated recruitment consultants can match you with your ideal employer and negotiate a competitive compensation package for your extremely valuable skills, so join our exclusive community at IgniteSAP.