For years, getting a date like "earliest deal create date" or "latest ticket activity date" onto a company record in HubSpot meant one of two things: a multi-step workflow with custom code, or a calculated property built on UNIX millisecond arithmetic that took three fields and a prayer to get right.

HubSpot now has native Earliest Date and Latest Date rollup types, and they do exactly what the name says.

Here's what they are, why they matter, and the three properties worth building first.

 

What Changed

Rollup properties have existed in HubSpot for a while. They let you automatically calculate aggregate values across associated records -total deal revenue on a company, count of open tickets on a contact, average deal size. The rollup types available were Min, Max, Count, Sum, and Average.

All of those work on numbers. None of them worked cleanly on dates.

HubSpot has now added two new rollup types specifically for date fields: Earliest date and Latest date. Earliest date returns the oldest date value across all associated records of a selected object. Latest date returns the most recent one.

Both update automatically whenever the underlying data on associated records changes. You set it up once and it stays current.

 

What You'll Need

Rollup properties are available on Professional and Enterprise tiers across Marketing Hub, Sales Hub, Service Hub, Data Hub, Content Hub, Smart CRM, and Commerce Hub.

Once created, rollup properties can be used in reports, dashboards, workflows, and automation logic - anywhere a standard property can appear.

 

How to Create a Date Rollup Property

Go to Settings > Properties and select the object you want the rollup to live on. For most of the use cases below, that will be Company.

Click Create property in the top right. Fill in the property label and any internal notes, then:

  • Set Field type to Rollup
  • Open the Rollup type dropdown and select either Earliest date or Latest date
  • Select the associated object you want to pull from (e.g. Deals, Tickets, Contacts)
  • Select the date property on that object you want to roll up (e.g. Create date, Close date, Last activity date)

Optionally, click Add condition to filter which associated records are included in the calculation. For example, you might want to roll up close dates only from deals in a specific pipeline, or ticket activity dates only from open tickets. You can add up to 50 conditions per rollup property using number and enumeration field types.

Click Create. The property will now appear on every record of that object and populate automatically.

 

Three Properties Worth Building Right Now

1. Nearest Upcoming Deal Close Date (on Company)

Object: Company
Rollup type: Earliest date
Associated object: Deals
Property: Close date
Condition: Deal stage is not equal to Closed Won/Closed Lost

This gives sales managers a single date field on every company record showing when the next open deal is expected to close. Instead of clicking into individual deal records or running a separate report, the answer is visible directly on the account. Useful for weekly pipeline reviews, priority sorting, and identifying accounts that need attention before the end of the month.

Add it to your company record view or a sales dashboard and it becomes a live pipeline signal without any manual checking.

 

2. Latest Ticket Activity Date (on Company)

Object: Company
Rollup type: Latest date
Associated object: Tickets
Property: Last activity date
Condition: Ticket status is not equal to Closed (optional - remove if you want to include closed tickets)

This surfaces the most recent support interaction across all associated tickets for an account. Customer success teams use this to identify accounts that have gone quiet. No recent ticket activity often means either the customer is happy or they have stopped engaging altogether. Both are worth knowing.

When combined with contract renewal dates or deal stage data, it becomes a useful early signal for churn risk or expansion opportunity. Set it as a condition in a workflow and you can automate a CS task when a high-value account has had no ticket activity in 60+ days.

 

3. Earliest Contract Start Date (on Company)

Object: Company
Rollup type: Earliest date
Associated object: Deals
Property: Close date
Condition: Deal stage is equal to Closed Won

This tells you when the customer relationship began - the date of their first closed-won deal. It's the HubSpot equivalent of a customer since field, built from real deal data rather than a manually entered property that may or may not have been filled in.

RevOps teams use this for cohort analysis, tenure-based segmentation, and customer lifetime reporting. It also gives account managers useful context that's easy to miss when a customer has been around for a few years and the original deal is buried in deal history.

 

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.

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.

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.

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.

 

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, 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, lands 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.


Happy HubSpotting!