Multiple Contact to Company Property Copy Workflow

[DMacdonald14]

I currently have a workflow running that is copying a contact property over to a company property.

It is working as designed, however, I'm struggling with backfilling historical information on companies where multiple contacts associated.

Here's the workflow currently set up;

When multiple contacts are associated, it is picking the date at random, and not updating with the most recent "Employer Notified Date". Ex;

John's property is 3/21/21
McKensie's property is 4/25/19
Sandra's property is 11/17/23
Stanley's property is 7/22/17

Since the workflow doesn't run in any particular, the date is stamped with one of those four dates, vs the most recent date of 11/17/23 (from Sandra's property). See here;

 
Is there any way to ensure that recency is taken into account here? I can't figure it out for the life of me.

FWIW; moving forward, since it overwrites data, I am having it work on recency - this is just for historical data we already have in the system. All our previous data was mass uploaded via an API on the same date, so created date is something we can't go by.

[karstenkoehler · Accepted solution]

Hi @DMacdonald14,

If you create a company based workflow and copy from contact to company, you can specify to copy the value from the contact update most recently:

It's not perfect, as the most recent update of the record might not be the most recent update of this property - but it's probably closer to the truth than what you have now.

In any case, workflows can't go back in time and you won't be able to resolve this issue entirely without a custom coded workflow action (available in Operations Hub Professional) and the help of a developer.

There's also a route without a workflow, the new sync properties: https://knowledge.hubspot.com/properties/create-sync-properties

The target field won't be editable but you can specify that the value from the contact updated most recently should be shown on the company record.

Hope this helps!

[DMacdonald14]

Your right, unfortuantely since the record updates are all bulk (~ same time) it isn't perfect, but go-forward is better.

Thanks!