SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Treat a duplicate suggestion as a review signal
Pipedrive identifies possible duplicate people using a matching name plus signals such as email, phone or organization, and possible duplicate organizations using name and address. These rules help find candidates but do not prove that two records represent the same entity. Branches with the same organization name or different people sharing a common name may need to remain separate.
Record the primary choice
When records conflict, Pipedrive prioritizes information from the chosen primary item while preserving unique information where the merge permits it. The official documentation states that merged records cannot be unmerged. Save the relevant identifiers and approved values before proceeding.
| Control | Primary candidate | Secondary candidate |
|---|---|---|
| Identity evidence | Verified customer email | Same person from an import |
| Approved values | Current owner and phone | Older conflicting phone |
| Relationships | Active deal and activities | Recent note requiring retention |
This is a fictional worksheet, not a customer merge.
Reconcile more than the visible name
- Record the original item IDs and URLs.
- Confirm one real person, organization or deal.
- Choose the primary item and approved conflict values.
- Inventory owners, visibility, deals, activities, notes and files.
- Preview the combined item.
- Perform the authorized merge only after review.
- Verify the surviving ID, values and relationships.
Account for viewer scope
A regular user may see only duplicate candidates within their visibility scope, while an administrator can review a broader set. A clean list for one user is not evidence that the account contains no other duplicates. Merge permissions must also be enabled for the relevant item type.
Accept a merge only when the identity decision is supported, the primary values are deliberate and the resulting relationships are complete. If evidence is uncertain, leave the records separate and record the reason. This checklist does not claim that any live record was merged.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.