HubSpot Object Merge Handling
HubSpot allows administrators to merge two records (for example, two Companies that represent the same organization) so that data is consolidated under a single surviving record. Magentrix detects these merge events during the next Scheduled Job run and updates its own records accordingly.
Supported Object Types
- HubSpot Companies (Magentrix Accounts).
- HubSpot Contacts (Magentrix Contacts).
HubSpot Deal merges are not handled by the integration.
How a Merge Is Detected
During each scheduled sync, Magentrix examines the HubSpot calculated-merge properties on Companies and Contacts to identify records that were merged in HubSpot since the last sync. The IDs of merged-out records and the surviving record are read directly from HubSpot.
What Happens During a Merge
- The surviving record is identified - The HubSpot record that remains after the merge becomes the surviving record in Magentrix. Its property values reflect the post-merge state in HubSpot.
- Lookup references are updated - Magentrix records that referenced the secondary (merged-out) HubSpot record are updated to point to the surviving record. For example, Contacts that were linked to the secondary Company are reassigned to the surviving Company.
- The secondary record is removed - The Magentrix copy of the secondary HubSpot record is deleted so that only the surviving record remains.
Audit and Troubleshooting
Each step of the merge (create, edit, and delete operations on Magentrix records) is logged. If part of a merge fails - for example, because a foreign-key constraint or validation rule prevents an update - the failure is recorded as an error in the system event log so an administrator can review and resolve it. Look for entries that reference the merge processing class when investigating incomplete merges.
<< Activating and Mapping HubSpot Entities | Troubleshooting >>