# Merging Contacts

**URL:** <https://community.hubspot.com/t/merging-contacts/2133>\
**Category:** CRM\
**Created:** [May 24, 2017, 3:50pm UTC](https://community.hubspot.com/t/merging-contacts/2133 "2017-05-24T15:50:01Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![realizeit](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/realizeit/32/102437_2.png) [@realizeit](https://community.hubspot.com/u/realizeit)\
**Post date:** [May 24, 2017, 3:50pm UTC](https://community.hubspot.com/t/merging-contacts/2133/1 "2017-05-24T15:50:01Z")

</div>

When I merge two contacts, it would be nice if the newly merged document included all the data of the two. I just did a merge and lost the phone number, job title, and all the other info that I’d spent much time collecting. A real PITA.

---

<div class="post-metadata">

**Author:** ![Phil\_Vallender](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/phil_vallender/32/48924_2.png) [@Phil\_Vallender](https://community.hubspot.com/u/Phil_Vallender)\
**Post date:** [May 24, 2017, 6:53pm UTC](https://community.hubspot.com/t/merging-contacts/2133/2 "2017-05-24T18:53:52Z")

</div>

Hi @realizeit

The contact object in HubSpot only has one of each main property inside. So, when merging two contacts, losing some data is possible and is the intended behaviour of the app.

For most contact properties, merging two contacts will result in the fields that have updated most recently being kept. Full details on the merge function are here: [What happens when I merge two contacts?](https://knowledge.hubspot.com/articles/KCS_Article/Contacts/What-happens-when-I-merge-two-contacts)

Hope that helps.

---

<div class="post-metadata">

**Author:** ![realizeit](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/realizeit/32/102437_2.png) [@realizeit](https://community.hubspot.com/u/realizeit)\
**Post date:** [June 2, 2017, 1:40pm UTC](https://community.hubspot.com/t/merging-contacts/2133/3 "2017-06-02T13:40:49Z")

</div>

But..I don’t like the “intended behavior of the app.” %-)

---

<div class="post-metadata">

**Author:** ![Evans4316](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/evans4316/32/101739_2.png) [@Evans4316](https://community.hubspot.com/u/Evans4316)\
**Post date:** [September 12, 2018, 4:20pm UTC](https://community.hubspot.com/t/merging-contacts/2133/4 "2018-09-12T16:20:07Z")

</div>

I don’t like the solution either…Especially if I want to designate one Contact as the primary and then merge the second Contact into it. Right now…the Contact with the most current activity is designated as the Primary arbitrarily (or by Hubspot design).

At a minimum, it would be nice if it created a note or something. I think more work is needed here.

---

<div class="post-metadata">

**Author:** ![Gameblr-Vincent](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/gameblr-vincent/32/82797_2.png) [@Gameblr-Vincent](https://community.hubspot.com/u/Gameblr-Vincent)\
**Post date:** [January 23, 2019, 8:18am UTC](https://community.hubspot.com/t/merging-contacts/2133/5 "2019-01-23T08:18:28Z")

</div>

Some fields (including lists) are just overrided ; it is not the most recent one kept up.

For example, if I merge a contact being part of a list into a contact without list, the result will have no list.

That makes no sens !

Best would be, in case of conflict of unruled case, to ask to the client : pop-in with two tables, primary and secondary info ; keep or don’t.

Best example is the conflict resolution of GIT, your developers must know about it  
 ![16x16_smiley-happy.png.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/2/22d5e40d253def47f5f4ea7f0e3e70be19010689.png)

---

<div class="post-metadata">

**Author:** ![MCollins38](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@MCollins38](https://community.hubspot.com/u/MCollins38)\
**Post date:** [June 5, 2025, 3:56pm UTC](https://community.hubspot.com/t/merging-contacts/2133/6 "2025-06-05T15:56:22Z")

</div>

This should not be the case with properties that allow for multiple selections. That defeats the purpose of a property like that, if it can be overwritten. This seems common sense, that if I am choosing to create a property that will allow for multiple data points, that it should actually allow for those multiple data points to be retained when it is merged.

---

<div class="post-metadata">

**Author:** ![tankney](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tankney/32/56182_2.png) [@tankney](https://community.hubspot.com/u/tankney)\
**Post date:** [June 17, 2019, 5:06pm UTC](https://community.hubspot.com/t/merging-contacts/2133/7 "2019-06-17T17:06:42Z")

</div>

Merging contacts is always a horrible task for me. In a perfect world, I could merge through a screen that shows the properties for contact 1 on the left and contact 2 on the right and I can select which fields I would like to keep. Keeping the most up to date field is not always the best or relevant information to keep.

---

<div class="post-metadata">

**Author:** ![Evans4316](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/evans4316/32/101739_2.png) [@Evans4316](https://community.hubspot.com/u/Evans4316)\
**Post date:** [June 17, 2019, 6:53pm UTC](https://community.hubspot.com/t/merging-contacts/2133/8 "2019-06-17T18:53:22Z")

</div>

I so agree!! Drives me crazy~

---

<div class="post-metadata">

**Author:** ![deborahfelicio](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/deborahfelicio/32/91832_2.png) [@deborahfelicio](https://community.hubspot.com/u/deborahfelicio)\
**Post date:** [July 15, 2019, 9:25am UTC](https://community.hubspot.com/t/merging-contacts/2133/9 "2019-07-15T09:25:48Z")

</div>

totally agreed! We have some serious issues with losing info as our check boxes gets replaced rather than merged or combined. Simpler CRMs (we came from Agile CRM) had that option and it was great.

---

<div class="post-metadata">

**Author:** ![Rachel\_KL](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rachel_kl/32/57633_2.png) [@Rachel\_KL](https://community.hubspot.com/u/Rachel_KL)\
**Post date:** [April 9, 2020, 10:46pm UTC](https://community.hubspot.com/t/merging-contacts/2133/10 "2020-04-09T22:46:33Z")

</div>

I really need the ability to “pick and choose” which fields overwrite when merging. Sometimes I want info from contact a and sometimes I want other info from contact b. Merging them together should give me the ability to have the best of both worlds, or in this case, contacts. I don’t want the most recent. I want what’s accurate or what most accurately applies to a contact.

---

<div class="post-metadata">

**Author:** ![Evans4316](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/evans4316/32/101739_2.png) [@Evans4316](https://community.hubspot.com/u/Evans4316)\
**Post date:** [April 10, 2020, 12:25am UTC](https://community.hubspot.com/t/merging-contacts/2133/11 "2020-04-10T00:25:52Z")

</div>

I totally agree on this one! Well said Rachel!

> * * *
> 
> [@Rachel\_KL](https://community.hubspot.com/t5/user/viewprofilepage/user-id/107401) wrote:
> 
> I really need the ability to “pick and choose” which fields overwrite when merging. Sometimes I want info from contact a and sometimes I want other info from contact b. Merging them together should give me the ability to have the best of both worlds, or in this case, contacts. I don’t want the most recent. I want what’s accurate or what most accurately applies to a contact.
> 
> * * *

---

<div class="post-metadata">

**Author:** ![joseph\_cone](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/joseph_cone/32/22074_2.png) [@joseph\_cone](https://community.hubspot.com/u/joseph_cone)\
**Post date:** [February 17, 2021, 2:32am UTC](https://community.hubspot.com/t/merging-contacts/2133/12 "2021-02-17T02:32:10Z")

</div>

Adding my two cents here to keep this conversation alive… we have many contacts that we NEED to be able to manually pick which property should stay on the merged contact. Most recent does **not necessarily** = most accurate. Even a more basic CRM like Keap allows for this:

![]()

Please HubSpot product team, make it so.

---

<div class="post-metadata">

**Author:** ![TitiCuisset](https://avatars.discourse-cdn.com/v4/letter/t/8baadc/32.png) [@TitiCuisset](https://community.hubspot.com/u/TitiCuisset)\
**Post date:** [February 17, 2021, 9:01am UTC](https://community.hubspot.com/t/merging-contacts/2133/13 "2021-02-17T09:01:31Z")

</div>

Hi [@joseph\_cone](https://community.hubspot.com/t5/user/viewprofilepage/user-id/140663)

Thank you for reaching out.

This is not possible at this stage within HubSpot, I’d recommend upvoting [this Idea](https://community.hubspot.com/t5/HubSpot-Ideas/Choose-which-properties-to-keep-when-merging-contacts/idi-p/302484) in our [Ideas Forum](https://community.hubspot.com/t5/custom/page/page-id/ideaslandingpage) regarding this. You can also subscribe to the idea ( **Options \> Subscribe** ) to get notified if the status changes.

Thank you

Best

Tiphaine

---

<div class="post-metadata">

**Author:** ![BSingh36](https://avatars.discourse-cdn.com/v4/letter/b/3bc359/32.png) [@BSingh36](https://community.hubspot.com/u/BSingh36)\
**Post date:** [May 4, 2026, 3:15pm UTC](https://community.hubspot.com/t/merging-contacts/2133/14 "2026-05-04T15:15:40Z")

</div>

Hi Tiphaine,

Thank you for your response and for clarifying.

I understand that this functionality isn’t currently available in HubSpot. I’ll go ahead and upvote the idea in the Ideas Forum and subscribe for updates on any progress.

Appreciate your guidance on this.

Best regards,  
Joseph

---

<div class="post-metadata">

**Author:** ![RBozeman](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rbozeman/32/8786_2.png) [@RBozeman](https://community.hubspot.com/u/RBozeman)\
**Post date:** [June 14, 2023, 6:06pm UTC](https://community.hubspot.com/t/merging-contacts/2133/15 "2023-06-14T18:06:05Z")

</div>

Hi @realizeit,

Data retention features when merging still need to be fully fleshed out. I’ve seen this on the HubSpot ideas forum several times. [HubSpot keeps the most recent value](https://knowledge.hubspot.com/crm-setup/merge-records) across the duplicate record, except for a handful of fields where they have specific rules for how those fields are handled. There is no way to customize this as far as I know without custom coding a solution. It is also potentially possible through Ops Hub, but you’d have to build out your rules and code them into there as well.

Also wanted to mention that Insycle could help with this. Full disclosure, I work for Insycle.

With Insycle, you can set rules for choosing the resulting post-merge master record, or even choose how to retain data in each and every field. You can set rules on the field-level. For example, you could instruct Insycle to combine and append all values held by the duplicate records for a custom multi-select picklist field, so that you don’t lose selections when HubSpot chooses the data that has been most recently updated.

[Here](https://blog.insycle.com/data-retention-merging-duplicates) is a recent article we published on data retention when merging that you might find helpful. If you have any questions about it let me know.

Ryan

---

<div class="post-metadata">

**Author:** ![kvlschaefer](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kvlschaefer/32/71076_2.png) [@kvlschaefer](https://community.hubspot.com/u/kvlschaefer)\
**Post date:** [June 14, 2023, 7:53pm UTC](https://community.hubspot.com/t/merging-contacts/2133/16 "2023-06-14T19:53:29Z")

</div>

Hi @RBozeman,

Thank you for sharing this insight with @RBozeman!

Best,

Kristen

---

<div class="post-metadata">

**Author:** ![musabmalik](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@musabmalik](https://community.hubspot.com/u/musabmalik)\
**Post date:** [January 2, 2025, 10:26am UTC](https://community.hubspot.com/t/merging-contacts/2133/17 "2025-01-02T10:26:59Z")

</div>

I completely understand your frustration. Losing valuable information after spending time collecting it is definitely not ideal. It would be great if the merge process allowed for retaining all data or gave an option to choose what to keep. Hopefully, this feedback will lead to improvements.

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 7, 2025, 5:23am UTC](https://community.hubspot.com/t/merging-contacts/2133/18 "2025-03-07T05:23:10Z")

</div>

Hi @realizeit and everyone,

HubSpot has launched a public beta (Settings \> Product updates) that provides more clarity around what’s happening during the merge 🙂

> * * *
> 
> Data Quality
> 
> ### Property Control in Record Merges
> 
> March 6, 2025
> 
> ### **What is it?**
> 
> You can now select which properties will be retained on the final record when merging records, giving you unprecedented control over your data consolidation process.
> 
> ### **Why does it matter?**
> 
> As businesses grow, managing duplicate records becomes increasingly complex. By providing granular control over property selection during merges, this new tool allows users to maintain data integrity with precision.
> 
> It offers the flexibility to tailor the merge process to specific business needs, ensuring that every data consolidation aligns perfectly with your organization’s data management strategy.
> 
> ### **How does it work?**
> 
> To access this functionality, customers should navigate to a record page within HubSpot. Customers will now see a new modal when they attempt to merge, replacing the previous version.
> 
> This enhanced interface allows you to review the properties of records side-by-side and select the winning properties for your final, merged record.
> 
> By choosing which data points to keep, you can ensure that the most accurate and up-to-date information is preserved during the merge process.

 ![karstenkoehler_1-1741324901565.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/4/c/4c5b8eda118f6641a061610faef0fef258c3a839.png)

> ### **Who gets it?**
> 
> All hubs and tiers
> 
> * * *

Have a great day!
