HubSpot
Salesforce
Pipedrive
Intercom
Mailchimp
Pairs, not groups
Three records for one person appear as several separate pairs, creating more review and more merges.
HubSpotIntegrations
HubSpot Deduplication, merge duplicates in bulk, safely, and keep them from coming back.
Go beyond one-by-one review: match on any fields with fuzzy logic, merge whole groups instead of pairs, control which record and which data survive, and preview every merge before it is real. Then automate deduplication from the HubSpot Workflows you already run.
HubSpot App Marketplace PartnerNative integration and HubSpot SSOPreview before mergingKeeps the Salesforce sync active
Pairs vs. groups
HManage Duplicates
Pair 1 of 3
Alex Morgan
alex@acme.com
Alex Morgan
alex.morgan@gmail.com
Review this pair
IInsycle
1 complete group
Alex Morgan
MasterWork email · active owner
+ 5 related records
All reviewed together
Merge the group once
Six records · one controlled decisionPreview only
Native detection, scale-ready execution
HubSpot helps you find duplicates for review. Insycle turns that review into a controlled, repeatable bulk process.
See the complete duplicate group, apply the same master and retention logic every time, simulate the result, and keep the process running as forms, imports, integrations, and people add new records. Teams that need to bulk merge HubSpot records handle whole duplicate groups at once, not pair by pair.
Built for review, not volume
Where HubSpot’s Manage Duplicates stops.
HubSpot has useful native duplicate detection. The friction begins when a real portal has thousands of suggestions, groups larger than two, and business-specific rules for what should survive.
One at a time
Accept, reject, repeat. That works for occasional review, not a backlog numbering in the thousands.
A daily display cap
At real volume, you see today’s slice rather than the complete duplicate population.
Email drives identity
The same person submitting a personal address can create another contact instead of updating the existing one.
Limited matching flexibility
No configurable fuzzy names, name plus phone, name plus company, or domain-variant company matching.
Limited outcome control
No reusable rules for master selection or field-by-field decisions about which values survive.
Whole groups, your rules
Merge the whole group, with rules for who survives and what’s kept.
Use fuzzy names, name plus phone, name plus company, and domain matching that can ignore subdomains or TLD variations. Insycle assembles every related record into one group, then applies reusable logic to the entire merge.
Choose the master at scale
Evaluate your priorities in order until one record wins. Use manual review for strategic accounts and bulk execution when the template is proven.
- 1
Prefer an active owner
Avoid preserving abandoned ownership
- 2
Prefer a work email
Keep the business identity primary
- 3
Prefer the most engagement
Protect the strongest activity history
- 4
Prefer the oldest record
Use create date as a final tiebreaker
Control what the master keeps
Apply field-retention logic instead of accepting a single default for every property.
- Primary emailMaster’s email remains primary
- Other email addressesPreserve as Additional Emails
- Lifecycle stageKeep the most advanced value
- First conversionKeep the earliest date
- Notes and historyCarry to the master
- Custom propertiesApply field-specific logic
HubSpot-specific behavior, made explicit. Native merges carry associations, activities, notes, emails, tasks, and attachments to the master. Unique custom properties can block a merge; Insycle reports the error for review. For native-limit and unsupported-object edge cases, Synthetic merge preserves the selected master Record ID.
No native unmerge
“HubSpot has no unmerge”, here’s how you merge anyway.
HubSpot cannot natively undo a merge. The answer is to make the decision inspectable before it runs, protect exceptions, introduce volume gradually, and retain a complete record of every executed group.
- Simulate the entire merge. Preview the master, every before value, and the after state before the portal changes.
- Exclude false positives permanently. Mark records “not duplicates” once, and remove that exclusion later if circumstances change.
- Use operational guardrails. Skip oversized groups, roll out in chunks, and hand-review the accounts that warrant it.
- Keep a receipt. Every run retains a downloadable before-and-after report in the Activity Tracker.
A documented partial-restore procedure, not an unmerge. If a merge produces the wrong result, rebuild records from the report’s before values with Magical Import, clear conflicting Additional Emails or domains first, and repair associations. The records are recreated; their prior IDs, associations, and history are not automatically restored.
HubSpot merge preview.csv
Groups evaluated
3,842
Ready to merge
3,761
Skipped or error
81
| Row | Record ID | Owner | |
|---|---|---|---|
| Master | 104928 | alex@acme.com | M. Lee |
| Before | 117204 | alex@gmail.com | , |
| After | 104928 | Primary + additional | M. Lee |
Preview complete · no HubSpot changes made
HubSpot-specific operations
Deduplication that speaks fluent HubSpot.
These are not generic matching examples. Each workflow starts with a behavior or data structure specific to a HubSpot portal.
01
Start from HubSpot’s duplicate list
Export Manage Duplicates’ detected pairs, upload the CSV to Insycle, and merge them in one controlled operation with your master and retention rules.
See the duplicate-export workflow02
Find where duplicates originate
Bring Original Source fields into the review, group duplicate patterns by source, isolate a form, integration, or recurring import, and fix the pipe creating them.
Trace duplicates with Original Source03
Clean up auto-created companies
Merge domain variations into the main company and purge empty shells left by HubSpot’s automatic company creation behavior.
See bulk cleanup controls04
Tidy Additional Emails
Remove accumulated secondary addresses in bulk when your policy requires it, including the cleanup needed before a partial restore.
See the secondary-email workflowStanding process
From cleanup project to continuous deduplication, inside your Workflows.
Run hourly-to-monthly schedules for standing sweeps, or place an Insycle recipe directly inside a HubSpot Workflow: a form creates or updates a contact, the dedupe recipe runs, and the rep receives one workable record.
Use the modified-by-Insycle bypass pattern to prevent unwanted re-enrollment loops. For CSVs, Magical Import matches against existing HubSpot records before the file lands, so the trade-show list does not become the next duplicate backlog.
Scheduled sweepsWorkflow-triggered recipesRe-enrollment hygieneImport prevention
HubSpot Workflow
H
Form submitted
Contact created or updated
INative action
Run Insycle recipe
HubSpot contact deduplication
One contact continues
Classify · associate · assign
The hard-dollar case
Duplicates and junk cost real money in HubSpot.
When HubSpot billing is tied to marketing-contact volume, duplicate and unusable contacts are not only untidy, they can push the database toward a higher tier. Deduplicate so one person equals one record, then identify the records that should be deleted, marked non-marketing, unassigned, or held for review.
The operational cost matters too: duplicate people can enter the same automation twice, receive competing messages, or trigger a promotion after they have already converted.
Marketing-contact review
- Duplicate contactsMerge
- No email addressReview or purge
- Hard bouncedNon-marketing
- Years inactiveSuppress or purge
Manage the count before renewalNo invented savings claim
HubSpot + Salesforce
Running HubSpot and Salesforce? Deduplicate both, without breaking the sync.
Merging on one side without accounting for the connector can recreate records or undo the intended master decision. The sync-safe process starts in Salesforce, then deduplicates the corresponding HubSpot records with the settings and identifiers that preserve the relationship.
Use an inclusion-list pattern to stop duplicates and junk from syncing from HubSpot into Salesforce in the first place. The result is a coordinated sequence, not a claim that both CRMs merge in one pass.
S
1. Deduplicate Salesforce
Choose the authoritative account or contact
2. Preserve the sync relationship
Carry forward the shared identifiers
H
3. Deduplicate HubSpot
Keep the connector aligned with the chosen master
The questions every HubSpot admin asks
Straight answers about HubSpot deduplication.
Why do HubSpot and Insycle show different duplicate counts?
They use different detection methods by design. HubSpot suggests pairs using an evolving AI-based process; Insycle applies the deterministic matching criteria you configure. The totals will not match exactly. You can import HubSpot’s duplicate export when you want to use its suggestions, or use Insycle rules when you need reproducible results and automation.
What happens to my HubSpot data during a merge?
In a native HubSpot merge, associations, activities, notes, emails, tasks, and attachments carry to the master record. The master’s email remains primary, and non-master email addresses can be preserved as Additional Emails. Insycle adds reusable master-selection and field-retention logic around that native behavior.
Will merging contacts trigger my HubSpot Workflows?
Workflow enrollment and re-enrollment depend on the triggers configured in your portal. Review those triggers before a bulk run and use the modified-by-Insycle bypass pattern when needed to prevent unwanted re-enrollment loops.
Can I undo a merge in HubSpot?
No. HubSpot does not provide a native unmerge. Insycle reduces the risk with a complete preview and run report, and documents a partial-restore procedure that recreates records from before-values and then repairs associations. It is a recovery process, not an undo button.
Manage Duplicates vs. Insycle
Keep HubSpot’s native experience, and add the control required at scale.
| Capability | HubSpot Manage Duplicates | Insycle |
|---|---|---|
| Detection | AI-suggested contact and company pairs | Deterministic rules on any fields, including fuzzy, multi-field, and domain-variant matching |
| Review unit | Pairs, reviewed one at a time with a daily display cap | Complete duplicate groups, reviewed and processed together |
| Master record | Choose within each pair | Reusable selection rules applied at scale |
| Data retention | HubSpot’s native merge defaults | Per-field retention logic wrapped around native merge semantics |
| Objects | Contacts and companies | Contacts, companies, deals, tickets, and supported custom objects |
| Dry run | No complete bulk simulation | Full merge previewed to CSV before records change |
| Undo | No native unmerge | Preview-first process, audit trail, and documented partial restore |
| Automation | No standing, rules-based bulk deduplication process | Schedules and HubSpot Workflow-triggered recipes |
| Salesforce sync | Outside the native duplicate-review workflow | Documented cross-CRM sequence designed to keep the sync active |
| Cost control | Duplicate marketing contacts continue to count | Dedupe plus targeted cleanup helps manage the marketing-contact population |
Trusted in real HubSpot portals
Preview the decision. Prove the result. Trust the data again.
“The ability to scan and surface data quality issues gives us immediate visibility into where problems exist and how widespread they are.”
Ronak S. · Associate Marketing Automation, Enterprise
“What we especially appreciate is the flexibility to build in logic based on custom fields and set hierarchical rules that determine which records take priority during merges.”
Kyla S. · Head of Marketing Operations · Enterprise
G2 reviewStart with the duplicates already in HubSpot
Preview your first bulk merge on real records.
Connect through the native HubSpot app and SSO, inspect the complete groups, and see the proposed result before choosing to merge. Create one reliable customer view from the duplicates already in your portal. Free trial, no credit card.
Keep HubSpot clean
Duplicates return because the pipes keep flowing.
See how teams automate HubSpot cleanup and prove the database is staying aligned as forms, imports, integrations, and people change it.
See the complete HubSpot data system