Skip to main content

​
What merging does

Merging combines duplicate records into one. You pick the record to keep (the primary, or survivor) and the records to merge into it (the duplicates). Reevo moves their data onto the survivor, then archives them. You can merge up to 10 records at a time: the primary plus as many as 9 duplicates. Use merge when the same company or person exists twice in your CRM, for example “Acme Inc.” and “Acme Corporation”, or “Jane Smith” and “J. Smith”. Merging is available for accounts and contacts, and both use the same guided wizard. The merge wizard gives you control over what carries forward: you resolve field-level conflicts, decide which values win, and review every linked record before anything changes.
Merging cannot be undone. The duplicate records are archived and their data is folded into the survivor. Always use the final preview step to confirm before you merge.

​
Before you start

You need edit access to the records you want to merge. If you cannot edit a record, the Merge action does not appear on it. Merging is available on account and contact records only. Every record in a merge must be the same type. You cannot merge an account into a contact.

​
How to merge records

  1. Open the detail page of either record you want to merge.
  2. Open the More actions menu (top right of the record) and select Merge.
  3. The merge wizard opens on Select records. Work through its four steps below.

​
Step 1: Select records

This step is titled Select the records you want to merge. Choose which record survives, and which ones merge into it.
  • The primary record is the survivor. It keeps its ID and is marked with a star.
  • Every other record listed is a duplicate. Each one is merged into the primary, then archived.
Use the control on each row to set which record is primary. Click Add account or Add contact to bring in more candidates, up to the limit of 10 records total. Once you reach the limit, the add button is disabled.
Every other record in the list is merged into the primary by default. Remove any record you don’t want merged before you continue. A running count under the list tells you how many records will merge.
If Reevo has more suggested duplicates than the wizard can take at once, it shows the top candidates and notes that you should merge these, then reopen the wizard to review the rest.

​
Step 2: Review fields

This step is titled Review and resolve field conflicts. A subheading shows how the primary will look after merging, with a badge counting the fields where values disagree. Each field appears as its own card showing:
  • The field name.
  • Result: the value the merged record will have, based on your current choice.
  • A count of how many distinct values the records hold for that field.
  • A row of buttons, one per distinct value, ticked on the one currently winning and starred on the value that came from the primary. Where several records share a value, the button shows a multiplier such as ×3.
Click any value button to make it the result. Where a field is empty on some records, one button is labelled Empty, so leaving the field blank is a deliberate choice rather than an accident. By default you see only fields where values disagree. Select View all fields to see every field, or Show only conflicts to collapse back. To compare the records side by side for a single field, select Compare all N records on its card, then Hide records to close it again. For editable fields you can type a custom value instead of picking any of the offered ones.
Fields that Reevo calculates for you (such as rollups and other read-only fields) are shown for reference but cannot be edited or resolved. Their value is derived automatically after the merge.
For fields that point to another record (such as Owner, Owner Team, or Created By), the value buttons show the linked record as a chip with its name, not a raw ID. This lets you see exactly which person or team each option refers to while you choose a winner, without leaving the wizard.

​
Step 3: Review linked records

This step shows what happens to the records connected to each record being merged, and lets you resolve association-level conflicts. Role conflicts. When records disagree on a role, the wizard surfaces it so you can pick the value to keep on the merged record. For an account merge this appears as Contact role conflicts (a contact holding a different role on each account). For a contact merge it appears as Account role conflicts (contacts holding a different role on the same account). Records being carried forward. Below the conflicts, the wizard lists the linked records that will move to the merged record, such as contacts, opportunities, and custom-object records. There is one section per record being merged in, headed Records carried forward from that record’s name. Everything listed here is preserved on the survivor.

​
Custom association transfer

Custom associations on each duplicate record are transferred to the survivor as part of the merge. The links are copied onto the surviving record and removed from the archived ones, so associations to your custom objects are never lost.

​
Step 4: Preview and merge

The final step summarizes the merge before you commit: the surviving record, the records being archived, and totals for what moves across (records merged, contacts, opportunities, and activities). Below that, a Fields section lists the values that will appear on the merged record, showing the first six with an option to see the rest. Review the summary, then start the merge. Most merges finish within a minute. You can track progress from the notification Reevo posts, or from the job status page under Settings > Integrity Jobs.

​
After the merge

  • The duplicate records are archived, not deleted. Reevo does not hard-delete records during a merge, so history is preserved.
  • Associations, activity history, contacts, opportunities, and custom-object links are consolidated onto the surviving record.
  • Every field the merge changed on the surviving record is tagged in Field History with a Data integrity job source. Open Field History on the record to see which values changed and open the merge job that made the change.

​
Troubleshooting / FAQs

No. A merge cannot be reversed once it runs. The duplicates are archived and their data is folded into the survivor. Use the Preview and merge step to confirm everything is correct before you start.
Pick the record you want to keep as the system of record, usually the one with the correct ID, the cleaner data, or the wider set of associations. You resolve individual field values separately in the Review fields step, so choosing a primary does not lock you into all of its values.
Their field values are available to select in the Review fields step, and their linked records (contacts, opportunities, custom-object associations, activity history) are carried forward to the survivor. The records themselves are then archived.
Fields that Reevo calculates automatically (rollups and other read-only fields) cannot be resolved by hand. They are shown for reference, and their value is recomputed on the merged record after the merge.
Merge requires edit access to the record, and is available on accounts and contacts only. If you do not have edit permission, the action is hidden. Ask your admin if you believe you should have access.
Open Field History on the surviving record. Fields changed by the merge carry a Data integrity job source that links to the merge job, so you can trace exactly what was updated and by which merge.
Most merges complete within a minute. Larger records with many linked items can take a little longer. Reevo notifies you when the job finishes.
Up to 10: the primary plus as many as 9 duplicates. Once you reach that, the button to add another record is disabled. If a group of duplicates is larger than 10, merge the first batch, then reopen the wizard to work through the rest.
Yes. Every record other than the primary is merged in by default, so remove any you don’t want included before you continue. The count under the list tells you how many will merge.