More recently I have been writing little bit more about data migration techniques and best practices. I have to say, it is a point where we all make mistakes. If you don’t map migrate the data properly, whatever the solution you may deliver, will not work. Especially when the current work of the client is dependent on existing data. If your CRM solution is not working, then you will get the blame no matter how good your solution is.
When providing client solutions with CRM, majority of the time clients want to migrate their existing data. The purpose of this article is to provide a comprehensive guide to migrate data with many to many relationships. As we all know support for many to many relationships is one of the coolest features in Dynamics CRM.
For instance, let’s assume a client wants to upload the accounts(companies) with the primary contact intact. In this scenario, accounts has a reference to contacts and contacts has reference to accounts (company). You can see the references in the below images.
Data migration is one of the top priority tasks in Dynamics 365 solutions. For majority of clients they have some data to be migrated to the new solution. And every client want their data to be perfect. So it is highly important that data is well prepared before doing any imports. Objective of this article is to highlight some of the best practices that you should follow up when preparing data.