# Identify Merged Contact

**URL:** <https://community.hubspot.com/t/identify-merged-contact/16205>\
**Category:** HubSpot Ideas\
**Tags:** object\
**Created:** [September 12, 2019, 2:19am UTC](https://community.hubspot.com/t/identify-merged-contact/16205 "2019-09-12T02:19:06Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![achia](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/achia/32/53612_2.png) [@achia](https://community.hubspot.com/u/achia)\
**Post date:** [September 12, 2019, 2:19am UTC](https://community.hubspot.com/t/identify-merged-contact/16205/1 "2019-09-12T02:19:06Z")

</div>

HI team,

Currently, the de-duplication tool allows users to merge contacts. This is currently an irreversible merge, which is understandable as some information is lost during the merge. However, it would be great if there could be a way to identify which contacts have been merged. Perhaps by creating a ‘last merged’ contact property that can be filtered by or the ability to filter for ‘Email address is more than one’.

I think that if users can at least identify merged contacts, they will have the option to manually unmerge the contacts by creating new records for the contacts that have merged.

---

<div class="post-metadata">

**Author:** ![Melly2022](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/melly2022/32/81147_2.png) [@Melly2022](https://community.hubspot.com/u/Melly2022)\
**Post date:** [September 2, 2020, 7:55pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/2 "2020-09-02T19:55:37Z")

</div>

I second this suggestion - currently working on thousands of merges and would be great if we can identify those who have had a merge on their activity history for several reasons.

---

<div class="post-metadata">

**Author:** ![Dedicated](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dedicated/32/22307_2.png) [@Dedicated](https://community.hubspot.com/u/Dedicated)\
**Post date:** [December 27, 2020, 8:25pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/3 "2020-12-27T20:25:48Z")

</div>

I would love to have a property like this.

When merging two contacts, if the primary contact has no value for a property and the secondary contact does, then the secondary property value will populate the merged record, from what I understand.

If we have made a custom property to hold some email info that we find relevant, and then someone else at our company merges the contact into another contact that has a different email, the info on the merged contact will reflect an email with email info that refers to a different email. Having a property that lets us know that a merge happened, and which can automate certain updates/checks would help tremendously to make sure our data is reliable and consistent.

---

<div class="post-metadata">

**Author:** ![jpeluso](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jpeluso](https://community.hubspot.com/u/jpeluso)\
**Post date:** [April 13, 2021, 6:29pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/4 "2021-04-13T18:29:51Z")

</div>

This would come in extremely handy for something I am currently working through now. Upvoted! 👍

---

<div class="post-metadata">

**Author:** ![DHeywood](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dheywood/32/92090_2.png) [@DHeywood](https://community.hubspot.com/u/DHeywood)\
**Post date:** [June 23, 2021, 4:13pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/5 "2021-06-23T16:13:45Z")

</div>

this is really import for us when it comes to companies - we have an integration with other platforms that use this data and being able to identify when a company has been merged, either as it happens or through a report would be really helpful.

---

<div class="post-metadata">

**Author:** ![elanashama](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/elanashama/32/48165_2.png) [@elanashama](https://community.hubspot.com/u/elanashama)\
**Post date:** [February 15, 2022, 6:57am UTC](https://community.hubspot.com/t/identify-merged-contact/16205/6 "2022-02-15T06:57:18Z")

</div>

Definitely need to be able to see which contacts were merged!

---

<div class="post-metadata">

**Author:** ![jgillan](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jgillan/32/48165_2.png) [@jgillan](https://community.hubspot.com/u/jgillan)\
**Post date:** [April 5, 2022, 2:41pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/7 "2022-04-05T14:41:51Z")

</div>

Yes being able to seperate out the companies that have been merged by a merge date property would be super handy.

---

<div class="post-metadata">

**Author:** ![Kyle\_Turner](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kyle_turner/32/10180_2.png) [@Kyle\_Turner](https://community.hubspot.com/u/Kyle_Turner)\
**Post date:** [April 5, 2022, 3:01pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/8 "2022-04-05T15:01:28Z")

</div>

Same would be true for Merged Deals

---

<div class="post-metadata">

**Author:** ![RiccardoPisani](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/riccardopisani/32/104209_2.png) [@RiccardoPisani](https://community.hubspot.com/u/RiccardoPisani)\
**Post date:** [July 26, 2022, 6:04am UTC](https://community.hubspot.com/t/identify-merged-contact/16205/9 "2022-07-26T06:04:17Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![Beata\_W](https://avatars.discourse-cdn.com/v4/letter/b/4da419/32.png) [@Beata\_W](https://community.hubspot.com/u/Beata_W)\
**Post date:** [August 26, 2022, 8:16am UTC](https://community.hubspot.com/t/identify-merged-contact/16205/10 "2022-08-26T08:16:28Z")

</div>

Definitely needed

---

<div class="post-metadata">

**Author:** ![AdrianaVargas](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/adrianavargas/32/56947_2.png) [@AdrianaVargas](https://community.hubspot.com/u/AdrianaVargas)\
**Post date:** [August 30, 2022, 12:52am UTC](https://community.hubspot.com/t/identify-merged-contact/16205/11 "2022-08-30T00:52:34Z")

</div>

Gracias por la idea, estaría genial poder realizar listas de contactos combinados para poder filtrarlas en fechas específicas. Últimamente las hemos requerido.

---

<div class="post-metadata">

**Author:** ![APastran](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@APastran](https://community.hubspot.com/u/APastran)\
**Post date:** [November 21, 2022, 6:58pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/12 "2022-11-21T18:58:33Z")

</div>

Yesss, please.

---

<div class="post-metadata">

**Author:** ![Courtney\_Clark](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/courtney_clark/32/60590_2.png) [@Courtney\_Clark](https://community.hubspot.com/u/Courtney_Clark)\
**Post date:** [January 19, 2023, 10:27pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/13 "2023-01-19T22:27:01Z")

</div>

Yes, this is definitely needed and would be extremely helpful.

---

<div class="post-metadata">

**Author:** ![tmcginnis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tmcginnis/32/4408_2.png) [@tmcginnis](https://community.hubspot.com/u/tmcginnis)\
**Post date:** [April 12, 2023, 12:58pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/14 "2023-04-12T12:58:33Z")

</div>

+1 to this!

---

<div class="post-metadata">

**Author:** ![RFaurel](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rfaurel/32/29368_2.png) [@RFaurel](https://community.hubspot.com/u/RFaurel)\
**Post date:** [January 5, 2024, 5:41pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/15 "2024-01-05T17:41:49Z")

</div>

Same for merge tickets ! ✋

---

<div class="post-metadata">

**Author:** ![AStrong5](https://avatars.discourse-cdn.com/v4/letter/a/74df32/32.png) [@AStrong5](https://community.hubspot.com/u/AStrong5)\
**Post date:** [April 1, 2024, 5:16pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/16 "2024-04-01T17:16:40Z")

</div>

Yes, please! We have custom code written to merge contacts based on phone number but we get contacts merged over time that shouldn’t be (e.g. contacts all have the same phone number from their company in the standard phone number field). When I upload a list of contacts I want to send to, it would be helpful to be able to see how many are part of a merged record. Or a property as mentioned in this post where I can filter them out.

---

<div class="post-metadata">

**Author:** ![heath](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/heath/32/81915_2.png) [@heath](https://community.hubspot.com/u/heath)\
**Post date:** [June 13, 2024, 2:18am UTC](https://community.hubspot.com/t/identify-merged-contact/16205/17 "2024-06-13T02:18:03Z")

</div>

Much needed feature for [our company](https://plyco.com.au). With over 100K contacts and the recent addition of Operations Hub, the ability to segment merged customers will help identify and troubleshoot erroneous merges via an automated workflow.

---

<div class="post-metadata">

**Author:** ![jmbray](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jmbray/32/23574_2.png) [@jmbray](https://community.hubspot.com/u/jmbray)\
**Post date:** [June 19, 2025, 6:48pm UTC](https://community.hubspot.com/t/identify-merged-contact/16205/18 "2025-06-19T18:48:43Z")

</div>

+1. Would be helpful to somehow identify, filter, or build a list for contacts or any object for that matter that have been merged.

---

<div class="post-metadata">

**Author:** ![MVA15](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@MVA15](https://community.hubspot.com/u/MVA15)\
**Post date:** [July 9, 2025, 10:01am UTC](https://community.hubspot.com/t/identify-merged-contact/16205/19 "2025-07-09T10:01:15Z")

</div>

We need this to be able also to double check when a merge was done incorrect. I am searching for my contact since 30min with no luck and I was hoping there was a work around given here.

This is still a needed feature in 2025.
