Merge Duplicates Functionality Proposed Improvement

Damian Wilson
Damian Wilson Member Posts: 1

New to the Pipedrive Community and found a proposed functionality improvement that the team here at TurnSignl would greatly value.

 

Two things could be added to the 'Merge Duplicates' functionality that could great improve user experience.

1) Adding a 'Merge All' button

2) Allowing users to customize the fields that are used to determine if a suggested duplicate contact or account is truly duplicative.

 

An example of a helpful unique field that is very predictive of whether a contact or account is duplicative would be their LinkedIn profile URL. John Smith will come up with hundreds of potential matches, but John Smith LinkedIn Profile URL would be a unique identifier that could quickly separate the true match from the hundred of potential matches.

Hope this helps!

Damian Wilson

0
0 votes

· Last Updated -

Comments

  • Amit Sarda (AmitSarda.xyz)
    Amit Sarda (AmitSarda.xyz) Member Posts: 1,489
    First Answer 5 Insightfuls 5 Up Votes First Anniversary
    CONSULTANT
    edited April 2022 #2

    Hi @Damian Wilson - Have you used Dedupely?

  • Sven Amann_76110
    Sven Amann_76110 Member Posts: 67
    5 Up Votes Name Dropper 5 Likes First Comment
    edited April 2022 #3

    We would highly appreciate that, too. Checking for duplicates by email only or even by name only would be very valuable for our data cleaning processes.

    One addition: If we could then additionally apply that to only a fraction of the data, e.g., to only the contacts added in the last week, that would be a dream come true!

  • Amit Sarda (AmitSarda.xyz)
    Amit Sarda (AmitSarda.xyz) Member Posts: 1,489
    First Answer 5 Insightfuls 5 Up Votes First Anniversary
    CONSULTANT
    edited April 2022 #4

    We would highly appreciate that, too. Checking for duplicates by email only or even by name only would be very valuable for our data cleaning processes.

    One addition: If we could then additionally apply that to only a fraction of the data, e.g., to only the contacts added in the last week, that would be a dream come true!

    Hi Sven!

    Try Dedupely.

    Best,

    Amit

  • Sven Amann_76110
    Sven Amann_76110 Member Posts: 67
    5 Up Votes Name Dropper 5 Likes First Comment
    edited April 2022 #5

    We would highly appreciate that, too. Checking for duplicates by email only or even by name only would be very valuable for our data cleaning processes.

    One addition: If we could then additionally apply that to only a fraction of the data, e.g., to only the contacts added in the last week, that would be a dream come true!

    Thanks. I know I can throw more money at the problem (after I get clearance to use yet another service). However, why not improve a feature that is already there? Especially because engineers can already change the "duplicate criteria" in the backend, making this available to end users seems an obvious improvement.

  • Ryan Bozeman
    Ryan Bozeman Member Posts: 12
    First Comment First Anniversary Name Dropper Integration Partner
    edited June 2023 #6

    Hey @Damian Wilson,

    Not sure if this is still a problem for you as its been a little while.

    With the Merge Duplicates feature, Pipedrive will look to see if your contacts have the same name and one of the following: the same phone number, the same email address, or are part of the same organization. This will catch many duplicates, but yea there will be many that slip through for a variety of reasons, and the lack of a bulk merge is definitely not ideal.

    I also wanted to mention that Insycle (full disclosure, I work for them as a product marketer) allows you to bulk merge people, organizations, and deals. You can create custom rules for identifying duplicates, using any Pipedrive field as a potential matching field (plus advanced matching options like exact/similar matching).

    Then you can choose how data is retained on a field-by-field level. So for example you could:

    • Keep the Job Title from the record in which it was most recently updated
    • Keep lead status/pipeline data from the record that was furthest along
    • Collect any notes across all merged duplicates in a custom notes field

    Hope that helps!