Merged Records Creating New Record IDs

[ChrisDellen]

Our team has been confused by the Merge Contact Record Process.

The HubSpot user interface suggest that Contact A will be Merged Into Contact B. However, what happens is that Contact A and Contact B get combined into Contact C resulting in a brand new Record ID.

Creating a new contact ID creates significant integration challenges.

It would be fabulous if HubSpot would consider updating the Merge Behavior to update Contact B and maintain its original record ID.

[STierney · Accepted solution]

Hey @ChrisDellen - thanks for posting in the Community!

As noted here, "a new unique Record ID is created for the resulting merged record. The original Record ID values will still point to the new merged record, so searching records with the original Record ID will return the new one." Because I can definitely understand the value in your thought process, I might recommend posting the need for this in our Ideas Forum! This would allow other users to upvote your idea and allow for our Products team to see it directly!

Shane, Community Manager

[CMenikheim]

I am also in favor of keeping the Record ID. We used to leverage the Record ID as a point-of-reference for other systems in sales, billing, support, etc.

Now, we cannot rely on that value as being immutable while also maintaining a healthy CRM. There are times where a customer may e-mail from an updated domain and hubspot automatically creates a new company for them. If we merge those records, we have to update so many other systems across the company to reflect the new Record ID. However, we cannot update historic records ( invoices from years past, for example ).

[HybitHi · Accepted solution]

See this post of mine: https://community.hubspot.com/t5/CRM/Merging-Company-or-Contacts-Forces-New-Record-ID-for-Resulting/...

And also read the entired discussion.

[STierney]

Hey @ChrisDellen - thanks for posting in the Community!

It looks like the thread linked in @HybitHi's reply provides a lot of relevant context to your idea above. Feel free to give it a read and follow-up should you have any questions!

Shane, Community Manager

[STierney · Accepted solution]

Hey @ChrisDellen - thanks for posting in the Community!

As noted here, "a new unique Record ID is created for the resulting merged record. The original Record ID values will still point to the new merged record, so searching records with the original Record ID will return the new one." Because I can definitely understand the value in your thought process, I might recommend posting the need for this in our Ideas Forum! This would allow other users to upvote your idea and allow for our Products team to see it directly!

Shane, Community Manager