CRM merges now sync to lemlist contacts and companies
Cleaning up duplicates in your CRM used to leave lemlist out of sync: after a merge in HubSpot or Salesforce, the duplicate contact or company stayed in lemlist. lemlist now detects CRM-side merges and mirrors them.
When you merge two contacts in your CRM The two lemlist contacts become one. The contact linked to the surviving CRM record stays, the duplicate is folded into it and deleted, and nothing on the duplicate is lost:
History (emails, replies, calls, notes, tasks) moves onto the surviving contact in a single timeline
Inbox conversations merge into one thread
Campaign entries and pending sequence steps follow the surviving contact
Tasks move over with their status and assignee
Email addresses from the duplicate are added, not replaced, and enrichment history merges in
Lists, favorites and drafts follow, with no duplicate entry if both contacts were already on the same list
Mapped CRM fields are re-pulled from your CRM; fields your CRM doesn't own keep the survivor's values, and the duplicate only fills in what was empty
When you merge two companies in your CRM Contacts, history, tasks, campaign entries, lists and Copilot conversations from the losing company move to the surviving one. Contacts that belonged to each company are not merged with each other — they now simply share a company.
On a real delete in your CRM The lemlist contact is never deleted. It keeps its data, campaigns and history, and lemlist searches the CRM once for another matching record (by email, LinkedIn, then name) to reconnect it. If nothing matches, the contact stays desynced but intact. Companies are not re-matched on delete.
This is an opt-in, backend-only change with no UI, and it only applies to merges and deletes that happen after it's turned on — past duplicates are not backfilled. It is not available for Pipedrive, since its API does not indicate which record survived a merge.