Combining Multiple Contact Properties

[LizO]

Is it possible to combine multiple contact properties into a single contact property?  Will all the values in the multiple properties transfer over to the one contact property?

I saw merging values within 1 contact property but not how do you combine multiple contact properties.  

Example:

 Over the last 4 years we have some how created 5 contact properties for job title/role.  I'm looking at them and thinking all we really need is one contact property.  This makes mapping imports difficult and individaul data entry too. 

Please help! 

[relabidin · Accepted solution]

Hi @LizO,

At this time we do not offer a feature that allows you to merge together separate contact properties. However, I understand how this would be a useful feature and I encourage you to post it as a feature request on the Ideas board of this forum.

Rami 

[LizO · Accepted solution]

@jmliffrig

Not the easiest work around but I can tell you what I did to clean up our database.
1. Pick a property you want to keep and note the name of the other properties you want to remove or merge.   You can even rename the properties to make that more clear.
2. From the contact view select the filter by contact property then select one of the properties you want to remove and show all where that property is known.
3. Sort the list by that property column
4. You can select multiple contacts and batch edit the contacts to add the same information to the property you want to keep
5. Once you transfer the information from the undesired field to the one you plan to keep you can safely delete the undesired filed with no loss in your data.

I know, the above is tedious and maybe not worth your time. 

2nd Idea that I have not confirmed will work:

Try an export to CSV.  Shorten the spreadsheet to an e-mail column A (as that is HubSpots primary identifier of contacts) and adding the desired value to the property you want to keep in column B.  Try importing that CSV back into HubSpot to see if they all update.  

Good Luck!

[jmliffrig · Accepted solution]

That is helpful, thank you! I ended up being able to fix by changing the free text field into a "multiple checkbox" field. The free text only had 8 different variations, so as long as I used the exact same erbiage, I was able to change the type to multiple checkbox, and had all the old data change from free text to checkbox. 

Thanks so much for getting back to me!

[zackparkar · Accepted solution]

Similar idea suggested here: https://community.hubspot.com/t5/HubSpot-Ideas/Combining-Multiple-Contact-Properties/idi-p/656620#M1...

[torysher · Accepted solution]

Thanks for following up on this @MLynch33 ! I found calculated properties a few days later and it was just what I needed 🙂 

[LizO · Accepted solution]

Things have changed in the last 7 years and you can now transfer vlaues with workflows. 

Use the edit record action and pick to update the "keep" property with the the value in the "to archive" property.  If you are trying to transfer a drop down value you can make branches or use "contains" key words in single line text to distribute records to drop down values.  

[MBianculli]

It would be great to be able to combine Company properties as well. 

[torysher]

Upvoting this as well. 

We'd need this to support the Lead Scoring system we've developed. Our Lead Score is two-dimensional and uses fit (firmographic and demographic data) and activation (behavioral data) to determine the ultimate lead score. 

Put simply, Lead Score = Fit Score + Activation Score

HubSpot has a limit of 100 filters in 1 Score property. We'd need 75 of these just for Fit Score, so would exceed the limit if we included Activation Score in 1 property also. So, we'd need to create 2 Score properties: 1 for Fit Score, 1 for Activation Score. 

We'd then want to combine them to determine the ultimate lead score. 

For example, if the Fit Score = 75 and the Activation Score = 50, we'd want the total Lead Score to = 125

[MLynch33]

Hey @torysher,

Have you tried using calculated properties to achieve this?

In your case, the calculated property would be Fit Score + Activation Score = Lead Score. Please note: Calculated properties are available to Pro+ subscriptions.

Hope that helps 😀

[torysher · Accepted solution]

Thanks for following up on this @MLynch33 ! I found calculated properties a few days later and it was just what I needed 🙂 

[Eilo]

I totally UPvote with you 🙂

[jmliffrig]

I need the same function, any cance this has been resolved or anyone has a good workaround? 

[LizO · Accepted solution]

@jmliffrig

Not the easiest work around but I can tell you what I did to clean up our database.
1. Pick a property you want to keep and note the name of the other properties you want to remove or merge.   You can even rename the properties to make that more clear.
2. From the contact view select the filter by contact property then select one of the properties you want to remove and show all where that property is known.
3. Sort the list by that property column
4. You can select multiple contacts and batch edit the contacts to add the same information to the property you want to keep
5. Once you transfer the information from the undesired field to the one you plan to keep you can safely delete the undesired filed with no loss in your data.

I know, the above is tedious and maybe not worth your time. 

2nd Idea that I have not confirmed will work:

Try an export to CSV.  Shorten the spreadsheet to an e-mail column A (as that is HubSpots primary identifier of contacts) and adding the desired value to the property you want to keep in column B.  Try importing that CSV back into HubSpot to see if they all update.  

Good Luck!

[LizO · Accepted solution]

Things have changed in the last 7 years and you can now transfer vlaues with workflows. 

Use the edit record action and pick to update the "keep" property with the the value in the "to archive" property.  If you are trying to transfer a drop down value you can make branches or use "contains" key words in single line text to distribute records to drop down values.  

[APshegodskyi]

Hi,
I managed to get as far as selecting the source, but it has an incompatible format. I need to transfer free-text, comma-separated values into checkboxes. There are thousands of values in the free text, and I want each one to become a separate checkbox option in the target field.

Is this possible? Could you please help me with this?

[LizO · Accepted solution]

Hi @APshegodskyi

The 2 properties have to be the same type like number to number, date to date, single line text to single line text.  If you are tying to turn single line text into multi check box, an export, import situation is best.  

Export all records with the property you want to archive.  Use text to columns to get all values in separate cells then remove duplicates to shorten the list.  Back in HubSpot, make the consolidated multi check box property.  The final list of check box values can be copied and pasted. 

Then, import the original file back into HubSpot but this time mapping to your muli check box property.    

Good luck!

[jmliffrig · Accepted solution]

That is helpful, thank you! I ended up being able to fix by changing the free text field into a "multiple checkbox" field. The free text only had 8 different variations, so as long as I used the exact same erbiage, I was able to change the type to multiple checkbox, and had all the old data change from free text to checkbox. 

Thanks so much for getting back to me!

[relabidin · Accepted solution]

Hi @LizO,

At this time we do not offer a feature that allows you to merge together separate contact properties. However, I understand how this would be a useful feature and I encourage you to post it as a feature request on the Ideas board of this forum.

Rami 

[CHarter]

Is this still the case 8 years later? Please say you can merge contact properties now.

[zackparkar · Accepted solution]

Similar idea suggested here: https://community.hubspot.com/t5/HubSpot-Ideas/Combining-Multiple-Contact-Properties/idi-p/656620#M1...

[DBläsing]

Hey @LizO,

is this feature in progress or already implemented?

best,

David