Note: If you already have HubSpot connected and only want to fix something specific, go straight to the setup article or the errors article.
What Enginy can do with your HubSpot
The integration works both ways:
Export contacts and companies from Enginy to HubSpot, creating or updating them.
Import contacts and companies from HubSpot to Enginy, from a list or from a filtered search.
Sync specific fields continuously, with you deciding the sync direction for each field.
Log campaign activity in HubSpot: emails sent, LinkedIn messages, replies, and conversation tags.
The first thing Enginy does: find the right record
Every time Enginy is going to write to HubSpot, it first checks whether that contact or company already exists. If it finds a match, it updates the record. If it does not, it creates a new one.
That search is not magic: it uses the fields you choose as identifiers in the configuration. This is the most important decision in the whole integration, because an identifier that is too loose can create duplicates, while one that is too strict can create new records when the contact already existed.
By default, Enginy identifies contacts by first name, last name, and company name, and companies by domain. You can change this in the Sync Configuration step.
Bi-sync: what it is and why HubSpot is a special case
In HubSpot, you can decide the sync direction field by field. If you are coming from another integration, this behavior may be new and different in this case.
For each mapped field, you choose one of these five options:
Option | What it does |
Bi-directional sync | The field syncs in both directions. |
HubSpot overwrites Enginy | HubSpot is the source of truth. Changes there overwrite the value in Enginy. |
Enginy overwrites HubSpot | Enginy is the source of truth. Changes here overwrite the value in HubSpot. |
Sync if value is empty | Only fills the destination field if it is empty. It never overwrites an existing value. |
Sync deactivated | The field does not sync automatically. You will need to export it manually. |
Important: This choice also decides which fields are included when you import from HubSpot, not only what is sent out. A field set to Enginy overwrites HubSpot or Sync deactivated will not be filled during import. This is the most common reason behind “I imported contacts and some data is missing.”
What you get the day you connect
When you connect HubSpot, Enginy does not leave you with an empty configuration. It creates an initial mapping with the most common fields already matched, so you can start exporting from day one.
For contacts:
Field in Enginy | Property in HubSpot | Initial direction |
First name |
| Bi-directional |
Last name |
| Bi-directional |
Professional email |
| Bi-directional |
Phones |
| Bi-directional |
Mobile phone |
| Bi-directional |
Job title |
| Bi-directional |
Country |
| Bi-directional |
Contact CRM owner |
| HubSpot overwrites Enginy |
Last activity at CRM |
| HubSpot overwrites Enginy |
For companies, thirteen fields are mapped with the same logic: name, domain, website, LinkedIn, address, city, country, phone, description, and founding year as bi-directional, and lifecyclestage, hubspot_owner_id, and notes_last_updated with HubSpot as the source of truth.
It is a setup designed to work without configuring anything, but you should still review it. If you do not want HubSpot to overwrite the owner or lifecycle stage of your records in Enginy, change it before you start exporting.
The two association toggles are also enabled by default, so when you export a contact, Enginy will try to associate it with its company, and vice versa.
Only one CRM at a time
Enginy works with one active CRM integration at a time. If you already have another CRM connected, you will need to deactivate it before connecting HubSpot.
Changing CRM deletes your configuration. When you connect a different CRM from the one you had before, Enginy resets all the previous CRM configuration: field mappings, fixed value fields, manual export fields, engagement fields, campaign mapping, custom matching rules, default association type, and default CRM owner. User and identity mappings are also cleared.
There is no way to recover it from the interface. If you are considering changing CRM and have a carefully built configuration, contact us before changing anything.
Where to configure each part
Everything lives in the same place: Integrations, HubSpot card, Configure button.
If you want to… | Go to |
Avoid duplicates or change how records are identified | Sync configuration |
Decide which fields sync and in which direction | Field mapping |
Send campaign data to HubSpot, such as opens, replies, and status | Campaign mapping |
Make sure each exported record is assigned to the right person | User mapping |
If your account has the new task manager, you will also see a Tasks step to match HubSpot call outcomes with Enginy call statuses.