One of the keys for a smooth transition into a new ERP system is the migration of essential legacy data. That demands:
1. Mapping the legacy data to the F&O data structure.
2. Resolving legacy data integrity issues as F&O will reject bad data.
The challenging aspect of data migration is usually data integrity. A classic example would be having a flexible legacy system which allows users to enter address zip codes freely without verifying if the zip code existed. So, your customer address table has a total of 500k rows with 50k of those having invalid or corrupt zip codes.
When this data is imported into F&O, it will reject the bad data but import the rest. Getting that feedback only when trying the F&O import is time consuming. It is more efficient to run validation on the data before importing into F&O as running a database level validation is much faster. There is often a level of trial- and error- approach when working on data migration. Receiving immediate feedback on data integrity greatly speeds up that process.
It is important to have a clear step by step best practice plan on how to do Data Migration. Our AXTEND Data Management (ADM) assumes having all the legacy data present in Azure database tables and the ability to run validation scripts to verify and check the data for issues. This enables the data professional to validate the data and get immediate feedback. The ADM solution comes with a ready to use set of prebuild validations for core F&O data, for example:
• Customer and Vendor master data, including address and contact information.
• Customer and Vendor open transactions.
• Project and Project contract data.
• Project Transactions.
• General Ledger transactions.
This validation, like the example of customer master above, uses F&O configuration data that has been exported to the Azure database to verify the staged legacy data so that the data professional can resolve the issues before attempting the import into F&O.
