The Migration Decision Every SAP Customer Must Make

SAP’s mainstream maintenance for ECC 6.0 ends in 2027, with extended maintenance available until 2030. For the thousands of European enterprises running SAP ECC, this is no longer a future concern — it is an active project that needs to be scoped, funded, and executed.

The central technical decision is: greenfield, brownfield, or selective data migration? Each has fundamentally different implications for timeline, cost, business disruption, and what you can and cannot preserve from your current landscape.

This article gives you the technical substance to make that decision with clarity.

Understanding the Three Approaches

Greenfield: Build New on S4HANA

A greenfield migration is a reimplementation. You install a fresh S4HANA system and rebuild your business processes using S4HANA’s standard capabilities, without carrying forward your ECC configuration, custom code, or historical data (beyond what you choose to archive or migrate selectively).

What you gain:

Clean core from day one — no legacy custom Z-objects
Full use of S4HANA’s native capabilities (Fiori UX, embedded analytics, simplified data model)
No technical debt carried forward

What you give up:

All custom ABAP development (must be rebuilt as BTP extensions or CAP applications if still needed)
Historical transaction data (unless separately migrated)
Institutional knowledge encoded in ECC configuration (must be re-documented and re-configured)

When greenfield makes sense:

Your ECC system is heavily customised with outdated logic that no longer reflects current business process
You are undergoing a significant business transformation (merger, new market entry, business model change)
Your ECC data quality is poor — migration is cheaper than cleaning and carrying it forward

European context: Greek and Mediterranean businesses that have operated with heavily localised fiscal reporting (AADE, Intrastat, VAT reporting) should carefully audit whether S4HANA standard covers their local legal requirements before committing to greenfield. SAP’s localisation for Southern European countries is generally strong but not perfect.

Brownfield: System Conversion In-Place

A brownfield conversion uses SAP’s Software Update Manager (SUM) with the Database Migration Option (DMO) to convert your existing ECC system to S4HANA in one technical operation. Your configuration, custom code, and historical data all come with you.

What you gain:

Historical data preserved in the new system
Lower business disruption — processes continue as before
Faster time to go-live compared to greenfield

What you give up:

You carry all technical debt into S4HANA
Custom ABAP must be remediated before go-live (SAP’s Simplification List flags incompatibilities)
You don’t get the benefit of rethinking processes

The custom code problem: In a typical European mid-size enterprise with 8–10 years on ECC, we encounter 200–400 custom development objects. The brownfield process requires running SAP’s Custom Code Migration app (part of the Readiness Check) and triaging each object:

Object Type	Typical Count	Action
Z-reports (ALV)	60–80	Often replaceable with standard S4HANA reports or Fiori apps
Z-enhancemenets (BAdI, user-exit)	30–50	Must be re-assessed against S4HANA equivalents
Z-programs (batch jobs)	40–60	Audit each; many can be replaced by standard automation
Z-function modules	20–40	Assess reuse vs. replacement with BTP CAP services
Z-SmartForms / SAPScript	20–30	Replace with BRFplus or Adobe Forms

This triage and remediation is typically the longest phase of a brownfield project — 3 to 6 months for a typical landscape.

Simplification List check example (ABAP):

" INCOMPATIBLE in S4HANA — table MARA field MTVFP removed
SELECT matnr mtvfp
  FROM mara
  INTO TABLE @DATA(lt_material)
  WHERE werks = @lv_plant.

" S4HANA equivalent — field moved to MARC
SELECT matnr mtvfp
  FROM marc
  INTO TABLE @DATA(lt_material)
  WHERE werks = @lv_plant.

SAP’s Readiness Check identifies these automatically, but the fix must be manually implemented and tested.

Selective Data Migration (Shell Conversion)

The selective data migration approach (also called “shell conversion”) is a hybrid. You convert the system structure (configuration, open items) but selectively migrate historical data based on business need.

Typical migration scope:

Always migrate: Open purchase orders, open sales orders, open FI documents, asset master and values, material master, customer/vendor master
Selectively migrate: Completed orders from the last 3–5 years (based on statute of limitations and business need)
Archive, don’t migrate: Historical data older than retention requirements

The technical tooling: SAP provides the Migration Cockpit (part of SAP S4HANA) for structured data migration. It uses staging tables and transformation rules to load master data and open items. For large volumes, the LTMOM (Legacy Transfer Migration Object Manager) or BODS (Business Objects Data Services) provide ETL-based approaches.

Migration Cockpit Workflow:
1. Define migration objects (Customers, Vendors, Materials, etc.)
2. Generate migration templates (Excel or XML)
3. Extract data from ECC (using standard reports or custom extractors)
4. Transform data to S4HANA format (cleansing, enrichment)
5. Load via Migration Cockpit
6. Validate (automated + manual)
7. Sign-off

The European Compliance Layer: What Changes in S4HANA

For European enterprises, S4HANA brings changes to localisation that require planning:

1. Universal Journal (Table ACDOCA)

S4HANA merges FI and CO into a single journal (ACDOCA). This means:

Reconciliation between FI and CO is eliminated (they are now the same document)
Custom reports that join BSEG (FI document line items) and COEP (CO line items) must be rewritten

For companies with complex management accounting, this is a significant change. Plan for at least 3 months of finance team retraining and report remediation.

2. Material Ledger Mandatory

S4HANA mandates the Material Ledger for all company codes. If you weren’t using it in ECC, your costing configuration requires migration. For manufacturing companies using standard cost, this may require re-running cost estimates and aligning inventory valuation.

3. SAP Document Reporting Compliance (DRC)

For EU e-invoicing mandates (Italy’s SDI, Germany’s XRechnung, France’s Chorus Pro), S4HANA’s DRC framework centralises electronic document submission. If your ECC had custom e-invoicing solutions, these must be evaluated against the S4HANA DRC standard.

4. Intrastat Reporting

SAP S4HANA significantly reworked Intrastat in 2022. European subsidiaries relying on custom Intrastat extraction logic from ECC will find it either replaced by standard functionality or partially obsolete. Conduct a detailed Intrastat mapping exercise before go-live.

Timeline Benchmarks: What to Expect

Approach	Company Size	Typical Duration	Key Variables
Greenfield	200–500 employees	12–18 months	Process redesign scope
Brownfield	200–500 employees	9–14 months	Custom code volume
Selective	200–500 employees	10–16 months	Data quality, volume
Greenfield	500–2,000 employees	18–30 months	Multi-country complexity
Brownfield	500–2,000 employees	14–22 months	Interface landscape

These are business go-live timelines, not technical implementation timelines. The technical system conversion (brownfield) can complete in a weekend for a 10 GB database. The business change management, testing, and training is what takes 12+ months.

Practical Recommendation: A Decision Framework

Choose Greenfield if:

Custom code exceeds 500 objects AND most of it is old/poorly documented
You are changing your business model or entering new markets concurrently
Your current ECC processes are widely diverged from SAP best practice

Choose Brownfield if:

Custom code is well-documented and business-critical
Historical data continuity is a legal or business requirement
You need to be on S4HANA within 18 months (greenfield rarely achieves this)

Choose Selective if:

You want brownfield but have serious data quality problems
You operate in multiple countries with complex legal data retention requirements
You want to leave a division or legal entity on ECC temporarily

Starting the Journey: Readiness Assessment

Before committing to a migration approach, run SAP’s Readiness Check (free via SAP for Me):

Custom Code Analysis — Volume and complexity of Z-objects, Simplification List violations
Database Size — Impacts technical timeline and hosting costs
Add-on Compatibility — Third-party SAP add-ons (ADP, payroll, industry solutions) may not be S4HANA compatible
Business Function Assessment — Which ECC business functions are being used that have changed in S4HANA

The Readiness Check output gives you the data to have an informed conversation with your stakeholders about which migration path fits your constraints.

Conclusion

There is no universally correct migration path to S4HANA. The right choice depends on your custom code debt, data quality, timeline pressure, and appetite for business process change.

What is certain is that the 2027/2030 maintenance deadline is real, and the preparation time for a quality migration is substantial. Organisations that start their readiness assessment now will have more options than those that wait.

Planning your S4HANA migration? Contact AegeanFlows for a readiness assessment and migration roadmap.

Kostas Polakis — Senior SAP ABAP Architect with S4HANA migration experience across European enterprise landscapes.