> 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/merge-duplicates-in-dynamics-365-crm/merge-duplicates-1.md).

# Merge Duplicates

The Merge Duplicates button allows CRM users to instantly merge multiple selected records directly from any Dynamics 365 grid, and duplicate detection runs.

This gives business users real-time control over data cleanup while DeDupeD ensures that relationships, history, and integrity are preserved.

**What this feature solves**

Native Dynamics 365 allows users to merge only one duplicate pair at a time.

DeDupeD’s Merge Duplicates button removes all those limitations:

You can now:

* Select up to 10 records
* Merge them even if they were not flagged as duplicates
* Control which record becomes the Master
* Control field-level data survival
* Preserve all relationships, activities, files, and history

All in one controlled workflow.

How to Merge Records Using “Merge Duplicates”

### **Step 1 – Select the records**

Go to any configured entity view (Contacts, Accounts, Leads, etc.)\
Select all records you want to merge using the checkboxes.

 Example:You select 5 Contact records.

<div data-with-frame="true"><figure><img src="/files/12OWFXU0Zizmh5dpXywU" alt=""><figcaption></figcaption></figure></div>

### **Step 2 – Click “Merge Duplicates”**

From the command bar, click: Merge Duplicates

&#x20;DeDupeD will detect that:

“These records were selected manually and may not be identified as duplicates…”

&#x20;Click **Yes** to proceed.

&#x20;This gives users full freedom to clean data even when native duplicate rules are incomplete.

<div data-with-frame="true"><figure><img src="/files/H8t08ZWc7PT8ijj6HVUF" alt=""><figcaption></figcaption></figure></div>

### Step 3 – Review & Select the Master Record

&#x20;The DeDupeD merge screen opens.

&#x20;You will see:

* One Suggested Master
* All other selected records displayed side-by-side

{% hint style="info" %}
**Note:** If the master deciding rules are applied for the entity, the master will be suggested based on the master deciding rule score.
{% endhint %}

&#x20;Choose the record that should become the Master — this will be the surviving CRM record.

&#x20;The Master will keep:

* All relationships
* All activities
* All history
* All connected records

### &#x20;**Step 4 – Choose which field values to keep**

&#x20;For every field (Name, Email, Address, Phone, etc.) you can:

* Select values from different records
* Or use **“Select all fields”** from one record

This gives you field-level control, which native CRM does not provide.

<div data-with-frame="true"><figure><img src="/files/avbVFhypMgGjZYOduMB2" alt=""><figcaption></figcaption></figure></div>

### **Step 5 – Finish the merge**

Click **Finish**.

DeDupeD shows a confirmation:

The selected relationships will be merged into the master record and duplicates will be deactivated.

Click **Continue**.

The merge begins.

<div data-with-frame="true"><figure><img src="/files/YBDmA773IOFefvs5IUKe" alt=""><figcaption></figcaption></figure></div>

### **Step 6 – Background merge of relationships**

You will see a message:

“Related records are being merged in the background…”

DeDupeD now:

* Reassigns activities
* Moves opportunities, cases, quotes, etc.
* Reconnects emails, notes, files
* Deactivates duplicate records

All without breaking data.

<div data-with-frame="true"><figure><img src="/files/nfy3G7F41VMo44Ck9l5j" alt=""><figcaption></figcaption></figure></div>

### **Step 7 – Verify the result**

Open any of the duplicate records.

You will see:

“This record has been merged with \[Master Record]”

The duplicate is now:

* Inactive
* Fully merged
* All its data moved to the master

<div data-with-frame="true"><figure><img src="/files/ovGwfIQwFHrlLDru5NM5" alt=""><figcaption></figcaption></figure></div>

### **Step 8 – Audit & reporting**

&#x20;Every merge is logged in DeDupeD Job Runs.

You can see:

* How many records were processed
* How many duplicates were merged
* Which master record was created
* When it happened
* Who executed it

This gives IT and Compliance teams full visibility.

<div data-with-frame="true"><figure><img src="/files/n9O8yQlBmb6hJiUqidSi" alt=""><figcaption></figcaption></figure></div>

{% hint style="success" %}
For further queries, reach out to us at <crm@inogic.com>
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inogic.com/deduped/features/merge-duplicates-in-dynamics-365-crm/merge-duplicates-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.