How are duplicates prevented in the integration?
How does the HubSpot–Severa integration prevent duplicate records from being created? Which fields does the integration use to find an existing matching record for customers, contacts, and deals?
Duplicate records are prevented in the integration using two core principles:
- First, the integration searches for an existing matching record using comparison fields (such as Business ID, domain, name, or email address).
- When a matching record is found, the records are linked using technical ID identifiers between the systems. This ensures that the same records remain correctly linked even if, for example, the name or email address changes later.
Below is an overview of how the integration searches for an existing matching record for different objects. Please note that the sync direction can affect which comparison fields are used.
Severa Customer – HubSpot Company
The integration searches for a matching customer/company as follows:
HubSpot → Severa
- Based on Business ID
- If not found, based on company name
Severa → HubSpot
- Based on Business ID
- If not found, based on website address / domain
- If not found, based on company name
Contact
The integration searches for a matching contacts as follows:
- Email address
- If not found, based Name + phone number combination
Severa Sales case / Project – HubSpot Deal
For deals, the integration searches for a matching record:
- Based on the deal name, within the customer’s existing sales cases and projects
Practical tip
To further minimize the risk of duplicates, make sure that:
-
- Companies have a domain and Business ID filled in and correctly set in both systems
- Contacts have an email address filled in