Skip to main content

Bulk Actions: Merge Multiple Contacts

Use Bulk Actions to merge up to 10 duplicate contacts into a single master contact while preserving selected data, payments, and communication preferences.

Updated over 2 months ago

Who This Is For / When to Use

  • Account users cleaning up duplicate contacts.

  • Teams consolidating multiple records for the same person.

  • Admins maintaining accurate contact, payment, and communication data.


Select Contacts to Merge

  1. Go to CRM > Contacts or open a Smart List.

  2. Select 2–10 contacts using the checkboxes next to each record.

  3. Use filters or search to ensure only true duplicates are selected.

Important:
You cannot merge more than 10 contacts in a single bulk action.


Open the Merge Action

  1. With contacts selected, click More in the bulk action bar.

  2. Select Merge from the dropdown menu.

Result: A merge confirmation modal appears.

Choose the Master Contact and Field Values

  1. Review fields with conflicting values across contacts.

  2. Select which contact will be the Master record.

  3. For each field:

    • Choose the value to keep.

    • Retain additional emails and phone numbers if needed.

    • Set a primary email and phone number.

  4. Review conversation and opportunity data before proceeding.

Confirm the Merge Action

  1. Review the merge warning message.

  2. Check I understand this action cannot be reverted.

  3. Click Merge Contacts to continue.

Important:
Merging contacts is permanent and cannot be undone.


DND and Communication Preferences

  • DND preferences can be customized per channel during the merge.

  • SMS, email, and call preferences are preserved based on your selections.

  • This ensures compliance and accurate communication settings after merging.


Payments and Subscriptions After Merging

When contacts are merged:

  • All transactions, invoices, estimates, and subscriptions appear under the master contact.

  • Historical transactions may still show the original contact name in search results.

  • Clicking a historical record opens the master contact profile.

  • Failed subscription payments send invoices to the master contact’s email or phone.

Single contact payment view:

Merged contact payment view:


Automation and Workflow Behavior

  • Active workflows continue automatically.

  • Execution transfers to the master contact.

  • No automation progress is lost during the merge.


Common Use Cases

Duplicate Contact Cleanup

Merge multiple records for the same person into one complete profile.

Streamlined Communication

Keep all conversations, notes, and interactions under a single contact.

Data Consistency

Ensure accurate reporting and reduce confusion caused by fragmented records.


Common Issues and Fixes

  • Merge option not available:
    Ensure 2–10 contacts are selected.

  • Wrong data retained:
    Review all mapped fields carefully before confirming.

  • Unexpected master contact:
    Explicitly select the desired master record during field selection.


FAQ

How many contacts can I merge at once?

You can merge 2 to 10 contacts in a single bulk action.

Can I merge more than 10 contacts?

No. You must merge contacts in batches of 10 or fewer.

What is the master contact?

The master contact is the primary record that remains after the merge. All selected data is consolidated into this record.

Can I undo a merge?

No. Merging contacts is permanent and cannot be reversed.

What data can I choose during the merge?

You can choose which names, emails, phone numbers, conversations, and opportunities to retain or combine.

Are payments and subscriptions preserved?

Yes. All transactions and subscriptions are retained and shown on the master contact.

Will automations stop when contacts are merged?

No. Active workflows continue automatically under the master contact.

Is course progress merged?

No. Course progress is not currently merged when contacts are combined.

Why is there a 10-contact merge limit?

This limit prevents data errors and ensures accurate selection of the correct source-of-truth fields.

Did this answer your question?