Find out which SAP S/4HANA migration approach fits your existing system, data, and business requirements.
When companies start planning an SAP ECC to SAP S/4HANA migration, they often have a preferred approach in mind. Some want to keep their existing processes, while others see migration as an opportunity to rebuild the system from scratch. But what happens if an assessment shows that the preferred option will be more expensive or technically complicated than expected?
Brownfield allows you to convert your existing SAP ERP system to SAP S/4HANA while keeping much of its configuration, data, and established processes. With Greenfield, you implement a new system and can redesign the processes that no longer meet your business needs. Selective data transition, often referred to as Bluefield, gives you more flexibility in choosing which data and system elements to retain, transform, or transfer. Much depends on the condition of your existing system, custom code, data quality, and the changes you expect from the migration.
SAP's maintenance timeline adds urgency to this decision. Mainstream maintenance for SAP ERP 6.0 without an enhancement package or with EHP1–5 ended on December 31, 2025. For EHP6–8, it continues through December 31, 2027, with optional extended maintenance available until the end of 2030. These deadlines should be factored into the time needed for assessment, custom code remediation, and testing.
What Do Brownfield, Greenfield, and Bluefield Actually Mean?
The main difference between these approaches is how much of your existing SAP environment you keep and what you plan to change during migration.
Brownfield (system conversion). Your existing SAP ERP system is converted to SAP S/4HANA. Most configurations, historical data, and established processes are retained, although some custom code and system components may need adjustment.
Greenfield (new implementation). You implement SAP S/4HANA in a new environment, configure processes according to current business requirements, and decide which data to migrate.
Bluefield (selective data transition). You selectively transfer and transform data and other relevant system elements. This approach can be useful when you want to consolidate systems, change organizational structures, or preserve only certain parts of your existing SAP landscape.
|
Parameter |
Brownfield |
Greenfield |
Bluefield |
|
Main approach |
System conversion |
New implementation |
Selective data transition |
|
Existing processes |
Mostly retained |
Redesigned as needed |
Selectively retained or redesigned |
|
Historical data |
Generally retained |
Migrated according to the scope |
Selected data transferred |
|
Custom code |
Reviewed and adapted as needed |
Rebuilt, replaced, or retired |
Selectively reused or adapted |
|
Organizational changes |
Limited flexibility |
Broad redesign options |
Selective restructuring |
|
Main challenges |
Compatibility and legacy issues |
Process redesign and data migration |
Data selection and transformation complexity |
The target deployment model also determines which approaches are available. SAP Cloud ERP requires a new implementation, while SAP Cloud ERP Private and SAP S/4HANA on-premises support system conversion, new implementation, and selective data transition, subject to technical prerequisites.
Whichever approach you choose, consider how much custom code your future SAP S/4HANA system will need. SAP's clean core principles help companies avoid unnecessary modifications and make future upgrades easier to manage. Greenfield lets you apply these principles from the beginning, while Brownfield and Bluefield projects may require additional work on existing developments.
How Do You Assess Your SAP ECC Landscape Before Choosing?
Start by checking what your SAP ECC system actually contains and how much work it may need. How much custom code does it contain? Which integrations are still necessary? Are there data quality problems that should be resolved before migration? The answers can help you narrow down your options and avoid expensive changes later in the project.
SAP Readiness Check can help you identify potential issues before converting SAP ECC to SAP S/4HANA. It provides information about simplification items, custom code, add-on compatibility, financial data, and system sizing. For a more detailed review of custom ABAP code, you can use ABAP Test Cockpit (ATC).
SAP Readiness Check and ATC can help identify technical issues, but their findings still need interpretation. Review the results with SAP specialists to understand which changes are necessary and estimate the effort involved. If you're also planning to redesign processes or restructure the business, include those requirements in the assessment.
Along with the technical findings, consider the following factors before making a decision:
- System readiness and the technical condition of your current release
- Whether organizational structures need redesign
- Data quality, and how much history is worth keeping
- Compliance posture
- Whether custom code has been maintained or left to drift
- Whether a phased go-live matters to you
- Availability of business process owners and key users for project decisions, data validation, and testing
Even if the assessment leads you to reconsider your preferred migration approach, the findings will still be useful. You'll have a clearer picture of your custom developments, data quality problems, and technical dependencies. They also provide a basis for comparing project proposals and discussing scope with potential implementation partners.
What If the Assessment Contradicts the Path You Already Favored?
Suppose your team prefers Brownfield because you want to preserve existing processes. However, the assessment shows that adapting years of custom developments may require almost as much work as rebuilding the system. In this case, it's worth comparing the two options before making a final decision.
The opposite can happen, too. You might be planning a Greenfield implementation only to discover that your current processes work well and most customizations are still necessary. A complete rebuild could introduce costs and changes your business doesn't need.
Ask your implementation partner to explain which findings influenced the recommendation and how the alternatives compare in terms of cost, effort, and business disruption.
I recommend choosing the migration approach based on business objectives and assessment findings, then establishing a clear scope baseline. Proposed changes should be evaluated for their business value and impact on cost, timeline, and delivery risk. He also emphasizes assessing data readiness early, with preparation activities tailored to the selected approach, and involving business process owners throughout planning, testing, and go-live readiness.
— Dzmitry Shupayeu, Head of Delivery at LeverX
Photo: Dzmitry Shupayeu, Head of Delivery at LeverX
Brownfield: When Does a System Conversion Fit?
Brownfield fits when your existing processes work well, and the system is in reasonable technical shape. It can offer a shorter migration path because much of the configuration, historical data, and process design is retained. Data preparation focuses on meeting conversion prerequisites and resolving consistency issues rather than selecting and transferring data into a newly implemented system. However, the actual effort depends on your SAP environment, especially custom code, integrations, and data quality. Some workflows may also need to change to meet SAP S/4HANA requirements, and users may need to adapt to new interfaces.
A conversion fits when:
- Your process design still matches how the business actually runs.
- Custom code has been maintained and stays close to the standard.
- Historical data needs to stay in the system for reporting or audit reasons.
- You want the shortest technical path off ECC before maintenance ends.
It fits badly when:
- Modifications have piled up to the point where remediation costs approach the cost of a rebuild.
- Your migration requires significant restructuring of company codes, controlling areas, or other organizational elements.
- You need to move individual company codes or business units to SAP S/4HANA at different times, which may require a different transition strategy.
Keep in mind that a system conversion can bring existing problems into SAP S/4HANA. Poor data quality, unnecessary customizations, and outdated processes won't disappear automatically. If these issues have been causing trouble in ECC, it's worth addressing them during migration rather than carrying them into the new environment.
Brownfield in practice: SAP ECC conversion for an optical fiber manufacturer
For a global manufacturer of optical fibers and laser delivery systems, keeping production running was one of the main requirements during migration. The company used SAP ECC to manage manufacturing operations and had only a three-day holiday window when the system could be taken offline.
LeverX used the Brownfield approach to convert the existing SAP ECC system to SAP S/4HANA, preserving established processes and adapting custom code for the new environment. The team completed the technical conversion within the planned three-day cutover window. After the transition, LeverX also integrated SAP Production Planning and Detailed Scheduling (PP/DS) to extend the company's production planning capabilities.
Greenfield: When Is a Clean-Slate Rebuild Worth It?
If your existing business processes no longer meet your needs, Greenfield allows you to redesign them during the SAP S/4HANA implementation. You start with a new system, configure processes around your current requirements, and review which customizations are still necessary. Some existing developments can be replaced with standard SAP functionality, while others may need to be redeveloped for the new environment. You'll also need to review integrations, migrate the required data, and prepare employees for changes in their daily work. These activities can make Greenfield more demanding for the business, particularly when the project involves extensive process redesign.
A new implementation may also make sense when years of modifications have made the existing SAP ECC system difficult to maintain or adapt. It can suit companies that have grown through acquisitions and now operate several incompatible process models. Another reason to consider Greenfield is a major change in how the business operates, especially when the existing ERP configuration no longer supports current requirements.
Historical data can make a Greenfield project more complicated. A new implementation usually focuses on master data, opening balances, and selected open transactions. If your company needs years of transaction history in SAP S/4HANA, that requirement should be included in the migration scope from the beginning. You may also want to consider keeping older records in an archive or making them accessible through a separate reporting environment.
Greenfield in practice: SAP S/4HANA implementation for a construction group
A group of five European construction companies needed better financial control and coordination across its business units. One company already used SAP S/4HANA, but another needed an ERP system implemented from scratch.
LeverX carried out a Greenfield SAP S/4HANA implementation for the second company, covering financial accounting, procurement, sales, project management, and production planning. The project helped automate business processes, improve financial and logistics operations, and support coordination across the group.
Selective Data Transition (Bluefield): When Does the Middle Path Win?
According to SAP's guidance on selective data transition, companies can retain or transform selected data and system elements when moving to SAP S/4HANA. Unlike a standard system conversion, the transition scope can be defined around specific business requirements. However, the technical process depends on the source and target landscapes, as well as the data and system elements being transferred.
Selective data transition can be useful in several situations:
- Your company runs multiple SAP ERP systems and wants to consolidate them.
- You need to reorganize company codes or other organizational structures.
- Your business is going through a merger, acquisition, or divestiture.
- You want to transfer selected historical data without bringing everything from your legacy systems.
Depending on the target landscape, a selective transition can also support a phased migration. However, the technical approach and the rollout strategy need to be planned separately.
Before deciding what to transfer, check how the selected data and business processes depend on one another. Adding more records, company codes, or source systems can increase the work needed for mapping, testing, and reconciliation. Agree on the initial migration scope early, and review the impact of any additions before approving them.
How Do You Compare and Shortlist SAP Partners?
When comparing SAP migration partners, check whether they've worked with the approaches you're considering. Ask for examples of similar projects, including their scope, the challenges the team faced, and the results achieved. This will help you understand whether the partner's experience is relevant to your migration.
What should a partner's assessment actually produce?
Ask for the output rather than the methodology slide. A useful assessment should include an explanation of the SAP Readiness Check findings, a custom code inventory with an estimate of the remediation work involved, and a list of data quality problems that need attention. The partner should explain how these findings affect the migration options, including the work required and any limitations that could influence your decision.
At LeverX, we've worked on SAP S/4HANA migrations involving different system landscapes, business requirements, and transition approaches. As an SAP Gold Partner and SAP Global Strategic Supplier, we help companies assess their existing environments, choose a suitable migration strategy, and carry out the implementation.
For example, during the Eurasia Group Kazakhstan migration, 13 LeverX specialists worked alongside 25 experts from the customer's team. The project took 8.5 months and helped the company reduce system maintenance costs by 10% and improve data consistency by 15%. These figures describe one project, of course. Your migration timeline and required resources will depend on the condition of your SAP environment and the work involved.
If you're choosing between Brownfield, Greenfield, and selective data transition, don't rely on the general advantages of each approach alone. Check what needs to change in your SAP environment, how much work that involves, and what the transition will mean for the people running your business. These findings will give you a better basis for choosing a migration approach and planning the project.
