Using the Salesforce inclusion list, I have synced a list of 923 contacts over to Salesforce from HubSpot.
It seems that for every contact, Salesforce has created three additional duplicate contacts.
- This duplication only happened for two specific sales reps and their owned accounts. All other accounts owned by other reps only have one contact in Salesforce
- There is only one matching contact in HubSpot for all
- One contact is created by the HubSPot Service account, while the other three are created by the sales rep who owns the account
- When I tested deleting the sales “created” contacts, HubSpot and Salesforce both totally deleted the original Service Account created contact
- The service account contacts were created around 1:01 or 1:02 and the rep created duplicates were created around 1:07/1:08
Is there something that would have caused this to happen on either the Salesforce or HubSpot side?
I would recommend checking a few things:
1) Matching Rules: HubSpot uses email as a unique identifier. Salesforce allows multiple contacts (or leads) with the same email. If they used different emails, this could have happened. You may need to look at your matching rules. Salesforce duplicate rules need to be set up to block duplicates during syncing.
2) Permissions: HubSpot may not be able to see the users on the other side and create a new one because of integration user permissions. They usually need to be very extensive to avoid issues like this.
3) Automatically Create and Associate Companies: if you have this enabled, it can create new contacts to associate to a company (I am not sure this would be your issue based on your description, but we run into it so I’m giving you the list!)
I would also recommend ensuring you are using the latest version of the integration that includes alternate ways to dedupe instead of email built in- might be a better fit for you to use something other than email:
1) Matching Rules: The emails matched exactly, and our Salesforce has de-duplication rules in place, where is the email is the same, it will not create a duplicate
2) Permissions: The sync rules and integration is setup as two way and HubSpot can see Salesforce contacts and accounts
3) Automatically Create and Associate Companies: Not applicable
I notice my account does not have the de-dupe option on the hubspot sync side. where can I update to get this?
Re: permissions- does the integration user have full admin rights? It’s not just about Contacts and Accounts. We’ve had very specific, niche things HubSpot could not see cause issues. Based on your answer to the first, I do think this is likely an issue here.
To have that additional parameter on the HubSpot side, you need to be using the most recent version of the HubSpot/ Salesforce sync. It’s not in the legacy version.
I realized I should have specified- the new version of the HS/SFDC integration hasn’t rolled out to all the objects yet, and Contacts will be last. However, you’ll want to monitor it and be on it because it has that available on objects and that will help you avoid this!
Good that you caught this early! So, what’s likely happening here is a conflict between the HubSpot service account sync and your reps manually creating contacts within the same window. That 5 to 6 minute gap between 1:01 and 1:07 is kind of the tell.
The issue probably occurs due to these reps creating contacts manually just after the sync took place, and Salesforce considered them new contacts rather than duplicates of the HubSpot ones.
You need to double-check your duplicate detection settings on Salesforce, if email isn’t set as the unique identifier it just won’t catch contacts created by different users, even if it’s literally the same person.
If you leave this too long, every future sync is just going to keep stacking duplicates and your contact data will get messy across both platforms.
Hello - It isn’t as simple as that, though I wish it was. Each of the contacts had three duplicates created by the “rep” with over 100 duplicates total. They were not manually created. Salesforce duplicate rules were in place, with email being the identifier.