lemlist links a contact or company to your CRM by searching the CRM on its email, LinkedIn URL or domain. When several CRM records share a domain, for example the subsidiaries of a group, that search can link the wrong one.
A team admin can now give lemlist the CRM ID of the record directly. lemlist uses that ID as is to link the lemlist record with the CRM record, without searching. You can set it in the Contacts and Companies pages, or send it through the API.
This feature is in beta. If you don't see the edit button on the [CRM] ID field, your team is not in the beta yet, and the API refuses crmId as an unknown field.
Limitations
Works with HubSpot, Salesforce, Pipedrive and Attio. It is not available for Zoho: the button is hidden and the API answers
422 CRM_ID_UPDATE_NOT_AVAILABLE.Team admins only, in the app and in the API.
You can't set a CRM ID through a CSV import.
After a link is set or moved, the CRM wins on the first sync: the lemlist email, owner or company can be replaced by the CRM values.
The previous CRM record keeps everything lemlist already wrote into it. Activities imported from it stay in the lemlist timeline.
On HubSpot, after you move a company, HubSpot keeps the old company as a secondary association.
Phase 1: Set or change the CRM ID in the app
Open Contacts or Companies and click the record to open its side panel.
Find the [CRM] ID field (for example Salesforce ID) and click the pencil icon in it.
On a record not linked yet, Link to a record in [CRM] opens. On a record already linked, Change the linked [CRM] record opens.
Paste the ID in [CRM] record id, then click Link.
You can also do it from the table: add the [CRM] ID column to your view and use the same button on hover.
✅ Verify: the [CRM] ID field shows the new ID, and the [CRM] profile field no longer shows Not synced.
Phase 2: Understand the checks before the change
lemlist checks the ID before changing anything:
The ID must have the right format for your CRM.
The ID must not be used by another lemlist record. The error names that record.
The CRM record must exist. A deleted record is refused.
A merged record is refused, and lemlist gives you the ID of the record that survived the merge.
A converted Salesforce Lead is refused, and lemlist gives you the ID of the Contact it was converted to.
What happens when a link moves
Pending updates to the previous CRM record are cancelled.
If your team maps that field, the previous CRM record is marked as not synced with lemlist.
Campaign leads follow the new ID.
The activity history is pulled from the new CRM record.
For a company, each contact's association is pushed to the new CRM company.
The change is logged in the user activity.
Use the API
POST /contacts and POST /companies accept a crmId:
New record: lemlist links it straight to that CRM record, without searching the CRM, then runs a first sync with your field mapping rules.
Existing record with a different ID (found by its lemlist ID, email, LinkedIn URL or domain): lemlist moves the link to the new CRM record and syncs it again.
Same ID as today: nothing happens, so an integration can send the same payload on every run.
The response also returns the crmSync block (CRM, CRM record ID, errors), so you know which CRM record the row is linked to without a second call.
For the full parameters, see the lemlist API documentation at developer.lemlist.com.
Practical example
Your contacts reach lemlist from HubSpot through another tool, and each one already has its HubSpot ID. Your integration sends crmId with each contact in POST /contacts. lemlist links each contact to that HubSpot record directly, and a contact whose company has many subsidiaries on the same domain no longer ends up on the wrong account.
Troubleshooting
The ID is refused because it is already linked
Root cause: Another lemlist record already uses this CRM ID. The API answers 409 CRM_ID_ALREADY_LINKED and names that record in conflictingRecord.
Fix: Open the record named in the error and check which of the two should be linked to that CRM record.
The CRM record is not found
Root cause: The record doesn't exist in your CRM, was deleted, was merged, or is a converted Salesforce Lead. The API answers 422 CRM_RECORD_NOT_FOUND, or a 422 with survivorId (merged record) or convertedContactId (converted Lead).
Fix: Use the ID given in survivorId or convertedContactId, or check the ID in your CRM.
The integration gets a 409 after the link moved
Root cause: On the first sync after the link, the CRM values replaced the lemlist email. Your integration still sends the old email with the same crmId.
Fix: Send the email that is now in the CRM record.
Other errors
403: you are not a team admin.503: the CRM could not be reached. Try again later.
If your case is different
If you want lemlist to find and link many records at once, see Link or create your contacts and companies in your CRM in bulk.
If you want to see why a record did not sync, see Check why a contact or company didn't sync to your CRM.

