To access Field Mapping, go to Integrations → HubSpot → Configure → Step 2: Field Mapping.
Important: HubSpot can auto-convert some field types, but is strict on enumeration fields. Always review yellow warnings before saving.
Understanding the Status Icons
Icon | Status | What it means |
✓ Blue | Compatible | The field types match. No action needed. |
! Yellow | Warning | The field types may be incompatible. Review this mapping carefully before saving. (HubSpot may still process some mappings automatically, but not all.) |
✕ Red | Error | The mapping cannot be applied. The export will fail for any record using this mapping. |
Warning: Do not save a configuration with red icons. Exports will fail for all records using that field mapping.
Which HubSpot Field Type Should I Use?
Use this table as a reference when selecting the destination HubSpot property for each Enginy field.
Enginy field | Recommended HubSpot field type | Notes |
First name, Last name, Job title, Email, Phone | Single-line text | Standard text fields. Fully compatible. |
Number of employees, Years in role, Growth % | Number | Map to a HubSpot number property. |
Created at, Last activity at CRM | Date and time | Never map to a text property. |
Outreach Stage, Sequence Status | Enumeration (dropdown) | Value must match the internal option name exactly — see below. |
Languages, Sub-industries | Multi-select enumeration | Values must be separated by |
LinkedIn URL, Domain, Website | Single-line text or URL | Both types are compatible in HubSpot. |
Personal emails, Other phones | Multi-select or Single-line text | Use Professional email and Mobile phone instead where possible to avoid sending arrays. |
Yellow Warning: What to Do
HubSpot can auto-convert some field types automatically. However, yellow warnings still require attention because not all conversions succeed.
1. Text mapped to an Enumeration (dropdown) field
If you map an Enginy text field to a HubSpot enumeration (dropdown) property, HubSpot will reject the request if the value you send does not match one of the allowed options for that property. HubSpot returns a VALIDATION_ERROR (HTTP 400) in this case.
The value must match the internal option name of the HubSpot dropdown — not the display label visible in HubSpot.
How to fix it:
Create an AI Variable with output type One off and define the tag options to exactly match the HubSpot dropdown's internal option names.
For Fixed Value or Engagement fields: enter the exact internal name directly in the field mapping configuration.
For Manual Export fields: enter the exact internal name at the time of export.
Note: Internal option names may differ from the display labels you see in HubSpot. Go to HubSpot → Settings → Properties, open the property, and check the internal values for each option.
2.Date field mapped to a Text field
Enginy stores date fields (such as Created at or Last activity at CRM) as full date-time values in ISO 8601 format. Map these fields to HubSpot Date or Date/Time properties to ensure they are processed correctly.
3.Multi-select values — separator format
If you are mapping a multi-value field to a HubSpot multi-select enumeration property, HubSpot expects the values to be joined with a semicolon (;), not a comma.
Example: option_one;option_two;option_three
How to fix it: Make sure the values you send use ; as the separator. Using commas will cause HubSpot to store the entire string as a single unrecognised value.
Red Error: What to Do
A red icon means the mapping will always fail. There are two reasons this happens:
1.Incompatible field types
The field types on both sides are incompatible and HubSpot cannot convert them automatically.
How to fix it: Remove the mapping and select a HubSpot property with a compatible type. Use the reference table above to choose the correct type.
2.Read-only HubSpot property
The destination property in HubSpot is read-only and cannot be updated by Enginy. This typically affects system-generated properties such as record IDs or calculated properties.
How to fix it: Remove the mapping and choose a different HubSpot property, or contact your HubSpot administrator to confirm property permissions.
Common HubSpot Mapping Mistakes
Mistake | What happens | How to fix it |
Mapping a Company field in the Contacts tab (or vice versa) | Export fails with a field mapping error | Verify that only Contact fields appear under Contacts, and only Company fields under Companies |
Mapping an Enginy date field to a HubSpot text property | Date value not processed correctly | Map to a HubSpot Date or Date/Time property instead |
Mapping an Enginy text field to a HubSpot enumeration without matching internal option names | HubSpot returns VALIDATION_ERROR and the export fails | Use an AI Variable (One off) with the exact internal option names |
Using commas instead of semicolons for multi-select values | HubSpot stores the entire string as a single unrecognised value | Use |
Mapping to a HubSpot calculated or read-only property | Export fails | Choose a writable property instead |
Campaign Status Sync misconfiguration | HubSpot shows: "HubSpot conversation status sync is misconfigured. Please review your HubSpot campaign mapping" | Align the picklist values in Enginy with the existing options in the HubSpot property in Step 3: Campaign Mapping |
Saving mappings with red icons | All records using that mapping fail to export | Fix or remove any red-icon mappings before saving |
Need More Help?
If you have reviewed your mapping configuration and the export still fails, contact our support team with:
The name of the Enginy field and the HubSpot property you are trying to map
The error message or icon you are seeing
A screenshot of the Field Mapping configuration if possible