Short answer: in a greenfield implementation you design the new ERP for how you want to operate and carry forward only the data you need. The safest route is to assess the source, map to the new data model, cleanse and harmonise, then rehearse with reconciliation before cutover.
Why greenfield?
Years of customisation and workarounds accumulate in a legacy system. A greenfield approach avoids copying that complexity into the new ERP. It lets you adopt clean processes and bring across a clean data set.
The four steps
- Assess the source. Profile customised tables, organisational structures and data quality before any design decision.
- Map to the new model. Translate customers, vendors, materials, BOMs and GL structures into the cloud ERP data model.
- Cleanse and harmonise. Retire obsolete records, remove duplicates and assign clear data ownership.
- Rehearse and reconcile. Run repeated mock loads with reconciliation sign-off before cutover.
What to carry forward
Master data is the foundation: customers, vendors, materials, BOMs and GL structures. Beyond that, agree early what else the business genuinely needs, such as open items and balances, and what can stay in an archive. Every decision about scope is easier when you know where the data came from.
Knowing both sides of the move
Our team knows SAP ECC6 from many years of implementing and supporting it, including where its data comes from and where it needs to go. That knowledge shortens assessment and reduces surprises during mock loads.
Read more about our legacy ERP migration approach, or talk to our team.