Two contacts, two different histories
Your CRM contains two records for Jamie Lee. One came from a form; a colleague added the other after a call. The first holds a current inquiry, while the second contains notes and an earlier project. Deleting the less complete-looking record may remove the relationship you need next week.
Review a pair before attempting a bulk cleanup. One person can have several projects, and several people can share a company email address. The goal is a clear history for a verified contact, with separate jobs still distinguishable.
Use the review record and completed fictional example. Copy the template into a document or add it to the CRM record.
Confirm that the records describe the same person
Compare the name, organization, contact details, and source of each record. A shared info@ address does not establish identity. A different phone number does not automatically establish a different person either: it might be a replacement or a separate work number. Leave uncertainty for a human decision.
Pipedrive’s duplicate detection documentation describes matching a person’s name plus their phone number, email address, or organization. Treat the result as a review candidate. It is not proof of identity.
In the fictional example, the original conversation confirms that both cards belong to Jamie at the same studio and that their number changed. Jamie’s second inquiry remains a separate job.
Choose what should survive
Before merging, record both contact IDs, original values, and conflicting fields. Choose the primary contact, correct owner, and current contact details. Check linked deals, tasks, notes, files, and communication restrictions separately. Do not infer marketing permission from a missing field on the other record.
According to Pipedrive Merge Duplicates, the primary record takes priority when information conflicts, and merged contacts cannot be unmerged. Inspect the preview before confirming. Exporting important information does not guarantee that every relationship can be restored.
If you cannot see the full history, have someone with the necessary access review it. Limited visibility must not be mistaken for an empty record.
Perform a controlled Pipedrive merge
Open Tools and apps → Merge Duplicates using an account with the required permission and sufficient visibility. Select only the pair whose identity you verified. Choose the primary record and resolve conflicting values against the review record before selecting Preview.
In this model, C-014 should survive, but C-031 holds the current phone number. First preserve the original values in the review record, then put the verified current number into C-014. Preserve the newsletter restriction as well. The preview must show the current number, correct address and restriction; choosing C-014 alone does not ensure that. If it is wrong, choose Back, correct the records and inspect the preview again. Confirm Merge only after it agrees. The merge cannot be undone.
Check the result and its dependencies
Open the resulting contact and compare it with your review record. Can you find both jobs, the latest note, and the agreed next step? Does the next task have an owner and due date? Also inspect systems that retain the old CRM ID. A merge in one application does not repair their references automatically.
Record the resulting ID, decision maker, change time, and checks performed afterward. If something is wrong, pause further cleanup and keep the original evidence for an administrator or support. Another speculative merge will not resolve the uncertainty.
Stop the same duplicates returning
If the same pair appears each week, inspect the form, manual entry, and synchronization route. Agree to search before creating a contact. Retain stable source IDs where your tools support them. Distinguish the person, their inquiry, and each message: a returning client with a new job does not necessarily need a new contact.
Begin with a few pairs whose identity is clear. Give unresolved pairs an owner and next action. If you are still choosing a system, continue with Pipedrive or HubSpot.
Documentation checked October 10, 2026. This is a proposed operating procedure, not a trial in a particular CRM account.