Select Objects
      Back to home
      1. MMC Help Center
      2. Migration Process
      3. Select Objects

      How can I do cross-object mapping (e.g., Emails to Notes)?

      April 10th, 2025

      Object Mapping Isn’t Always Straightforward

      When migrating data between CRMs, you may need to adjust the default mapping, merge multiple source objects into a single target entity, or split one source object into several target entities. There are many reasons for this, including:

      • Different Object Types Across CRMs: For example, a source CRM might use “Projects,” while a target CRM organizes similar data as “Tickets” or “Deals.”

      • Activity Grouping Differences: Your current CRM might combine all activities—emails, calls, meetings, and tasks—under a single umbrella. You might prefer to separate these into distinct categories.

      • Custom to Native Object Mapping: Custom objects in your legacy system may align well with native objects in your new CRM.

      • API Limitations: Some CRMs, like Zoho or Pipedrive, don’t support migrating correspondence via API. In these cases, mapping emails to notes can serve as an effective workaround.

      Practical Examples of Object Cross-Mapping with MigrateMyCRM

      Modifying the Default Mapping

      Our migration wizard provides suggested default mappings, but you can tailor them to meet your specific needs:

      1. Click the pencil icon next to the target object to view all available mapping options.
        pencil-1

      2. Choose the one that best matches your source entity or create a new one:
        list

      3. Your changes will be auto-saved.

      Note: If your target CRM is monday.com, be sure to check the workspace name beneath each object (board) title when making changes.

       

      Merging Multiple Source Objects into One Target Object

      This process is pretty similar to the previous case. To merge several source objects into a single target object, repeat the described steps above for each source object you want to combine.

      Scenario:
      You want to merge People and Leads from your source CRM into Contacts in the destination CRM. After setting this up, the migration will either create new Contact records or match them with existing ones—if the matching toggle is enabled.

      contacts

       

      Splitting One Source Object into Multiple Target Objects

      To split a single source object into multiple target entities, use the Filters feature.

       

      Scenario:
      You want to divide your Contacts into Leads and People based on their Lifecycle stage.

      • If a contact has a 'Lead' stage in the source CRM, it should migrate to Leads.

      • Otherwise, it should go to People.

      Steps:

      1. On the Select Object page, map Contacts to People.

      2. Click the funnel icon to add a filter.
        split1

      3. Set a filter rule to identify records that should become People. (You may click Get Count to see how many records match the filter). Save the filter! 
        filter_people

      4. Scroll to the bottom of the object list and select Contacts again.

      5. Map it this time to Leads.
        leads

      6. Set the opposite filter: include only Contacts with the Lifecycle stage = Lead.

      lead1


      ⚠️ Remember: On the next step, you'll need to configure mappings for both pairs—Contacts → People and Contacts → Leads.

       


      Still need help?

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