Every potential duplicate account and contact in your workspace now lands in a single dashboard. Merge them, set parent-child relationships, or dismiss the ones that aren't really duplicates. The cleanup syncs straight to your CRM.
When we turned this on, here's what was hiding inside CRMs that everyone assumed were clean. Now it's all in one dashboard, grouped, ready to act on in a single sweep.
For most go-to-market teams, duplicate records are the silent tax. Two reps end up touching the same account. The same person gets emailed twice. Reports inflate. Deal ownership gets ambiguous. The Manage Duplicates workspace, now live for both Accounts and Contacts, brings every duplicate to a single place where you can act on them in seconds.
The Manage Duplicates view is linked from both the Accounts and Contacts lists. Every group of potential duplicates in your workspace shows up there, grouped together with all their relevant fields side by side. You decide what to do with each group.
The same grouped view, the same three actions, for both objects. Pick the records you want to act on (you can pick all of them, or just two out of three) and choose:
Detection logic, transparent and tuned per object.
acme.com, acme.com/about, and acme.com/contact?utm=linkedin all land in the same group, so the same company written three different ways doesn't slip through.Multi-record merging built in. Most CRMs only let you merge two records at a time. If a group has four duplicates, that's six clicks just to get to one record. Evergrowth merges as many as you select in a single step.
When you merge in Evergrowth, the merge is pushed to your CRM at the same time. Secondary records are deleted. Contacts move to the primary. Custom fields, tags, account plans, parent/child relationships, workflow schedules, and audit history are all consolidated. The primary's existing values are kept; only empty fields get filled in from secondaries. Then the primary record is re-synced to your CRM with the consolidated data.
You don't wait for duplicates to pile up. They get caught the moment they're created. Every contact entering Evergrowth, whether through Chrome Extension, Contact Finder Agent, CSV import, or single contact creation, is checked against the existing data before it lands. If it looks like a potential duplicate, it goes into pending status instead of being added blindly.
The user who added the contact gets a notification to review the pending status and decide what to do. For ambiguous cases (a new contact arrives but matches multiple accounts), the user picks which account it belongs to before it's committed.
This matters most for the Chrome Extension flow: if you're enriching someone on LinkedIn and that contact's company has five duplicate accounts in your workspace, you're shown the candidates and pick the right one. No more silent assignment to the wrong record.
The duplicate workspace touches a few surfaces. The first set is the cleanup flow itself. The last lives on the Account record so you spot duplicates without leaving the page.
Attio's API doesn't expose merge from external systems the way HubSpot, Salesforce, Pipedrive, Zoho, and Dynamics do. That's a platform-side limitation, not a missing feature on our roadmap.
Our team is currently working on a workaround so the Manage Duplicates flow can keep both sides in sync without merge endpoints. The plan is to drive the cleanup with the Attio APIs that are available (delete, update, relationship reassignment) and reproduce the merge result on the Attio side step-by-step. Until that ships, the merge happens in Evergrowth and the Attio side has to be cleaned up manually; the merge modal flags this clearly when Attio is connected.
If you're on Attio and want to be in the early-access cohort for the workaround once it lands, tell your CSM and we'll add you to the list.
Merges cannot be undone. The CRM-side merge is irreversible for most providers, and the secondary records are deleted in Evergrowth. Be sure before you confirm. We recommend starting with a small batch and checking the result before running through your full backlog.
Contacts are moved, not deduplicated. If two secondary accounts both had the same person on them, that person ends up listed twice on the primary after the merge. Plan to do a contact-merge pass after the account merge if you want a fully clean record.
Read-only users can review but not act. The dashboard is visible to everyone who can see the accounts list, but only users with edit permissions can merge, set parent-child, or dismiss.
Chrome Extension UI updates that flag pending contacts visually are rolling out next, so reps see at a glance which records are waiting for review. We're also extending the same detection logic to a handful of additional places contacts come into the workspace, and finishing the Attio merge workaround so the same one-step cleanup works for Attio customers despite the API limitations.