Good SAP data migration starts long before go-live weekend. Data migration is where many ERP projects slip. Not because loading data is hard, but because the data itself is messy and decisions about it come late. Here’s how to plan it so go-live weekend is uneventful.
- Start cleansing early, long before the build is finished.
- Move masters, open items and balances; leave most history behind.
- Plan at least two trial loads before go-live.
- Give every data object a business owner.
Why SAP data migration goes wrong
Cleansing starts too late, during testing
No business owner for each data object
Too much history is moved ‘just in case’
No reconciliation plan for balances
The six steps
What to move, and what to leave
| Usually move | Usually leave in the old system or archive |
|---|---|
| Customer, vendor and material masters | Closed historical transactions |
| Open sales and purchase orders | Old, inactive master records |
| Open receivables and payables | Superseded price lists and conditions |
| Opening balances and fixed assets | Data you can report from an archive |
For S/4HANA, SAP provides the Migration Cockpit with predefined templates for common objects, which speeds up mapping and loading.
Tips that save weeks
- Profile the data first to see duplicates, gaps and inconsistent codes.
- Agree naming and numbering rules before cleansing starts.
- Automate validation so each trial load produces an error report.
- Rehearse cut-over with timings, so go-live weekend runs to plan.
Clean data is the cheapest insurance an ERP project can buy.
Common mistakes to avoid with SAP data migration
Treating it as a technical task
SAP data migration needs business owners to decide what’s correct, not just IT to load files.
One trial load
A single test rarely catches everything. Plan two or three trial loads.
No reconciliation sign-off
Agree in advance how balances and counts will be checked and who signs off.
Cleansing in the new system
Fix data before loading it; cleaning inside SAP after go-live is far harder.
A worked example: rehearsing cut-over
This scenario is a composite of common situations, not a specific client.
A company plans its SAP data migration over three trial loads. The first load reveals duplicate customers and missing tax numbers; owners fix them in the source system.
The second load runs much cleaner, and finance tests reconciliation of open items and balances. The third load is a full cut-over rehearsal with timings.
On go-live weekend, the final load follows the rehearsed plan and reconciliation is signed off on time. Good SAP data migration made go-live uneventful.
Checklist before your SAP data migration starts
Use these questions with your team before you begin. Clear answers here make every later decision faster.
- A business owner for every data object
- Agreed rules for naming, numbering and units
- A decision on how much history to move
- At least two trial loads in the plan
- A reconciliation and sign-off process for balances
Frequently asked questions
How much history should we migrate?
Usually only open items and opening balances. History can stay accessible in the old system or an archive.
Who is responsible for data cleansing?
The business owns its data; the partner provides tools, templates and validation.
How many trial loads are needed?
At least two, often three, so the final load is a rehearsed routine.
What tools are used for SAP data migration?
For S/4HANA, SAP’s Migration Cockpit with predefined templates is commonly used.
How long does SAP data migration take?
It runs alongside the project; cleansing often takes longest.
Worried about your data?
We’ll profile your data and build a migration plan with clear owners and trial loads.