Zoho CRM merge: keep the right record and field values

A record merge combines known duplicates into one surviving record. It is different from mail merge and from the Merge integration platform. Start with the duplicate record IDs you have already reviewed.

Planning this work for your team? See our Zoho CRM migration and data work service.

Choose the survivor and final values before executing. Zoho documents that merged-away records are permanently deleted and the merge cannot be reversed. A merge therefore needs a clear identity decision, not just a list of similar names.

Confirm this is record merging

Write the module and IDs for each candidate. Confirm that the records represent the same person or organisation. Similar company names, shared office numbers and matching email domains are evidence to inspect, not automatic proof.

Zoho's manual merge documentation describes Find & Merge as targeting duplicates of a particular record. Keep this task focused on the known group rather than widening it into a bulk cleanup halfway through.

For contacts, verify the individual identity and company relationship. For accounts, check the organisation and whether branches or departments should remain separate. For leads, confirm that the enquiries belong to the same person and business context.

Do not try to solve an unclear data model by merging unlike records. Review accounts vs contacts if the uncertainty is about person and company roles. If the problem started with incoming files, revisit the import preparation checklist.

Choose the master record

The master is the record that will remain after the merge. Compare more than completeness. An older record may have important links, while a newer record may carry a verified identity and current owner.

Prepare a review sheet:

Item	Record A	Record B	Reviewed decision
Identity	Verified identifiers	Verified identifiers	Evidence they are the same entity
Owner	Current responsibility	Current responsibility	Intended owner after merge
Contact details	Current and historical values	Current and historical values	Final verified values
Relationships	Linked business records	Linked business records	Links to inspect afterward
Context	Notes and activities	Notes and activities	Information the team must retain

Record the reason for choosing the master. Do not let a convenient row order become the decision. Have the relationship owner review uncertain contact details and company associations.

If an external system stores one of these record IDs, identify that dependency before merging. Do not assume an integration will automatically learn the surviving ID. Plan the CRM-side reference check and ask the external operator to verify its side.

Resolve field conflicts before merging

Zoho lets the user choose a master and final field values. Make those choices in your review sheet before opening the final confirmation. A populated field is not necessarily more accurate than a blank one.

For each disagreement, record the selected value and evidence. A recent customer-confirmed phone number is stronger evidence than a value copied from an old import. If neither value is verified, assign the question rather than guessing.

Distinguish a conflict from a relationship problem. Two different company links may mean the contact changed employers, the original association was wrong or the records are different people. Resolve the meaning before deciding which link to retain.

If the current interface offers a conflicts-only view, use it as a review aid after checking Zoho's help docs. Do not rely on that view as your only record inventory. Values that agree can still be wrong, and related work needs a separate inspection.

Preserve permitted reference material before the irreversible action. An export or review note can support later investigation, but it does not make the merge reversible or guarantee reconstruction of every relationship.

Run the manual merge

Zoho documents a manual merge of up to three records. Work within that native limit and review each group deliberately. Do not attempt to bypass it by treating a large set of similar names as one identity.

Open the intended starting record and use Find & Merge Duplicates in your current interface. Compare the returned candidates with your approved IDs. Exclude any candidate whose identity has not been established.

Select the reviewed records, choose the master and compare the final values against your sheet. Before execution, check the surviving ID, owner and disputed fields again. Confirm that everyone reviewing understands the permanent deletion of merged-away records.

For contacts, accounts and leads, apply the same identity-first sequence in the relevant module and check the available action in your organisation. Do not treat a contact and a lead as interchangeable records to combine without reviewing the appropriate process.

Can you merge through the API? Check Zoho's help docs for the current endpoint, supported modules, permissions and request behaviour before designing an API route. The verified manual workflow is not evidence that any guessed API request will perform the same action.

Inspect ownership and automation effects

Open the master after execution and compare it with the approved values. Zoho documents that attachments, notes and activities transfer to the master. Inspect the information your team actually needs, including outstanding work and its owners.

Related-record ownership changes only under Zoho's documented conditions. Check the current merge guidance for the exact case and inspect the actual related records. Do not assume choosing a master owner assigns every linked item to that person.

Review automation effects from evidence. Check relevant tasks, workflow history and record values instead of assuming the merge either triggers everything or triggers nothing. Investigate a missing follow-up separately from the identity merge.

Retain the review sheet with the surviving ID and verification result. If something is missing, record the specific item and escalate promptly; do not describe the merge as undoable. Finish when the remaining record is accurate, its relationships make sense and the next owner can continue the work.

Get help with this CRM task

For help with a reviewed duplicate-cleanup process, contact zsetup. Include the matching criteria, surviving-record policy and relationships you must preserve. Share redacted examples rather than live customer details or credentials.

Our Zoho CRM migration and data work service explains the scope we can discuss and how the work is checked.