HubSpot
Salesforce
Pipedrive
Intercom
Mailchimp
Lead → User
Native path exists
IntercomIntegrations
Intercom Deduplication, merge duplicate users, leads, and companies, in bulk
Intercom can merge a lead into a user, and that’s where merging ends. Insycle finds duplicates on any field, merges whole groups with rules for which record survives, handles every attached conversation explicitly, and shows you the result before anything changes.
What happens to conversation history?Works inside Intercom, check from the inboxPreview before anything changesFree trial, no credit card
One customer · two incomplete records
AMAlex Morgan
User · alex@northstar.io
Live conversation
“Can you see my last ticket?”
Company
Northstar
AMAlex Morgan
User · alex.m@gmail.com
3 closed conversations
History lives over here
Tags
Enterprise · VIP
One controlled merge
Rules + preview + documented history handling
AM
Alex Morgan · master
One record for the teammate, inbox, and every message
- Live thread attached
- Closed history searchable
- Company + tags retained
Complete context, handled explicitlyPreview first
One customer should look like one customer
Every support experience is only as complete as the customer record behind it.
When one person exists twice, conversation history, company context, tags, and events split with them. Insycle brings those records back together, with exact, documented handling for everything attached.
The native limit
For the duplicates that matter most, Intercom has no merge.
Intercom can merge a lead into a user when they are the same person. That’s useful, and the end of the native path. Two duplicate users? There is no user-to-user merge in the UI or in bulk. Two duplicate companies? No company merge either.
User ↔ User
No native merge
Company ↔ Company
No native merge
The cost appears mid-conversation
Split records mean split context
Exactly when the customer needs an answer.
The teammate sees half the history.
The customer asks about their last ticket, but it lives on the duplicate. They repeat themselves to a company that should already know them.
Fin reads the record it can see.
A split person means split customer context. Answers built from one record cannot use history held on the other.
Series and outbound can double-send.
The same human appears twice in the audience, receives the message twice, and inflates the records your outreach reads.
Reporting counts phantoms.
User, company, engagement, and support metrics drift when one customer is counted as two.
Find the complete person
Match on any field, and across leads and users at once.
Use any standard or custom Intercom attribute: email, external ID, phone, name + company, or a combination of your own. Ignore formatting differences and use similar matching for near-misses.
When the same person exists once as a lead and again as a user, select Include Leads on a users template. Insycle searches the combined pool, then runs lead-to-user merges through Intercom’s own merge API.
Supported record types: users, leads, and companies. Whole duplicate groups appear together, expandable, with the columns you choose.
Intercom people · Find Duplicates
Record type
Users
Include Leads
Match rules
Email OR External ID
Ignore case and formatting
Alex Morgan
Group 02413 records · users + leads
- Useralex@northstar.ioID 9817
- Useralex.m@gmail.comID 7344
- Leadalex@northstar.coID 4139
One combined search poolWhole group visible
Merge them right
Your rules decide who survives
And exactly what happens to everything attached.
Choose the master consistently
The master is the record that remains. Apply priorities in order across every duplicate group, then use field-level rules for the data it keeps.
- 1Most recently activeKeep the record the team is working from
- 2Most conversationsPrefer the record with richer context
- 3First createdUse age as the final tiebreaker
For fields without a special rule, Insycle keeps the master’s value and fills blanks from the most recently updated duplicate. Run in Bulk for the backlog or Manual for high-touch accounts.
Use the right merge method
- Lead ↔ UserIntercom merge API
Intercom’s own supported merge path
- User ↔ UserInsycle Synthetic merge
Controlled reassignment and preservation
- Company ↔ CompanyInsycle Synthetic merge
Users, leads, tags, and fields consolidated
Open conversations
Detached from duplicates and reattached to the master
ReattachedClosed conversations
Preserved as searchable notes, one per conversation
Kept closedTickets
Collected from duplicates and converted into notes
PreservedTags + companies
Reassigned from duplicate users to the master
ReassignedNotes + events
Copied from duplicate users to the master
CopiedCompany members
Leads, users, tags, and chosen field data move to the master company
ConsolidatedWhy closed conversations become notes: Intercom cannot transfer a closed conversation without reopening it. Insycle preserves each one as a searchable note on the master, the same pattern Intercom uses for native lead-to-user merges, so history remains available without reopening resolved conversations.
Dedupe where the pain appears
Check for duplicates without leaving the conversation.
Install the Insycle app in Intercom and a widget appears in the conversation sidebar. Mid-chat, a teammate clicks Check for Duplicates. Insycle compares the person in the open conversation against the workspace and shows whether another record exists.
From there, the teammate can route the record to the right merge template. Duplicate detection becomes a support reflex at the moment context matters, not a separate project someone remembers later.
Inbox · Alex Morgan
Conversation
Can you see the ticket I opened last week?
Let me check your customer record.
Reply…
IInsycle Data Management
Customer record
Alex Morgan
alex@northstar.io
Check for Duplicates
1 possible duplicate
Open in merge template →
Safety you can inspect
See the merge on paper before Intercom changes.
Preview the full outcome.
Review every duplicate, chosen master, and retained value in a CSV.
Inspect conversation handling.
Include open, closed, ticket, tag, company, and other context in the review layout.
Exclude look-alikes permanently.
Mark records that should remain separate so they stay out of future analyses.
Start small.
Limit duplicate-group size and test a first batch in Intercom before widening the run.
Keep the receipt.
Every run has an Activity Tracker report and an email summary.
There is no unmerge.
Preview first, keep the before-values in the report, and increase the scope only after you verify the result.
Intercom merge preview.csv
184
Groups found
172
Ready
12
Excluded
| Status | Record | Open | Closed | Tickets |
|---|---|---|---|---|
| Master | Alex · 9817 | 1 attached | , | , |
| Duplicate | Alex · 7344 | 2 → master | 3 → notes | 1 → note |
| Master (After) | Alex · 9817 | 3 attached | 3 searchable notes | 1 note |
Preview complete · no Intercom changes made
Keep it clean, and mind the pipes
Put proven rules on a schedule, then stop duplicates from traveling.
Save the configuration you tested and run it hourly, daily, weekly, or monthly. New duplicates from signups and imports are swept on your cadence, with a report delivered to the team. Start schedules in Preview mode if you want review without updates.
Intercom rarely lives alone. If it syncs with HubSpot or Salesforce, deduplicate Intercom before or alongside the sync so split identities do not cross systems. One Insycle account can connect the stack, with each CRM handled deliberately.
HourlyDailyWeeklyMonthlyPreview mode
Intercom duplicate sweep
Every day · 6:00 AM
PreviewEmail report + Activity Tracker
Review
AuditHubSpot or Salesforce sync
Connected stack
Clean inputThe questions Intercom teams ask
Straight answers about Intercom deduplication.
Can you merge two users in Intercom?
Not natively. Intercom supports lead-to-user merging, but it does not provide a user-to-user or company merge. Insycle can merge duplicate users and companies in whole groups with master and retention rules, after a full preview.
What happens to conversation history when you merge?
Open conversations detach from duplicate users and reattach to the master. Closed conversations stay closed and are preserved as searchable notes on the master, one note per conversation. Tickets become notes; tags and company links reassign; notes and events copy to the master.
Can I find the same person across leads and users?
Yes. Select Users and enable Include Leads. Insycle searches the combined pool, groups matching lead and user records, and uses Intercom’s own merge API for lead-to-user merges.
Can I undo an Intercom merge?
No. There is no unmerge. Preview Mode shows the proposed master and retained values before anything changes, and the run report keeps the before-values for review. Start with a small batch and verify it in Intercom before scaling.
We sync Intercom with HubSpot or Salesforce, where should we deduplicate first?
Deduplicate Intercom before or alongside the sync so duplicate identities do not travel to the CRM. Insycle can connect the systems in the same account, while letting you review and run each database as a deliberate step.
Intercom native vs. Insycle
Keep Intercom focused on conversations
And add the data controls around them.
| Capability | Intercom native | Insycle |
|---|---|---|
| Lead → user merge | Yes, one at a time | Yes, through Intercom’s merge API, in bulk |
| User ↔ user merge | Doesn’t exist | Whole groups with your rules |
| Company merge | Doesn’t exist | Whole groups with your rules |
| Finding duplicates | Manual searching | Any field, similar matching, and Include Leads |
| Conversation history | No user-to-user merge path | Open reattached; closed preserved as searchable notes |
| Which record survives | Not available for user or company merges | Ordered master rules applied at scale |
| Dry run | No bulk merge simulation | Full merge simulated to CSV |
| Inside the inbox | No duplicate-check workflow | Insycle app checks from the conversation sidebar |
| Ongoing process | Manual | Scheduled hourly to monthly, with reports |
Built for support operations
Spend minutes maintaining Intercom, not hours rebuilding context.
“The platform includes well-designed setup templates that are easily customizable and can be automated for ongoing maintenance. We use it weekly to maintain data hygiene.”
Josh M. · Founder/CEO, Mid-Market
Start with real Intercom records
See your duplicate users in minutes.
Connect Intercom, inspect the complete groups, and preview your first merge on paper, including conversation handling, before anything changes.
Keep the backlog from rebuilding
Merged the duplicates once already?
See how teams automate routine CRM and customer-data cleanup as signups, imports, and integrations keep adding records.
See how teams automate data management