HubSpot's New Earliest and Latest Date Rollups, and the Three to Build First
The new Earliest Date and Latest Date rollups do in two minutes what used to need a custom code action or three calculated properties. Here is what they replace, and the UTC catch that bites Australian portals at a period end.
What This Replaces
Before this feature shipped, getting any of the above onto a company record required one of the following:
A scheduled workflow that ran periodically and used a custom code action to loop through associated records, find the earliest or latest date, and write it back to a custom property. This required Data Hub Professional or Enterprise, development knowledge, and ongoing maintenance when the associated object structure changed. Scheduled workflows still have their uses, building rolling date filters with scheduled workflows among them, but that is a lot of machinery for a first or last date.
A calculated property workaround using UNIX millisecond timestamps, because HubSpot's calculated property formulas work in milliseconds for date values, not readable dates. This meant creating intermediate calculated properties to convert, compare, and format the output. Community members documented needing three separate calculated fields to get a single usable date value this way. If you have ever gone down that road, turning a dropdown into a date field with Unix timestamps will look familiar.
Both approaches worked. Neither was clean, and both required more technical knowledge than most HubSpot admins should need for something this common.
The native rollup does the same thing in about two minutes.
One Thing to Keep in Mind
Rollup properties calculate across all associated records that meet your conditions at the time of calculation. If a company has 20 associated deals and you're rolling up close dates, the property reflects all 20 unless you narrow with conditions.
Be deliberate about which conditions you add. A close date rollup without a pipeline or stage filter might return dates from deals you don't want included, a renewal deal in a separate pipeline, for example, or a legacy deal that was closed years ago and is no longer relevant to the current customer relationship. Contract dates are the same story, so read simplifying contract end date calculations before you point a rollup at them.
Take two minutes to think through which records should and shouldn't be included before clicking Create. It saves a "why is this date wrong?" conversation later.
The Time Zone Catch for Australian Portals
HubSpot works in UTC underneath. Australia is a long way from UTC, and that is where date rollups get interesting.
Midnight UTC is 10am in Brisbane and Sydney during AEST, and 11am in Sydney and Melbourne during AEDT. So the UTC date ticks over in the middle of your working morning. A call logged at 9am AEST on 9 September 2026 is 23:00 UTC on 8 September, and anything reading that value in UTC will report it as the eighth.
For a latest activity date rollup that mostly does not matter, because you are looking at recency rather than a specific day. For anything measured against a month, quarter or financial year boundary it matters a lot: an activity at 8am AEST on 1 October can count as 30 September, and an earliest date can appear to sit a day before the record that caused it.
Not sure which workflow is setting that date?
Most portals have three of them, built by different people.
So before you build reporting on these rollups, check the account time zone under Settings > Account Defaults, confirm it matches the time zone the business actually runs on, and test one rollup against a record whose real timestamp you know. HubSpot's own product documentation on rollup properties is the place to confirm how each rollup type calculates, and it is worth reading before you rely on the output at a period end.
Want to Build a Cleaner HubSpot Data Model?
Date rollup properties are one piece of a larger picture. If your portal is carrying manual workarounds, calculated properties that nobody fully understands, or dashboards that don't actually reflect how your business operates, that's the kind of audit we run regularly.
Neighbourhood is a Diamond HubSpot Partner. If your HubSpot data model has grown faster than it was designed, have a look at NBH's RevOps and HubSpot work, then get in touch and we will help you clean it up properly.
Talk to us about your HubSpot setup.
Stay in the Loop
If you want more hacks like this one, practical, no-fluff, built for teams who actually run HubSpot day-to-day. Here's where to find us:
Ops Intel, our newsletter for HubSpot admins and RevOps teams, arrives in your inbox with exactly this kind of content. No padding, no roundups of stuff you've already seen. Subscribe to Ops Intel now.
We're also on Facebook and YouTube if you'd rather watch someone click through it than read about it. Follow us there for more updates.
Wondering what that old custom code is still doing?
Switching it off is harder than it was to write in the first place.
Happy HubSpotting.