Resolve duplicate accounts
When two or more accounts in your workspace share the same company web domain, they are grouped together as potential duplicates so you can decide what to do with them. The Manage Duplicates view collects these groups in one place. From there you can confirm an account is not a duplicate, merge a group into one record, set a parent-child relationship between them, or auto-merge every group at once. Use this when your imports or data sources have created several records for the same company.
Before you start
Section titled “Before you start”Duplicate grouping is based on the company web domain. Accounts without a domain are never grouped, so an account that has not been resolved to a domain will not appear here. The view is available to signed-in workspace members; if your role has read-only access you will not be able to open it.
How groups are formed
Section titled “How groups are formed”Evergrowth groups accounts that belong to the same company and share the same normalized web domain. As soon as two or more such accounts exist, they form one group. If you confirm a record is not a duplicate, it leaves the group and the remaining accounts are re-checked; once only one account is left with that domain, the group dissolves on its own.
A group is shown as a card headed with its account count (for example, 3 accounts). Each card lists the accounts in a table using the same columns as your Accounts list, and you can choose which columns show the same way you would there - see Choose and reorder table columns. The view shows five groups per page.
- Open the Duplicates view under Accounts. The page is titled Manage Duplicates for Accounts.
- Narrow the list with the filters at the top:
- The Search for account box finds a specific company.
- The Duplicate status filter switches between To review (groups still awaiting a decision) and Not a duplicate (records you previously dismissed).
- The Origin filter narrows groups by where their accounts came from: Evergrowth + CRM (the group mixes an account created in Evergrowth with one from your connected CRM), CRM only (every account in the group came from your CRM), or Evergrowth only (every account was created in Evergrowth). This is useful when you want to clean up duplicates from one source at a time - for example, reviewing the records that exist in both Evergrowth and your CRM before a sync, so the same duplicate does not keep coming back.
- Beyond these duplicate-specific filters, you also get the same advanced filters, saved views, and search you use on the main Accounts list - see Filter accounts. Use these to focus the cleanup on a slice of accounts, for example only those in one ecosystem or owned by one teammate. A group only appears if at least two of its accounts match your filters, so filtering can shrink or dissolve a group’s visible size without changing the underlying data. Filters and column choices you set here are scoped to this view and reset the next time you open it - they do not carry over to the main Accounts list or persist between visits.
- Inside a group card, select the rows you want to act on using the checkboxes. The action buttons appear above the table once you have a selection.
- Choose one of the per-group actions:
- Merge - available when two or more rows are selected. Opens the Select primary account to merge into dialog. Pick the one record that should survive; the dialog footer shows how many accounts are selected. The other selected accounts become secondaries and are removed once the merge runs. If the group is linked to a CRM that does not support account merging, a banner warns that the merge happens in Evergrowth only and the duplicates may reappear after the next sync. Otherwise a banner warns that the secondary accounts will also be deleted in your CRM and that the action cannot be undone. Choose the primary, then select Merge.
- Set parent-child relationship - available when two or more rows are selected. Opens the Select parent account dialog. Choose the account that should be the parent; the rest become its children. This keeps all the records but links them in a hierarchy rather than collapsing them. Select Assign to confirm.
- Not a duplicate - removes the selected accounts from the potential duplicates list. A confirmation asks whether you want to remove the chosen accounts; select Remove to confirm. Removed accounts no longer appear under To review.
- Restore duplicate - the reverse of the above. For accounts you previously dismissed, this puts them back into the potential duplicates list so they can be reviewed again. Confirm with Restore.
- Delete - available for seats with delete access, once one or more rows are selected. Removes the selected accounts entirely rather than merging or dismissing them. See Delete records for the confirmation flow.
- To clear every group at once, select Auto-merge at the top of the view. This is described below.
Auto-merge every group
Section titled “Auto-merge every group”The Auto-merge button opens the Auto-merge duplicate accounts dialog, which scans every group still awaiting review and merges each one into a single primary record. If you have any of the filters described above applied when you open the dialog, a banner reads Filters applied and only the duplicate groups matching those filters are merged - the rest are left for you to review separately. Clear the filters first if you want auto-merge to cover every open group.
You decide how the primary is picked by ordering a list of priority rules. The rule at the top wins; if two accounts tie on it, the next rule decides, and so on. Drag the rules to set your order. The available rules are:
- Latest qualification date - the account most recently qualified by agents wins.
- Most contacts available - the account with the largest contact base wins.
- Highest account score - the account with the strongest signals from research wins.
- Latest research date - the account whose research data was refreshed most recently wins.
- Connected to CRM - the account already linked to one of your CRMs wins.
- ICP status - an account marked Yes wins over Inconclusive, then No.
- Earliest created date - the account that was first created in your workspace wins, keeping the oldest record as the primary.
The list starts in this order, with Earliest created date last, so by default ties are broken in favour of the most recently qualified account and the oldest record only decides a tie nothing else could.
The dialog warns that the action cannot be undone, and that once started, secondary accounts in every group are merged into the chosen primary across Evergrowth and your connected CRMs. If a connected CRM does not support account merging, a second banner notes the merge happens in Evergrowth only for those accounts. Select Start auto-merge to begin.
What happens next
Section titled “What happens next”A single merge removes the secondary accounts and keeps the primary. A parent-child assignment keeps every record and links them, and you will see a confirmation that the parent was assigned. Marking accounts as not a duplicate (or restoring them) takes effect immediately and is reflected when you switch the Duplicate status filter.
When your CRM supports account merging and it rejects the merge for one or more of the selected accounts - for example, a conflicting related record on the CRM side - those accounts are left as they are rather than merged locally. Merging them anyway would only let the CRM re-create the same duplicate on the next sync, so Evergrowth waits for the CRM’s own merge to succeed before touching the local records. For a manual merge, if every selected account is rejected this way, you see an error explaining why instead of a completed merge; if only some are rejected, the rest still merge and the error names which accounts were held back so you can resolve the conflict in your CRM and try again.
Auto-merge runs in the background and can take a while. Track its progress on the task feed under the Merges tab. While a record is queued, its detail page shows a banner noting it is queued for an auto-merge and will either survive as the primary or be merged into another shortly. If your CRM rejects one or more merges during an auto-merge run, that run finishes with a “Auto-merge finished with issues” notification instead of a plain success, and the affected groups are left for you to resolve and retry.
Any account that is still part of a group shows a banner on its detail page, for example “2 potential duplicates found for this account,” with a Review link that opens this view filtered to that group.
When a CRM that does not support account merging is involved, the same duplicates can reappear after the next CRM sync, so it is worth re-checking the view after a sync completes.