.svg)
After completing a full migration, it’s not uncommon to notice a discrepancy between the number of records in your source CRM and the number of records migrated to your new CRM. This is usually due to how your target CRM handles data or how your migration settings were configured.
Here are the most common reasons why this happens and how you can verify each one using the Migration Details section in your migration wizard:
1. CRM Merging Rules
Many CRMs have built-in or custom merging rules and unique field constraints (e.g., email address, phone number) that can affect data migration.
For example:
-
If you're migrating a contact with an email that already exists in the new CRM, and your CRM has a merge rule based on email, the contact will be merged with the existing one rather than added as a new record.
-
In this case, a new record won't be created, but the data may still be attached to the existing one.
You can track this under the Existing column in the Migration Details to see how many records were merged instead of newly created.
2. Pending Records
Some records may not be migrated due to errors or data conflicts during the process.
To check:
-
Click the "View migration details" button in your wizard.
-
If a particular object (e.g., contacts, deals, notes) has pending records, their count will appear under the Pending column.
-
Click Details next to the object to review specific errors and resolve them accordingly.
3. Filters Enabled During Setup
If you applied filters to certain objects during the Objects step of your migration setup, only the records that match those criteria will be migrated.
For example:
-
You may have filtered contacts by creation date or assigned owner.
-
Records not matching your criteria will be excluded from the migration.
You can view how many records were filtered out by checking the Filtered column in the Migration Details.
Summary
Discrepancies in record counts are usually due to merging rules, migration errors, or filtering. You can use the Migration Details view in your wizard to identify exactly where and why records were not migrated, and take action accordingly.