# Sync 2 properties across objects

**URL:** <https://community.hubspot.com/t/sync-2-properties-across-objects/127404>\
**Category:** Tips, Tricks & Best Practices\
**Tags:** object, getting-started\
**Created:** [March 5, 2025, 6:06pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404 "2025-03-05T18:06:48Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 5, 2025, 6:06pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/1 "2025-03-05T18:06:48Z")

</div>

Hi there,

I’m having trouble following the documentation to set up a property sync. The goal is to showcase the ARR on a custom Customer Success card in the Overview tab of the Company Object.

I figured out how to set up the fields for manual entry. But ideally, i’d like it to be automated to automatically get populated when a deal is marked closed-won. We use “Amount” as the property in Closed-Won Deals to showcase the total contract value.

To take it a step further, it would be great if this field also totaled any upsells within that year. But I’m happy with this first step for now. The goal would be to only show case the totals from 1/1 - 12/31 of each year so always ensure an accurate reflection of Annual rev coming in for that customer, ultimately allowing us to report on all customers in a CS Dashboard for overall total ARR.

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 5, 2025, 7:01pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/2 "2025-03-05T19:01:20Z")

</div>

![Screenshot 2025-03-05 at 1.03.03 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/9/2/92aee9eee9e921ba29be3f8bc0cf8a092009b0b5.png)

 ![Screenshot 2025-03-05 at 1.03.21 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/d/d64773968dc996bdef4ca24e90a33c9209d04a21.png)

 ![Screenshot 2025-03-05 at 1.03.32 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/0/0/00d8cd1637e5d063aeadbb1139a8e2e3996e7167.png)

Update: I think I’ve gotten 90% of the way there… I’m just stuck on how to properly formulate the conditional logic to ensure its only pulling in closed-won deals for the current year we are in.

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 5, 2025, 7:09pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/3 "2025-03-05T19:09:53Z")

</div>

@JNo you’ll need an assisting property and workflow here - for example a dropdown “Closed won year” with options 2025, 2026, 2027. In a deal-based workflow, you would enroll won deals and set this to the value that corresponds to the close date, using a branch and the Edit record workflow action. Once populated, you can use it as a condition in the roll up property.

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 5, 2025, 11:18pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/4 "2025-03-05T23:18:17Z")

</div>

Thank you, @karstenkoehler! Definitely a hard concept to understand as a newbie. Do i need to have the Format Data functionality to do this? I’ve tried to ask ChatGPT and Gemini on how to actually do this step by step and it’s guidance is inconsistent at best.

 ![Screenshot 2025-03-05 at 5.17.52 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/9/96836969383637052beb74e815854af45026cda2.png)

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 6, 2025, 5:07am UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/5 "2025-03-06T05:07:04Z")

</div>

Hi @JNo,

No, let me specify:

1. You’re currently enrolling based on deals associated to deals. I’d recommend removing your enrollment criteria again and filtering directly for “Is closed won” (deal property).
2. The branch should be an AND/OR branch, where each path corresponds to a “Close date” year, not a branch by the new property.
3. In each branch, you would set the value of the “Close date year” using the “Edit record” action

No format data needed 🙂

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 6, 2025, 7:02pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/6 "2025-03-06T19:02:52Z")

</div>

Oh!! I had to read that a few times to understand it since I’m still learning, but I think I get it now… like this, @karstenkoehler?

 ![Screenshot 2025-03-06 at 1.02.35 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/2/6/26b83a6b23dccd02e48b59b6eae2c0df10fcb62a.png)

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 6, 2025, 7:14pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/7 "2025-03-06T19:14:23Z")

</div>

@JNo could you click into the branch so I can see the criteria and confirm? 🙂

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 6, 2025, 7:26pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/8 "2025-03-06T19:26:22Z")

</div>

Yes, @karstenkoehler!

 ![Screenshot 2025-03-06 at 1.25.31 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/2/c/2ce32cf5f25987770838400a90cd7aa0f9f2132e.png)

 ![Screenshot 2025-03-06 at 1.25.43 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/6/6/66b9cd8aef6a60b72d9e74dfb6795abda350bd34.png)

 ![Screenshot 2025-03-06 at 1.26.05 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/3/4/34f017b675eec70d71eaa85f18a0958da6418880.png)

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 6, 2025, 7:30pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/9 "2025-03-06T19:30:20Z")

</div>

@JNo almost! The branch filters should be for the property “Close date” (is between Jan 1 and Dec 31 of that year), not for the new drop-down property.

If the date falls within that range, then set the new property to the corresponding year. The workflow translates the date into something the calculation property will “understand”.

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 6, 2025, 7:32pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/10 "2025-03-06T19:32:26Z")

</div>

Got it - are the “branch filters” the “edit record” boxes?

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 6, 2025, 7:38pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/11 "2025-03-06T19:38:59Z")

</div>

@JNo the branch is the action numbered as 1, right after your enrollment.

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 6, 2025, 8:23pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/12 "2025-03-06T20:23:55Z")

</div>

@karstenkoehler - Will try the screenshots here, for some reason the thread isnt updating on [community.hubspot.com](http://community.hubspot.com) for me and I’m only getting the emails now. Understood - I’ll set a reminder at the start of each year to update the property’s condition to say 2025.

 ![Screenshot 2025-03-06 at 2.23.25 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/f/f9dcd2427d7f03b9d269670ed71782850fc7a24f.png)

 ![Screenshot 2025-03-06 at 2.23.40 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/b/c/bc5783d33e39b5db87466defc1f23ef5c36e8bf2.png)

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 6, 2025, 8:28pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/13 "2025-03-06T20:28:47Z")

</div>

@JNo looks good!

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 6, 2025, 8:29pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/14 "2025-03-06T20:29:42Z")

</div>

Wow!! I got that one right on the first try lol - thank you so much! Couldn’t have done this without you, @karstenkoehler

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 6, 2025, 7:43pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/15 "2025-03-06T19:43:49Z")

</div>

AH! okay… so _hopefully_ this, @karstenkoehler? lol

 ![Screenshot 2025-03-06 at 1.42.49 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/5/6/5680f0c1cf71491710757561a64c75ae264a43c3.png)

 ![Screenshot 2025-03-06 at 1.43.09 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/b/b/bba175371003b0beb9f18ad600302bf1757560a3.png)

 ![Screenshot 2025-03-06 at 1.45.31 PM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/d/ddd6810b965022c9822455831a73c077d9298beb.png)

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 6, 2025, 7:52pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/16 "2025-03-06T19:52:59Z")

</div>

@JNo perfect! Turn that on, enroll all records meeting the criteria already and use the new property as a condition in your calculation 🙂

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 6, 2025, 8:14pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/17 "2025-03-06T20:14:20Z")

</div>

THANK YOU!! Wowzers lol  
Is the “new property” the one I’m creating from scratch to host this data?  
If so, this is what i’ve come up with:  
[image: Screenshot 2025-03-06 at 2.01.48 PM.png]  
[image: Screenshot 2025-03-06 at 2.03.30 PM.png]  
If this is correct, my Question then becomes, how do I get this field to  
automatically update at the turn of the year? Or do I have to manually  
create a new property and update the card every year?  
Thanks again, @karstenkoehler  
\<\>!

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 6, 2025, 8:20pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/18 "2025-03-06T20:20:46Z")

</div>

@JNo I can’t see the screenshots unfortunately, weil not file names - but yes to the rest of your message 🙂

---

<div class="post-metadata">

**Author:** ![JNo](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JNo](https://community.hubspot.com/u/JNo)\
**Post date:** [March 6, 2025, 11:22pm UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/19 "2025-03-06T23:22:40Z")

</div>

@karstenkoehler - the saga continues… I just realized that this ARR is not netted. Example: A person signs on for a pilot at, let’s call it $1,000. If they move to contract, that money is “deducted” from their first bill. If they do not move to contract, then that money is not refunded.

But here’s the kicker… pilots are always marked as closed won - so it’s always going to fall into the FY ARR workflow and rollup I built with the contracted deals and other upsells throughout the year. So when the customer is moved to contract using a separate deal, HubSpot will show the total Amount (let’s say $5k) but we will only bill them for the $4k since the pilot was a “Deposit” towards contract. As the formula is built right now… it’s reading $5k contract deal + $1k pilot deal = $6k ARR when in actuality it should stay as a $5k deal in the FY ARR field (as they will only get billed $4k).

BUT if the customer does not move to contract, the pilot deal is nonrefundable. Is this possible to accomplish by editing the work flow logic I just built by adding a few pieces of criteria? Or do I have to start over or add another separate workflow to work simultaneously with this one? Or do i need to recreate the property as a formula instead of a rollup?

Essentially, I need it to say omit Pilot deals if there is a New Contract deal, and include pilots if the customer opts out. I can probably do without the latter, tbh, since the goal is ARR for current customers, but wasnt sure if both could happen.

While I’m builing formulas, I should probably also have it subtract downgrades too 😳

I hope that all makes sense lol 😅

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [March 7, 2025, 5:15am UTC](https://community.hubspot.com/t/sync-2-properties-across-objects/127404/20 "2025-03-07T05:15:31Z")

</div>

@JNo approaches to this could be the following:

- Once a contract starts, someone removes the number from the new property you created, so that it’s not pulled into the calculation.
- You start associating the deals, using association labels (pilot \<\> contract) and, if a contract is won, a workflow enrolls contract deals and clears the custom property on the associated pilot deal so it’s not pulled into the calculation.

Let me know if I should describe one of the points more in detail.

[Next page](https://community.hubspot.com/t/sync-2-properties-across-objects/127404.md?page=2)
