I would start exporting all data from legacy system and conducting thorough review on the data: - what are the essential part of the data - what needs to be adjusted/converted w.r.t. requirements in new system - what part of the data is obsolete/outdated Transactional data is usually quite straight-forward but master data is more complicated. Many times customers/consultants miss the opportunity to strenghten data integrity. This can be done by: - removing unnecessary data from migration - converting or adjusting data to similar values/categories - updating data with new information stored somewhere else

Safeguarding data integrity during an ERP migration is crucial to avoid costly errors. Start with a thorough data audit to identify what's essential. For example, while migrating, categorize data into “must-have,” “should-have,” and “can-live-without” lists. Create a backup of all data before starting the migration, ensuring you can revert if something goes wrong. Conduct testing in stages, verifying data accuracy after each phase. Finally, engage users in reviewing migrated data to spot any discrepancies early on. This proactive approach minimizes risks.

It is vital to ensure data integrity when moving to a new ERP system. That seems obvious, but it does not always happen. The first step is to identify any problems with the data that currently exist in the legacy system. Conduct a thorough data audit and cleaning. Then audit the cleaned data against business processes. Make sure that the data are valid and useful before you move them. Next, create an "old-to-new" data field mapping formula or strategy. In any given test of success, the "old" data field must be able to successfully navigate through to the other side or to the "new" data field in the "new" system. If you can't do that, you might have to do the right thing and work with the data problem first.