HubSpot
Salesforce
Pipedrive
Intercom
Mailchimp
A small group per manual pass
The standard merge experience is practical for occasional review, not tens of thousands of duplicate records.
SalesforceIntegrations
Salesforce Deduplication, merge whole groups in bulk, safely, leads included.
Salesforce duplicate rules can flag or block likely matches, but the backlog still depends on manual review, and leads are not matched against contacts. Insycle merges entire groups with rules for which record survives and which data is kept, previews the outcome before production, then keeps the process running on a schedule or from Salesforce Flow.
- Salesforce AppExchange Partner
- Native Apex merge
- Preview before production
- Sandbox-friendly
Manual review vs. whole group
Salesforce review
One manual pass
Jordan Leejlee@acme.com · Contact
Jordan A. Leejordan@acme.com · Contact
Choose values and merge
Insycle
One complete group
Jordan LeeMaster
Synced ID · active owner+ 6 related recordsContacts and leads reviewed together
Merge the group once
Seven records · one controlled decisionPreview only
Flagging is not resolving
Salesforce protects records at entry. Insycle resolves the duplicate population already inside the org.
Find complete groups across contacts, accounts, leads, opportunities, and supported custom objects; apply the same master and retention policy every time; prove the result in a preview; and keep that policy running as imports, integrations, and people create new records. Teams that need to bulk merge Salesforce records work through whole duplicate groups at once, not pair by pair.
Built for review, not a six-figure backlog
Where Salesforce duplicate management stops.
Salesforce matching and duplicate rules are valuable controls. The friction begins when a large existing population must be resolved consistently across objects and kept clean after the project ends.
Rules flag or block
Duplicate rules can alert, report, or stop entry. They do not resolve the existing backlog automatically, and can interfere with cleanup merges.
Leads and contacts stay separate
The same person can exist once as a lead and once as a contact without native cross-object duplicate detection.
Duplicate emails are allowed
Two contacts can share an email address, so even obvious collisions still require a governed matching and merge process.
Reports show only part of the work
Pair-oriented duplicate reporting can make a large, connected population hard to size and resolve as complete groups.
Cleanup is not a standing process
Without scheduled or event-triggered execution, the next import and integration cycle begins rebuilding the backlog.
Whole groups, your rules
Choose the record that survives, and the data that survives with it.
Match on any standard or custom field: fuzzy account names, phone across phone fields, normalized company suffixes, external IDs, or multiple fields together. Add guard conditions that prevent unsafe merges as deliberately as the matching rules find them.
Make the master decision once
Evaluate business priorities from top to bottom until one record uniquely wins. This example keeps the record that participates in the HubSpot-Salesforce sync before considering other qualities.
- 1Synced master flag existsPreserve the record aligned across both CRMs
- 2Active territory owner existsKeep the record already in the working motion
- 3Most Salesforce activityProtect the richest engagement context
- 4Earliest create dateUse record age as the final tiebreaker
Retain data field by field
Keep the master’s values, fill empty fields from the most recently updated duplicate, and add explicit rules only where the business needs a different outcome.
- TerritoryKeep from the selected master
- Account ownerKeep the active owner
- Topics of interestCombine multi-select picklist values
- Lead sourceKeep the earliest known source
- Blank fieldsFill from the freshest duplicate by default
- Everything elseCapture in the Activity Tracker report
Guard conditions stop merges, too. Exclude groups when Salesforce IDs conflict, skip groups beyond the configured size threshold, or route strategic accounts to Manual mode. Bulk mode is for a trusted policy; Manual mode is for the exceptions that deserve hands-on review.
The shortlist questions, answered first
The mechanics your Salesforce admin will ask about.
Native merge for contacts, leads, and accounts
Insycle uses Salesforce’s Apex APIs through the AppExchange app. Salesforce governs how activities, opportunities, attachments, relationships, triggers, flows, and other automation behave.
Synthetic merge where Salesforce has none
For opportunities and supported custom objects, Insycle uses CRUD APIs and schema metadata to re-parent related records while preserving the selected master Record ID. Test one or two groups first.
Contacts to Multiple Accounts conflicts
When duplicate contacts share an indirect account relationship, Salesforce blocks the merge. Insycle removes the redundant relationship from the record being merged and preserves it on the master.
API usage stays visible
See the per-connection quota, run controlled batches, and adjust processing caps rather than discovering API pressure after the operation starts.
Sandbox first, if you want
Connect a sandbox, prove the complete workflow, document any validation-rule or duplicate-rule interference, then move the same reviewed policy to production.
Contacts to Multiple Accounts · merge guard
Salesforce merge errorThese contacts have the same related account.
Detect overlapRemove redundant relationshipPreserve on master
Merge completed without manual AccountContactRelation cleanupRelationship retained once
One person across two Salesforce objects
Deduplicate leads against contacts, and merge them in one step.
Native duplicate management treats leads and contacts separately. Insycle searches the combined population: select Contacts, enable Include Leads, and apply the same matching, master-selection, retention, and preview process to groups containing either object type.
When a duplicate group contains both a lead and a contact, the lead merges into the contact using Salesforce’s convert API. Edge-case policy stays explicit: a group holding conflicting sync identifiers can be skipped and flagged for manual review instead of forced through automation.
Combined lead + contact poolContact survivesConvert APISkip-and-flag policy
Merge Duplicates · Contacts
Record typeContacts Include Leads
Jordan LeeContact · active opportunityMaster
Jordan A. LeeLead · same email + phoneMerge
LeadSalesforce convert APIContact
Preview, receipt, and a documented way back
Merge with the entire result in view.
Every bulk merge begins as a simulation. Inspect the chosen master, every duplicate, and the Master (After) row before production changes. Then apply the same policy gradually with exclusions, group-size guardrails, chunked rollout, and Manual mode for sensitive groups.
- Simulate the complete merge. Preview produces a CSV with the group, Master, Duplicate, Master (After), selected fields, and any errors.
- Exclude false positives. Keep a group out of Bulk-mode analysis across templates, then remove the exclusion if the decision changes.
- Roll out in controlled chunks. Test a few groups, verify the Salesforce result, then increase volume.
- Keep the operation receipt. Activity Tracker retains the downloadable report and Run ID for the executed merge.
Salesforce provides a restore-and-repair path, not a time machine. Restore the merged-away records from the Recycle Bin, then repair relationships that moved to the master. Field values copied into the master remain and are not removed automatically.
Salesforce merge preview.csv
Groups evaluated7,248
Ready to merge7,102
Skipped or error146
| Status | Type | Record ID | Owner |
|---|---|---|---|
| Master | Contact | 0038X... | M. Lee |
| Duplicate | Lead | 00Q5A... | Queue |
| Master (After) | Contact | 0038X... | M. Lee |
Preview complete · no Salesforce changes made
Keep it clean after the project
From cleanup project to standing process, inside Salesforce Flow.
Run scheduled sweeps from hourly to monthly, or trigger an approved Insycle Recipe from a record-triggered Salesforce Flow. A record is created or changed, the Recipe runs in the asynchronous path, and the Flow continues with one reviewed record.
Build the template preview-first, save the Recipe in Update mode, use strict Flow entry conditions, and test with one record before scaling. For CSVs, Salesforce Import matches against existing leads, contacts, and accounts before the file lands.
Scheduled sweepsAsynchronous Flow actionStrict entry conditionsImport prevention
Salesforce Flow · Contact created
Record-triggered FlowContact created or updated
Insycle, Run RecipeSalesforce contact deduplicationAsync path
Flow continuesAssociate · assign · notify
Salesforce + HubSpot
Deduplicate both, without breaking the sync.
A merge on one side can disrupt pairing or let the connector recreate an unwanted record. Start by hardening the sync settings, deduplicate Salesforce first, stamp the chosen master, then deduplicate the corresponding HubSpot records with aligned master-selection logic.
The full settings, fields, sequence, and cleanup steps live on the shared integration page. This is a coordinated two-system process, not a claim that both CRMs merge in one pass.
Deduplicate HubSpot and Salesforce while keeping the sync active
1. Deduplicate SalesforceSelect and stamp the authoritative master
2. Let the identifier syncCarry the master decision across the connector
3. Deduplicate HubSpotAlign master selection to the Salesforce decision
Switching from a Salesforce-only point solution?
One platform, both CRMs, priced on records.
For teams evaluating an alternative to DemandTools, RingLead, Cloudingo, or a collection of admin utilities, compare the operating model rather than a feature checklist that will age.
Use the tools the job requires
Deduplication, import, standardization, association, assignment, and audit share one platform without forcing every team into the same module bundle.
Work both sides of the stack
Apply one operating model across Salesforce and HubSpot, including the sequence required to keep their connector healthy.
Price the data, not collaboration
Record-based pricing with unlimited users and operations lets admins, RevOps, and business owners work from one policy.
The questions Salesforce admins ask
Straight answers about Salesforce deduplication.
How many records can Salesforce merge at once?
The standard Salesforce interface handles a small group per manual pass, with details that vary by object and should be verified against current documentation at launch. Insycle resolves complete duplicate groups in bulk and can repeat the approved process on a schedule or from Salesforce Flow.
Can I deduplicate Salesforce leads against contacts?
Yes, with Insycle. Select Contacts, enable Include Leads, and search the combined lead-and-contact population with the same matching rules. When a group contains both object types, the duplicate lead merges into the surviving contact using Salesforce’s convert API.
How do I fix “Can’t merge contacts. These contacts have the same related account”?
The error means duplicate contacts share an indirect AccountContactRelation under Contacts to Multiple Accounts. Insycle detects the overlap, removes the redundant relationship from the record being merged, preserves it on the master, and completes the merge without manual relationship cleanup.
Will merging trigger my Salesforce flows, triggers, and validation rules?
For contacts, leads, and accounts, Insycle uses Salesforce’s native Apex merge behavior, so downstream automation behaves as it does for a Salesforce merge. Validation and duplicate rules can still interfere; test the operation in Preview and on a small sandbox or production sample before scaling.
Can I undo a Salesforce merge?
Salesforce lets you restore merged-away records from the Recycle Bin, but this is not a one-click unmerge. Restore the records, repair relationships that moved to the master, and remember that field values copied into the master are not removed automatically.
Salesforce native vs. Insycle
Keep Salesforce’s controls, and add a governed process for the backlog.
| Capability | Salesforce native | Insycle |
|---|---|---|
| Finding | Matching and duplicate rules flag, report, alert, or block | Deterministic matching on any standard or custom field, including fuzzy, multi-field, external IDs, related fields, and guard conditions |
| Fixing the backlog | Small groups handled through manual review | Complete duplicate groups processed in bulk |
| Leads vs. contacts | Separate object populations | Combined-pool search and lead-to-contact merge |
| Opportunities and custom objects | No standard native merge path | Synthetic merge with the selected master Record ID preserved |
| Contacts to Multiple Accounts | Overlapping indirect relationships can block the merge | Redundant AccountContactRelation resolved during the merge |
| Master and retention | Choose records and values during each manual pass | Reusable master waterfall and field-level retention policy |
| Dry run | No complete bulk simulation | Full merge previewed to CSV; sandbox supported |
| Restore | Recycle Bin restores merged-away records | Preview-first workflow, audit report, and documented restore-and-repair procedure |
| Automation | Duplicate controls at entry; no standing native bulk-resolution policy | Schedules and Salesforce Flow-triggered Recipes |
| HubSpot sync | Outside the native duplicate-management workflow | Documented Salesforce-first process designed to keep the connector aligned |
Prove the policy before the volume
Preview the master. Inspect the after-state. Trust the bulk run.
Use the first preview and small Update sample to prove how Salesforce IDs, relationships, picklists, triggers, and downstream automation behave before expanding the operation.
“We used Insycle to clean up data in standard and custom objects in Salesforce. It is helpful for the initial deduplication, as well the ongoing deduplication.”
Laura N. · Salesforce Business Analyst · Mid-Market
G2 reviewStart with the duplicates already in Salesforce
Preview your first bulk merge on real records.
Connect a sandbox or production org, inspect complete duplicate groups, and see the selected master and after-state before choosing Update. Build one reliable record from the duplicates already in Salesforce.
Keep Salesforce clean
Duplicates return because the pipes keep flowing.
See how teams automate Salesforce cleanup, and then hold records to declared standards while Observability shows whether the data stays aligned.
Explore the complete Salesforce data system See how teams make this the last cleanup