Greenfield vs brownfield is a decision that moves seven figures and sets how many days your company runs blind at cutover, and most teams inherit the answer from whichever partner pitched last. That should bother you. A 2025 analysis of S/4HANA implementation patterns found that organizations picking their migration path based on their own characteristics, rather than industry trends or a vendor’s preference, achieve roughly 72% higher implementation success rates.
So here is the verdict up front: there is no universal winner. There is a right answer for your specific system, and it falls out of four questions about customization, process maturity, timeline pressure, and budget. What follows are the numbers the first page of Google declines to print, and then the framework.
Greenfield vs Brownfield in Plain English
A greenfield implementation builds SAP S/4HANA (SAP’s current ERP suite) as a brand-new system. Nothing carries over from your existing SAP ECC (ERP Central Component, the legacy suite most of the installed base still runs): no custom code, no configurations, no transaction history. You redesign your processes against SAP’s standard and load the data you choose to keep.
A brownfield implementation is a system conversion. Your existing ECC system becomes an S/4HANA system in place, and your configurations, most of your customizations, and your full transaction history survive the trip.
There is a third path almost every comparison skips: selective data transition, often sold under the trademarked name Bluefield. It migrates selectively, keeping the parts of your system that work and redesigning the parts that don’t. More on it below, including the part its vendors leave out.
One disambiguation, because this SERP is genuinely confused: the same two words describe software projects, foreign direct investment, and warehouse construction. The terms come from land development, where a greenfield is an empty site and a brownfield has a previous life on it. This post is about the SAP decision only.
How the market actually votes: a PwC and LeanIX study found just 14% of companies choose full greenfield, while 44% plan brownfield and 42% plan a hybrid. The clean slate is popular in keynotes. It is rare in signed statements of work. This choice also sits inside a much bigger program, and our S/4HANA migration guide walks the whole arc from readiness assessment through hypercare.
The Numbers Nobody Prints: Cost, Timeline, and Downtime
Every page ranking for this keyword tells you greenfield costs more and brownfield goes faster. Not one of them says how much more or how much faster. The closest thing to a public answer sits in a 2025 white paper in the World Journal of Advanced Engineering Technology and Sciences, which compiled implementation-pattern data attributed to LeanIX across the three approaches.
| Metric | Greenfield | Brownfield | Selective (Hybrid) |
|---|---|---|---|
| Typical timeline | 18-24 months | 15-19 months | 20-28 months |
| Implementation cost ($1-5B revenue company) | $7-9M | $5-6M | $8-10M |
| Business disruption at cutover | 7-10 days | 4-6 days | Wave-dependent |
| Custom code eliminated | ~85% | 10-15% | ~45% (est.) |
| Existing customizations preserved | ~15% | 85-90% | ~55% |
| Long-term maintenance reduction | ~67% | 10-15% (est.) | ~40% (est.) |
| Teams rating the outcome “highly effective” | 65% | 55% | 75% |
Treat these as calibrated ranges, not quotes. Your data volume, org count, and scope move every one of them. But the shape of the trade is stable: brownfield implementations come in roughly 30% cheaper than equivalent greenfields, and the same analysis says about 45% of that saving comes from the smaller design phase and about 35% from lighter change management. The money isn’t saved in the server room. It’s saved in the workshops you don’t run and the retraining you don’t do.
You will also find a claim floating around that a greenfield core can stand up in about three months. The page that publishes that figure disclaims it in the next breath. Believe the disclaimer. For how a real migration calendar spreads across those months, phase by phase, see our breakdown of the SAP project timeline.
Bottom line: brownfield buys speed, continuity, and a smaller invoice. Greenfield buys standardization and a cheaper system to live with for the next decade. The delta is measurable: about 30% on cost, 3 to 5 months on schedule, and 3 or 4 fewer days of disruption at cutover.
What Greenfield Really Buys You (and What It Costs)
The case for the clean slate has real receipts. Greenfield implementations cut custom code volume by roughly 85%, and the simpler system that results needs about 67% less long-term maintenance. Process standardization averages 83% against 46% for conversions, and measured process efficiency gains run 42% against 19%. If your ECC system is two decades of accumulated Z-code that three consultants and one retiree understand, this is the exit.
Now the bill. Greenfield runs 18 to 24 months and sits at the top of the cost table. Change management is the heavy line item: your users lose the transactions they have memorized since 2009 and start over. And the satisfaction data deserves a flat reading: 65% of greenfield teams rate the result highly effective. Better than brownfield’s 55%. Not the transformation euphoria the slideware promises.
The demo of a clean system is flawless. Year one of living in one isn’t.
Not everyone buys the clean-slate gospel, and the dissent has numbers. A Panaya survey cited by Deloitte found that while SAP itself recommends the greenfield route, only about 14% of organizations take it, against 31% committed to brownfield and the rest undecided. The market has read the invoice.
The Cloud Question
One factor is close to binary. If your destination is a public cloud edition of S/4HANA, greenfield is the realistic road: standardized processes, minimal custom code, SAP’s rules. A brownfield conversion drags your customizations with it, which is precisely what public cloud won’t host, so conversions land on-premise or in a private cloud. Decide where you want to live before you pick how you move.
What Brownfield Preserves (and What It Locks In)
Brownfield’s pitch is continuity, and it delivers. The conversion preserves 85-90% of existing customizations (the remaining 10-15% must be remediated for S/4HANA compatibility), keeps your complete transaction history, and finishes in 15 to 19 months at roughly 30% less cost. Pathlock’s Keri Bowman, a practitioner who has sat inside these programs for 15 years, puts the same spread in plainer terms: a conversion is a one-year-to-18-month project, while a greenfield with real process change becomes a three-year program.
The cutover number matters more than most buyers realize. Brownfield conversions average 4 to 6 days of business disruption at go-live against 7 to 10 for greenfield, a reduction of roughly 40%. If you run manufacturing lines, retail volume, or financial transactions, each of those days has a revenue figure attached.
Disruption is controllable on any path, and the levers are boring on purpose: multiple rehearsed mock cutovers, a strict change freeze, tuned extract-and-load runs, and delta mechanisms for the highest-volume data objects. What actually drives the window is transactional volume in scope, the number of dependent data objects, and how much reconciliation your auditors demand before release. But the floor is simply lower when the system already knows your data.
The Debt Comes With You
Here is what the conversion locks in. Every inefficiency, every workaround, every undocumented Z-table gets a faster database underneath it and keeps going. Process improvement caps out near 19%, and the maintenance burden barely drops. There are also technical prerequisites: your ECC release, your add-ons, and your custom code must pass conversion checks before the tooling will take you at all, and a heavily customized system can turn the testing phase into the longest line on the plan.
A conversion is an upgrade with the difficulty setting raised. It is not a transformation, whatever the deck says.
The Third Path: Selective Data Transition, Honestly
Selective data transition (SDT) migrates by choice rather than by default. Two flavors exist. A shell conversion copies your system’s configuration shell without master or transactional data, converts it, and loads only what you select. Mix-and-match builds a new S/4HANA system and transports chosen configuration elements into it. Both fit cases the binary paths handle badly: consolidating multiple ERP systems, carving out company codes, or keeping deep history for some units and none for others. SAP runs its own Selective Data Transition Engagement, so this is a real SAP-supported category, not just a partner trademark.
The hybrid path is sold as the best of both worlds. The data says it is the most expensive and the slowest of the three, and also the one users end up happiest with. All three claims are true. Only the first one makes it into the sales deck.
The numbers: 20 to 28 months, the highest cost band ($8-10M for the reference company size), 35-40% more technical resources than a brownfield, plus specialist tooling and the people who know how to run it. What that buys is precision. Hybrid programs typically aim about 70% of their redesign effort at the 30% of system scope that carries roughly 65% of the business value, and 75% of teams rate the outcome highly effective, the best score of the three.
Pay for targeting, get targeting. Just don’t sign the SDT contract because someone called it a shortcut. It isn’t one.
One more honest caveat: selective programs live or die on scoping discipline. The cut line per data domain (what must exist in S/4HANA on day one versus what can stay in an archive or a read-only legacy system) is a strategic decision, and every wave you add multiplies the testing matrix. Budget governance time for it, or the balanced path becomes the meandering one.
How to Actually Decide: Four Questions That Pick Your Path
Factor lists don’t make decisions. These four questions do, and the 72% success delta for fit-based selection is the argument for answering them honestly before a partner answers them for you.
| Question | If This Is You | Your Path |
|---|---|---|
| How customized is your ECC? | Mostly standard, well maintained | Brownfield |
| Two decades of Z-code nobody fully understands | Greenfield | |
| Heavy, but a defined slice is genuinely worth keeping | Selective | |
| Do your processes work? | The processes are the problem | Greenfield |
| The processes are fine; the platform is aging | Brownfield | |
| How much runway to 2027? | Under 2 years and counting | Brownfield (15-19 months) |
| 3+ years and board patience | Greenfield or selective | |
| What does the budget honestly allow? | $5-6M band, capex scrutiny | Brownfield |
| $7-10M with a transformation mandate | Greenfield or selective |
The 2027 line deserves its dates. SAP ends mainstream maintenance for ECC at the close of 2027, with extended maintenance available to 2030 at a premium. That is not a siren; it is arithmetic. A greenfield started in mid-2026 lands at the deadline with zero slack, and slack is the first thing every ERP program spends.
Three more answers that override the table. If you are consolidating multiple ERP instances into one, selective is built for exactly that. If regulators or auditors require full transaction history in the production system, brownfield is the only path that keeps it natively. And if security workstreams worry you, relax on one point: per Pathlock’s Bowman, roles, provisioning, and controls get rebuilt on every path. Only the speed differs.
- Score your customization: standard, salvageable, or archaeology.
- Ask process owners whether the processes or the platform is the complaint.
- Count backward from your maintenance deadline, minus a contingency you’ll actually use.
- Match the honest budget band, then read the TCO line: brownfield is cheaper now, and greenfield’s 67% maintenance reduction compounds for a decade.
What Your Choice Does to Your Partner Shortlist
Here is the section the rest of this SERP can’t write. The path you pick changes the team you should hire. Greenfield needs 30-40% more functional consultants during design phases (the people who redesign your order-to-cash flow) while using about 15% fewer technical migration resources. Its design and build phases take 23% more effort, and then testing and cutover run about 31% faster because there’s less legacy to fight. Brownfield inverts that: conversion tooling, custom-code remediation, basis depth. Selective demands the deepest technical bench of all, 35-40% more than brownfield, plus the transformation-tool specialists.
Which brings us to the thing an SAP partner can’t say out loud: the recommendation you receive tracks the bench your partner needs to fill. Firms staffed with process consultants find greenfield reasons. Conversion factories find brownfield reasons. Shops that own a migration tool discover, reliably, that your situation calls for exactly that tool. None of them is lying. All of them are selling.
The table above tells you which path fits. It doesn’t tell you which 40-person shop has actually shipped six conversions in your industry. That matching problem is what our engine exists for: describe your system and your constraints, and watch it rank vendors for your specific path. Free, anonymous, no signup.
Frequently Asked Questions
What Is the Difference Between Greenfield and Brownfield?
Greenfield builds a completely new S/4HANA system with redesigned processes and no carried-over code or history. Brownfield converts your existing ECC system in place, keeping configurations, most customizations, and full transaction history. Greenfield maximizes standardization; brownfield minimizes cost, duration, and disruption. Typical spread: 18-24 months versus 15-19, with brownfield about 30% cheaper.
What Is Brownfield in SAP?
In SAP terms, brownfield means system conversion: your existing ECC installation is technically converted into S/4HANA using SAP’s standard tooling. Around 85-90% of customizations survive, the rest need remediation for compatibility. It is the fastest and cheapest route, averaging 15-19 months, with roughly 4-6 days of business disruption at cutover.
What Is Greenfield in S/4HANA?
A greenfield S/4HANA project is a new implementation from a clean slate. Processes are redesigned against SAP best practices, custom code volume drops by about 85%, and you migrate only the data you choose. It typically runs 18-24 months, costs the most upfront, and cuts long-term maintenance requirements by roughly two-thirds.
What Are Greenfield, Brownfield, and Bluefield?
They are the three S/4HANA migration paths. Greenfield is a new build, brownfield is a conversion of the existing system, and bluefield (a vendor trademark for selective data transition) migrates selectively, keeping chosen data and processes while redesigning the rest. Adoption splits roughly 14% greenfield, 44% brownfield, and 42% hybrid.
What Is the Difference Between Bluefield and Brownfield in SAP?
Brownfield converts your entire system as-is: everything comes along, including inefficiencies. Bluefield-style selective data transition migrates by choice, carrying selected history and configuration while standardizing the rest. Selective costs more (a $8-10M band versus $5-6M) and runs longer (20-28 months versus 15-19), but reports the highest user satisfaction of the three approaches.
Sources
- World Journal of Advanced Engineering Technology and Sciences, 2025, 15(01), 1415-1436: the comparative approach analysis behind the cost, timeline, cutover, code, staffing, and satisfaction figures, and the 72% fit statistic.
- Deloitte UK, “Greenfield vs Brownfield”: the Panaya adoption survey (31% brownfield vs 14% greenfield) and SAP’s stated greenfield preference.
- SAP Support: Selective Data Transition Engagement: SAP’s own selective-migration service and approach definitions.
- Pathlock, “SAP Greenfield vs Brownfield Implementation”: practitioner timeline brackets and the security-workstream point, per Keri Bowman.
Both paths get you to S/4HANA. Only one of them gets this particular company there on its own numbers, and now you have the four questions that find it. When you’re ready to see who has actually delivered your path, browse the vendor directory by module, industry, and migration approach.
