Evaluate greenfield, brownfield, and selective data transition strategies to determine their technical impact on legacy ABAP custom code and master data.
Every company moving from SAP ECC to SAP S/4HANA must choose how to make the move. The path your leadership picks directly decides how much custom code you will keep, how much you will delete, and how much work lands on your desk.
Previous lesson: SAP ECC End of Maintenance: What It Means for ABAP Developers | Next lesson: The Simplification List: What Changed in S/4HANA
Organizations choose between three technical transition paths when moving to SAP S/4HANA.
The first path is a new implementation, often called greenfield. In this approach, the company installs a clean SAP S/4HANA system from scratch. Business processes are configured anew, and historic transactional data stays behind in the old system.
The second path is a system conversion, often called brownfield. In this approach, you convert the existing SAP ECC system in place. All custom code, configuration, master data, and transaction history move directly into the new SAP S/4HANA release.
The third path is a selective data transition, sometimes called bluefield. This approach combines elements of both. A fresh system is built, but selected business units, company codes, and historical data migrate over using specialized migration tooling.
According to ISG research published in February 2026 covering 200 senior decision makers, 34 percent of organizations chose a brownfield system conversion, 18 percent selected greenfield, and nearly half chose a mix of approaches. At Harbor Supply Co., leadership chose a brownfield conversion to keep historical sales orders and preserve active warehouse processes.
A brownfield conversion uses the SAP Software Update Manager (SUM). SUM upgrades the database to SAP HANA, replaces the application software components, and converts database tables to the new data model.
Because SUM converts your existing system in place, every single custom repository object carries over into the target environment. If your company has 4,000 custom objects like Harbor Supply Co., all 4,000 objects arrive in the upgraded system on day one.
During the conversion, SUM asks you to adjust SAP objects your company modified: dictionary objects in transaction SPDD and other repository objects in transaction SPAU. SUM does not fix your own Z and Y programs. They arrive unchanged, and you adapt them after the conversion using the findings from ATC.
Until you adapt them, custom programs that reference removed function modules fail to compile, and programs that read replaced tables can return wrong or empty results when users run them.
Common Mistake: Assuming that a brownfield conversion automatically modernizes your ABAP code. SUM updates standard SAP tables and programs, but it leaves custom programs untouched until you manually remediate them.
If your project selects a greenfield implementation, your custom code baseline resets to zero. You do not bring your entire custom codebase into the new system.
Instead, business process owners review standard SAP S/4HANA features against their operational requirements. Custom code gets brought over only when standard functionality cannot satisfy a validated business requirement.
When an object is approved for migration to a greenfield environment, developers extract the logic from SAP ECC, rewrite it to match modern guidelines, and transport it into the fresh system. Programs like ZSD_PRICE_EXPORT are usually discarded if standard application programming interfaces handle the export instead.
In a selective data transition, the project team chooses which custom packages move to the new shell system. Unused packages stay behind in the legacy system. The selected packages still require remediation because the target runtime environment is SAP S/4HANA.
Pro Tip: Even in a greenfield project, you still need to inspect legacy code. Developers frequently review the logic in legacy programs to understand custom calculation rules that business analysts forgot to document.
For a brownfield conversion, master data changes force custom code adjustments long before the actual system conversion starts. The primary prerequisite is Customer Vendor Integration (CVI).
In SAP ECC, customer master data lives in table KNA1, while vendor master data lives in table LFA1. In SAP S/4HANA, the central Business Partner (BP) model replaces separate master records. Every customer and supplier must be linked to a Business Partner record.
SUM will refuse to convert an SAP ECC system to SAP S/4HANA if CVI synchronization is incomplete. You must run CVI in SAP ECC, resolve duplicate records, and synchronize all customers and vendors with business partners before running SUM.
It is recommended, but not mandatory, that the business partner ID matches the customer or vendor ID during number range setup.
This requirement changes custom code. Any custom interface or dialog transaction that creates customers using transaction XD01 or vendors using XK01 must be retired or replaced with Business Partner application programming interfaces.
Before touching code, project teams execute the SAP Readiness Check. This diagnostic tool runs in your SAP ECC system and uploads system metrics to a secure cloud analysis dashboard.
The tool evaluates several critical migration dimensions:
For ABAP developers, the custom code section of the readiness report gives an early high-level count of affected objects. It categorizes issues by SAP functional area, identifying whether your custom code hits inventory management, sales and distribution, or general finance changes.
At Harbor Supply Co., the readiness check revealed that report ZSD_ORDER_STATUS collided with simplification items around sales status tracking, while ZMM_STOCK_MOVES collided with inventory management data model changes.
Quick Challenge: Open transaction SE11 in your current development system. Inspect whether any custom tables reference data element MATNR or include direct fields declared with data type CHAR and length 18.
Review your current SAP ECC landscape to understand the scope of your custom code:
In the next lesson, The Simplification List: What Changed in S/4HANA, you will explore the Simplification Database, learn how to run transaction SYCM, and interpret simplification items that affect your code.
Was this lesson helpful?