# Create Cross-object properties

**URL:** <https://community.hubspot.com/t/create-cross-object-properties/22566>\
**Category:** HubSpot Ideas\
**Tags:** crm-objects-contacts-companies-deals-tickets\
**Created:** [July 7, 2020, 6:04pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566 "2020-07-07T18:04:09Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![KarineP](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karinep/32/99782_2.png) [@KarineP](https://community.hubspot.com/u/KarineP)\
**Post date:** [July 7, 2020, 6:04pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/1 "2020-07-07T18:04:09Z")

</div>

Hi,

It would be very useful to be able to create cross-object properties, especillay for the following reasons:

- we will no longer need to create additional properties across various objects

- we will no longer need to create workflows to copy a value across objects. I.e. If property X gets updated at contact level, the value would be the same at Company level without having the need to create a workflow

- most of the time contacts/companies/deals can’t be easily re-enrolled. This means as the value is updated in one object it doesn’t always get updated across all objects automatically

- this will also be helpful from a reporting perpective as it would allow us to create more single object reports/dashboards

Best,

---

<div class="post-metadata">

**Author:** ![jpeluso](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jpeluso](https://community.hubspot.com/u/jpeluso)\
**Post date:** [July 7, 2021, 7:20pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/2 "2021-07-07T19:20:45Z")

</div>

This would be extremely useful for us as well.

---

<div class="post-metadata">

**Author:** ![Joacimbr](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/joacimbr/32/59131_2.png) [@Joacimbr](https://community.hubspot.com/u/Joacimbr)\
**Post date:** [October 28, 2021, 9:21am UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/3 "2021-10-28T09:21:36Z")

</div>

Yes please, and this idea needs way more attention!

---

<div class="post-metadata">

**Author:** ![spatrizi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/spatrizi/32/26344_2.png) [@spatrizi](https://community.hubspot.com/u/spatrizi)\
**Post date:** [March 10, 2022, 10:53pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/4 "2022-03-10T22:53:33Z")

</div>

This, soooooo much!!! 🙏

---

<div class="post-metadata">

**Author:** ![MHigginson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mhigginson/32/193960_2.png) [@MHigginson](https://community.hubspot.com/u/MHigginson)\
**Post date:** [March 14, 2022, 11:20pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/5 "2022-03-14T23:20:40Z")

</div>

Good idea. Single data point that is visible on all objects, similar to Company Name, but would be a customizable field.

---

<div class="post-metadata">

**Author:** ![dwc1993](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@dwc1993](https://community.hubspot.com/u/dwc1993)\
**Post date:** [April 7, 2022, 2:07pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/6 "2022-04-07T14:07:42Z")

</div>

Yes please! We are having to create the same properties on multiple OBJECTS and setup WFs to update the property values.

---

<div class="post-metadata">

**Author:** ![StormJenkin](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@StormJenkin](https://community.hubspot.com/u/StormJenkin)\
**Post date:** [November 25, 2022, 3:36am UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/7 "2022-11-25T03:36:15Z")

</div>

Yes this would save a LOT of time. ATM I have clients who need a handfull of properties that are exactly the same across multiple object E.g. BRAND.

We arre currently creating automaions to make sure if one is edited then they all get updated etc. But it is very frustrationg having to create the exact same property across 3-4 objects and then create workflows to match. it would be great too have this option even if it is only needed for 3-5 properties a client!

---

<div class="post-metadata">

**Author:** ![Goddess\_Sarah](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/goddess_sarah/32/197684_2.png) [@Goddess\_Sarah](https://community.hubspot.com/u/Goddess_Sarah)\
**Post date:** [February 10, 2023, 3:32pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/8 "2023-02-10T15:32:03Z")

</div>

YES I agree and have asked for this! I would like to be able to see the same properties in my deals view that I see in contact view. I would like to attach the tme zone to each view along with other properties.

It makes for an easy read instead of wassting time searching in the profile

---

<div class="post-metadata">

**Author:** ![MDay0](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mday0/32/52738_2.png) [@MDay0](https://community.hubspot.com/u/MDay0)\
**Post date:** [April 24, 2023, 6:29pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/9 "2023-04-24T18:29:41Z")

</div>

I couldn’t agree more, adding properties across deals/companies etc indivually is redundant …but judging by the fact this thread is nearly 3 years old and the issue hasn’t been resolved.. not feeling confident that the customer support rep I spoke to today that said “I recommend that you vote and leave a comment on this idea. HubSpot’s product managers regularly review new ideas and engage with customers for their feedback. They’ll put every effort into implementing ideas that will benefit the majority of HubSpot’s user base and fit in within our product roadmap.” really, every effort? Yet the issue is still unresolved. Clearly this would improve productivity of the app, please implement a solution!!!

---

<div class="post-metadata">

**Author:** ![Thibtech](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Thibtech](https://community.hubspot.com/u/Thibtech)\
**Post date:** [April 27, 2023, 3:11pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/10 "2023-04-27T15:11:13Z")

</div>

This is messed up in HubSpot  
Creating multiple workflows just to copy paste properties across objects. Makes everything so much more complicated than need to be. Having this feature would drastically improve many features:

- Contact & company filtering

- Displayed properties in cards & boards

- …

Hope to see this soon.

---

<div class="post-metadata">

**Author:** ![GScott-Lister](https://avatars.discourse-cdn.com/v4/letter/g/5f8ce5/32.png) [@GScott-Lister](https://community.hubspot.com/u/GScott-Lister)\
**Post date:** [June 13, 2023, 10:41am UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/11 "2023-06-13T10:41:04Z")

</div>

🙏

🙏

🙏

🙏

---

<div class="post-metadata">

**Author:** ![cjl2016](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cjl2016/32/42091_2.png) [@cjl2016](https://community.hubspot.com/u/cjl2016)\
**Post date:** [June 23, 2023, 3:33pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/12 "2023-06-23T15:33:05Z")

</div>

This is a HUGE need! Because HubSpot currently doesn’t allow us to use cross-object personalization tokens in certain aspects of tasks, workflows, etc., we are constantly having to duplicate properties across objects in order to get the data we have into the hands of the right people.

Additionally, when we create a property with defined options (multi-checkbox, dropdown, etc.) that needs to be recreated across objects, we have to manually update every iteration of that property whenever a slight change needs to be made. This turns the 30 seconds it takes to add a choice into a 5 minute endeavor because we have to cycle through all of the objects with the identical property and manually update each of those, as well. And if we forget to do it to one or multiple, it can drastically screw up workflows that rely on that information being the same across objects.

PLEASE fix this!

---

<div class="post-metadata">

**Author:** ![TH7](https://avatars.discourse-cdn.com/v4/letter/t/6a8cbe/32.png) [@TH7](https://community.hubspot.com/u/TH7)\
**Post date:** [August 14, 2023, 8:04pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/13 "2023-08-14T20:04:07Z")

</div>

Yes, please. The number of workflows that need to be created is absurd.

---

<div class="post-metadata">

**Author:** ![CMcIntosh4952](https://avatars.discourse-cdn.com/v4/letter/c/779978/32.png) [@CMcIntosh4952](https://community.hubspot.com/u/CMcIntosh4952)\
**Post date:** [September 14, 2023, 5:54am UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/14 "2023-09-14T05:54:53Z")

</div>

Yes please, not having is a major drawback. Often leading to duplicate properties being created and silos between different objects if WF not set up correctly.

---

<div class="post-metadata">

**Author:** ![kkashiva616](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kkashiva616/32/1638_2.png) [@kkashiva616](https://community.hubspot.com/u/kkashiva616)\
**Post date:** [September 21, 2023, 6:15am UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/15 "2023-09-21T06:15:36Z")

</div>

Absolutely needed. Current workaround of copying properties across objects is just bad database design (aka database denormalization).

Leads to update anomalies if the workflow doesn’t work or is only one-way. If workflow is 2-way, can cause loops.

BTW Salesforce solves for this using Lookup fields. Basically instead of ‘copying by value’ it just shows the value ‘by reference’ from the related object.

---

<div class="post-metadata">

**Author:** ![AGelker](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@AGelker](https://community.hubspot.com/u/AGelker)\
**Post date:** [October 27, 2023, 4:25pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/16 "2023-10-27T16:25:47Z")

</div>

It would be incredibly useful to have this please.!

---

<div class="post-metadata">

**Author:** ![DHill5](https://avatars.discourse-cdn.com/v4/letter/d/c77e96/32.png) [@DHill5](https://community.hubspot.com/u/DHill5)\
**Post date:** [December 7, 2023, 6:45pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/17 "2023-12-07T18:45:04Z")

</div>

Any update on implementing this feature? It would be a huge time saver and data hygenie improvement.

---

<div class="post-metadata">

**Author:** ![KKuswandi](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@KKuswandi](https://community.hubspot.com/u/KKuswandi)\
**Post date:** [March 4, 2024, 10:26am UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/18 "2024-03-04T10:26:07Z")

</div>

This would be super usefull!

---

<div class="post-metadata">

**Author:** ![ErikaJ](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/erikaj/32/2401_2.png) [@ErikaJ](https://community.hubspot.com/u/ErikaJ)\
**Post date:** [October 29, 2024, 3:38pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/19 "2024-10-29T15:38:56Z")

</div>

This would also solve the use case of needing Company or Contact records to be updated at certain stages in a Deal pipeline. For example, when a Deal reaches X stage, we must ensure that the associated Company record has X value updated to function for our integration. If we had cross-object fields, we could make this required easily.

---

<div class="post-metadata">

**Author:** ![WEvans-V0L7](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/wevans-v0l7/32/60402_2.png) [@WEvans-V0L7](https://community.hubspot.com/u/WEvans-V0L7)\
**Post date:** [May 9, 2025, 2:24pm UTC](https://community.hubspot.com/t/create-cross-object-properties/22566/20 "2025-05-09T14:24:08Z")

</div>

+1 for this suggestion

[Next page](https://community.hubspot.com/t/create-cross-object-properties/22566.md?page=2)
