Merge Function Logic

[EmmaSchmitt]

Please can Hubspot confirm this is the correct behaviour, or provide a simialr summary?
Your Knowledge Base article doesn’t cover this level of logic detail - Merge records
DRAFT LOGIC:

If you have manually selected any “Set properties to review,” (even just 1 property) the merge tool only shows the properties you picked to check. If there are decisions to make on any other property, the tool does not add these as extra rows for you to check. Anything that isn’t in your custom review list will follow the blunt rule - keep the left (primary) value, unless it’s blank in which case keep the right (secondary) value.

• If you HAVE NOT selected any properties to manually review: HS shows you ALL the properties where both left and right have values and gives you the chance to decide which one you want to retain
• If you HAVE selected properties to manually review:
  • if one record has the property populated and the other is empty - HS chooses the known property to retain for the new merged record
  • if both left and right versions of a property have values - HS retains the left version of the property (therefore deletes data that was in record on the right side)
  • for the properties you have selected for manual review - HS will default to choosing ALL the left properties, giving you the chance to decide if you want to retain the left or the right version of those properties.
  • for the remaining properties that you did not select for manual review –

There are some circumstances where HS keeps both left and right values on the new merged record. These are examples, not the full list:

• Create date - the value for the oldest record is maintained
• Contacts Email: while the email address of the primary contact is maintained as the primary email address, the secondary contact’s email address will be added as a secondary email address.
• Company domain name: while the domain name of the primary company is maintained as the primary domain, and the secondary will be added as the secondary domain name.

[Jaycee_Lewis]

Hey, @EmmaSchmitt Thanks for the detailed feedback.

Is this a fair summary of your question?
"While the article explains the basic rule (primary record wins) and lists property-specific exceptions, it fails to explain the behavior of the review screen itself. It doesn’t clarify what happens to conflicting properties when a user customizes the review list versus when they use the default view.” Thanks! — Jaycee

[EmmaSchmitt]

Yes - complete behaviour across any variable is not covered.

[Jaycee_Lewis]

Thanks for confirming, @EmmaSchmitt. In this case, because it is a documentation issue that involves the Knowledge Base, your best next step is to submit the feedback form at the bottom of the original article. The technical writers do not work out of the community forum and the feedback option is the most direct way to get your input in front of the right folks.

Best,

Jaycee