Movement of data plays key role in migration process. Entity by Entity data need to be moved from on-premise CRM to Online CRM as there is no direct way to restore complete DB in Online CRM server. Below are the steps to remember while moving the data:
The first step in Migration is to determine the entities order. From CRM point of view below is the process for entity Migration
a. Migrate system and Business Settings (See section 3.2)
· Business Unit
· Users and their Roles
· Teams
· Currencies
· Subjects
· Territories
· Equipment’s and etc.
b. Decide the Business entities and custom entities order based on their relationships and migrate them as below:
· Migrate Parent entities
· Migrate child entities
Note: If we have chain relationship, then migrate the first entity by removing second entity reference, migrate second entity and finally update first entity with second entity reference.
Ex: Account and Contacts in CRM have cyclic relationship. So, here is the migration process below:
· Migrate Account records by removing Contact lookup field mapping
· Migrate Contact records
· Update Account records with Contact lookup field.
c. Migrate Activities
Don’t map “Status and Status Reason” fields for activity migration. The reason behind this is that we cannot update the completed activities. But, in next step we need to create activity parties for these activities.
d. Migrate N:N relationship records
e. Migrate Activity Parties
f. Migrate Notes and attachments
g. Migrate Email Attachments
Please refer the blog to migrate Email attachments.
h. Update Activities Status and status reason
I have given high level steps. Please let me know if I miss anything here so that I will update this page.
Hope this helps someone ![]()

Like
Report
*This post is locked for comments