Before you run the merge accounts job, you must run the duplicate check job. The duplicate check job identifies duplicate pairs among account records. Before you run the merge contacts job or merge leads job, you must run the duplicate contact check job. The duplicate contact check job identifies duplicates among contact records, lead records, and custom object records.

Ensure each duplicate pair is a valid duplicate. You can enable the Ignore Duplicate flag to prevent

Customer 360 for Salesforce

(

Customer 360 for Salesforce

) from merging a duplicate pair.

The merge job eliminates the duplicate record and keeps the master record based on the merge rules that you configure in the merge settings. You can toggle the master record to select which record ID in the pair the merge job eliminates. If a contact is associated with a duplicate record, the merge accounts batch job associates the contact with the master record. If a duplicate record has child records, notes, attachments, and activities associated with it, the batch merge job associates these with the master record. If the duplicate record contains data that is not in the master record, such as a phone number, the data is lost when you batch merge the records. You can perform a manual merge to preserve data in a duplicate record.

During the merge process, if the accounts to be merged have hierarchy enabled,

Customer 360 for Salesforce

asynchronously processes hierarchy operations for both large and small hierarchies. When you run the merge account job, in the performance settings, set the Batch Size to 5 for the job to run without any exceptions. Default is 10.