Hi, we have thousands of duplicate contacts in Pipedrive, due to contacts not being pre-checked as duplicates at the API level. Using the Merge Duplicates ‘manual’ option in Pipedrive Settings isn’t a viable option at scale. Does anyone have any solutions to control duplication of Contacts using “email” as identifier? Thanks!
Hi Michael 
What about Dedupely?
The root cause here is usually that duplicates get created at write time, something (an import, a form, a script) is inserting new Person records instead of checking for an existing one first. A few ways to fix this going forward, not just clean up the backlog:
Prevent new duplicates at the point of insert: Before any API call creates a Person, always search first using the Persons search endpoint, filtered by email, and update the existing record if found instead of creating a new one. This has to happen in every integration/script that writes to Pipedrive, not just one, if even one workflow skips the check, duplicates creep back in.
Clean up the existing backlog: Export all Persons via API, group by normalized email, then use the /persons/{id}/merge endpoint programmatically to merge in bulk instead of one-by-one in the UI. A dedicated dedup app like Dedupely (mentioned above) also handles this UI-side if you don’t want to script it.
For the long term: if Persons are also being created from an external system (a database, another CRM, a signup flow), the dedup problem tends to keep recurring unless that write path always upserts against a shared key (email) instead of blindly inserting. Full disclosure, I work at Stacksync, we build two-way sync specifically around keyed upsert logic (matching on email/external ID before writing), plus a sync-issue view where you can retry or revert bad writes in bulk, which is built for exactly this failure mode. Worth a look if the source of your duplicates is an external feed rather than manual entry.