Zoho CRM Deduplication: Find and Merge Records

Duplicate records creep into Zoho CRM from every direction: web forms, imports, integrations, business card scans and reps who create a new contact because searching took too long. Zoho includes several deduplication tools, but each has limits, and running them across tens of thousands of records without breaking integrations or losing history takes planning. Zoho CRM deduplication done well combines the built-in features for prevention and day-to-day cleanup with an automated, rate-aware process for large backlogs. This guide explains what each Zoho tool does, where it stops, how to automate merges through the API within credit limits and how to recover when things go wrong, with a worked example.

Zoho CRM deduplication tools at a glance

ToolWhat it doesLimits to knowUnique fieldsBlocks or warns when a new record repeats a value marked uniqueWorks going forward; does not clean existing dataFind and MergeSearches for duplicates by chosen fields and lets you merge themUp to three fields per search; up to three records merged at a timeDe-duplicate (auto-merge)Automatically merges records with identical values in chosen fieldsConflicting values must be resolved manuallyMerge Records APIMerges records programmatically, choosing the master and field valuesOne master and up to two child records per callDuplicate check on API writesUpsert matches on duplicate check fields instead of creating new recordsDepends on integrations using upsert

According to Zoho's help on merging duplicate records, Find and Merge can check up to three fields at a time and merge up to three records at once. The auto-merge tool merges records with identical values in the chosen fields, but conflicts in other field values still need a person to decide.

Prevention first

Cleaning without prevention is a treadmill. Before tackling the backlog:

• Mark fields such as email or a customer number as unique where your data allows
• Make every integration write through upsert with duplicate check fields, not plain insert
• Configure web forms to update existing leads or contacts by email where possible
• Train reps to search before creating, and make search quick with sensible default views

Zoho's Upsert Records API checks system-defined and user-defined unique fields, updating a match or inserting a new record, which stops most integration-created duplicates.

When built-in tools are not enough

The interactive tools suit day-to-day cleanup and modest backlogs. They become impractical when:

• Thousands of duplicate groups need merging
• Matching needs fuzzy rules, such as similar company names or normalised phone numbers
• Survivorship rules are complex, such as keeping the newest email but the oldest owner
• Merges must be logged for audit or coordinated with external systems that store CRM IDs

In these cases, an automated process finds duplicate groups outside the CRM, decides the master and field values by rule, and merges through the API.

Automating merges with the Merge Records API

Zoho's Merge Records API merges up to three records: one master, retained after the merge, and up to two child records, which are deleted. You can specify which child record supplies particular field values. It supports Leads, Contacts, Accounts, Deals (open deals only), Vendors and custom modules. If a child record has more than 1,000 records in any related list, the merge is scheduled and runs asynchronously, returning a job ID you can check later.

Design points for automated merges:

• Groups larger than three need several merge calls in sequence, each folding up to two children into the master
• Each call consumes API credits, so plan large backlogs across days and leave headroom for other integrations
• Record every merge: master ID, child IDs, fields taken from each and the time
• Update external systems that store child IDs, so they point at the master afterwards

Worked example: deduplicating 120,000 contacts

Suppose a company finds roughly 9,000 duplicate groups among 120,000 contacts after years of imports. Most groups have two records; some have four or five. It runs a matching script that normalises emails and phone numbers, groups records, and applies survivorship rules: the master is the record with the most activities, the newest non-empty email wins and the original owner is kept.

Group sizeGroupsMerge calls needed per groupTotal merge calls2 records7,60017,6003 records1,10011,1004 or 5 records3002600Total9,0009,300

The team spreads the 9,300 calls over five nights, about 1,860 per night, outside business hours and within a credit budget agreed with the owners of other integrations. Each night starts with high-confidence groups only. Groups with conflicting owners or very different company names go to a review list for sales operations. Before each run, it exports the affected records as a backup. The figures are hypothetical, but the planning steps apply to any large backlog.

A short run log keeps everyone informed:

NightMerge callsScheduled (async) mergesErrorsSent to review11,86012914021,8608495

Errors are mostly records already merged by a rep during the day or closed deals, which the API refuses to merge. They are logged and skipped.

Recovering from mistakes

Merges delete child records, so mistakes are costly. Protect yourself:

• Export affected records, including related list summaries, before each batch
• Start with exact matches and widen rules only after reviewing results
• Keep the merge log so any merge can be traced
• Before you start, confirm in a sandbox whether merged child records can be restored in your edition, and how, so you know your options if a merge was wrong

Common mistakes

• Running auto-merge on loose fields that produce false matches
• Ignoring integrations that keep creating new duplicates
• Merging without telling systems that store CRM IDs
• Using the whole day's API credits on a merge backlog
• Skipping backups because "the tool handles it"

For matching rules, survivorship and the wider hygiene programme, start with our guide to CRM data hygiene. API credits are the main constraint on large merges; our guide to Zoho CRM API limits explains how to budget them.

Frequently Asked Questions

How do we remove duplicates in Zoho CRM?

Use unique fields and upsert to prevent new ones, Find and Merge or De-duplicate for everyday cleanup, and the Merge Records API with your own matching rules for large backlogs.

How many records can Zoho merge at once?

Find and Merge and the Merge Records API handle up to three records at a time: one master and up to two duplicates.

Can Zoho CRM merge duplicates automatically?

The De-duplicate tool merges records with identical values in the selected fields automatically, but conflicts in other fields need manual resolution.

What happens to related records when contacts are merged?

They move to the master record. If a child record has more than 1,000 records in a related list, the API schedules the merge to run asynchronously.

Clean up your Zoho CRM with us

We plan and run Zoho CRM deduplication, from prevention rules to automated, logged merges of large backlogs. See our Zoho CRM automation services, or talk to us about your duplicates.

About the Author

Manav Sharma is the founder of Insyrge and a CRM solutions architect. He works across Zoho, Salesforce, HubSpot, Odoo and more, designing the CRM setups, integrations and automations that keep sales and operations teams working from the same data.