Guide

ECC to S/4HANA migration approaches: how to choose

System conversion, new implementation or selective data transition: what each route involves, where each fits and how to decide.

By the Steady Rabbit SAP team · Updated 2026-11-17 · 21 min read

Free PDF · 15 pages

Take the guide with you.

The full guide is below. If you would like the designed PDF to read offline or share with your team, tell us where to send it. Instant download, no call required.

  • The three SAP migration routes in plain English
  • A side-by-side comparison table and a team-effort table
  • Eight decision questions, each with an owner
  • An illustrative weighted-scoring worked example
  • A ten-point checklist and eight FAQs

We use your details to send you the guide. See our Privacy Policy.

Thanks. Your guide is ready.

Download the PDF

15 pages. Want to talk through one of your own objects? Bring us a question.

Every ECC-to-S/4HANA programme starts with the same question: do we convert the system we have, start again from a clean build, or move only part of it? The answer shapes the budget, the timeline, the amount of testing, how much your people have to change, and how much risk sits on go-live weekend. It is also the decision that is hardest to undo once the project is under way.

This guide explains the three routes SAP describes, in plain English, and gives you a way to choose between them. It is written for CIOs, finance and operations leaders, SAP programme managers and the partners who advise them. You do not need to be an SAP specialist to follow it, and SAP professionals will recognise the tools and terms.

~50%of customers moved by system conversion, in SAP's own estimate.SAP Community, updated Dec 2022
~45%chose a new implementation, starting from a fresh S/4HANA build.SAP Community, updated Dec 2022
~5%used selective data transition, typically large, complex estates.SAP Community, updated Dec 2022
Lead figure: the choice at a glance
Start here: how much of your current system and way of working do you want to carry forward?
Most of it
System conversionOften called brownfield. Your ECC system is converted in place: database, software and data model move to S/4HANA.
Very little
New implementationOften called greenfield. A new S/4HANA system is built and only the data you choose is loaded into it.
Some of it, or only part of the business
Selective data transitionA shell copy or a mix-and-match build, then selected data. Suits phased go-lives, mergers and carve-outs.
Many real programmes mix routes by system or business unit. SAP notes that hybrid approaches are common.

The three routes in plain English

SAP describes three ways to reach S/4HANA from SAP ERP 6.0 (ECC). The labels used in the market, brownfield and greenfield, are shorthand. They are not SAP product names, but they are close enough to SAP's own descriptions that we use them here alongside the official terms.

System conversion

SAP's term is "system conversion". Your existing ECC system is converted in place. The database moves to SAP HANA if it is not there already, the software is updated, and the data is converted automatically to the S/4HANA data model. Your configuration, custom code, history and users carry across. Finance needs an additional step after its configuration is done to convert accounting data to the new model.

The simplest way to picture it: the house stays where it is, but the wiring, plumbing and foundations are replaced while you still own the contents.

New implementation

You install a new S/4HANA system and build it again, usually starting from SAP's best-practice content. Then you migrate the master data, balances and open items you want, using tools such as the SAP S/4HANA Migration Cockpit. Nothing comes across by default. Every process, interface and report is a decision.

The picture here is moving into a new building. You take what you choose, leave what you do not, and design the layout fresh.

Selective data transition

This route sits between the two. Data Management and Landscape Transformation (DMLT) services from SAP, which used to be called System Landscape Optimization, move selected configuration and data from one or more ECC systems into S/4HANA. There are two common ways to build the target. In a shell conversion, a copy of your production system is made without master or transaction data and then converted. In a mix-and-match approach, a clean S/4HANA install receives selected configuration and code, either transported or transferred manually. In both cases data migration follows.

Think of renovating one wing of a large estate while keeping the rest running, or merging several buildings into one.

Tip

Use SAP's terms in contracts and plans. "Brownfield" and "greenfield" mean slightly different things to different vendors, and "bluefield" is a market label rather than an SAP term. If a proposal uses the labels, ask the vendor to describe exactly what is converted, what is rebuilt and what data is migrated.

Why the choice matters now

SAP's published maintenance strategy states that mainstream maintenance for SAP Business Suite 7 core applications, which includes SAP ERP 6.0, runs until the end of 2027. SAP also offers optional extended maintenance from the beginning of 2028 through 2030. SAP states that extended maintenance carries a premium of two percentage points on the maintenance basis. For customers who do not opt in, SAP describes customer-specific maintenance after mainstream or extended maintenance ends.

A further option, the SAP ERP private edition transition option, has been described in SAP's announcements and in SAPinsider reporting. It is a subscription that can be bought starting in 2028 and used from 2031 to 2033. SAP says it is not a maintenance extension for SAP ERP. Eligibility conditions apply, including a move to SAP ERP private edition on SAP HANA before the end of 2030, a minimum system size and a separately charged success plan. Check the current terms with SAP before relying on it.

On the S/4HANA side, SAP announced in February 2020 an innovation commitment for S/4HANA on-premise through the end of 2040, and states that there will always be at least one release of S/4HANA in maintenance until then.

What this means for the migration route: the calendar is a constraint, not a reason to rush the decision. A conversion can be shorter than a new implementation because it carries more across. A new implementation gives you more redesign but usually needs more time for process design, data migration and training. If your internal deadline is tight, that alone may point you towards one route. If it is not, the other criteria in this guide carry more weight.

Watch out

Dates and fees for SAP maintenance have changed before. Treat the figures in this guide as a starting point and confirm them with SAP or your SAP account team before building a business case around them.

System conversion: what it involves

How it works

A system conversion is a technical project wrapped in a business one. The technical core is run with SAP's Software Update Manager (SUM), which updates the software and, where the database changes, uses the Database Migration Option (DMO) to migrate to SAP HANA in the same procedure. SAP's downtime-optimized conversion approach can reduce production downtime by moving parts of the data conversion into uptime, with extra planning and test effort.

Before SUM runs, you prepare the system. That means checking the source system meets the prerequisites, working through SAP's simplification items, cleaning up and adapting custom code, converting customer and vendor master data to business partners, and checking that your add-ons and third-party products have a supported path to the target release.

Prerequisites SAP lists

  • The source system is SAP ECC 6.0 at a supported enhancement package level.

  • The system is Unicode.

  • The system is ABAP single stack. A dual-stack system, with both ABAP and Java in one system, has to be split first.

  • Customer and vendor master data is ready for the business partner approach, with Customer Vendor Integration (CVI) in place. SAP states that systems without CVI are declined in the pre-checks.

What it is good at

  • Continuity. Users, roles, history and most business processes carry over, so training and change management are lighter.

  • Speed to a supported platform. There is less to design and less to migrate than in a new build.

  • Reuse of what works. Custom code and interfaces that are still needed can be adapted rather than recreated.

  • A single go-live for a single instance, which is simple to plan.

Where it struggles

  • It carries your history. Years of unused custom code, duplicated master data and legacy workarounds come with you unless you clean them first.

  • It limits redesign. You can improve processes after go-live, but the conversion itself is not a redesign project.

  • A single large cutover can mean a big-bang weekend, which needs careful rehearsal.

  • Finance and some master-data areas change structurally, which still needs testing and sign-off from business owners.

SAP's own pocket description is that most simplification items are technical and need little fit-to-standard work, but custom code still needs review. In other words, a conversion is not an upgrade in the old sense. It is a technical migration plus a defined set of functional changes.

New implementation: what it involves

How it works

You start from a fresh S/4HANA system, usually from SAP Best Practices content, which SAP says covers many countries and a large library of processes. You decide which processes to adopt as delivered, which to adapt and which to retire. Then you extract master data, open items and balances from ECC, cleanse them, and load them into the new system with tools such as the Migration Cockpit. You can optionally reuse some extensions and interfaces from ECC, but each one is a decision.

What it is good at

  • Process redesign. If your processes grew by accident over twenty years, a clean build lets you adopt standard processes and drop workarounds.

  • A lean starting point. You carry only the data and code you choose, which can keep the new system small.

  • Fit with a cloud-first or clean-core strategy. If your aim is to keep the core close to standard and extend through supported channels, a fresh build is the natural moment to enforce that.

  • A natural moment for structural change, such as new legal entities, a new chart of accounts or a new organisational model.

Where it struggles

  • It is the most change-intensive route. Process owners have to make many decisions, and users have to relearn their work.

  • Historical data is not there by default. You need a plan for what is migrated, what is archived and how auditors and users will reach old records.

  • Custom requirements have to be rebuilt or dropped. Every dropped requirement needs a business owner who agrees.

  • The timeline depends heavily on how quickly the business can make design decisions, not only on how fast the technical team works.

Watch out

"Greenfield" projects often drift into a re-creation of the old system because every business unit asks for its existing behaviour. Agree a fit-to-standard principle at the start, with a named executive who can say no, or the project will rebuild the complexity it was meant to remove.

Selective data transition: what it involves

How it works

Selective data transition is delivered mainly through SAP's DMLT services. It transfers selected parts of the ABAP repository, configuration, master data and transaction data into S/4HANA. The SAP PRESS description of the approach, adapted from the book SAP Activate, names two target-creation methods: shell conversion and mix and match. Both need a separate data migration step covering master data, balances and open items.

What it is good at

  • Phased go-lives, for example by country, company code or business unit, which reduces big-bang risk.

  • Landscape consolidation: merging several ECC systems into one S/4HANA system, or splitting one apart.

  • Carve-outs and acquisitions, where only part of an estate moves.

  • Leaving old data behind. The conversion is simpler when it does not have to carry all historical business data.

Where it struggles

  • It needs specialist skills and tooling, and SAP describes complex scenarios as generally needing SAP services and support. Third-party tools may fall outside SAP's support arrangements.

  • Where several source systems are involved, their repositories and configuration need harmonising, which is manual work.

  • Projects can run for several months and need several test cycles in a dedicated sandbox.

  • Only a small share of customers use it. In SAP's estimate it is around 5 per cent, so there are fewer reference projects to learn from.

Hybrid is normal

SAP states that hybrid approaches are common. A group might convert its main ERP system, use selective data transition to bring a recently acquired company onto the same platform, and run a new implementation for a business that was always on a different system. Each system gets the route that fits it. The cost is more coordination, so a single programme office and shared design principles matter.

Comparing the routes side by side

The table below puts the three routes against the questions that matter most to a business buyer. It is a qualitative comparison, based on how SAP and its community describe each route. It is not a measurement, and your own result will depend on your landscape, your data and your people.

Comparison of the three SAP migration routes
QuestionSystem conversionNew implementationSelective data transition
What happens to your current system?Converted in place, with its configuration, code and data.Left behind. A new system is built and selected data is loaded.Partly carried across, via a shell copy or a clean build with selected content.
Process change for usersLower. Processes change where S/4HANA simplifications require it.Highest. Processes are redesigned or re-adopted from standard.Varies by design. Can be low for retained parts, high for rebuilt parts.
Custom codeAdapted and carried over. Cleanup before conversion reduces effort.Rebuilt or retired by choice. Some can be reused.Selected objects are transferred. The rest is left behind.
Historical dataCarried across, with a larger database to convert.Only what you migrate. Archive strategy needed for the rest.Selected periods and entities. Large historical volumes can stay behind.
Typical fitOne main ERP instance, stable processes, need to keep history.Process redesign, clean-core goals, structural change.Mergers, carve-outs, multi-system consolidation, phased go-lives.
Go-live shapeUsually one cutover per system, with downtime to plan and rehearse.One or more cutovers, with data migration rehearsals.Can be phased by country or business unit.
Main riskCarrying old problems forward; downtime window.Scope creep and slow design decisions; data migration quality.Complexity and specialist dependency.
Share of customers (SAP's estimate)About 50%About 45%About 5%

What each route asks of your teams

The effort does not fall evenly. Each route moves work between IT and the business, and the balance matters when you plan who is released from their day job.

Where the effort lands, by team and route
TeamSystem conversionNew implementationSelective data transition
FinanceValidate the new data model, reconcile balances, test closing processes.Redesign the chart of accounts and controlling if wanted; approve migrated balances and open items.Agree which entities and periods move; reconcile at the cut-off.
Operations and supply chainRegression-test existing processes and enhancements.Rework process design, then train and test the redesigned processes.Test the retained and rebuilt areas separately.
IT and ABAPClean up and adapt custom code, interfaces and authorisations.Decide what to rebuild; build extensions and interfaces; run data migration.Harmonise repositories; prepare transport and transfer of selected objects.
BasisPlan and rehearse the SUM and DMO runs, landscape and cutover.Install and size the new system; plan data migration runs and cutover.Build the shell or clean target; coordinate several systems.
Change and trainingTargeted training on what changed.Broad training and a large change programme.Training by wave, aligned to the phased rollout.

The practical lesson is that a conversion looks cheaper on the business side and heavier on the technical side, while a new implementation reverses that. If your business teams are already stretched, a route that needs hundreds of design decisions from them can fail for lack of attention, however good the technical plan is. If your technical team is small, a route with large amounts of code to adapt may be the bottleneck. Match the route to the capacity you really have, not the capacity on the organisation chart.

How to choose: eight questions and who answers them

The route is not a technical choice. Finance, operations, IT, compliance and the executive sponsor all have a stake, and each question below has a natural owner. Work through them together in a single workshop, record the answers, and let the pattern of answers point to a route.

Decision table: questions, what each answer suggests, and the owner
#QuestionIf the answer is...Leans towardsOwner
1Do our core processes still fit the business?Yes, mostlySystem conversionProcess owners, COO
No, they grew by accident or the business has changedNew implementation
2Do we need years of transaction history in the live system?Yes, for operations or auditSystem conversionFinance, compliance
No, an archive is enoughNew implementation or selective
3How much of our custom code is still used?A lot, and it is valuableSystem conversionIT, ABAP lead
Little, or it can be replaced by standardNew implementation
4Is the landscape changing: mergers, carve-outs, several ERP systems?YesSelective or hybridCIO, corporate development
5How much change can our people absorb in 12 to 24 months?LimitedSystem conversionHR, change lead
A lot, with executive supportNew implementation
6How firm is our deadline?Fixed and closeSystem conversionCIO, CFO
Flexible, with a business case for redesignAny route
7Do we want phased go-lives by country or unit?YesSelective data transitionProgramme sponsor
8What is the state of our data and add-ons?Clean data, supported add-onsSystem conversion is practicalData owners, IT
Duplicate or poor data, unsupported add-onsNew implementation, or clean first

Two things are worth saying about this table. First, you will rarely get eight answers that all point the same way. The aim is to see where the weight sits and to name the trade-off you are accepting. Second, question 8 is the one most often skipped. Data quality and add-on compatibility can quietly rule out a route, and you want to find that out before a vendor has quoted for it.

Tip

Before the workshop, run SAP Readiness Check and a usage analysis of your custom code. Facts about simplification items, add-ons and unused code make the discussion far less speculative. Our companion guides on the readiness check and on custom code cleanup explain how.

A worked example (illustrative)

The company below is invented to show the method. It is not a client and the figures are not market data. The weights and scores are a team's judgement, not measurements.

Illustrative example

The situation. A mid-sized distributor runs one ECC 6.0 system for three legal entities. Processes are fairly stable, but a large share of its custom reports and enhancements dates from an earlier ownership. Leadership wants to be on a supported platform before the end of 2027 and has no plan to change its operating model. A recent small acquisition runs on a separate legacy ERP.

The scoring. The programme board scores each route from 1 (poor fit) to 5 (strong fit) against five criteria, weighted by how much each matters to this company.

Illustrative weighted scoring (invented numbers)
CriterionWeightSystem conversionNew implementationSelective
Meets the deadline with manageable risk30%533
Keeps history and valuable custom code25%523
Limits change for users20%423
Opportunity to redesign processes10%253
Handles the acquired company15%244
Weighted score (out of 5)100%4.02.93.2

The result. System conversion wins for the main system. The acquired company is a poor fit for the conversion, so the board decides to treat it as a separate, later workstream: a new implementation or a selective transition into the converted system, decided once the main project has stabilised. Before the conversion starts, the board commits to a custom code usage analysis, because the large legacy code estate is the biggest cost driver. The outcome is a hybrid plan: convert first, handle the acquisition second.

What the example shows. The scoring is less important than the discussion it forces. The board had to say out loud that the deadline outweighs redesign, and that the acquisition is a different problem from the core system.

Risks and mistakes to avoid

Choosing the route by habit or by what the vendor sells

Every implementation partner has a preferred approach, and it is usually the one they deliver best. A good partner will explain the trade-offs and tell you when another route fits better. Ask for a written rationale that refers to your own facts: custom code volume, data quality, deadline, landscape.

Treating conversion as an upgrade

System conversion does not mean "nothing changes". Finance data moves to a new model, customers and vendors become business partners, and a list of simplification items can change how specific transactions behave. Business testing is still the largest part of the effort.

Underestimating custom code

Custom code is where schedule and budget surprises usually come from, whichever route you pick. In a conversion you adapt it. In a new implementation you rebuild or replace it. In both cases an object you retire first costs nothing to move. See the guide on cleaning up custom code before S/4HANA.

Ignoring data quality

Duplicate customers, inconsistent vendor records and old open items hurt every route. The business partner conversion in particular needs clean customer and vendor data, and SAP provides notes and a synchronisation cockpit for that work. Start early. Data cleansing is slow because it needs business owners, not just developers.

Leaving add-ons and third-party products to the end

SAP's Maintenance Planner checks whether your add-ons are compatible with the target release, and marks third-party add-ons with unknown status for you to confirm with the vendor. An add-on that is not supported can block a conversion if no uninstaller or successor exists. Confirm these early.

Budgeting on the route name alone

A route label does not set a price. The main cost drivers are the same for all three: the volume of custom code you carry, the number of interfaces and integrations, the quality of master data, the number of test cycles the business can support, the number of go-lives, and how many sources of data you consolidate. Two companies that both call their project "brownfield" can differ several times over in effort. When you compare quotes, ask each vendor to state its assumptions on each driver so you compare like with like.

Skipping the rehearsals

Whatever the route, the go-live depends on cutover rehearsals. The technical team should run the conversion or migration several times on copies of production, measure the timings and fix the problems before the real run.

Watch out

Do not let a fixed price quoted before an assessment decide the route. Price follows scope, and scope depends on what you find in your system. Run the assessment first, then quote.

Checklist: before you commit to a route

  • We have written down our deadline and the reason for it, and confirmed current SAP maintenance terms.
  • We have run SAP Readiness Check on our ECC system and reviewed the simplification items with the business.
  • We know how much custom code is used in production, based on at least a year of usage data where possible.
  • We have checked every add-on and third-party product against the target release.
  • We have assessed customer and vendor data quality and our readiness for business partners.
  • We have named an owner for each of the eight decision questions and recorded the answers.
  • We have agreed what historical data must stay in the live system and what can be archived.
  • We have decided whether any entity, country or acquired company needs a different route.
  • We have agreed how many rehearsal runs and test cycles the plan allows.
  • We have a written route recommendation with its trade-offs, signed by the business sponsor and IT.

How Steady Rabbit can help

Steady Rabbit is an India-based SAP delivery company, working since 2016, with about 60 engineers across the company and team leads who bring 7 to 16 or more years of SAP delivery. Our engineers are certified in ABAP Cloud and SAP BTP. We help with the parts of this decision that depend on engineering evidence: assessing your custom code, planning the technical conversion, and running the work once the route is chosen. We work directly with enterprises and as a subcontract partner inside SAP partners' programmes.

Talk to an SAP lead   S/4HANA Migration   ABAP Code Modernization   Basis and Support   Services   For SAP partners

FAQs

What is the difference between greenfield and brownfield?

Greenfield usually means a new implementation: a fresh S/4HANA system built from scratch, with selected data loaded in. Brownfield usually means a system conversion: your existing ECC system is converted in place and keeps its configuration, code and data. SAP's own terms are new implementation and system conversion.

Which route is fastest?

A system conversion is usually the shortest route to a supported platform because it carries more across, but the timeline depends on custom code volume, data quality and testing. A new implementation depends heavily on how quickly the business can make design decisions.

Can we use different routes for different systems?

Yes. SAP states that hybrid approaches are common. A group can convert one system, use selective data transition for another and run a new implementation for a third. Plan one programme office and shared design principles so the pieces fit.

What happens to our historical data in a new implementation?

Only what you migrate goes into the new system. Most programmes load master data, balances and open items, and keep older history in an archive or a reporting system. Agree with finance and compliance what must remain reachable and for how long.

What is selective data transition?

It is an approach delivered through SAP's DMLT services that moves selected configuration and data into S/4HANA, either by converting a shell copy of your system or by building a clean system and transferring selected content. It suits phased go-lives, mergers and carve-outs.

Does the route change how much custom code work we have?

Yes. In a conversion you adapt the code you keep. In a new implementation you rebuild or replace what you still need. In every route, retiring unused code before you start reduces the work, so a usage analysis helps whichever route you pick.

When should we decide?

As soon as you have evidence from a readiness check, a custom code analysis and a data assessment. Deciding before that risks a route chosen on opinion. Deciding too late compresses the programme into the final year before maintenance changes.

Can Steady Rabbit help us choose?

Yes. We can run the readiness check and custom code analysis and give you a written recommendation based on your own system. Use the contact form on this page to start.

Sources

SAP products, terms and dates change. We checked these sources in November 2026. Confirm current details with SAP before you make commercial decisions.

Want this as a PDF?

Get the designed PDF

Related reading

Related reading.

Where to go next.

Next step

Tell us about the conversion you are planning.

A 20-minute call. We listen first, then tell you whether and how the team can help. No system access needed.

Request a briefing

We reply within one working day.