Similar to configuration management, data migration is an important activity in a project. By data migration, we mean the data that you need to migrate from the legacy system, such as master data and opening balances. Data is needed for any kind of task and has multiple attributes. Hence, to ensure that it is managed and utilized well, we need to undergo a systematic approach. In the context of implementing a Dynamics 365 solution, we are focusing on overall data management and would like to share a visual for an end-to-end understanding of all the activities involved in planning for data:

The full suite of activities involved in data migration is as follows:

• Planning for data migration: Involves planning the scope, tools, techniques, volume, and environment
• Data extraction and cleansing: Cleansing is a business function; however, milestones and dates must be well planned and baked in the data migration plan
• Data transformation: Seek and agree on the transformation requirements and rules
• Data validation: Maintain a checklist of validation criteria for the business for extracted data
• Mapping of information between the source and target systems: This mapping is per entity level; for example, customer entity can span account related information, contacts, address, and so on. One must ensure to have find a home for entity information to be exchange at the field level including any transformation needs on the data.
• Import of validated data in packets: Maintain a log of what all data and which all records have been extracted, cleaned, validated, and migrated
• After migration: Always confirm with the business about data accuracy and completeness

To be successful, involve business users and data experts right from the start of the project. Based on the size, complexity, and nature of the customer business, you may also need to include a data governance strategy in data migration planning.

Data migration may just seem like a one-time activity of moving data from the source to the Dynamics 365 solution, but it goes through the same lifecycle as that of any other requirements in a project. Planning for data migration is a must in order for us to be able to systematically identify and execute a number of activities spread over time with multiple stakeholders. It also eases out potential unknowns and makes it easier to know what to expect next.