> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/deduped/features/field-merge.md).
# Field Merge
With Field Merge, you can merge data at the individual field level from multiple records with precision. Evaluate and combine specific fields based on predefined criteria, such as selecting the most frequent entry, concatenating values, summing numeric fields, or creating a comprehensive list of all field values. This enables precise control over merging duplicate data based on field specifics.
Here are the results of all the [configured](https://docs.inogic.com/deduped/configuration/merge-settings/field-merge) Field Merge Criterion **(Append, Join, Add Up, Most Frequent Values).**
1. **Append:** Now you can easily merge data from the fields of subordinate records into a single field in the master record, separated by your chosen delimiter. **Example:** If you have a **master lead** record and several **subordinate lead records** that have different product interests. You can now combine all the product interests from these related records into one field in the master lead record, separated by a colon or any separator of your choice. In order to merge record fields based on the **“Append”** merge criterion, follow the steps below:
* Navigate to **Sales Hub** → **Lead Entity** → Select and open the record for which you want to detect and merge duplicates based on the **'Append'** field merge criteria → Click on the **'Show Duplicates'** button.
* Select all the duplicate records and click on the **“Merge”** button.
* Now click **“Finish”** to combine all the values from the subordinate records into a single master record.
* Now all the values (Product Interests) from the subordinate records will be combined in the **“Interested in products”** field of the master record.
2. **Join:** With this criterion, you can merge all the selected options from the multi-select option set fields of subordinate records with a master record. **Example:** If you have multiple lead records for the same person in your CRM, each with different **"Contact Preferences,"** you can merge these into a single, comprehensive list in the master lead record. By using the **Join** merging criterion, all selected preferences from the duplicate records are combined, ensuring no information is lost during the merge. In order to merge record fields based on the **“Join”** merge criterion, follow the steps below:
* Navigate to **Sales Hub → Lead Entity →** Select and open the record for which you want to detect and merge duplicates based on the **'Join'** field merge criteria → Click on the **'Show Duplicates'** button.
* Select all the duplicate records and click on **“Merge”** button.
* Now click **“Finish”** to combine all the options from the subordinate records in the master record.
* Now all the options (contact preferences) from the subordinate records will be combined in the **“Contact Preferences”** field of the master record.
3. **Add Up:** With this criterion, you can sum all the values in the numerical fields of the subordinate record with the master record while merging. **Example:** You have duplicate lead records for the same person in your CRM, each containing different budget values in the **“Budget”** field based on their product interests. Using the **Add Up** merging criterion, you can automatically sum these values into a single comprehensive total, which is then stored in the master lead record. In order to merge record fields based on the **“Add Up”** merge criterion, follow the steps below:
* Navigate to **Sales Hub → Lead Entity →** Select and open the record for which you want to detect and merge duplicates based on the **“Add Up”** field merge criteria → Click on the **'Show Duplicates'** button**.**
* Select all the duplicate records and click on the **“Merge”** button.
* Now click **“Finish”** to sum all the values (Budget Amount) from the subordinate records in the master record.
* Now all the values (Budget Amount) from the subordinate records will be summed up in the **“Budget Amount”** field of the master record.
4. **Most Frequent Value:** With this criterion, you can take the most common value among the master and subordinate records and set it in the master record while merging. **Example:** If your CRM has duplicate lead records for the same person, all with the same company name in the Company Name field. Using the Most Frequent Value merging option, you can ensure the company name that appears most often is retained in the master record after merging. In order to merge record fields based on the **“Most Frequent Value”** merge criterion, follow the steps below:
* Navigate to **Sales Hub → Lead Entity →** Select and open the record for which you want to detect and merge duplicates based on the **“Most Frequent Value”** field merge criteria → Click on the **'Show Duplicates'** button.
* Select all the duplicate records and click on the **“Merge”** button.
* Select the most common value (Company Name) among the master and subordinate records and click **“Finish”** to set it in the master record.
* Now the most common value from the subordinate and master records will be set in the master record.
5. **Value from Oldest Created Record:** With this criterion, you can select the field value from the oldest created record among the eligible duplicate records while merging. DeDupeD compares the Created On date of the records and selects the field value from the oldest record that contains a valid value.
**Example:** Suppose you have multiple duplicate Lead records for the same person, each containing a different Lead Source. By using the “Value from Oldest Created Record” merging criterion, you can retain the Lead Source from the Lead record that was created first. If the oldest record does not contain a value for the selected field, DeDupeD checks the next oldest record until a valid value is found. In order to merge record fields based on the “Value from Oldest Created Record” merge criterion, follow the steps below:
Navigate to **Sales Hub** → **Lead Entity** → Select and open the record for which you want to detect and merge duplicates based on the **“Value from Oldest Created Record”** field merge criterion → Click on the **“Show Duplicates”** button.
• Select all the duplicate records and click on the **“Merge”** button.
• Now click **“Finish”** to set the field value from the oldest created record in the master record.
• Now the field value (Lead Source) from the oldest created record will be set in the Lead Source field of the master record.
6. **Value from Latest Created Record:** With this criterion, you can select the field value from the latest created record among the eligible duplicate records while merging. DeDupeD compares the Created On date of the records and selects the field value from the latest record that contains a valid value.
**Example:** Suppose you have multiple **duplicate Lead records** for the same person, each containing a different email address. By using the **“Value from Latest Created Record”** merging criterion, you can retain the Email value from the Lead record that was created most recently. If the latest created record does not contain a value for the selected field, DeDupeD checks the next latest record until a valid value is found. In order to merge record fields based on the **“Value from Latest Created Record”** merge criterion, follow the steps below:
Navigate to **Sales Hub** → **Lead Entity** → Select and open the record for which you want to detect and merge duplicates based on the **“Value from Latest Created Record”** field merge criterion → Click on the **“Show Duplicates”** button.
• Select all the duplicate records and click on the “Merge” button.
• Now click “Finish” to set the field value from the latest created record in the master record.
• Now the field value (Email) from the latest created record will be set in the Email field of the master record.
7. **Value from Oldest Modified Record:** With this criterion, you can select the field value from the oldest modified record among the eligible duplicate records while merging. DeDupeD compares the Modified On date of the records and selects the field value from the oldest modified record that contains a valid value.
**Example:** Suppose you have multiple duplicate Lead records for the same person, each containing a different Industry. By using the **“Value from Oldest Modified Record”** merging criterion, you can retain the Industry value from the Lead record that was modified first. If the oldest modified record does not contain a value for the selected field, DeDupeD checks the next oldest modified record until a valid value is found. In order to merge record fields based on the **“Value from Oldest Modified Record”** merge criterion, follow the steps below:
Navigate to **Sales Hub** → **Lead Entity** → Select and open the record for which you want to detect and merge duplicates based on the **“Value from Oldest Modified Record”** field merge criterion → Click on the **“Show Duplicates”** button.
• Select all the duplicate records and click on the “Merge” button.
• Now click “Finish” to set the field value from the oldest modified record in the master record.
• Now the field value (Industry) from the oldest modified record will be set in the Industry field of the master record.
8. **Value from Latest Modified Record:** With this criterion, you can select the field value from the latest modified record among the eligible duplicate records while merging. DeDupeD compares the Modified On date of the records and selects the field value from the latest modified record that contains a valid value.
**Example:** Suppose you have multiple duplicate Lead records for the same person, each containing a different value in the Annual Revenue field. By using the **“Value from Latest Modified Record”** merging criterion, you can retain the Annual Revenue value from the Lead record that was modified most recently. If the latest modified record does not contain a value for the selected field, DeDupeD checks the next latest modified record until a valid value is found. In order to merge record fields based on the **“Value from Latest Modified Record”** merge criterion, follow the steps below:
Navigate to **Sales Hub** → **Lead Entity** → Select and open the record for which you want to detect and merge duplicates based on the **“Value from Latest Modified Record”** field merge criterion → Click on the **“Show Duplicates”** button.
• Select all the duplicate records and click on the “Merge” button.
• Now click “Finish” to set the field value from the latest modified record in the master record.
• Now the field value (Annual Revenue) from the latest modified record will be set in the Annual Revenue field of the master record.
This is how you can merge field values based on various field merging criteria.
