How to Find and Merge Duplicate Contacts in GoHighLevel

Written by Niyamul Islam Sajal, COO & GHL Certified AdminBlog
GoHighLevel duplicate contacts: a person reviewing contact records on a laptop

A merge in HighLevel can't be reversed, so the order you do things in decides whether you tidy your database or damage it. GoHighLevel duplicate contacts usually come from forms, calendar bookings, imports and tools like Zapier, and each has a different fix. This guide covers finding them, merging them by hand, merging them automatically, and stopping them at the source.

Here we go into the mechanics: which tool does what, who can use it, and what happens to tags, notes and running workflows.

Where GoHighLevel duplicate contacts come from

HighLevel's own help article lists the usual routes: manual entry, CSV imports, forms, calendar submissions and third-party tools such as Zapier. If the same person fills in a form with a work email and later books a call with a personal one, you get two records for one human.

The behaviour depends on one account setting. With Allow Duplicate Contact switched on, a matching form or Zapier submission creates a new record. Switched off, it updates the existing one instead, as HighLevel's deduplication preferences article explains.

Messenger is a special case. With duplicates off, a Facebook or Instagram Messenger contact that later shares a matching email or phone is merged into the existing record automatically. With duplicates on, no automatic merge runs, so those pairs sit there until somebody merges them.

How to find duplicates with the Manage Duplicates tool

Open Contacts, click the three-dot menu and choose Manage Duplicates. The tool is for admins only (Agency Admin or Sub-Account Admin), so team members won't see it, and a missing option almost always means the user isn't an admin.

  1. Pick what to match on: Email (the recommended default), Phone or Name.
  2. Click Find Duplicates, then expand a group with the arrow to see every record in it.
  3. Click Review to compare the conflicting fields side by side and choose which value survives for each one.
  4. Confirm the merge, or click Reject if the records are genuinely different people.

Start with Email. It's the safest match, because two people can share a phone number or a name far more easily than an inbox. Switch to Phone or Name afterwards to catch the records that differ in email.

Manage Duplicates is the fastest way to merge duplicate contacts in bulk, and Manage Duplicates can also be the fastest way to lose a good record. Be careful with Reject. HighLevel's help article says a rejected email, phone or name won't be used to find duplicates again, and that the rejection can't be reverted. Use it only when you're sure.

How to merge GoHighLevel duplicate contacts by hand

For a handful of GoHighLevel duplicate contacts, skip the scan. Go to Contacts and your Smart Lists, search by name, email, business name, tag or phone, and select the contacts. Click More in the top action bar, then Merge, pick the master record and choose which conflicting values to keep.

The limits are firm. The Merge option only appears when you've selected between 2 and 10 valid contacts from the same sub-account, so a large clean-up has to run in batches of ten. A confirmation box warns that the action can't be undone, and the Merge button stays disabled until you tick it.

Searching a saved Smart List is a quick way to pull up every contact with the same tag or source before you start selecting.

What a merge keeps, combines and overwrites

The master record is the one that survives, and its existing values are kept by default. That default catches people out, so read this part before you click.

According to the same HighLevel merge guide (modified 2 September 2026), custom field values from the other contacts are added only where the master's matching field is blank. Tags are combined. Notes, tasks and opportunities are combined into the master, while appointments, payments, orders and invoices default to the master's values.

Workflows need more thought. Active executions can transfer to the master, but if the master is already in the same workflow, its existing run is kept and the extra one stops. Waits, goals and re-entry settings can also behave differently afterwards.

So make the older, fuller record the master unless the newer one holds better data, and check the field comparison rather than trusting the defaults.

Which method should you use?

Each way of handling GoHighLevel duplicate contacts suits a different job, and they differ on who can use them and which record survives.

MethodWho can use itMatches onWhich record survives
Manual merge from ContactsAnyone who can select contactsYou choose, by selecting 2 to 10 recordsThe master you pick
Manage Duplicates toolAdmins onlyEmail, phone or nameThe master you pick in Review
Merge Contact workflow actionWhoever builds workflowsEmail, phone, or bothAlways the older record

To merge duplicate contacts across a messy account in one sitting, the Manage Duplicates tool is the right start. For a steady trickle of new duplicates, a workflow is less work than a monthly scan.

On accounts we set up, the order is almost always the same. We stop new duplicates first, clear the backlog second, and automate what's left. With more than 100 GHL accounts built and configured, that sequence has saved us from merging the same people twice.

Merging duplicates automatically with a workflow

Merge GoHighLevel duplicate contacts: colleagues checking records on a screen

Photo by Artem Podrez on Pexels

The Merge Contact action runs inside a workflow, so GoHighLevel duplicate contacts are dealt with as they arrive. In Automations, open Workflows, add a trigger such as Contact Created or Form Submitted, then add the merge action and choose what to match on.

According to the Merge Contact workflow article, you can match by email, by phone, or by both together, and both is the strictest option. If nothing matches, the action does nothing and the contact carries on.

One rule differs from the manual tools. The newer contact is always merged into the older one, so a merge contact workflow action gives you no say in which record is the master. If the better record is the newer one, the workflow will still discard it in favour of the old.

The same article lists real limits. Goals tied to the old contact ID may not work, Wait for Reply steps can be affected if the email or text went out before the merge, and trigger link waits may fail. Test with sample contacts and check the Workflow Execution Logs before you switch it on for everyone. A custom build of this sort is the kind of thing our automation service handles.

Stopping new duplicates at the source

Merging GoHighLevel duplicate contacts is clean-up, and prevention is cheaper. Click Settings in the lower-left corner to open Business Profile Settings, then find the contact duplication preferences panel and switch Allow Duplicate Contact off. Changes apply straight away, with no Save button.

Next, choose the field HighLevel looks up first, Email or Phone. You can add a second preference, such as phone when no email matches. Pick the field your forms always collect, because a lookup on a field that's often blank misses the match.

CSV imports are already covered. The help article says they merge automatically by phone or email whatever the setting, so an upload can't create duplicates. That's useful when you're importing contacts, deals and notes from another system.

A safe routine before you merge anything

Export first. A merge can't be undone, so a backup is the only undo you have, and our guide to exporting and protecting your CRM data shows how.

Then merge one small batch, open the master record and check the tags, notes and opportunities. Only once that looks right should you run the rest. If you're still getting to know the platform, HighLevel's 30 day Bootcamp trial is a low-risk place to practise before touching live data.

And if you'd rather not do this yourself, our team can run the clean-up as part of a GHL setup, so your pipeline reports stop counting the same lead twice.

Frequently asked questions

Can I undo a merge in GoHighLevel?

No. HighLevel's help article says a completed merge can't be reversed, and the confirmation box asks you to acknowledge that before the button works. Export your contacts first.

How many contacts can I merge at once?

Between 2 and 10, all in the same sub-account. For a bigger clean-up, merge in batches.

Who can use the Manage Duplicates tool?

Only admins, meaning an Agency Admin or a Sub-Account Admin. Team members and users don't get the option.

Do CSV imports create duplicate contacts?

No. Imports are merged automatically by phone or email regardless of your duplicate setting, according to HighLevel's deduplication preferences article.

Sources

Cover photo by Yan Krukau on Pexels

Need help implementing this in GoHighLevel?

Our team builds, automates, and scales GoHighLevel systems for agencies every day. Book a free call and we'll map out exactly what to ship next.

Book a free call