When one patient has several records, the problem is larger than an untidy directory. Appointments, payments, notes, and follow-up details become divided across files, preventing staff from seeing the current situation at a glance. A durable Zoho setup separates two tasks: stopping a new copy at entry and carefully merging exact matches that already exist. The second task corrects earlier damage but cannot replace prevention.
A patient who visited three months earlier calls the front desk. The employee searches the name and finds two records. The old X-ray and treatment note are in one, while last week’s payment appears in the other. Unable to decide which file is authoritative, the employee opens a third record and adds the appointment there. One duplicate has now produced another, increasing uncertainty for the next conversation.
What two records cost you
At month-end, a manager requests calls to patients who have not returned, and the resulting list contains 340 rows. Two days after calling begins, the team realizes that some rows are second files for people whose treatment has finished. Much of the effort has gone into asking completed patients why they did not return. The problem is not only list length but a wrongly defined workload.
Fragmented records force employees to investigate which file is reliable before every contact. One file may hold the current phone number, while another retains the latest conversation note. Different employees then rely on different versions. The organization loses a shared account of the person, and the context, owner, and next step of earlier work remain scattered. As cleanup is delayed, daily decisions rest on progressively weaker information.
Why duplicate records appear
The same phone number may be entered with a leading zero, a country code, or spaces, while one person may also arrive through separate channels. The critical point is that Zoho compares exact values only in the criteria fields you select. It performs no approximate matching, and identical values in excluded fields do not affect the result. You therefore cannot assume the system will connect different written forms automatically.
Find and Merge searches through the criteria fields you define. De-duplicate likewise treats records as matches only when the chosen field values are exactly equal. A consistent entry convention is therefore a prerequisite for later cleanup. When staff do not share one format for phone numbers and email addresses, two copies that look obvious to a person can remain separate during comparison. The discipline begins by choosing the identity field in advance.
Stop the duplicate at entry
Uniqueness is a property of a field and applies throughout its module. The general limit is two unique fields per module, rising to three in Leads, Contacts, Products, and custom modules. Text, Email, Phone, Integer, Long Integer, and URL fields are eligible. Tasks, Calls, and Meetings do not offer this property. Zoho compares without case sensitivity, and indexing after the field is marked can take several minutes.
A unique field does not merely warn the user and offer a way to continue. It prevents creation of another record carrying the same value. The check applies during manual creation, import, API calls, web forms, integrations, and lead or quote conversion. This is not a cleanup step that acts after the copy exists. By selecting the right identity field, you establish a separate protection layer at the moment of entry.
Close the lead-to-patient gap
When someone exists first as a lead and later as a separate Contacts record, uniqueness within one module may not be enough. After a Leads field is marked unique, Duplicate Check Preference can extend the check to converted leads or the Contacts module. For Contacts, you also specify the unique comparison field. The Zoho path is Setup > Customization > Modules and Fields > Leads > Duplicate Check Preference, where this scope is selected.
When the check finds a match, it prevents creation of the new record. A single match presents an option to view the existing record, while several matches produce a merge suggestion. This is not a fuzzy search that freely compares every field across the two modules. It works through the designated unique field. The identity criterion in Leads and its selected Contacts counterpart therefore need to follow the same entry convention.
Finding and merging are separate jobs
Find and Merge starts from a record detail page, provides six criteria fields, and combines no more than three records in one operation. It is available in Leads, Accounts, Contacts, Deals, Vendors, and custom modules. In Deals, it considers only opportunities that are not closed. The user chooses the master record. This method suits an investigation that starts with one known file and retains human control over which record survives.
De-duplicate works from a list view and scans exact matches across the module. It permits up to three selected fields. The user does not choose the master; the record with the latest Last Activity Time is selected automatically, and that choice cannot be changed. Users resolve conflicting values manually. Only one person can run it in a module at once. With more than three copies, three must be selected, and the resolve link remains available for three days.
Understand what merging changes
During a merge, attachments, notes, and activities move to the master record, and transferred activities adopt that record’s owner. Created Time and Created By come from the oldest record in the merged set. Copies are deleted permanently, and the operation cannot be reversed. Ordinary deletion keeps a record in the recycle bin for 60 days, but merging is outside that protection. More than a thousand related-list entries cause scheduling and lock the records until completion.
In a manual merge, Edit triggers run for the master and Delete triggers run for removed copies. This applies to workflow rules, Blueprint, CommandCenter, approval processes, and scoring rules, but not to the review process. Automatic merging runs neither Edit nor Delete triggers. When choosing between Find and Merge and De-duplicate, you should therefore consider not only the comparison scope but also how connected automations will respond to the operation.
A list cannot discover duplicates
A custom-view criterion evaluates each record through its own values. Because it cannot compare one record with others, it cannot express a query that identifies files sharing a phone number or email address as duplicates. A view can filter by an attribute already present on each record, but it cannot discover the relationship between copies. Expecting a special duplicate list gives a comparison task to a mechanism that does not perform comparisons.
An assignment rule is likewise not a tool for finding or merging duplicate records. A mechanism that distributes record ownership should not be expected to decide whether separate files describe the same person. Use Find and Merge from a record detail page or De-duplicate from a list view to inspect existing copies. Preventing new copies belongs to unique fields and, when relevant, lead conversion checks. This separation keeps ownership logic distinct from deduplication.
Entry discipline replaces monthly cleanup
No edition threshold is specified for these core mechanics; access conditions are specified instead. Marking a unique field requires the Customize Zoho CRM profile permission, Find and Merge requires its corresponding profile permission, and De-duplicate requires an administrator profile or the highest role in the hierarchy. Placing uniqueness on a custom field differs: because custom fields are unavailable in Free, Standard is the minimum. The tools can operate in custom modules, but module capacities by edition are not asserted here.
A cleanup tool merges copies created earlier, but it cannot prevent new ones while the same entry habits continue. For durable order, connect the unique field to the correct identity detail, configure the required check between Leads and Contacts, and give the whole team one format for phone numbers and email addresses. Monthly cleanup then stops being the primary method and becomes a controlled response to older or exceptional exact-match copies.
