April 8th, 2025
After connecting your source and target CRMs, the next step is object mapping. MigrateMyCRM performs this automatically and enables most of available objects for migration—except for Users, which are set for matching.
If you have chosen the ‘Start Quick Sample’ option, you’ll launch an instant test migration, skipping the object and records mapping review. Once the sample is complete, you can return to the first wizard steps at any time to review and update your mappings.
To customize your object mapping from the beginning, click the ‘Customize Your Mapping’ button on the first screen of the migration wizard.
On the Select Objects page, you’ll see a list of CRM entities that are going to be involved in your data migration project. The left panel displays entities from your source CRM, while the right panel shows the corresponding entities in your target CRM.
1 - enable an object for migration on matching
2 - disable an object
3 - set a strategy for an object: migration, matching, or both
4 and 5 - helpful documentation
6 - refresh the list of objects in case of any updates are done in any of the CRMs
7 - select another target object
8 - set filter for records migration
Can’t Find a Source Object?
If you don’t see a source object in the left panel, click the “+” icon below the last listed object to reveal the full list. Then, select a corresponding destination object in the target CRM and save your changes.
A green tick sign in a row means the object is available for mapping. A green sprout icon indicates that it's a native (system) object, and a tiny hummer is for a custom one:
If an object is missing from the list or appears greyed out, check whether the CRM account you connected has the necessary permissions to access it. Once you have upgraded your user's permissions set to access the objects, click Refresh icon to get the missing objects into the mapping UI.
You can also create a custom object in the target CRM and map it accordingly, supposing your user role allows it in certain target CRMs that allow creating custom objects via API:
Default Disabled Objects
You might notice a stopwatch icon next to some source objects.
This indicates that, for technical reasons, processing these entities requires a large number of API requests and may take a significant amount of time. These objects are disabled by default to help you run quicker samples and validate the mapping of other objects. Once you're confident that the core of your mapping is correct, you can enable these time-consuming objects and run a final sample.
Pay attention, that enabling these objects increases the total record count and potentially might affect the price of your migration.
Pro Tips
-
✅ Merge multiple source objects into one target object. Select the destination entity for every source object you want to merge.
Example: Migrate both Leads and Contacts into Contacts in HubSpot. -
🔍 Split one source object into multiple target entities using filters.
Example: In Salesforce, you can divide Tasks by type—such as Calls, Emails, and Meetings—into separate entities in the target CRM.
Please submit an inquiry on the contact page, email support@syncmatters.com, or
reach out to us via chat.