# How to Merge Duplicates Without Changing the Owner | Dedupely > Merging duplicates can hand a record to the wrong rep or a former employee. Choose which owner survives every merge, before you merge in bulk. - URL: https://dedupe.ly/knowledge-base/merging-duplicates-without-breaking-ownership - Section: knowledge-base - Site index: https://dedupe.ly/llms.txt - Any page: append `.md` to its URL for this plain-text form --- ## Merging Duplicates Without Breaking Ownership By [Gaby Salinas](https://www.linkedin.com/in/gbyslns) Updated October 30, 2026 Choose which owner survives each merge, so records never land with the wrong rep or a former employee. When two records for the same customer have different owners, only one owner survives the merge. If you don't decide which one, the record can move to another rep, a placeholder user or someone who left the company. In Dedupely, you control this with your Primary Record setting and a field-level Merge Rule for the owner field, and you check the result in the Merge Preview before you merge. ### Before you start - **Your owner list:** which users are active, which have left, and any placeholder users (like "Marketing" or "Unassigned"). - **Who decides ownership conflicts**, usually a sales manager or RevOps. See [Working as a Team in Dedupely](https://dedupe.ly/knowledge-base/working-as-a-team). ### Why does the owner change when you merge? Each record keeps one owner. When records merge, the surviving record takes the owner of whichever record wins, so: - A contact owned by an active rep can end up with the rep who created the duplicate. - A customer can end up with a former employee whose old record was the oldest. - A record can end up with a placeholder user from an import or integration. The owner is the person your CRM shows as responsible for the customer, so the wrong owner means the wrong person gets the follow-up. ### How to choose which owner survives - **Set your Primary Record.** In [Merge Rules](https://dedupe.ly/knowledge-base/merge-rules), the Primary Record decides the default for every field, including the owner. **Last Updated Record** usually keeps the record your team works on now. - **Add Lose Rules on the owner field.** Choose **Custom** on the owner field (for example **Contact owner**), then add a **Lose Rule** for each owner who should never win. For a former employee or a placeholder user: **When field** Contact owner, **Operator** is equal to, that user, **In Duplicate Search** All. For unassigned records: **When field** Contact owner, **Operator** is blank, so an unassigned record never wins over an assigned one. - **Remember the order.** Lose Rules run before Win Rules, and Win Rules run from top to bottom. ### How to check ownership before you merge - **Add the owner field to Visible Fields**, so you see each record's owner in the results. - **Open View Match Details** and check the **Merge Preview** column: it shows which owner will survive. - **Filter for conflicts:** add a filter with your owner field and **is unique across match**, in all records. It shows only the matches where every record in the match has a different owner, so you can review those first. Leave **Count blanks as a value** unchecked unless you want unassigned records to count as their own owner. See [Filters](https://dedupe.ly/knowledge-base/filters). ### What to do with real ownership conflicts Some conflicts aren't data problems. Two reps may both work the account. Don't merge those in bulk: - **Send them to Manual Review**, so the sales manager decides. See [Manual Review](https://dedupe.ly/knowledge-base/manual-review). - **Merge them one at a time with Custom Merge**, choosing the owner by hand in **View Match Details**. ### Example setup A sales team of 12 reps has duplicates from imports and two reps who left this year. - **Merge Rules:** Primary Record set to Last Updated Record. Contact owner on Custom: Lose Rules for the two former reps (is equal to), the "Imports" placeholder user (is equal to) and unassigned records (is blank). - **Visible Fields:** Owner and Last Activity Date. - **Review:** a copy of the search filtered on Contact owner **is unique across match** shows the conflicts. Those go to Manual Review for the sales manager every Friday. - **Merge:** the rest is bulk merged after checking the Merge Preview on the first page. ### Common mistakes - **Leaving ownership to the default.** The oldest record often belongs to someone who left. - **Reassigning former employees' records after merging.** Reassign them, or add a Lose Rule, before you merge. - **Bulk merging real conflicts.** If two reps both work an account, a person should decide. - **Forgetting deals.** Deals have their own owner. Check them too in [How to Dedupe Deals and Opportunities](https://dedupe.ly/knowledge-base/how-to-dedupe-deals-and-opportunities). ### FAQs about owners and merging - **Which owner does the merged record keep?** The owner of the record that wins: your Primary Record, unless a field-level rule on the owner field says otherwise. - **Can I make sure a former employee never wins?** Yes. Add a Lose Rule on the owner field: is equal to their user. - **Can I find the matches where owners differ?** Yes. Filter on the owner field with "is unique across match". - **Can I see the surviving owner before I merge?** Yes. The Merge Preview column in View Match Details shows it. - **What if the wrong owner already won?** Merge History shows the original values. Reassign the record in your CRM. See [I Merged the Wrong Records: What Now?](https://dedupe.ly/knowledge-base/i-merged-the-wrong-records) ### Next up [Merge Rules Set field-level rules for the owner and every other field.](https://dedupe.ly/knowledge-base/merge-rules) ### Still stuck? Our team helps on every plan and during the free trial, by chat, email or Zoom. - Need help? [Talk to support](https://dedupe.ly/contact) - Questions about plans? [Book a Zoom with sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales) - Reading this with a model? [Read this page as Markdown](https://dedupe.ly/knowledge-base/merging-duplicates-without-breaking-ownership.md) - Feeding it the whole site? [Read llms.txt](https://dedupe.ly/llms.txt) Behind the article ### Gaby Salinas Marketing Assistant at Dedupely Gaby Salinas came to CRM data from marketing and advertising, so she looks at duplicates from two sides: the match and merge logic behind them, and what they do to the people using the CRM, like the rep who calls a customer twice, the admin who gets blamed and the cleanup nobody wants to start. As Marketing Assistant at Dedupely, she follows how RevOps teams, end users, consultants and technical teams actually work with their data: the records they stop trusting, the workarounds they build and the moment they finally decide to clean up. What she finds shapes most of what Dedupely publishes. [Connect with Gaby on LinkedIn](https://www.linkedin.com/in/gbyslns) ### Get started for free 20 free trial merges and as much free support as you need to get your duplicates under control. [Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)[Try for free](https://v2.app.dedupe.ly/signup) [Or sign up with Google](https://v2.app.dedupe.ly/signup/google) Running CRM cleanup for clients? [See the Partner Program](https://dedupe.ly/become-a-partner) Skip to content