When setting up the HubSpot integration in lemlist, you map lemlist contact fields to HubSpot properties so data can sync in both directions. Not all HubSpot property types are supported — this article covers which ones you can map, which ones are excluded, and how types translate between the two platforms.
Accepted HubSpot field types
lemlist only offers HubSpot properties for mapping when their property type is one of the types below. A property's HubSpot fieldType (the UI widget) can vary, but it is the underlying type that decides whether the field is mappable.
HubSpot UI type | HubSpot property type | Typical fieldType |
Single-line text | string | text |
Multi-line text | string | textarea |
Number | number | number |
Date picker | date | date |
Date and time | datetime | date |
Single checkbox (Boolean) | bool | booleancheckbox |
Dropdown select | enumeration | select |
Multiple checkboxes | enumeration | checkbox |
Radio select | enumeration | radio |
Phone number | phone_number | phonenumber |
HubSpot user / owner | enumeration (referencing the Owner object) | select |
HubSpot stores every value as a string over the API. lemlist converts values on the fly: a Date field is sent as a midnight-UTC timestamp, a Date and time field as a full ISO timestamp, and enumeration values as the option id/label.
Not supported field types
These HubSpot properties are not accepted for two-way mapping and either do not appear in lemlist's field mapping dropdown, or appear as read-only (CRM → lemlist only).
HubSpot property | Behaviour in lemlist | Reason |
Calculated / score properties (calculated = true) | Read-only — appears as CRM → lemlist only | Computed by HubSpot, cannot be written back |
Read-only properties (modificationMetadata.readOnlyValue = true) | Read-only — appears as CRM → lemlist only | HubSpot blocks updates on these fields |
Hidden properties (hidden = true) | Not offered for mapping | Not exposed in the HubSpot UI |
Any other property type (e.g. object_coordinates, json, file/HTML-style properties) | Filtered out — not shown in the dropdown | Type not in the accepted list above |
Field mapping cheat sheet (lemlist ↔ HubSpot)
This table shows which lemlist field type can be mapped to which HubSpot 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 → HubSpot (push)
When a lemlist contact field is pushed to a HubSpot property.
lemlist field type | Compatible HubSpot types | Notes |
Text | Single-line text (string), Multi-line text (string), Dropdown (enumeration), Phone number (phone_number) | Most flexible — a text value fits any string-based HubSpot property. |
Number | Number (number) | A non-numeric value is rejected (validation error) and not synced. |
Date | Date picker (date) | Sent as a midnight-UTC timestamp (date only, no time). |
DateTime | Date and time (datetime) | Sent as a full ISO timestamp. |
Boolean | Single checkbox (bool) | — |
URL | Single-line text (string) | HubSpot has no native URL type; stored as text. |
Phone | Phone number (phone_number), Single-line text (string) | — |
Select | Dropdown (enumeration / select), Multiple checkboxes (enumeration / checkbox) | For multi-value enumerations, values are joined. |
User | HubSpot owner (enumeration referencing the Owner object) | Maps a lemlist user to a HubSpot owner via the user mapping. Only owner-referencing enumerations are supported. |
HubSpot → lemlist (pull)
The lemlist field type a HubSpot property becomes when imported.
HubSpot type | Becomes in lemlist |
Single-line text (string), Multi-line text (string) | Text |
Number (number) | Number |
Date picker (date) | Date |
Date and time (datetime) | DateTime |
Single checkbox (bool) | Boolean |
Phone number (phone_number) | Phone / Text |
Dropdown / Checkboxes / Radio (enumeration) | Select / Text |
HubSpot owner (enumeration → Owner) | User |
Read-only HubSpot properties (calculated/score fields, and any property where readOnlyValue is true) can only sync HubSpot → lemlist. They appear in the mapping dropdown as read-only and are never pushed from lemlist back to HubSpot.