HubSpot deduplication that shows every duplicate contact before it merges

The native tool compares properties. Email address, first and last name, phone, zip, IP country, company name. Two records that share one of those strongly enough get proposed as a pair, and you review them field by field before they merge. It is a good tool for the duplicates it was built for: the same person entered twice, in the same way, by two people.

It is a property match, so it stops where the properties stop agreeing. Jose Munoz at jmunoz@ridgeline.com, created by a form, and Jose Munoz at Ridgeline Partners LLC, created by a trade show import with the email column left blank, are two contacts with no shared email, a company name that differs by a suffix and no phone on either record. Nothing in the property set says they are one person. The pair is invisible to the match and stays in the portal through every pass you run.

That is the shape of most duplicate debt in a HubSpot portal. It arrived in bulk, from a file, with fields that were typed rather than validated, and it does not look duplicated to a rule that reads one field at a time.

A merge in HubSpot is not something you unwind later. The two records become one, and the losing record is no longer a place you can read the old field values from. If the merge was wrong, the argument about which value was correct is an argument nobody has the evidence for.

That is the reason the review step is worth the extra half hour. The export pass costs you one CSV download and one upload, and what it buys is a list you read before anything in the portal changes, plus a file that records what you decided. Six weeks later, when someone asks why a contact has the wrong company, the answer is in a column rather than in a memory. The merge mechanics themselves, contacts and companies two at a time, are set out on HubSpot merge contacts.

The same reasoning applies to any CRM export, which is why the general version of this page is CRM data cleansing, the Salesforce version is Salesforce deduplication, the Zoho version is Zoho CRM deduplication and the Pipedrive version is Pipedrive duplicate contacts. The pass is identical. Only the column names change. When the file is an export on its way into a new portal, the import side matters as much as the matching, and that case is covered in Salesforce to HubSpot migration, and for a lead database coming over from Marketo in Marketo to HubSpot migration.

Working on the export is the right shape when the duplicates arrived from files, when you want the matching to be fuzzy rather than rule based, and when someone has to sign off on the merge list before the portal changes. It is deliberately a manual loop, and the merges are applied by a person.

If what you want instead is a scheduled job that runs inside the portal and writes back through the API, that is a different product and you should buy one. Insycle connects to HubSpot directly and treats deduplication as one operation in a broader data operations platform, and Dedupely is the narrower app that merges duplicates in the portal on a schedule, compared on the Dedupely alternative page. We do not connect to your portal and we are not pretending otherwise. What this data cleaning tool gives you is the file, the matching and the record of the decision.