# The seven Dedupely integrations and how merging works | Dedupely

> Dedupely works with HubSpot, Salesforce, Pipedrive, Close, Nimble, Google Contacts and spreadsheets. See what you can dedupe in each and what a merge does.

- URL: https://dedupe.ly/blog/dedupely-integrations
- Section: blog
- Published: 2026-10-19
- Site index: https://dedupe.ly/llms.txt
- Any page: append `.md` to its URL for this plain-text form

---

[Blog](https://dedupe.ly/blog)
Dedupely Insights

## The seven Dedupely integrations and how merging works

By
[Gaby Salinas](https://www.linkedin.com/in/gbyslns)
Updated October 19, 2026
#
min read
TL;DR
- Seven integrations cover HubSpot, Salesforce, Pipedrive, Close, Nimble, Google Contacts and spreadsheets.
- Each merge follows the CRM's own merge behavior, including which record ID survives.
- Close and Nimble have no contact merge in their APIs, so some activity can't move.
- Several CRMs can share one account, each with its own searches, rules and history.
- Dedupely finds and merges duplicates in all seven integrations, with rules for which value wins.
Dedupely connects to six CRMs and works on spreadsheets as if they were a seventh. Finding duplicates works the same way in all of them. Merging doesn't, because every merge goes through the CRM's own API and follows its rules.
That's why the same merge can keep a record ID in one CRM and create a new one in another. Some CRMs move every activity to the surviving record, and others can't move all of it.
In this post, you'll see each Dedupely integration, which objects you can dedupe in it and what happens when you merge. You'll also see how several CRMs work together in one account, with links to the deeper guide for each one.

### What every Dedupely integration has in common

Connecting a CRM syncs whole objects into Dedupely. Syncing only reads your data, and nothing is merged, edited or deleted until you say so. After the first sync, Dedupely refreshes your data automatically and sees new records within minutes.
Matching works the same way in every integration. You build duplicate searches with a match option for each field or start from preset searches. Dedupely Intelligence covers contacts, companies and leads where your CRM has them.
~~Merges can't be undone: they happen directly in your CRM, and most CRMs can't undo them either.~~ Every merge is recorded in Merge History with the original values, and most can be undone there for 30 days. Dedupely also never matches or merges across objects, like a lead into a contact. See [how to undo a merge](https://dedupe.ly/knowledge-base/undo-a-merge).

### The seven integrations at a glance

| Integration | Objects you can dedupe | What happens when you merge |
| --- | --- | --- |
| HubSpot | Contacts, Companies, Deals, Leads, Tickets, Custom Objects | HubSpot gives the merged record a new record ID by default |
| Salesforce | Accounts, Contacts, Leads, Opportunities, Individuals, Custom Objects | The master keeps its ID; the others go to the Recycle Bin for 15 days |
| Pipedrive | People, Organizations, Deals, Leads, Products | Every unique email and phone number stays on the surviving record |
| Close | Leads, Contacts, Opportunities | Contacts are merged by Dedupely; tasks and meetings can't be moved |
| Nimble | Contacts (people and companies) | Fields are combined and tags and notes move; the duplicate's deals and tasks can't |
| Google Contacts | Contacts | The duplicate goes to Google Contacts Trash for 30 days |
| Spreadsheets | Any CSV with a header row | Merges stay in Dedupely; you download the clean file |

### What happens when you merge in each integration

#### HubSpot

Dedupely dedupes HubSpot contacts, companies, deals, leads, tickets and custom objects. Associated contacts, deals and timeline history move to the surviving record.
By default, HubSpot gives the merged record a new record ID, and both original records leave their active workflows. Portals in HubSpot's opt-in Primary ID Preservation beta keep the primary record's ID instead, and there the primary record stays in its workflows. Dedupely follows whichever behavior your portal has.
HubSpot also caps how many associations a record can hold and how often it can be merged. For those cases, you choose in Dedupely whether to ask each time, merge what fits or skip the set.
Source for HubSpot's merge behavior, as of October 2026: HubSpot Knowledge Base, [Merge records](https://knowledge.hubspot.com/records/merge-records).
Example
Some teams link HubSpot contacts to another platform by record ID, like a learning platform. A merge gives the record a new ID, so they first check with their tech team which field drives that link.
Our [HubSpot deduplication guide](https://dedupe.ly/integrations/hubspot)
covers HubSpot's own tools, and the [HubSpot Deduplication Guide](https://dedupe.ly/knowledge-base/hubspot-deduplication-guide) in the knowledge base covers the setup.

#### Salesforce

Dedupely dedupes Salesforce accounts, contacts, leads, opportunities, individuals (when your org has them on) and custom objects. The master record keeps its ID, and the other records go to the Recycle Bin, where Salesforce keeps them for 15 days.
When accounts, contacts or leads merge, opportunities, tasks, cases, notes and custom related lists are reparented to the master. Child accounts of a merged-away parent move to the surviving account, and a merge stops for accounts in the same parent–child hierarchy. Merges fire standard Salesforce events, so Apex triggers and record-triggered flows run.
Salesforce has no merge for opportunities or custom objects, so Dedupely merges them itself. It updates the surviving record and moves child records to it, but the duplicates' emails, files, notes, contact roles and product lines don't move.
A native Salesforce merge takes up to three records, while Dedupely bulk merges thousands in one action. You can also connect a Sandbox to test searches and rules first. See [Salesforce deduplication and where native tools stop](https://dedupe.ly/blog/salesforce-duplicate-management) and the [Salesforce Deduplication Guide](https://dedupe.ly/knowledge-base/salesforce-deduplication-guide).
Source for the Recycle Bin, as of October 2026: Salesforce Help, [Recycle Bin](https://help.salesforce.com/s/articleView?id=sf.home_delete.htm&language=en_US&type=5).

#### Pipedrive

Dedupely dedupes Pipedrive people, organizations, deals, leads and products. Activities, notes, deals and linked organizations move to the surviving record.
Multi-value fields are combined, so every unique email and phone number stays on the primary record. Blank fields never overwrite existing values. Archived deals and leads can't be merged.
Our post on [Pipedrive duplicates and where native merging stops](https://dedupe.ly/blog/pipedrive-duplicates)
goes deeper, along with the [Pipedrive Deduplication Guide](https://dedupe.ly/knowledge-base/pipedrive-deduplication-guide).

#### Close

Dedupely dedupes Close leads, contacts and opportunities. In Close, a lead is a company. Leads merge through Close's own merge, so the primary lead keeps the other lead's history and contacts.
Close's API has no merge for contacts, so Dedupely merges them itself. It moves the field values onto the surviving contact, moves opportunities, notes, calls and emails, then removes the duplicate. Tasks and meetings can't be moved, which is a limit of Close's API.
Opportunities carry no activity of their own, so merging them moves none. Merging leads before contacts keeps the work simpler. See [duplicate leads and contacts in Close CRM](https://dedupe.ly/blog/close-crm-duplicates)
and the [Close CRM Deduplication Guide](https://dedupe.ly/knowledge-base/close-crm-deduplication-guide).
Source for Close's API, as of October 2026: Close API docs, [Contacts](https://developer.close.com/api/resources/contacts) (no merge endpoint; leads have one).

#### Nimble

Dedupely dedupes Nimble contacts, which cover both people and companies. People and companies are separate record types, so a person never matches a company. Nimble's API has no merge, so Dedupely merges every record in a match at once.
You pick the record to keep with "Set as primary" in a manual merge, or with the primary record rule in Merge Rules. The kept record keeps its own deals and tasks. Dedupely combines multi-value fields, fills empty fields from the duplicate and moves its tags and notes.
Deals, tasks, events and message history can't be moved by outside apps, which is a Nimble limitation. If both records have items you need, move them by hand in Nimble before merging.
Nimble sends no instant updates, so new records appear on the next sync. Our post on [duplicate contacts in Nimble](https://dedupe.ly/blog/duplicate-contacts-nimble)
and the [Nimble CRM Deduplication Guide](https://dedupe.ly/knowledge-base/nimble-crm-deduplication-guide) cover the details.
Source for Nimble's API, as of October 2026: Nimble Help, [Nimble API access](https://support.nimble.com/en/articles/502755-nimble-api-access) ("MERGE contact" listed as TBD).

#### Google Contacts

Dedupely dedupes Google Contacts, one Google account per connection. Contacts under "Other contacts" aren't included.
When you merge, Dedupely moves the winning values onto the contact that stays, following your rules. It also adds that contact to the duplicate's labels, including custom labels and Starred.
Google's older built-in labels, like Friends, Family and Coworkers, aren't carried over. The kept contact keeps its own photo, so choose the contact with the photo you want as the one to keep.
The duplicate is deleted and goes to Google Contacts Trash, where you can restore it for 30 days. See [how to find and merge duplicate Google Contacts](https://dedupe.ly/blog/duplicate-google-contacts)
and the [Google Contacts Deduplication Guide](https://dedupe.ly/knowledge-base/google-contacts-deduplication-guide).
Source for Trash, as of October 2026: Google Contacts Help, [Edit or delete contacts](https://support.google.com/contacts/answer/7280886?hl=en&co=GENIE.Platform%3DDesktop).

#### Spreadsheets

Dedupely works on spreadsheets as if they were a CRM. You upload any CSV with a header row, match and merge with the same options and rules, and download the clean file.
Several files can be combined into one when their headers match. Spreadsheet merges stay in Dedupely and never change a CRM. Our post on [finding duplicates across several spreadsheets](https://dedupe.ly/blog/find-duplicates-across-spreadsheets) covers multi-file cleanups.

### Several CRMs in one Dedupely account

You can connect as many CRMs as you need to one Dedupely account, including several accounts of the same CRM. Each one is independent, with its own searches, Merge Rules, safety settings, Merge History, users, Security Policy and Audit Log. Billing and the record limit are shared.
Dedupely matches records within each CRM and never across two of them. If the same customer lives in two CRMs, you dedupe each one on its own.
The [Several CRMs in One Dedupely Account](https://dedupe.ly/knowledge-base/several-crms-in-one-dedupely-account) playbook covers the setup. Our post on [managing duplicates across more than one CRM](https://dedupe.ly/blog/duplicates-across-multiple-crms) covers how teams handle a customer who lives in two CRMs.

#### HubSpot and Salesforce synced together

The one exception is a HubSpot–Salesforce sync. With both CRMs connected and linked, Dedupely merges a synced pair in both at once. The next sync doesn't bring the duplicate back.
If the other CRM isn't connected, Dedupely blocks the merge rather than break the sync. Our post on [merging duplicates with the HubSpot–Salesforce sync on](https://dedupe.ly/blog/merge-duplicates-with-hubspot-salesforce-sync-on) and the [HubSpot–Salesforce guide](https://dedupe.ly/knowledge-base/merging-with-hubspot-salesforce-integration) cover the setup.

### How to start with your first Dedupely integration

Connect the CRM where duplicates cost your team the most, or upload a spreadsheet. Dedupely's preset searches show the matches and the records in them. Set rules for which value wins and preview each merge, so you see what your CRM will keep before anything changes.
[Connect your CRM to Dedupely](https://v2.app.dedupe.ly/signup)

### Same matching, different merges

Across all seven integrations, Dedupely finds duplicates the same way. What changes is the merge, because each CRM decides what happens to IDs, activity and the record that's merged away.
Knowing those rules before your first merge tells you what to check afterward. That might be integrations that store HubSpot IDs, Salesforce records in the Recycle Bin or Nimble tasks you want to keep.

### Frequently asked questions

#### Which CRMs does Dedupely integrate with?

Dedupely integrates with HubSpot, Salesforce, Pipedrive, Close, Nimble and Google Contacts, and works on spreadsheets as a seventh integration. Each integration syncs the objects you turn on. You can connect several CRMs, or several accounts of the same CRM, to one Dedupely account.

#### Can Dedupely merge records across two different CRMs?

No, Dedupely matches and merges records within each connected CRM. If the same customer is in two CRMs, you dedupe each one separately. The exception is a synced HubSpot–Salesforce pair: with both CRMs connected and linked, Dedupely merges it in HubSpot and Salesforce at once.

#### What happens to the record ID when Dedupely merges records?

It depends on the CRM, because Dedupely follows each CRM's own merge behavior. In Salesforce, the master record keeps its ID. In HubSpot, the merged record gets a new ID by default, unless the portal is in HubSpot's opt-in beta that keeps the primary's ID. Any tool that stores HubSpot IDs may need updating after the merge.

#### Can a Dedupely merge be undone?

~~No, merges happen directly in your CRM, and most CRMs can't undo them either.~~ Yes, within 30 days for most merges, from Merge History. Merges made before undo was released, HubSpot leads, HubSpot companies in a Salesforce-synced portal, merges made in HubSpot and Salesforce at once and Pipedrive products can't be undone. Undo is for records that weren't duplicates, so treat every merge as permanent. Merge History also keeps the original values and record IDs, which you can download as a CSV. See [how to undo a merge](https://dedupe.ly/knowledge-base/undo-a-merge).

#### Does Dedupely work with spreadsheets?

Yes, Dedupely works on CSV files as if they were a CRM. You match and merge with the same options and rules, combine files with matching headers and download the clean file. Spreadsheet merges stay in Dedupely and never change your CRM.
Behind the article

### Gaby Salinas

Marketing Assistant at Dedupely
Gaby Salinas came to CRM data from marketing and advertising, so she looks at duplicates from two sides: the match and merge logic behind them, and what they do to the people using the CRM, like the rep who calls a customer twice, the admin who gets blamed and the cleanup nobody wants to start.
As Marketing Assistant at Dedupely, she follows how RevOps teams, end users, consultants and technical teams actually work with their data: the records they stop trusting, the workarounds they build and the moment they finally decide to clean up. What she finds shapes most of what Dedupely publishes.
[Connect with Gaby on LinkedIn](https://www.linkedin.com/in/gbyslns)

### Contact us

We’d be happy to help you get this set up.

#### Write us a message

We probably know the answer to your question already
help@dedupe.ly
Email copied to your clipboard!
[Book a Zoom Whether you’re getting started or getting intense. Get in touch! Book a zoom](https://meetings.dedupe.ly/meetings/gaby-salinas/dedupely-zoom-scheduler)

### Discover Related Blog Posts

Stay updated with our latest articles and insights.
[CRM Organization Native CRM deduplication vs. deduplication tools Native CRM tools block some duplicates and merge a few at a time. Dedupe apps and scripts add custom matching and bulk merges. Compare all four. Gaby Salinas October 15, 2026](https://dedupe.ly/blog/the-limits-of-native-deduplication-in-crms)
[Duplicates How to deduplicate HubSpot and Salesforce while they sync You can dedupe HubSpot and Salesforce while they sync if each merge covers both CRMs. See why one-sided merges come back and what to check first. Gaby Salinas October 28, 2026](https://dedupe.ly/blog/merge-duplicates-with-hubspot-salesforce-sync-on)
[Productivity How to find duplicates across multiple spreadsheets To find duplicates across several spreadsheets, line up the headers, combine the files into one list, then match and merge before you import. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/find-duplicates-across-spreadsheets)

### Get started for free

20 free trial merges and as much free support as you need to get your duplicates under control.
[Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)[Try for free](https://v2.app.dedupe.ly/signup)
[Or sign up with Google](https://v2.app.dedupe.ly/signup/google)
Running CRM cleanup for clients? [See the Partner Program](https://dedupe.ly/become-a-partner)
Skip to content