Before creating a Contact or Company, Enginy tries to find an existing record in HubSpot. A good matching configuration reduces duplicates and allows later synchronizations to update the same ID.
Contact Identifier
In the current integration, Contact matching can use several available data points:
LinkedIn URL, when mapped.
Professional email.
First and last name together with the associated Company.
A custom property when you choose Custom Mapping.
Matching does not always treat these signals as isolated alternatives. Even if you configure a standard identifier, Enginy may try email, LinkedIn, or name with company when those details are available.
Contact Identifier options
Contact Identifier configuration
Recommendations for Contacts
Map professional email if your data includes it.
Use the full LinkedIn URL and avoid saving search or redirect URLs.
Review the associated Company before relying on first and last name.
If you choose Custom Mapping, use a stable and unique property.
Company Identifier
You can choose one of these criteria:
Domain: searches by domain.
Domain or Company Name: tries the domain and can fall back to the name.
Custom Mapping: uses the selected custom property.
Company Identifier options
Company Identifier configuration
Recommendations for Companies
Use the domain when it is available.
Avoid overly generic names if you enable Domain or Company Name.
Do not use a custom property that may be repeated across several Companies.
What happens when a match is found
Enginy keeps the HubSpot ID in the linked record. Later exports update that record instead of creating a new one, as long as the link remains valid.
If several HubSpot records match the same contact or company, the operation may end as a conflict. Enginy should not silently choose or merge duplicates. Review duplicates in HubSpot and run the operation again.
Associations between Contacts and Companies
In General, you can enable export of the Company associated with the Contact and the Contact associated with the Company.
General association options
These options decide whether Enginy includes the other entity during export. The append, primary, or replace mode then decides how the association is changed in HubSpot.
When importing Contacts from HubSpot, Enginy keeps the available primary association. It does not necessarily reproduce all historical associations for the record.