TL;DR
- A merged record keeps one owner, usually the owner of the record chosen as primary.
- Most CRMs start from the primary record's values, and some let you pick the owner in the merge.
- The wrong surviving owner moves a customer to another rep, a former employee or a placeholder user.
- An owner rule, like "active owner with the most recent activity wins", keeps bulk merges consistent.
- Dedupely keeps the primary record's owner unless your owner rule says otherwise, with a preview first.
When you merge duplicates, the merged record usually keeps the owner of the record that wins the merge, the one chosen as primary. A record holds one owner. If the duplicates belong to different people, one of them loses the customer, unless you choose the owner separately.
That's easy to miss in a cleanup. You pick the primary record for its email, its history or its age, and the owner comes along with it. Weeks later, a rep asks why their account now belongs to someone else.
In this post, you'll see what HubSpot, Salesforce, Pipedrive, Close, Nimble and Google Contacts do with the owner when records merge and why it matters. You'll also see how to decide which owner wins before you merge in bulk.
What each CRM does with the owner
Most CRMs' merge help pages don't single out the owner, so it follows the general rule for field values. Nimble is the exception: its merge window lets you set the contact owner.
| CRM | How values are chosen in a merge | What it means for the owner |
|---|---|---|
| HubSpot | The primary record's property values are selected by default, and you can click other values to keep. If the primary record has no value, the secondary record's value is used. Records merge two at a time. | The primary record's owner stays by default, unless you pick the other one or the primary has none. For tickets, HubSpot keeps the owner of the most recently updated conversation. |
| Salesforce | You select one principal record, then choose the field values you want to keep. Up to three records per merge. | The help page doesn't name the owner, so check which owner value is selected before you merge. |
| Pipedrive | The primary item's information is prioritized when the items conflict. The owner is shown in the duplicate details before merging. | The help page doesn't say which owner the merged item keeps, so check the preview before you confirm. |
| Close | You merge two leads, and one is kept as the winner by a rule you pick: created first, most recent status change or highest-priority status. | Close has no built-in lead owner. Teams add a custom User field, often called "Lead Owner". The help page doesn't say which value a merge keeps, so check the field after merging. |
| Nimble | Up to five contacts at a time. You choose the primary contact and which data remains. | The merge window includes the contact owner, so you choose it as part of the merge. |
| Google Contacts | Merge & fix combines duplicate contacts in your account. | Contacts have no owner field. Each contact belongs to the Google account it's saved in. |
As of October 2026, from HubSpot's Merge records article, Salesforce Help (Merge duplicate accounts and Merge duplicate contacts) and Pipedrive's support center (Merge duplicates). Close: Finding and merging duplicates and Lead assignment. Nimble: How to merge duplicate contacts.
Merging accounts in Salesforce also takes the right access. You must be an admin, the account owner or a user above the account owner in the role hierarchy.
Why the surviving owner matters
The owner is the person the CRM shows as responsible for the customer. When the wrong owner survives, the effects show up in places nobody connects to the cleanup.
Commissions and credit
Reports that credit revenue or activity by owner now credit someone else. If two reps both worked the account, one of them disappears from it.
Territories and routing
Accounts assigned by region or segment can land outside their territory. Routing and assignment rules that look at the owner then send new leads and tasks to the wrong person.
Former employees and placeholder users
The oldest record often belongs to someone who left, or to an import or integration user. If the oldest record wins, so does that owner, and the customer ends up with nobody. How to handle those records is covered in what to do with duplicates owned by former employees.
Follow-ups
Tasks, reminders and notifications go to the record's owner. With the wrong owner, follow-ups reach someone who doesn't know the customer.
What happens to linked deals, tasks and activities
When records merge, what's linked to them generally moves to the record that survives. HubSpot's help page says the timeline activities and associations of both records appear on the merged record. Salesforce's developer documentation says the main record becomes the new parent of the merged records' related records.
Deals, opportunities and tasks have their own owner fields, separate from the contact's or company's owner. So the owner decision for the merged contact or company is one question, and who owns each linked deal is another. Check both when two reps are involved.
As of October 2026, from HubSpot's Merge records article and Salesforce's developer guide (merge call reference).
How to decide which owner wins
Ownership is a sales decision, so agree on the rule with sales leadership or RevOps before you merge. Then write it down per object, since deals and companies may need different rules.
| Rule | When it fits |
|---|---|
| The owner with the most recent activity wins | Teams where the person talking to the customer now should keep them |
| Only active users can win | Every team. Former employees, placeholder users and blank owners should never win |
| The owner with an open deal wins | Sales-led teams, so an open opportunity stays with the rep working it |
| The territory owner wins | Teams that assign accounts by region, segment or account size |
| Send it to a person | Two active reps who both work the account, or any commission dispute |
Rules can stack, and the order matters. Some teams give the account to whoever contacted the company in the last 90 days, and send the rest to a person.
Check ownership before you merge in bulk
A few checks catch most ownership problems before they happen.
- Reassign records owned by people who left. Then the merge only chooses between people who still work there.
- Find the sets where owners differ. Sets with one owner have no ownership decision to make. Review the sets with different owners first.
- Preview a sample. Before merging a page of duplicates, check which owner survives in a few of them, including your edge cases.
- Keep the original owners. Treat every merge as permanent, and keep a record of each record's original owner in case one needs to be reassigned later.
Two reps working one account is often a sign of duplicates in the first place, as covered in why two sales reps end up working the same account.
How to keep the right owner when you merge with Dedupely
In Dedupely, the merged record keeps the owner of the primary record, unless a rule on the owner field says otherwise. A rule can make former employees and placeholder users always lose, and a blank owner never overwrites a filled one. You can filter for the matches where owners differ, check the surviving owner in the preview and send real conflicts to review. Linked deals, tasks and activities move to the record that's kept. The full setup is in the playbook Merging Duplicates Without Breaking Ownership.
Decide the owner before the merge decides it
A merge keeps one owner, and by default that's the owner of whichever record wins. In most CRMs that starts with the primary record. In Salesforce and Nimble, you choose it in the merge.
A cleanup that leaves ownership to chance moves customers to the wrong rep, to people who left and to placeholder users. An agreed owner rule keeps customers with the people who work them. So does keeping inactive owners from winning and reviewing sets with two reps.
Frequently asked questions
Which owner does a merged record keep in HubSpot?
By default, the primary record's owner. HubSpot selects the primary record's property values, and you can click the other record's values to keep them instead. If the primary record has no owner, the secondary record's value is used. For tickets, HubSpot keeps the owner of the most recently updated conversation.
Which owner does a merged account keep in Salesforce?
The one selected in the merge. In Salesforce, you choose a principal record and then the field values you want to keep, for up to three records. To merge accounts, you must be an admin, the account owner or a user above the account owner in the role hierarchy.
What happens to tasks and activities when records merge?
They generally move to the record that survives. HubSpot shows the timeline activities and associations of both records on the merged one. Salesforce makes the main record the parent of related records. Tasks and deals have their own owner fields, so check those separately.
Can a merge give a customer to a former employee?
Yes. If the record that wins belongs to someone who left, the merged record keeps that owner. That often happens when the oldest record wins. Reassign records owned by former employees before you merge, or use an owner rule that keeps inactive users from winning.
Can I change the owner after a merge?
Yes. The owner is a field like any other, so you can reassign the merged record in your CRM. The merge itself can't be undone in most CRMs. Keep a record of each original owner before a large merge, in case you need it later.
Or sign up with Google
