Enginy can send Contacts and Companies to HubSpot through a manual export, a workflow, or automatic synchronization of already linked records.
Manual export
Use a manual export when you want to control a specific set of records and review options before sending it.
Enginy first tries to find an existing record. If it finds one, it updates the linked ID. If it does not find one, it can create a new Contact or Company.
Fields with the CRM overwrites Enginy or DEACTIVATED direction are not sent as normal mappings. Fixed values and manual export fields can complete the operation when configured.
Values available during manual export
Automatic synchronization
Automatic synchronization works with linked records and enabled fields. It does not scan all of HubSpot every time.
BI-SYNC allows incoming and outgoing changes.
Enginy overwrites CRM allows outgoing changes.
CRM overwrites Enginy allows incoming changes.
IF_EMPTY does not act as continuous synchronization in both directions.
DEACTIVATED is excluded.
Associate Contacts and Companies
When an export includes both entities, choose how Enginy should handle HubSpot associations.
append
Adds the new association and keeps existing ones.
primary
Associates the exported Company and sets it as primary, without using the destructive replace behavior.
replace
Removes the Contact's existing associations and creates the association indicated by Enginy.
Association Type selector
Important: Review Association Type before confirming. In some manual export and workflow flows, replace may appear as the initial value. If you want to keep associations created in HubSpot, choose append or primary.
The replace option affects associations; it does not delete the Contact or Company.
Resync
A resync reevaluates the configured fields and may overwrite values according to their directions. Before running a broad resync:
Review BI-SYNC and Enginy overwrites CRM mappings.
Check fixed values.
Confirm Association Type.
Test with a small sample.
Record owner
Enginy can write hubspot_owner_id with the owner resolved by User Mapping or Default CRM owner. The owner is assigned to the record, but Enginy still accesses HubSpot with the integration's shared token.
Export result
When the export finishes, review the export report. It may separate created records, updated records, existing records, duplicates, and validation errors.
If a specific record fails, correct its data and export it again. An individual error does not necessarily mean every record in the batch failed.
Record deletion
Contact and Company export and synchronization do not delete those records from HubSpot. Deleting a contact or company in Enginy also does not revoke the app or automatically delete the remote record.