lemlist does the same on its side, automatically. When you merge contacts or companies in your CRM, lemlist merges the lemlist records linked to them. When you delete one, lemlist unlinks the lemlist record and looks for another match in your CRM. There is nothing to turn on: it works with your current CRM connection.
When you merge records in your CRM
lemlist finds the lemlist record linked to the CRM record you kept, and keeps it linked to that record.
The other lemlist records linked to the merged CRM records are merged into it.
The kept lemlist record keeps its values. Its empty fields are filled with the values of the merged records.
Campaign enrollments, activity history, tasks, list memberships and signal agents move to the kept record. If one of the records was marked Do not contact, the kept record is too.
The merge appears in the kept record's Activities tab, for example "HubSpot merged Thomas Baker into this contact".
If no lemlist record was linked to the merged CRM records, nothing changes in lemlist.
When you delete a record in your CRM
lemlist unlinks the lemlist record from the deleted CRM record.
lemlist searches your CRM for another record that matches it: by email, then name, for a contact; by website domain, then name, for a company.
If it finds one, the lemlist record is linked to it. If it finds none, the lemlist record stays in lemlist, unlinked.
lemlist never recreates a record you deleted in your CRM, and it never deletes the lemlist record.
When lemlist picks it up, CRM by CRM
CRM | Merge | Delete |
HubSpot | Within seconds. HubSpot notifies lemlist of every merge. If a notification is missed, the next sync of that record catches it. | Within seconds |
Salesforce | At the next sync of the merged record. Salesforce does not notify merges, so lemlist detects the merge the next time it updates that record. | At the next sync of that record |
Pipedrive (beta) | Within seconds. Pipedrive notifies the deletion of the merged record and names the record that was kept. | Within seconds |
Attio (beta) | Within seconds. Attio creates a new record when it merges, and lemlist links the kept lemlist record to it. | Within seconds |
Zoho CRM (beta) | Within an hour. lemlist checks Zoho's deleted records every hour. Zoho does not say which record was kept, so lemlist treats a merge as a deletion: it unlinks the merged records, then matches them again. | Within an hour |
💡 Zoho CRM: after a merge, two lemlist records can end up matching the same Zoho record. Only one can stay linked. You find the pair in Settings > Data management > Duplicates, type CRM record, ready to merge.
Does a merge in lemlist merge my CRM records?
No. lemlist only repeats what happens in your CRM, never the other way around. When you merge in lemlist, the CRM record linked to the record you keep receives the values you kept. The CRM records of the deleted lemlist duplicates stay in your CRM, untouched and no longer linked to lemlist. To merge them, merge them in your CRM.
Does deleting a record in lemlist delete it in my CRM?
No. Deleting a contact or a company in lemlist does not delete it in your CRM.
I merged two records in Salesforce. Why does lemlist still show both?
Salesforce does not notify merges. lemlist picks up the merge the next time it syncs the merged record, then merges its own records.
Where do I see the merges picked up from my CRM?
In the Activities tab of the kept record, and in your CRM sync logs (Settings > Logs).
What to do instead
Clean your CRM first. A merge done in your CRM reaches both tools; a merge done in lemlist stays in lemlist.
For duplicates that only exist in lemlist, see Merge two contacts or companies into one record.
For contacts that never reached your CRM because another lemlist contact took their CRM record, see Fix: "Value not applied" or "Contact already synced with another lemlist contact".
To merge many duplicate groups at once, see Merge duplicate contacts and companies in bulk.

