# Merge properties

**URL:** <https://community.hubspot.com/t/merge-properties/1167>\
**Category:** CRM\
**Tags:** account, companies, contacts\
**Created:** [February 28, 2017, 1:25pm UTC](https://community.hubspot.com/t/merge-properties/1167 "2017-02-28T13:25:20Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![HarveyL](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/harveyl/32/88643_2.png) [@HarveyL](https://community.hubspot.com/u/HarveyL)\
**Post date:** [February 28, 2017, 1:25pm UTC](https://community.hubspot.com/t/merge-properties/1167/1 "2017-02-28T13:25:20Z")

</div>

Hi

I’ve just ran an import and made a custom property called Position and since noticed that there was already a property called Job Title. Is there any way of merging the two properties or change the Position property to Job Title? The reason I’d like to change it is because the Job Title field shows on the company page by the contacts.

Thanks

---

<div class="post-metadata">

**Author:** ![BrettLanguirand](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/brettlanguirand/32/39945_2.png) [@BrettLanguirand](https://community.hubspot.com/u/BrettLanguirand)\
**Post date:** [March 7, 2017, 2:44pm UTC](https://community.hubspot.com/t/merge-properties/1167/2 "2017-03-07T14:44:12Z")

</div>

Hello @HarveyL,

There isn’t a way to merge to properties together, but one workaround is to export your contacts and include the properties “Position” and “Job Title” on the export file. Open the file in Excel, copy the values from the “Position” column" into the “Job Title” column, and then import that file. Make sure that the Job Titles are accurate in the CSV, because importing the new values will overwrite any current Job Titles in the CRM. In this case, there won’t be any surprises because by including the “Job Title” column in the CSV, you’ll see any current values and can choose to not copy the “Position” value for certain contacts.

Once the values are added to Job Title, you can delete the contact property “Position”.

I hope this helps!

Brett

---

<div class="post-metadata">

**Author:** ![tmurtha](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tmurtha/32/31184_2.png) [@tmurtha](https://community.hubspot.com/u/tmurtha)\
**Post date:** [November 28, 2017, 8:24pm UTC](https://community.hubspot.com/t/merge-properties/1167/3 "2017-11-28T20:24:35Z")

</div>

Hi, sorry to be dense, but this sounds like you’re importing a contact that already exists in the system. How does the system handle imports that match existing contacts (that’s based on having the same email?)? Does it duplicate contacts, just replace information in the existing contact with anything different in the CSV, or create an entire new contact (possibly losing tracked history with the contact)? I have the merge properties problem, and I’d like to import new properties on existing contacts, and wonder if I can solve both problems with your suggestion.

Thanks for your help!

---

<div class="post-metadata">

**Author:** ![meagherman](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/meagherman/32/93181_2.png) [@meagherman](https://community.hubspot.com/u/meagherman)\
**Post date:** [August 14, 2018, 6:57pm UTC](https://community.hubspot.com/t/merge-properties/1167/4 "2018-08-14T18:57:42Z")

</div>

Merging cells would be a great feature. I too have Titles and Job Titles to combine. I’ll do work around but maybe you guys could offer that feature in the future.

---

<div class="post-metadata">

**Author:** ![EAhm](https://avatars.discourse-cdn.com/v4/letter/e/f19dbf/32.png) [@EAhm](https://community.hubspot.com/u/EAhm)\
**Post date:** [May 30, 2024, 7:11pm UTC](https://community.hubspot.com/t/merge-properties/1167/5 "2024-05-30T19:11:02Z")

</div>

Quick question: can you delete a property if there are objects that have values with that property?

---

<div class="post-metadata">

**Author:** ![Dave\_1](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dave_1/32/42114_2.png) [@Dave\_1](https://community.hubspot.com/u/Dave_1)\
**Post date:** [October 23, 2019, 7:33pm UTC](https://community.hubspot.com/t/merge-properties/1167/6 "2019-10-23T19:33:48Z")

</div>

There a couple of ways this could be done, the manual way via import and exports as described above, and this is a method I have used myself.

But the easier way, via an integration maintaining all future edits and additions:

> **[HubSpot Marketplace](https://ecosystem.hubspot.com/marketplace/apps/marketing/marketing-automation/integration-agent-concatenator-198181)**

Disclaimer: I am the author of the above integration, and it is paid (though I’ve done my absolute best to keep it affordable). But it was very much built to help us internally avoid having to do repeated manual export imports across a number of our accounts.

---

<div class="post-metadata">

**Author:** ![SimonDEBRITO](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/simondebrito/32/20414_2.png) [@SimonDEBRITO](https://community.hubspot.com/u/SimonDEBRITO)\
**Post date:** [June 29, 2022, 2:21pm UTC](https://community.hubspot.com/t/merge-properties/1167/7 "2022-06-29T14:21:38Z")

</div>

Hi,

I think I’ve found a way to do this. Let’s say you want to merge {first name} + {last name} into a {full name} property.

All you have to do is create a workflow:

1. Start a workflow from scratch
2. Select a trigger, like “email address is known”
3. Add a new action: “Set property value”
4. Select the destination field or property to set: “full name”
5. In the new tab that appears, click on “add contact tokens”
6. Select the contact token “first name”
7. Add a space
8. Select the contact token “last name”
9. Save
10. Publish your workflow

 ![System - Job Title Matching - All _ HubSpot (2).png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/f/fc5fd8c7f9f6dc4d5507109bee8eeedfbc044e57.png)

😊

---

<div class="post-metadata">

**Author:** ![DOriade](https://avatars.discourse-cdn.com/v4/letter/d/bc79bd/32.png) [@DOriade](https://community.hubspot.com/u/DOriade)\
**Post date:** [May 24, 2023, 9:38pm UTC](https://community.hubspot.com/t/merge-properties/1167/8 "2023-05-24T21:38:43Z")

</div>

This is Great! Thank you!

---

<div class="post-metadata">

**Author:** ![RLeonNavas](https://avatars.discourse-cdn.com/v4/letter/r/ecc23a/32.png) [@RLeonNavas](https://community.hubspot.com/u/RLeonNavas)\
**Post date:** [October 20, 2023, 10:02pm UTC](https://community.hubspot.com/t/merge-properties/1167/9 "2023-10-20T22:02:21Z")

</div>

Such an smart solution! Thank you!

---

<div class="post-metadata">

**Author:** ![RBozeman](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rbozeman/32/8786_2.png) [@RBozeman](https://community.hubspot.com/u/RBozeman)\
**Post date:** [March 3, 2023, 9:58pm UTC](https://community.hubspot.com/t/merge-properties/1167/10 "2023-03-03T21:58:10Z")

</div>

Hi @HarveyL,

I realize that this thread is pretty old, but thought I would share in case others came across this issue as well.

For now, the only way to merge properties is either through the API, or using a custom-coded solution in Operations Hub.

Also, I wanted to share that [Insycle](https://ecosystem.hubspot.com/marketplace/apps/marketing/data-management/insycle) can help with this. With Insycle, you can analyze any field in your database, along with the variations of the data contained within that field, to consolidate and retire legacy fields that are creating clutter in HubSpot. [Here is our help documentation article](https://support.insycle.com/hc/en-us/articles/6586196513303-Consolidate-and-Retire-Legacy-Fields) for doing this.

Hope that helps!

Best,

Ryan

---

<div class="post-metadata">

**Author:** ![kvlschaefer](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kvlschaefer/32/71076_2.png) [@kvlschaefer](https://community.hubspot.com/u/kvlschaefer)\
**Post date:** [March 6, 2023, 3:39pm UTC](https://community.hubspot.com/t/merge-properties/1167/11 "2023-03-06T15:39:46Z")

</div>

Hi @RBozeman,

Thank you for sharing these options with us!

Best,

Kristen
