Prerequisites

• Any security role that allows grants Read, Write, Append and Append To permissions for both entities of selected records.
• Configured Column Mappings for the entities of the selected records.

How To Merge Records From Different Entitites

Merging records from two different entities works similarly to merging records within the same entity, with a few key differences. For an overview of the general merge interface and process, refer to Merging Records.

In the Master Record row, you will additionally see the record’s Entity displayed below its name, indicating which entity the record belongs to. As with standard merges, select the master record you want to remain active and choose the column values to retain.

In addition to the standard column filters in the header bar, only the columns you have defined mappings for in the Entity Configuration’s Column Mappings will be available for selection.

Once you have made your selections, click Merge to start the process.

Cross-Entity Merge Restrictions

Currently there are some limitations specific to cross-entity merges that do not apply to same-entity merges:

• No related data – except lookup columns explicitly defined in the Column Mappings – will be transferred from the non-master records to the master record. This includes related activities such as Emails, Notes, and Tasks.
• Only mapped columns can be selected and have their data transferred.
• The Merge Master Reference column configured in Merge Settings is not applied in cross-entity merges.
• The Status Reason setting from Merge Settings is ignored. All non-master records are simply set to inactive with their default status reason.

Next Steps

Set up Column Mappings.