Control the sync direction for CRM owner and contact-company association
You can now choose the sync direction for the owner and contact ↔ company association fields, just like any other mapped field. Previously these fields were locked to bi-sync, and any manual action in lemlist would overwrite your CRM.
In the field mapping table, each field now has two controls:
Create & update sync direction: Bi-sync, CRM priority, lemlist priority, Bi-sync on create with CRM priority on update, or Deactivate sync.
1st sync: applies only the first time a lemlist record links to an existing CRM record, and only for fields set to Bi-sync. Auto-fill always fills an empty side from the other. On conflict, choose whether CRM overwrites lemlist (default) or lemlist overwrites CRM.
An empty value never overwrites a filled one, in any direction or mode.
Owner and contact ↔ company association keep two differences from other fields: the CRM side stays locked (it's required to create a CRM record), so only Bi-sync and Bi-sync on create with CRM priority on update are available, and Deactivate sync isn't offered.
This applies to the contact and company objects on HubSpot, Salesforce, and Pipedrive. Existing defaults are unchanged — owner and primary company stay on Bi-sync with 1st sync set to CRM overwrites lemlist unless you switch them.