How to Deduplicate People and Companies in Bulk and Automatically

You have multiple records in your CRM that represent the same underlying entities—contacts and companies. These duplicates cause your sales team to step on each other's toes, hurt customer experiences, and cause headaches across your organization. Your employees are forced to search through multiple records to gain full context.

Insycle's Merge Duplicates module can identify duplicate records and merge them flexibly, in bulk, using advanced rules to select the master record and control data retention.

Process Summary

  1. Set rules to identify duplicates.
  2. Review and analyze the identified duplicates.
  3. Choose Bulk Mode.
  4. Set rules to select the master record and determine what field data is retained.
  5. Deduplicate your records.

 

Step-by-Step Instructions

Step 1: Configure Rules to Identify Duplicates

Navigate to Data Management > Merge Duplicates, pick the record type, and explore the default templates for a pre-built solution.

Step 1 looks through the records in your database, examining the fields that you specify for a match.

Click the + Field button to add fields you want to look at for duplicates, along with some parameters on what to look for. You want to choose fields that, in combination, give a high degree of certainty that the matched records are duplicates. See the Advanced How-Tos for more details.

For example, to find duplicate people you may use the "First Name," "Last Name," and "Email Domain" fields. People with the same first name AND last name AND email domain will show as possible duplicates. 

bulk-merge_1.png

When finished, click the Find button, and Insycle will generate a list of duplicates for you to review.

Expand Criteria for Matching Duplicates

If you'd like to look at the data in two different fields (that contain similar data) as if it were one, you can set up Related Fields under the Advanced tab. For example, you might want to look at both the Email and Additional Email fields for duplicate values.

step-1-advanced-tab-related-email.png

The Conditions tab provides rules one or more of the records in a duplicate group will need to meet.

  • Value Required in All Records - Each record must contain a value in this field to be considered a duplicate.
  • Empty Allowed in Any Record - A record can still be considered a duplicate if this field is blank. Allowing empty values requires using two or more fields to identify duplicates.
  • At Least One Record With Non-Empty - At least one record in the duplicate group must contain a value.
  • At Least One Record Match - At least one record in the duplicate group must match the specified value, and the other records cannot be blank. If none of the records have the specified value, the duplicate group will not be merged.
  • Only One Record Match - If more than one record in a duplicate group contains the specified field value, the duplicate group is skipped (not merged).
  • Within Timeframe - Set a time parameter that can find duplicates created or modified within a specific timeframe, such as the last 20 minutes.

merge-duplicates-hubspot-contacts-step-1-conditions-all-6.png

Step 2: Analyze the Identified Duplicates

Records that have the same values in the fields specified in Step 1 are considered matches. When two or more records represent the same entity (person, company, or other) based on your matching rules, they are clustered together into duplicate groups. Each duplicate group shows the total number of records that were identified as duplicates based on your settings. For example, if you had four records for the same person, it would count as one duplicate group with four duplicate records.

Under Step 2, each row represents a duplicate group, with the number indicating how many duplicate records were found. When you click a row, it expands and shows the duplicate records in the group.

dup2.png

Explore the record data in the duplicate groups. Double-check to make sure that the fields you set up in Step 1 are showing what you expected. 

Looking at the record details in several duplicate groups, decide the best way to determine which is the master record the other records will be merged into. Learn more about common practices for picking a master record.

Add more columns to the view using the gear button on the right to get more context.

Step 3: Choose Bulk Mode

The most efficient and sustainable way to merge duplicates is in Bulk mode. This allows you to set rules for determining the master record automatically across all records in your database. With Bulk mode, you'll be able to use saved templates and recipes to repeat the process on a regular basis. 

Under Step 3, the Bulk operation tab is automatically selected. Leave this as is.

dup3.png

If you have duplicate groups that contain more than five records, you may want to change the value in Skip duplicate groups with more than [5] records per group to make sure you can get them all.

Note: When merging in bulk, Insycle limits the duplicate group size based on the entered 'skip' value, skipping groups that contain more records. This is a precaution to ensure that if you use a duplicate matching filter that is too broad in Step 1, you don't accidentally merge a lot of non-duplicate records together. You can adjust the skip value as needed, up to 100 per duplicate group. 

In Manual mode, you have complete control over which records are merged together by selecting them from the Record Viewer. Manual mode should be reserved only for cases where you need a careful, controlled process. Learn more about merging duplicates in Manual mode.

Step 4: Set Rules for Master Record Selection and Data Retention

Configure Rules to Automatically Select the Master Record

Under Step 4 on the Records tab, you define how all of the matching duplicate groups should be merged at scale. To do this you need to create a series of rules that tell Insycle how to select the record from each group to become the master. The master is the record that will remain after the merge.

For example, if you had four records representing the same company, they would make up one duplicate group with four records, all of which would be merged into one master record. The other three records would not exist anymore.

On Step 4, select the matching method—Priority Match, or Absolute Match.

Priority Match looks through the master selection rules one by one, in order. As soon as a record meets one of the criteria, this becomes the master and the rest of the rules are skipped. Most de-duplication operations should use Priority Match.

With Absolute Match, a record must meet all of the listed rules in the Record tab in Step 4 to become the master. If a record does not match every rule listed, no master record will be identified. Absolute Match is appropriate for less flexible master selection. Learn more about these options in the Advanced How-Tos below.

step-4-priority-match-no-arrow-2023-06-01.png

For each duplicate group, Insycle will look at each Record rule to see which of the records in the group meet the criteria. Rules are read in order, from top to bottom and as soon as a record is the only one to meet a rule, it is selected as the master record. The subsequent rules are ignored. 

step-4-record-mktg-eml-high-low-w-blank-rule.png

If none of the records in the duplicate group match any of the rules, the automatic master selection for the group fails. See the Troubleshooting section below for more details.

Configure Rules That Determine Values to Keep

After Insycle has identified the master record, it will use the Field selection rules to automatically pick which values from a duplicate group will be used in the master record.

Under Step 4, click the Fields tab. For each field you want to control the data retention for, you need to select a Field and tell it where the data for the field should be taken from. This is merged into the master. Any data that is not in the master or not copied to the master is deleted.

step-4-fields-tab-arrow.png

The Criteria dropdown gives you various options for choosing the data to keep, and the Group Fields lets you keep values of multiple fields from the same record:

merge-duplicates-hubspot-contacts-step-4-field-rules-9.png

  • From master record – Use the value that exists in the master record.
  • From master record (even empty) – If the field on the selected master record is blank, keep it that way. Don’t automatically fill it in with a value from the most recently updated record.
  • Most frequent value* – If the same value appears in multiple records, use the one that appears most frequently.
  • From record where value – Select data from one of the records in the duplicate group based on the values. These options vary depending on the field type. For example, retain the data in the Email field that is using a professional domain rather than a free one.
  • From record based on other field value – Look at the value in a different field to decide which value from the duplicate group should be kept. The example above highlights how a Last Modified Date value can be used to determine which Lifecycle Stage value to use.
  • Combine and append all values* – You can merge the values from the selected field for all records in the group. For example, if there is some type of Notes field, you could keep the notes from all of the records in the duplicate group.
  • Collect all values from other field* – Select a destination field to copy and combine values into, then select what field the data should come from. For example, this could be used to keep the record Owner values of all duplicates and combine them into a custom field.
  • Collect non-master values from other field* – Aggregate the values of all the duplicates that are not the master and not the same as the master, meaning all instances of that value are excluded from collection. This can be especially helpful if you want a record of the object IDs that were removed, so you can also remove them from another system. Select a destination field to copy and combine values into, then select what field the data should come from.

* Indicates Criteria options that do not allow you to Group Fields.

  When one or more fields are added to the Fields tab, a special row –Master (After)– will appear in the CSV report. For each duplicate group, the Master (After) row shows the values the final record will contain based on your Field rules and the default behavior. 

Step 5: Review Changes and Merge Records

Preview Merged Changes in CSV Report

Now with the filters and master record set up, you can preview the changes you are making to your data. That way, you can check to ensure your deduplication configuration is working as expected before those changes are pushed to your live database. The CSV report that Insycle generates includes records from all the duplicate groups.

Under Step 5, click the Review button and select Preview mode.

dup7.png

Click the Next button to go to the Notify screen, where you can select recipients for the email report. You can also add additional context on this screen.

On the When tab, click the Run Now tab, and select which records to apply the change to (in most cases this will be All), then click the Run Now button.

dup8.png

Insycle will generate a preview CSV and send it to your email. Open the CSV file from your email in a spreadsheet application and review the data.

There's a row for each record, which includes:

  • The Result of the action
  • A Message with details
  • The Duplicate Group ID which indicates which records will be merged together
  • A record Status that identifies which were picked as master and which were identified as duplicates and merged into the master. See below for more details
  • All fields used to identify the duplicates in Step 1
  • The record ID, record name or email, and Deeplink to the CRM record
  • All fields selected for the Record and Fields rules in Step 4. Note that if a field is used on both tabs, it will only appear once in the CSV. 

merge-duplicates-hubspot-contacts-csv.png

 The Status column indicates:

  • Duplicate – The record is part of a duplicate group.
  • Master The master record chosen for the duplicate group based on default behavior and your Record rules. Review the selections in this row to determine whether the appropriate records are being chosen.
  • Master (After) – This appears only if at least one or more fields have been specified in Step 4 on the Fields tab. For each duplicate group, the Master (After) row shows the values the final record will contain based on your Field rules and the default behavior. 
  • Error – If Insycle is not able to determine which record would be the master, an error message will appear here. See the Troubleshooting section below for more details.

If everything looks good, return to Insycle and move forward with applying the changes.

Apply Changes to Your CRM Records

When you're satisfied with the preview results, you can apply the merge changes to your CRM.

Under Step 5, click the Review button again, and this time select Update mode.

On the When tab, you should use Run Now the first time you apply these changes to the CRM. If you have a large number of records, you may want to do a smaller batch to review the results in your CRM.

merge-duplicates-step-5-review-update-run-now-all.png

Save Templates and Setup Automation

After you've seen the results in your CRM and are satisfied with how the operation runs, you can save your configuration as a template, and set up automation so this merge operation runs on a set schedule. If you have several templates you'd like to run together automatically, you can create a Recipe.

By automating with a template, you'll save time and ensure that your duplicates are merging consistently on an ongoing basis.

Return to the Template menu at the top of the page and click Copy to save your configurations as a new version of whatever template you started with. Then click the pencil to edit your new template name.

save-template-copy-and-rename.png

Under Step 5, click the Review button, and select Update mode.

On the Notify tab, select the send option appropriate for your automation: Always send, Send when errors, or Do not email.

Add any additional recipients who should receive the CSV (and make sure to hit Enter after each address). You can also provide additional context in the message subject or body.

merge-duplicates-step-5-update-notify-tab-always-send.png

On the When tab, select Automate, and configure the frequency you'd like the template to run. When finished, click Schedule.

merge-duplicates-step-5-review-update-automate-daily.png

You can view all your scheduled automations at any time on the Operations > Automations page.

Advanced How-Tos

Step 1: Setting Up the Fields to Find Duplicates

Each row in your matching fields setup is cumulative, so records must meet all of the criteria. For example, looking for records that have the same First Name and Last Name and Phone Number returns only results where all three values are the same.

  The minimum required length for the matching values is four characters or more. Values such as "Joe" or "Ace" will be disregarded.

Field Name Comparison Rule Ignored Match Parts

Pick a field that you think has some duplicate values.

Running a very simple match operation like just First and Last Name is okay for giving you an idea of what you have, but it is too broad to use for reliable analysis and deduplication. There may be legitimate duplicate names–different people with the same first and last name. You need additional, unique criteria to narrow it down.

Choosing Unique Identifiers

Matching duplicates requires unique identifiers—data that is unlikely to be shared by any other record unless it is a duplicate. If you don't use unique identifiers, you are likely to identify unrelated records as duplicates and may accidentally merge them.

Many CRMs match first names, last names, and email addresses. If all of those match, or are similar, you can confidently determine that the record is a duplicate.

Other unique identifying fields that are commonly used in deduplication include:

    • Phone number
    • Domain name
    • Mailing address
    • ID number
Step 1: Matching Using Two Different Fields

Sometimes, you might want to match duplicates using data in two separate fields. For example, you might want to compare your Phone Number field to a Mobile Phone Number field to identify duplicates.

Using the Related Fields feature, you can use two different fields (that contain similar data) as matching fields to catch more duplicates.

You can set up Related Fields in the Advanced tab.

bulk-merge_2.png

Common Examples of Related Field Matching

Matching Field Related Fields
Phone Number Mobile Phone Number, Company Phone
Email Domain Website, Company Domain
Email Additional Email Addresses
Address Company Address
Step 1: Allowing Empty Values When Matching

When using two or more fields to identify duplicates, records can still be considered matches even if one of the field values is blank. You just need to specify which field(s) allow a blank value.

Under Step 1, configure your matching rules in the Simple tab, then click the Conditions tab.

step-1-conditions-tab-arrow.png

All the matching fields you included will automatically appear with the Value Required in All Records condition selected. Change the condition to Empty Allowed in Any Record to allow empty values for certain fields. You can also use the At Least One Record with Non-Empty condition to help you determine which is the master record. Make sure at least one field remains required and is a reliable unique identifier to ensure the records are really duplicates.

step-1-conditions-empty-not-empty.png

For example, on the Simple tab, you may have the matching fields: First Name, Last Name, and Phone Number. But on some of your records, the Phone Number field may be empty. Using the conditions "Empty Allowed in Any Record," or "At Least One Record with Non-Empty," all records with the same name, same phone number, and no phone number will be considered duplicates.

step-2-group-w-empty.png

Step 1: Find Duplicates Created within X Minutes of Each Other

When customers encounter an issue when making a transaction, they often seek help from one of your support channels. However, whenever a contact is created from a chat, like Facebook Messenger, Hubspot Chat, and others, very little information is provided—usually just a name and timestamp. This makes finding other instances of the same contact, such as their customer record, difficult.

With the Merge Duplicates module, under Step 1, you can use the Conditions tab to match contacts with the same name that were created or modified within the same period of time.

First, select the fields in the Simple tab. Then, on the Conditions tab, select the Within Timeframe condition and set the Minutes, Hours, or Days criteria. 

merge-duplicates-hubspot-contacts-step-1-conditions-created-within-15-minutes.png

Step 4: Selecting Priority Match vs Absolute Match

step-4-priority-match-no-arrow-2023-06-01.png

Priority Match: Looks through the master selection rules in order, one by one. As soon as a record meets one of the criteria, Insycle makes the master selection and skips the rest of the rules on the list. The vast majority of duplicate templates should use Priority Match.

Absolute Match: The master record must meet all of the listed rules in the Record tab in Step 4. If a record does not match every rule listed, no master record will be identified. Absolute Match is appropriate for less flexible master selection.

For example, if a company wanted to ensure the chosen master record is in their sales pipeline and already has a sales rep working the record, they can choose Absolute Match and set the Record rules:

  • Lifecycle Stage is lead
  • Contact Owner exists

Choosing Absolute Match can often result in no master record being identified since the record has to match every rule listed, so in most cases, you should select Priority Match.

Step 4: Understanding Master Record Selection

Let's say we have four records that represent the same person—Marta Vaskovitch. The Merge Duplicates module will identify this as one duplicate group consisting of four records.

Here is the data that we have for this duplicate group:

mceclip11.png

Here are the master selection rules we have set up:

step-4-record-mktg-eml-high-low-not-gmail.png

We haven't sent any emails to Marta yet, so when Insycle processes the first three rules—Marketing emails clicked, emails bounced, and emails opened—Insycle cannot eliminate any record because they all have the same value of zero.

In the next rule about contact owner, records 61301, 61201, and 61251 are eliminated since no contact owner exists for those records. Now, only one record remains, 61351, therefore that's the master record.

mceclip13.png

Step 4: Considerations When Picking a Master Record

For contacts, it's often useful to pick master records based on engagement, such as the highest number of email clicks or the most recent email opened. You can also use other statuses to pick a master record, such as the furthest along in your sales lifecycle or the most recently updated record.

merge-duplicates-hubspot-contacts-step-4-record-tab-7-rules.png

For companies, it's often useful to use associated records, such as the highest number of associated contacts or deals, to determine the master record.

If you have a connected app, like Salesforce or an ERP system, pick the master record that is syncing with the other apps.

merge-duplicates-hubspot-companies-step-4-record-tab-5-rules.png

Step 4: Control What Field Data is Retained

Though it's possible that duplicate records may be exactly the same, often there is only partial data overlap between them. When data is split between two different records, both records may contain unique and important information about the customer you'd like to keep.

By default, Insycle will keep the master record values; if the master field is blank, the value from the most recently updated duplicate will be used. The Merge Duplicates module allows you to control the values saved in the master record after the merge, regardless of the default merge behavior. By adding each field you want to control the data retention for in the Fields tab under Step 4 and selecting a Criteria, you can tell Insycle where the data for the field should be taken from and how to handle it.

If you want to preserve data from several fields based on one Criteria, select them under Group Fields. Note that this is not available for all Criteria.

merge-duplicates-hubspot-companies-step-4-fields-tab-group-fields.png

If you want to preserve the record IDs of the duplicates that are merged into the master record, you can create a custom field, "Merged Record IDs,” in your CRM.

Then, in the Merge Duplicates module, add a Fields rule to override the default merge behavior. Select the "Merged Record IDs" field you created, the "Collect all values from other field" criteria, and "Record ID" as the other field. 

step-4-fields-collect-all-values-from-other-field.png

You can use the Preview to see how this will preserve the Record IDs of all the duplicates in each duplicate group.

step-4-collect-all-values-from-other-field-CSV-example.png

You could set multiple criteria for the same field, which can be useful when establishing a hierarchy for selecting the value so "Value A" takes precedence over "Value B."

In this example, two different rules are defined for the 'Lifecycle Stage' field. The first rule states that if a record has the value "Customer," that value will be merged into the master record. However, if no records match the "Customer" criteria, the second rule for "Opportunity" comes into play.

step-4-fields-two-lifecycle-stage-rules.png

Granular Control for Picking Duplicate Records

For situations where there are no common rules you can apply for identifying duplicates for all or some of the records, you may need more granular control for picking records to include or exclude from the process.

To do this in bulk, you can create a CSV and use the Magical Import module.

In these cases, you can use CSV files to customize your bulk merging, designate master records, and exclude records from deduplication. Then you can import the CSV from the Magical Import, and use the Merge Duplicates module for complete control over the final merge operation. Learn how to customize merging Duplicates in bulk using a CSV.

To do this one record at a time, you can use Manual mode of the Merge Duplicates module.

In Manual mode, you have complete control over which records are merged together by selecting them from the Record Viewer. Manual mode should be reserved only for cases needing a careful, controlled process. Learn more about merging duplicates in Manual mode.

Tips for Bulk Merging Duplicates

  • Begin with easy-to-find duplicates. Iterate through fields and rules you know will surface duplicates. Don’t expect to resolve all your duplicates by setting up and running this process once. You will need to run this process multiple times for different fields or nuanced variations.
  • Each time you get a merge process to run the way you want in your database, save it as a template. When you have a solid set of templates that reliably resolve most of your duplicates, you can put them together as a Recipe that can run on a regular, automated schedule.
  • You may also need to look for edge cases that fall outside your standard rules. These may be operations you run manually, so you can adjust based on what you find.
  • Do some experimentation. Use the Preview mode CSV report to analyze patterns in the duplicates. You may learn what is causing the duplicates and learn how to avoid having them in the first place. You may also want to explore your data in the Grid Edit module to understand what you have so you can design templates that catch all potential variations. 

Troubleshooting

If you're not seeing the results you expect when merging duplicates, consider these issues:

Not all identified duplicates are merging into the master

You have duplicate records that have been identified by Insycle but not all of them are merging into the master. Check to see how many duplicates are in the affected duplicate groups. If you have duplicate groups that contain more than five records, you may want to change the value in Skip duplicate groups with more than 5 records per group to make sure you can get them all.

merge-duplicates-step-3-bulk.png

This setting is intended to protect against the accidental merging of non-duplicate records if the filter in Step 1 is too broad.

Message in CSV, "Change rules in Step 4 'Master Selection'" 

If the Message column of the CSV report displays this text:

Change rules in Step 4 'Master Selection'. Failed to pick master record because multiple records (X) meet the selection criteria. In 'Master Selection', change, add, or reorder the rules such that only one record matches (if cannot determine master based on field values, use 'Record ID is lowest' as the last rule).

merge-duplicates-salesforce-accounts-csv-w-error.png

This means that based on all the rules, Insycle could not figure out which record in the duplicate group would be the master. None of the records meet more of the rules than others.

There are a few things you can try to resolve this:

  1. Under Step 4, on the Record tab, experiment with reordering or adding additional fields that are likely to have unique values.
  2. In the Step 4 heading, check to ensure that you have Priority Match selected and not Absolute Match.

    step-4-priority-match-w-arrow-606px.png
    With Priority Match, your master record only has to match one rule. Using Absolute Match, your master record would have to meet all of the rule criteria. The majority of the time, it is best to select Priority Match.

    If Priority Match was used, then none of the records in the duplicate group meet any of the criteria on the list more than the others. In this case, you'll need to experiment with the Record tab, reordering or adding additional rules for fields likely to have unique values.

  3. As a last resort, you can add a rule on the Record tab of Step 4 that says Record ID is lowest, or Create Date is earliest.
    merge-duplicates-hubspot-contacts-step-4-record-tab-last-resort-rules.png
Non-duplicate records are being merged together

There are a couple of things to look at that may be misidentifying records as duplicates.

First, you may need a better unique identifier. Under Step 1, if you only use fields that could correctly contain the same values in multiple records, these aren't unique identifiers. In this case, you are likely to identify unrelated records as duplicates and may accidentally merge them.

Unique identifiers are data that is unlikely to be shared by any other record unless it represents the same underlying entity. Fields commonly used in deduplication include phone numbers, email addresses, mailing addresses, and ID numbers.

Second, this may indicate the Comparison Rule under Step 1 is too broad. Try using the Exact Match comparison rule instead of Similar Match. Similar Match looks for values that may be close but with a one-character difference (maybe a typo) which broadens the search. 

Remember, always run your deduplication in Preview Mode to confirm things are working as expected before running them in Update Mode and applying the changes to your CRM records.

Insycle isn't finding any duplicates

Most of the time, when Insycle can't find duplicates, it is due to your matching rules in Step 1. It is important to analyze the underlying data to better understand how to set up your rules. A useful exercise can be to set up your matching filters to look for exact matches of just First Name and Last Name

bulk-merge_3.png

When you click Find, these rules can show you a broad overview of what duplicates are potentially in your database and what fields might be useful to include in your matching fields. These settings are just for discovery and should not be used for a final merge operation; many people can have the same first and last names and are not duplicates. 

To get further context, on Step 2, click the layout gear button on the right side of the title bar. Here, you can add any field in your database as a column to the duplicate group review to better understand the data inside these records. 

dup15.png

It's taking a long time for Insycle to find duplicates

It can take a while for Insycle to find and match duplicates if the fields being used to identify them have very long values. The longer the values, the longer it takes Insycle to process the data and generate the results. This might come up when looking for matches based on long ID numbers, LinkedIn bio links, or other URLs with long strings attached (ex, https://www.linkedin.com/in/svadin%C3%ADr-n%C4%9Bmec-1234b31a3/).

You can speed this up by limiting how much of the value Insycle looks at.

If the values' beginning or ending portions are all unique, you can limit the comparison to the first or last several characters using the Match Parts parameter under Step 1

merge-duplicates-linkedin-bio-step-1-match-parts-last-9-chars.png

merge-duplicates-linkedin-bio-step-2-last-9-chars.png

Or use the Ignore Text (Substrings) parameter, then click the Terms button.

merge-duplicates-linkedin-bio-step-1-ignored-text-terms-button.png

On the Ignored Text tab of the popup, add the common portion of the URL or text string.

merge-duplicates-linkedin-bio-step-1-ignored-text-popup.png

For more help troubleshooting issues with Insycle, refer to our Troubleshooting Issues article.

Frequently Asked Questions

How can I find duplicates when one field is empty?

When using two or more fields to identify duplicates, records can still be considered duplicates even if one of the matching field values is blank. You just need to specify which field(s) allow a blank value.

See the Advanced How-To, Step 1: Allowing Empty Values When Matching above for full details.

Can I match duplicates using two different fields?

Yes, you can match duplicates using data in two separate fields. For example, you can look at both the Business Phone and Mobile Phone field values as a single pool of values to compare records and identify duplicates.

Using the Related Fields feature, you can use two different fields (that contain similar data) as matching fields to catch more duplicates. You can set up Related Fields in the Advanced tab of Step 1.

merge-duplicates-salesforce-contacts-first-last-name-phone-step-1-advanced-tab.png

How do I ensure that I am not merging non-duplicate records together?

There are two ways to make sure that the records that you are merging are indeed duplicate records.

First, always run your deduplication templates in Preview Mode before running them in Update Mode. This produces a CSV that shows you how your records would have been merged. Then you can ensure that your Merge Duplicates template is working as expected and not merging non-duplicate records together.

Additionally, to ensure a smooth merge process, consider narrowing down the matching settings in Step 1. Try the Exact Match Comparison Rule instead of Similar Match. Then make sure that you are using actual uniquely identifying fields—first name, last name, email, and phone number are popular choices. The more tightly defined your filter is, the less likely you are to merge non-duplicate records.

Insycle is having trouble determining a master record. What could be causing this issue?

If the Message column of the CSV report displays this text:

Change rules in Step 4 'Master Selection'. Failed to pick master record because multiple records (X) meet the selection criteria. In 'Master Selection', change, add, or reorder the rules such that only one record matches (if cannot determine master based on field values, use 'Record ID is lowest' as the last rule).

merge-duplicates-salesforce-accounts-csv-w-error.png

This means that based on all the rules, Insycle could not figure out which record in the duplicate group would be the master. None of the records meet more of the rules than others.

There are a couple of things you can try to resolve this:

  1. Under Step 4, experiment with reordering or adding additional fields that are likely to have unique values.
  2. In the Step 4 heading, check to ensure that you have Priority Match selected and not Absolute Match.
    step-4-priority-match-w-arrow-606px.png
    With Priority Match, your master record only has to match one rule. Using Absolute Match, your master record would have to meet all of the rule criteria. The majority of the time it is best to select Priority Match.
    If Priority Match was used, then none of the records in the duplicate group meet any of the criteria on the list more than the others. In this case, you'll need to experiment, reordering or adding additional rules for fields likely to have unique values.
  3. As a last resort, you can add a rule on the Record tab of Step 4 that says Record ID is lowest, or Create Date is earliest.
    merge-duplicates-hubspot-contacts-step-4-record-tab-last-resort-rules.png
Can I select which data is retained in my master record on a field-by-field basis?

Yes, Insycle allows you to select which field data is retained in the master record using the Fields tab under Step 4. See Step 4: Set Rules for Master Record Selection and Data Retention section of this article for more details.

dup19.png

I need to exclude some records from deduplication. Can I do that?

Yes. You can exclude records from deduplication by creating a CSV with a "Deduplication Exclude" field.

First you'll export a Preview CSV from the Merge Duplicates module, add an exclude column, and specify which records should be excluded from the merge process. Next, create a custom field in your CRM to facilitate the merging. Use the Magical Import module to import the edited CSV file into the CRM, populating the new custom field. Finally, utilize this custom field to merge the remaining duplicate records in the Merge Duplicates module.

Learn how to customize bulk deduplication using exclusions.

My team needs to review and approve the master, can I accommodate that with Insycle?

Yes, there are several ways to share details and get approval before merging duplicates.

You can manually approve master records and mark them in a CSV, then use Insycle to bulk deduplicate down to those master records. See the Customize Bulk Deduplication Using Exclusions and Pre-Defined Masters article to learn more.

Or, you can run the Merge Duplicates module in Preview Mode and then deliver the preview CSV that Insycle generates. The CSV report includes your entire merge operation down to individual duplicate groups but does not update your live data. Then your team can approve the merge based on this report, before running Merge Duplicates in Update Mode.

Additionally, team members can review duplicates and manually select the master for each record under Step 4. Review the Manually Merge Duplicates article for more detail.

dup20.png

Do the field values I use to match need to be exactly the same?

No, your field data does not need to match exactly. The Similar Match Comparison Rule found in Step 1 looks for values that may be close but with a one-character difference (maybe a typo) and broadens the search.

similar-match.png

This search behaves like when Google shows results for a slightly different term, or says “Did you mean...” For example, if an Email of, “huey@coahulldu.co” is found, it could include records with the values “hueyy@coahulldu.co," or "hue.y@coahulldu.co,” as a match.

similar-match-_1.png

When you do use Similar Match, make sure to carefully review the results to ensure the duplicates being identified are what you're expecting.

Review the Understanding Similar Matching best practices for more detail.

I already have a list of duplicates, can Insycle bulk merge them?

Yes. You can use an existing CSV with duplicate record details. The file needs to include the record IDs and a "Deduplication Master" column, specifying which records should be the master, kept after the merge. Next, create a custom field "Deduplication Master" in your CRM to facilitate the merging. Use the Magical Import module to import the edited CSV file into the CRM, populating the new custom field. Finally, utilize this custom field to merge the duplicate records in the Merge Duplicates module.

Learn more about customizing bulk deduplication from a CSV.

Why can I only process 50 duplicate groups at a time?

Insycle shows 50 records on the module screen as a preview; this isn't the entire list of records. To see everything, include All records when you view the Preview CSV report.

Insycle can process thousands of duplicate groups in one operation. Potentially, you could deduplicate your entire database in one operation. 

How many duplicates can I merge into one master record?

You can merge up to 100 duplicates into one single master record. 

If you have duplicate groups that contain more than five records, you may want to change the value in Skip duplicate groups with more than 5 records per group under Step 3 to make sure you can get them all.

merge-duplicates-step-3-bulk.png

This is a precaution to ensure that if you use a duplicate matching filter that is too broad in Step 1, you do not accidentally merge many non-duplicate records together. If you are going to set this number at a high level, it is a good idea to run Preview Mode first to make sure your deduplication template is operating as you intend.

Are there any limits on the number of records that can be identified and merged with my paid subscription?

All paid plans include unlimited usage, unlimited users, and unlimited operations. During the free trial, there is a cap of 500 records updated, cleansed, or merged. See the pricing page for more details. 

Additional Resources

Related Help Articles

Related Blog Posts