> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/records/duplicates.md).

# Find duplicate CRM records

Use **Records → Find duplicates** to inspect CRM records that share an email or company domain. This is a read-only scan; it does not merge, delete or rewrite the results.

## Run the scan

1. Connect the intended CRM account.
2. Open **People** for contact/lead email duplicates, or **Companies** for company/account domain duplicates.
3. Select **Find duplicates**.
4. Review the provider, scan size and grouped identities.
5. Open the records in your CRM before choosing how to resolve them.

Salesforce groups matching CRM identities through its query API. HubSpot checks a bounded set of recently changed contacts or companies; a partial scan is not proof that the rest of the CRM has no duplicates. Results can be cached for ten minutes.

## Prevent new duplicates

In a workflow, match first and create only on No match. For Salesforce creation, use **Update instead when this field already matches** when one field is a reliable unique identity.

Handle ambiguous matches deliberately. A record with the same company domain is not necessarily the same person, and a duplicate scan does not establish which owner should receive the lead.

See [CRM workflow steps](/workflows/crm-steps.md) and [Link to CRM](/records/link-to-crm.md). Perform merges using your CRM's supported controls and your team's record-retention rules.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/records/duplicates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.