How to De-Duplicate & Merge Duplicate Leads
How to
De-Duplicate & Merge Duplicate Leads
If you
have used any CRM software, you can certainly relate to the challenges of
detecting duplicate leads and merging them.
Duplicate leads can creep into your data when you or others enter leads
manually or import leads in bulk. Obviously, it is a best practice to search
history before creating leads, still, duplication of leads happen. It is a
challenging task to keep your database free from duplicates when you are
dealing with a massive volume of data. The chances of duplicate entries are
inevitable as the avenues to create records in CRM increase. In such scenarios,
you need to give your sales team a tool enabling them to de-duplicate leads and
merge duplicate leads. SalezShark understands this and introduced a “Merge
Duplicate Leads” tool built in to help you de-duplicate and merge duplicate
leads.
“Merge
Duplicate Leads” tool allows users to merge leads which are found duplicate
basis certain criteria set by the user, for identifying duplicate records. There
are total of six fields on which users can specify the criteria to identify
duplicates. Once the duplicates are been found, Users can merge them all
manually, to generate a single lead. Let’s have a look how these features work
in a “Merge Duplicate Leads” tool.
·
The
Administrator or a user with the “Merge Duplicate” permission will be able to
use this tool.
·
Once
the Permission “Merge Duplicate” is given to user from Profile, they will be
able to access the Duplicate leads function, under Actions button, in their
lead module.
·
Users
will have an option of selecting maximum of 3 parameters out of six fields, to
find duplicates.
·
Users
can merge a maximum of three duplicate records at a time.
·
Merge
Duplicate method will work on “And Operator” for setting the criteria for
identifying duplicate Leads.
·
If
there are more than three duplicate records, Users will be prompted to choose
any three records to merge from the list of all duplicates.
·
The
first chosen record will be considered as the Master record.
·
Users
will have an option to select each field value from 3 records to generate a
master record.
·
The
record(s) merged to the master record will be deleted permanently.
·
All
related entities like documents, activities and read only field values will be
transferred to the master record.
