When setting up the Salesforce integration in lemlist, you map lemlist contact fields to Salesforce fields so data can sync in both directions. Not all Salesforce field types are supported — this article covers which ones you can map, which ones are excluded, and how types translate between the two platforms.
Accepted Salesforce field types
The following field types can be selected in lemlist's field mapping dropdown. When pushing data to Salesforce, make sure the value you're sending respects the target field's max length — values that exceed it will be truncated or rejected.
Salesforce UI type | Salesforce API type | Max characters |
Checkbox | boolean | — |
Currency | currency | — |
Date | date | — |
Date/Time | datetime | — |
Number (decimal) | double | — |
255 | ||
Number (integer) | int | — |
Picklist | picklist | 255 |
Multi-Select Picklist | multipicklist | 4099 |
Percent | percent | — |
Phone | phone | 40 |
Text | string | 255 |
Text Area | textarea | 255 |
Long Text Area | textarea | 131 072 |
Rich Text Area | textarea | 131 072 |
URL | url | 255 |
Not supported field types
Fields of these types won't appear in lemlist's mapping dropdown (or are restricted to read-only CRM → lemlist sync). Trying to map them manually will have no effect.
These Salesforce field types are not accepted for mapping and will not appear in lemlist's field mapping dropdown.
Salesforce UI type | Salesforce API type | Reason |
Auto Number | string | System-generated, read-only (appears in dropdown as readonly, CRM → lemlist only) |
Formula | varies (result type, e.g. string, double) | Computed field, read-only (appears in dropdown if result type is accepted, CRM → lemlist only) |
Roll-Up Summary | varies (result type, e.g. double, date) | Computed field, read-only (appears in dropdown if result type is accepted, CRM → lemlist only) |
Lookup Relationship | reference | Relationship field |
Master-Detail Relationship | reference | Relationship field |
External Lookup | reference | Relationship field |
Geolocation | location | Compound field |
Address | address | Compound field |
Time | time | Not implemented |
Encrypted Text | encryptedstring | Not implemented |
ID | id | System field |
Base64 | base64 | Binary data |
Field mapping cheat sheet (lemlist ↔ Salesforce)
This table shows which lemlist field type can be mapped to which Salesforce field type, in both sync directions. A pairing not listed below is incompatible: the value won't sync correctly (or the field won't appear in the mapping dropdown).
lemlist → Salesforce (push)
When a lemlist contact field is pushed to a Salesforce field.
lemlist field type | Compatible Salesforce types | Notes |
Text | string, textarea, email, url, phone, picklist | Most flexible — a text value fits any string-based Salesforce field. Respect the target's max length (e.g. 255 for Text/Email/URL). |
Number | int, double, currency, percent | A non-numeric value is rejected (validation error) and not synced. |
Date | date | Sent as YYYY-MM-DD. |
DateTime | datetime | Sent as a full ISO timestamp. |
Boolean | boolean | — |
URL | url, string | — |
Phone | phone, string | Salesforce Phone max length is 40. |
Select | picklist, multipicklist | For multi-select, values are joined. |
User | reference → User | Maps a lemlist user to a Salesforce User. Only references pointing to the User object are supported (not Account, Opportunity, etc.). |
Salesforce → lemlist (pull)
The lemlist field type a Salesforce field becomes when imported.
Salesforce type | Becomes in lemlist |
Checkbox (boolean) | Boolean |
Currency (currency), Decimal (double), Percentage (percent), Number (int) | Number |
Date (date) | Date |
Date/Time (datetime) | DateTime |
Single-line text (string), Multi-line text (textarea), Email (email) | Text |
URL (url) | Text |
Phone (phone) | Phone / Text |
Picklist (picklist), Multi-select picklist (multipicklist) | Select / Text |
User lookup (reference → User) | User |
Read-only Salesforce fields (Formula, Auto Number, Roll-Up Summary, and any non-updateable field) can only sync Salesforce → lemlist. They appear in the mapping dropdown as read-only and are never pushed from lemlist back to Salesforce.