Duplicate relations can appear in your CRM despite careful data entry and checks. The merge feature helps you combine two records by moving all relevant data into one correct relation and removing the duplicate safely. You might use this when the same organisation or person has been created more than once. By following this guide, you will be able to merge duplicate relations while keeping important history and linked records intact.
Table of Contents
What Does Merging Relations Do?
Why Or When Should You Merge Relations?
Step By Step Instructions
What To Check Before You Merge
Quick Summary
What Does Merging Relations Do?
Merging relations allows you to transfer data from a duplicate relation into the correct one. This includes field data, linked contacts, activities, and time records. Once all data has been moved, the remaining duplicate relation can be deleted. This process helps keep your CRM clean and accurate without losing important information.
Why Or When Should You Merge Relations?
You should merge relations when the same organisation or person exists more than once in Tribe. Duplicate records can cause confusion, incomplete reporting, and data inconsistencies. Merging ensures all history and linked records are stored in a single, correct relation.
Step By Step Instructions
Open the relation record you want to keep or review first.
Click the Dot Menu and select Merge.
Search for the duplicate relation you want to merge with. The currently opened relation is automatically excluded from the results.
Review the comparison screen showing both relations side by side.
Use Copy All Non-Conflicting Fields To… to move matching field data where no conflicts exist.
Use Move All To… to transfer linked records such as contacts, activities, and time records.
Review the header and tabs to confirm all required data has been moved to the correct relation.
Once the data is correctly placed, open the Dot Menu on the remaining duplicate relation and select Delete.
Note: Any field changes made during the merge are saved immediately, just like normal edits in Tribe.
What To Check Before You Merge
Merging is only possible between relations of the same type, such as organisation to organisation or person to person. You cannot merge different relation types or activities. If a relation has an external ID from a financial integration, this ID is not transferred during a merge. Make sure the relation connected to your financial system remains as the main record.
You must also have the correct permissions and edit rights for both relations and their linked activities to complete a merge.
Quick Summary
Merging duplicate relations allows you to combine data into a single, accurate record. You can move field data and linked history before deleting the duplicate safely. This process helps keep your Tribe CRM organised and reliable for everyday use.