New Workflow Action - Merge Contact Live!

Cleaning up duplicates in your CRM can feel like busywork that never ends. That is why automating the process inside HighLevel workflows is a game changer. The new Merge Contact workflow action lets you automatically identify and merge duplicate contacts based on email, phone, or both — all without leaving your automations. It speeds up agency operations, keeps your contact timelines clean, and reduces manual cleanup on the contacts page.

What the Merge Contact action does

At its core, the Merge Contact action automates the same merge logic you already use, but it runs inside a workflow. Instead of manually selecting duplicates and hitting merge, you add this action to any workflow and let HighLevel handle the rest according to the matching criteria you choose.

Key behaviors to know

• Match options: You can match by email, by phone, or by both email and phone.
• Preserves the older record: When two contacts are merged, the system preserves the older contact record (the one that existed first) and merges the newer duplicate into it. The original wins.
• Execution logs: Every merge is logged in the workflow execution logs so you can audit what happened.
• No automatic undo: Merges are permanent. If you run a mass merge and regret it, there is no one-click undo — you will need to manually fix or restore from an export.

Why this matters for agencies and HighLevel users

Duplicate contacts create noise: multiple timelines, split messaging, inaccurate metrics, and the risk of sending duplicate emails or SMS messages. For agencies scaling their HighLevel setup, keeping a clean CRM is crucial for reliable automations, accurate reporting, and professional client communication.

Automating merges inside workflows fits naturally into common agency operations:

• After a CSV import, automatically merge contacts that match by email or phone.
• When leads arrive from multiple funnels, merge duplicates to consolidate conversation history.
• After integrations (Zapier, native webhooks, form integrations) create a follow-up workflow that both tags and merges duplicates.
• Maintain clean mailing lists for campaigns and avoid sending duplicate messages.

How the Merge Contact action works — step by step

Here is a practical sequence you can build into a workflow to start using Merge Contact responsibly.

1. Create or edit a workflow — choose a trigger that makes sense. Common triggers are contact created, tag added, or after an import process.
2. Add filters or decision steps to limit which contacts the merge action will touch. For example, only run on contacts tagged "Imported-2026" or only if a custom field is set.
3. Add the Merge Contact action and select your match criteria: email, phone, or both.
4. Test with a small sample — add a handful of test contacts or run the workflow against a small tag group. Check execution logs to verify the behavior.
5. Review execution logs — every merge is recorded with enough detail to review which contacts were merged and when.
6. Go live at scale once you are confident in the behavior. But remember to export or backup contacts before large, irreversible changes.

Best practices and safety tips

This action is powerful. With power comes responsibility. Follow these best practices to get great results without surprises.

1) Always run spot tests first

Before running merges across thousands of contacts, test the entire workflow on a small set (50–200 contacts). Confirm the intended winner is preserved and that the merged history looks correct.

2) Backup contacts before mass merges

Export your contacts to CSV or create a snapshot before running any broad automated merge. If you ever need to recover information, having the export will save a lot of time.

3) Normalize matching fields

Mismatched formatting prevents merges. Make sure emails are in a normalized form (trim spaces, lowercase), and phone numbers have consistent country codes and formatting. If needed, run a normalization workflow first that rewrites phone and email fields into a consistent format.

4) Use filters to avoid unintended merges

Don’t attach the merge action directly to a trigger that can fire en masse without any guardrails. Use decision steps and tags so merges only happen for contacts matching specific criteria.

5) Preserve data you care about

Remember that the older contact record is preserved. If you rely on a newer contact’s custom field data, consider copying important fields to the older record before merging or creating a routine that consolidates fields into the winner record.

6) Tag merged contacts and track events

When a merge completes, tag the winner with something like "merged:YYYYMMDD" and record metadata in a custom field if you want to track the merge source. That makes auditing and rollback easier.

Common use cases and examples

Use case: Cleaning up import duplicates

Scenario: You regularly import CSVs from different lead sources and need to avoid duplicate workflows triggering or duplicate campaigns being sent.

Workflow example:

1. Trigger: Contact created via CSV import
2. Action: Add tag "imported-2026-03"
3. Action: Merge Contact (match by email and phone)
4. Action: If merge occurred, tag winner "merged-import"

Use case: Consolidating multi-funnel leads

Scenario: A prospect fills multiple forms or interacts across funnels, creating multiple contact records. Merging ensures single conversation history and prevents duplicate outreach.

Workflow example:

1. Trigger: Form submission
2. Decision: If contact has tag "prospect", run merge
3. Action: Merge Contact (match by email or phone)
4. Action: Route to owner or start nurture sequence

Use case: Post-integration cleanup

Scenario: Integrations from external tools can create duplicates. Automating merges after inbound webhook events keeps CRM tidy.

Workflow example:

1. Trigger: Webhook received
2. Action: Merge Contact (match by email)
3. Action: Add tag "integration-merged"

Troubleshooting and recovery strategies

If merges aren’t happening as expected or you need to recover information, here’s how to proceed.

Why a contact didn’t merge

• Matching field is blank or formatted differently. Check phone formatting and email cleanliness.
• Contacts don’t meet workflow filters. Verify decision steps and tags.
• The match criteria used different fields than you expected. Confirm selection is email, phone, or both.

How to recover after an accidental merge

There is no automatic undo for merges, so prevention is key. If an accidental mass merge happens:

• Restore from an exported contact CSV if you created one before merging.
• Manually recreate contacts using the data in the execution logs and any backups you have.
• Use tags and custom fields to help identify merged records and speed up manual restoration.

Using execution logs

Execution logs show each merge activity. Use those logs to identify which contacts were merged and when. This is extremely useful for audits and for manual recovery steps.

Implementation tips for agency setups and scaling

HighLevel agencies that manage multiple client accounts can add merge automation to agency-wide templates and make it part of onboarding and import SOPs. Consider adding a standard workflow to all client accounts that runs on imports and normalizes contact data before merges run.

Some practical implementation tips:

• Template workflows: Add a Merge Contact action to agency template workflows so clients inherit best practices.
• SOPs: Include a step to export contacts before any bulk merge in client playbooks.
• Use Nexus Hub resources: If you need templates or community support, Nexus Hub offers workflows and resources for HighLevel agency implementations.
• Training: Train team members to run spot tests and review logs before executing large merges.

Quick checklist before running merges at scale

• Export contact CSV backup.
• Normalize emails and phone numbers.
• Limit initial run to a small test cohort.
• Confirm the older contact is the desired winner.
• Tag merged winners for auditability.
• Review workflow execution logs after the test run.

Want to try it in your account?

If you are already on HighLevel, look for the Merge Contact action inside your workflow actions list. When you add it, follow the checklist above and run a small test before scaling. If you are exploring HighLevel, consider starting a free trial to experiment with workflows, automations, and this Merge Contact feature. For templates, guides, and community support, Nexus Hub is a great place to find prebuilt workflow examples and implementation help.

Summary

The Merge Contact workflow action is a practical addition to HighLevel that automates a common CRM maintenance task. It consolidates duplicate contacts automatically on the criteria you choose, keeps your timelines and campaigns accurate, and reduces manual cleanup. Use tests, backups, and filters to make sure merges behave exactly as you expect, and incorporate the action into agency templates and SOPs to scale clean CRM practices across accounts.

FAQ

What match options are available with the Merge Contact action?

You can match contacts by email, by phone, or by both email and phone. Choose the option that best fits your dataset and normalization practices.

Which contact is preserved when a merge occurs?

HighLevel preserves the older contact record — the one that existed first. The newer duplicate is merged into the older contact and removed as a separate record.

Can I undo a merge?

There is no built-in undo for merges. Always export contacts before running bulk merges so you can restore data if necessary.

Are merges logged?

Yes. Every merge action is recorded in the workflow execution logs so you can audit merges and see what changes occurred.

What precautions should I take before running a large merge?

Run spot tests on small batches, export a contact backup, normalize email and phone formatting, and add workflow filters to prevent unintended merges.

Can I use Merge Contact in agency templates?

Yes. Add the action to agency template workflows and SOPs so every client setup gets consistent duplicate handling. Combine it with normalization and tagging steps for reliable results.