Two-way unsubscribe sync with your CRM
Unsubscribes now sync both ways between lemlist and your CRM, so an opt-out recorded on either side is respected on the other.
lemlist adds 4 boolean contact fields you can map to your CRM in Settings → CRM → Field mapping:
Do not contact (global)
Email unsubscribed
Phone unsubscribed
LinkedIn unsubscribed
lemlist → CRM: any unsubscribe in lemlist (app, extension, API, bounce, abuse report, or the lead clicking the unsubscribe link) updates the mapped CRM field. A channel field turns true as soon as one value on that channel is unsubscribed.
CRM → lemlist: ticking the mapped field in your CRM unsubscribes the contact in lemlist and stops them being contacted in campaigns. This is a polling sync, so a change in the CRM is picked up on the next cycle rather than instantly.
Do not contact works as a master switch: ticking it unsubscribes all 3 channels and pushes all 4 fields back to the CRM. Unticking it re-subscribes all 3 channels, provided every unsubscribe on the contact can be lifted. Unticking a single channel field re-subscribes only that channel and releases Do not contact, leaving the other channels untouched.
Some unsubscribes can't be lifted from the CRM: bounces, abuse/spam complaints, unsubscribes made by the lead themselves, and domain- or team-level unsubscribes are protected. A false sent from the CRM for one of these is rejected, logged on the contact as a field rejection, and the sync stops retrying until the CRM value changes.
Setup notes:
Available for HubSpot, Salesforce and Pipedrive. Mapping is opt-in — nothing syncs until you map the fields.
Salesforce suggests its native Email Opt Out and Do Not Call fields; Do not contact and LinkedIn unsubscribed need a custom field. HubSpot and Pipedrive require custom boolean fields for all 4.
The mapped CRM field must be boolean, or the sync raises an error until you fix it.
To push unsubscribes you already have in lemlist, map the fields then run a bulk Search & connect on your contacts.
If a contact changes on both sides between sync cycles, the most recent change wins.