Separate Contacts and Companies
Configure Contact fields in the Contacts tab and Company fields in Companies. Do not mix company fields into the Contact mapping, even if the names look similar.
Available field types
Enginy Fields: data from the contact or company itself, such as name, email, domain, or country.
Fixed Value Fields: a fixed value sent to all included records.
Manual Export Fields: fields you can complete during a manual export.
Engagement Fields: properties related to activity and conversations.
Sync directions
BI-SYNC
Allows changes to be received from HubSpot and sent from Enginy. In automatic synchronization, HubSpot webhooks can update Enginy and Enginy changes can update HubSpot.
Use it only when both systems should be able to modify the field.
CRM overwrites Enginy
HubSpot is the source for the field. Enginy can receive the value during an import or an update coming from HubSpot, but it does not send it back as a normal mapping.
Enginy overwrites CRM
Enginy is the source for the field. Exports and outgoing synchronization can update HubSpot. Values received from HubSpot do not replace the Enginy value for that mapping.
Sync if value is empty
Fills the field when the destination is empty during supported one-off operations, such as an import or manual export. It does not work as continuous automatic synchronization in both directions.
Sync deactivated
Enginy ignores the mapping. A deactivated field is not added later simply because you run a manual export.
Sync direction selector
What the icons mean
The blue check means that option is selected. By itself, it does not certify that all values are compatible.
The yellow icon shows a warning. You can save the mapping, but you should check the data type and format.
The red icon means the option is disabled. It usually appears on read-only properties or options that cannot be selected.
A type mismatch usually creates a yellow warning, not necessarily a red error.
Type compatibility
Whenever possible, match equivalent properties:
Text with text.
Number with number.
Boolean with boolean.
Date with Date or DateTime.
Enumeration with a property whose values match HubSpot’s internal options.
Manual date fields support dd/MM/yyyy, dd-MM-yyyy, and yyyy-MM-dd. Enginy converts the value to the format HubSpot expects when exporting.
Before saving
Review yellow warnings.
Check that no required property is read-only.
Verify the internal options for Enumeration fields.
Confirm the direction of each sensitive data point.
Test with a few records before enabling broad synchronization.
Which records Enginy may create
Two settings decide whether Enginy creates a record in HubSpot that it could not match. They are the most common reason a contact "never arrived".
The creation toggles
In Sync configuration you will find two switches, both on by default:
Create contacts in HubSpot when no match is foundCreate companies in HubSpot when no match is found
Turn one off and Enginy updates what it matches and skips the rest. Nothing new is created for that entity.
Required fields
Each row in the Field mapping table has a checkbox in the Required column. Tick it and a record missing that field is skipped instead of created.
Note: This never blocks an update. A record that already exists in HubSpot keeps being updated as usual — the rule only gates creation.
Three things worth knowing before you use it:
One configuration covers every CRM. The check runs on the Enginy values, before they are translated into HubSpot property names. If you connect a different CRM later, the same rules apply.
0andfalsecount as filled in. A field is only missing when it is empty, contains nothing but spaces, or is an empty list.Turning creation off does not erase your selection. The list stops applying while the toggle is off, and comes back untouched when you turn it on again.
The checkbox is disabled while creation is off for that entity. Enable the matching toggle in Sync configuration first.
The rule that always applies
A contact with no email, no phone, no LinkedIn URL and no CRM ID cannot be exported at all, whatever you configure here. Enginy would have no way to match or identify it in HubSpot.
Where you see the effect
Export to CRM checks your selection before running and tells you how many records are missing required fields. If every record in the selection would be skipped, it blocks the export with None of these contacts will be created in your CRM.
These rules also apply to automatic campaign syncs, not just manual exports.