Mapping step in MigrateMyCRM

April 9th, 2025

Records Mapping is the third step in the wizard, following Select Objects. This step is crucial for the success of your migration project. If you notice missing fields or relationships in your migration results, reviewing your records mapping should be your first step.

If you selected Start Quick Sample after connecting your source and target CRMs, the test migration will use automatically generated mappings. Once the sample migration is complete, you can return to the Records Mapping step via the wizard’s top menu to review and adjust the mappings as needed.

Use the drop-down menu to switch between objects. The left panel displays the list of fields and relationships for the selected object in your source CRM, while the right panel shows the corresponding properties in your target CRM.

The horizontal menu includes helpful features to support building your ideal migration setup

1. Filter source fields by type—for example, show only relations or only fields that have any utilization in your CRM.
2. Sort fields by priority (default), usage, or alphabetically.
3. Refresh fields after making changes to their name, type, or accessibility in either CRM. Note: Refreshing the browser tab does not have the same effect!
4. Unmapped fields—a list of fields available for mapping.
5. Custom fields section displays a list of custom properties available in the target CRM. You can also use it to create new custom fields in bulk.
6. Test your mapping using a specific record ID from your source CRM to validate the setup.
7. Click Save whenever the icon turns green to preserve your changes.
8. Access advanced settings (these are rarely used during self-service migrations).
9. Explore additional options—the most commonly used are Fields Usage and viewing previous Mapping Versions.

10. Documentation: Access guidance and descriptions of all interface features.

11. Comments: View notes left by you or your teammates during the mapping of this object—helpful for collaboration and continuity.

Some fields have icons before their names to indicate their type. Hovering over the (i) icon next to a field’s name reveals its system name, whether it’s native or custom, and the type of data it stores—such as text, number, or relation.

Pay attention to the two types of icons between source and target fields:

• Right Arrow shows the direction of the data transfer. This icon is informational only and not clickable.

• Down Arrow indicates that the field is a drop-down picklist. Click this icon to review and ensure that all options are mapped correctly.

There is an individual menu for a field. Click on icons in it to get more insights about data in it:

1. View sample values from the field. Click again to load other examples.
2. Display values for drop-down picklists. You can also get a list of unique values for text fields. This is especially helpful when mapping an open-text field from the source CRM to a picklist in the target CRM.
3. Field usage shows the percentage of source records that contain a value in this field.
4. Combine multiple fields from the source CRM to map them into a single field in the target system with a function option.
5. Adjust field format as needed during migration.
6. Add comments about a field for collaborating with your team members or leaving notes for yourself.

Additional Mapping Details & Actions

• Hidden fields: If a field is marked as hidden, it means it’s not visible in your CRM’s user interface. However, we can still access its values and migrate them if needed.

• Yellow exclamation mark (!): This icon signals a mismatch between the source field’s data type and its corresponding field in the target CRM. For example, it may indicate an attempt to migrate numeric data into a drop-down field, which could lead to issues.

  
  
  

Now that you're familiar with the available tools, you're ready to move on to data mapping. The concept is simple: only data from mapped fields will be transferred to the target CRM; unmapped fields will not.

Mapping a Source Field That Isn’t Yet Mapped

1. Click “+ Select field” to open the list of available target fields.

2. Choose the appropriate target property and click Apply.

If the corresponding field doesn’t exist yet, you can create a new one either in your CRM’s settings or directly within the mapping wizard.*

*Some CRMs (like Capsule) do not allow the creation of custom fields via API. In these cases, you’ll need to create the custom field directly in your CRM. After that, refresh the mapping page to see the newly created field in the list of available properties.

Creating a Custom Field in the Target CRM Using MigrateMyCRM

1. In the right panel, click “+ Select field.”

2. In the pop-up window, click “Add custom field.”

3. Review the field type. The system will suggest a type based on the source field, but you can change it if necessary.

4. Edit the field name if you wish.

5. (Optional) Adjust any additional settings using the checkboxes provided.
   

6. Click Apply to create the field.

7. Then, click Apply again to map this new field to the source property.

Editing or Removing Field Mappings

If two fields have been mapped and you want to make changes, you have two options:

• Unmap a field: Click the red X at the end of the row to remove the mapping. This does not delete a field in either CRM—it simply prevents the data from being transferred.

• Edit the mapping: Click the pencil icon to replace the currently mapped field with another one.

Still need help?

Please submit an inquiry on the contact page, email support@syncmatters.com, or simply reach out to us via chat.