Workflow: copy country property from company to contact

[Alexrott]

So I want to set up a workflow that copies the country (gathered through Hubspot Insights) property from a company to the corresponding contact.

The standard fields that come with Hubspot don't allow that since they are different field types: single-line text fo companies, dropdown for contacts.

is there a way to set up this workflow without having to set up a new contact property (as single-line text)?

[dianalcont]

Hi @Alexrott 

The two fields would need to be the same type in order for it to do a 1:1 mapping of the properties.

What might be a solution is to:

• clear the field for the contact using a workflow
• convert it to the same type of field as the company property
• create a workflow to copy the property over to the contact

A few things to consider:

1. would your data be accurate? – why are they different in the first place? maybe the company is headquartered in one country and the contact works remote, at a satelite campus, or could represent a branch of the company completely separate of corporate.
2. is this necessary? – how does this help you understand who you are doing business with or who your prospects are?
3. could this lead to wires gettiing crossed on your team? – how does this change outcomes of current workflows or lead assignments?

Unless you know for sure that changing the data will not disrupt the customer/prospect experience, I wouldn't recommend this as a necessary action to take.

Be careful with the data you manipulate. If it isn't needed you could potentially be triggering internal conflict among sales reps or falling short on delivering a good experience to the folks that engage with you.

Hope this helps!

Diana

[Alexrott]

Hello @dianalcont,

thanks for your reply.

---

@dianalcont wrote:

1. would your data be accurate? – why are they different in the first place? maybe the company is headquartered in one country and the contact works remote, at a satelite campus, or could represent a branch of the company completely separate of corporate.

That's exactly the question we are debating internally at the moment since we don't want to manipulate the data unnecessarily. Sure there are examples where a company has branches in different countires or employees in field sales, and we want to have the right correspondence addresses for each contact (to send letter mailing to f.e.). 

We are still wondering what Hubspot's reasoning is of having the 2 fields of different types. Setting up the workflows for street, zip code, etc. is super easy and convenient and fills out a bunch of properties from the information gathered through Hubspot Insights for the company. I can't understand what the difference is with countries.

Would you recommend leaving the addreess property fields out of the contact object level, and just having them on the company object?

Thanks for your input

Alex

[dianalcont · Accepted solution]

@Alexrott depends on how you do business. There isn't one way that I recommend doing this for clients because the way they sell differs.

Scenario 1:

The company is technically the customer while the contacts live under the company umbrella. This is usually the case when a company holds a contract with you and all of it's employees have access to your product or service. This is usually the case for SaaS.

Scenario 2:

The contact is the customer. Although the company information is important the contact level data is more important. This is typically seen with products or more tangible services (restoration, cleaning, photography...you get it).

It sounds like maybe you are in the first scenario. For outliers that might not fit the data you have for the company ask yourself:

1. do we need to make the distinction between company branch and corporate? If so you might want to create a company for each branch – I.e. company west, company publishing vs. broadcasting
2. who owns the contract (contact at main site or someone at a satelite office - default to whoever has the decision making/signing authority for the data you want to prioritize.

Hoping that helps move the conversation along with your team!

Diana