An ERP runs on data quality. Carrying over stock levels, customer records, and open orders without review digitizes inconsistencies. Migration is not purely an IT topic, it is a joint task for business departments and the project team.

Useful steps:

1. Define scope: which entities are go-live critical? What can follow later?
2. Clean up: resolve duplicates, outdated items, and dead customer records before import
3. Mapping: document fields and codes between the old and new system
4. Spot checks: verify business-critical records after the test migration
5. Rollback plan: what happens if the test migration fails?

Nuclos provides import and migration tooling. Business ownership still matters most: departments know the edge cases that no generic mapping covers.

Running migration alongside a process-oriented rollout reduces load: core master data first for the pilot process, the rest step by step.

More on project pitfalls: ERP implementation. Core system context: ERP core system.