Many migration projects start with wrong expectations.
What is the hardest thing about starting data migration?
Not knowing what to do and who is responsible.
Many organizations get confused when it comes to moving their information to a new ERP system.
Here are main assumptions that get are usually wrong.
1. ERP experts will do everything for data migration.
It is true that the implementation partner can suggest the overall process for migration, provide instructions for data load and suggest some tools for automation. But they cannot decide which data is needed for migration. It is the business problem to make sure that data is correctly migrated. Internal resources like employees from Finance and other departments should participate in data migration.
2. Data migration activities should start as early as possible.
Yes, it is recommended to start preparation for data migration well in advance. Early discussions about data requirements can help to shape the final solution. But how data will be presented in the new system depends on the agreed features and business processes. The best time to start data preparation is when the Design phase of a project is in progress.
3. Data migration strategy is just a formality.
Some ERP implementation partners provide templates for the strategy documentation. They all look rather technical and focused mainly on extract-transform-load process and technical details like list of systems, number of records, etc. But in fact the strategy is very specific for each business and goals of the project. Business stakeholders should agree key principals to make sure that the critical data is delivered to the new system on time and with good quality.
At the beginning of the ERP implementation it is very helpful to have an advisor who can prepare a roadmap and clarify main principals of data migration. Several consultations will save a lot of time and minimize frustration of the business team.
Please feel free to contact me to discuss your concerns about data migration initiation.
Advisory and guidance about data migration to Dynamics 365 F&O.