This is in direct response to Support Ticket #16429918286 and for anyone interested to see how absolutely ridiculous this behavior from HubSpot is - here’s a 4:45 Minute Long Loom.
Essentially if you have two records you’re trying to merge, let’s say:
- Company A
- Company B
And you know that 100% of the property values in Company B are outdated and/or garbage, and you KNOW you don’t want any properties in Company B to override values in Company A, then set a workflow to clear all values in company B then merge into company A right?
Well all good in theory, but HubSpot still treats that null value from a workflow as the most recent value, and will in turn overwrite any valid values on the good record with NULL.
This essentially gives users 0 control to mitigate how merging record data is handled, most recent value DOES NOT EQUAL CORRECT.