What This Update Actually Is
HubSpot shipped six new calculated properties for custom objects on May 18, 2026. These properties update automatically as records move through pipeline stages. No formulas to write, no workarounds to build.
Here are the six properties, exactly as HubSpot named them:
- Date Entered {stage id}: timestamps when a record first entered a specific stage
- Date Exited {stage id}: timestamps when a record left that stage
- Latest Time in {stage id}: duration of the most recent visit to that stage
- Cumulative Time in {stage id}: total time across all visits to that stage
- Time in Current Stage: how long a record has been sitting in its current stage right now
- Date Entered Current Stage: the date the record moved into the stage it's in today
These have existed on Deals, Tickets, and Projects for years. Custom objects are now catching up. This is available on Content Hub Enterprise, Marketing Hub Enterprise, Data Hub Enterprise, Sales Hub Enterprise, Smart CRM Enterprise, and Service Hub Enterprise.
Why HubSpot Shipped This
Custom objects exist because every business has processes that don't fit the default Contact-Company-Deal-Ticket model. An equipment rental company tracks asset requests. A professional services firm tracks project deliverables. A SaaS company tracks implementation milestones.
Before this update, those custom pipelines were flying blind on timing. Humans running operations could see where a record was. They couldn't easily see how long it had been stuck there, or how that compared to last quarter, or when to fire an escalation.
That's a real gap. If you'd built a custom object pipeline to manage a post-sale process, for example, you were essentially running that process without a clock. This update installs the clock.
How to Use It Step by Step
The properties are already live. HubSpot is populating them as records move going forward. Here's how to find and start using them:
- Go to Settings, then Properties, then select your Custom Object from the object type dropdown.
- Search for "time in" or "date entered" to surface all six new properties at once.
- Add relevant properties to your record views so your team can see stage timing right on the record.
- Build a custom report using these properties. Filter by cumulative time in a specific stage to find where records stall most often.
- Set up a workflow on the custom object. Use Time in Current Stage as an enrollment trigger. Fire a task, notification, or status update when a record has been sitting too long.
- Create saved views filtered by Date Entered Current Stage so your team can see which records need attention today without hunting through the full pipeline.
What It Touches in Your HubSpot Strategy
This update is small in scope but wide in impact. Here's what it ripples into across your portal.
Reporting and Dashboards
You can now build velocity reports for custom object pipelines the same way RevOps teams build deal velocity reports. Average time in each stage, median time to close, and stage-by-stage drop-off analysis all become possible without exporting to a spreadsheet.
If you're sharing dashboards with partners or clients, this pairs well with the reusable dashboard template feature HubSpot released for Solutions Partners. Build the timing report once and share it across portals.
Key Takeaway
Cumulative Time in Stage is the property to build your bottleneck analysis around. It catches records that have re-entered the same stage multiple times, which is often where process problems hide.
Workflow Automation
Time-based triggers on custom objects were limited before this. Now you can enroll records when Time in Current Stage exceeds a threshold. That means automatic escalations, SLA alerts, owner notifications, and stage nudges, all running without anyone checking a dashboard.
Teams running structured post-sale processes will feel this most. If you use custom objects for customer onboarding milestones, for instance, these properties let you automate the "this milestone has been open for seven days" alert that currently lives in someone's head. The Onboarding Plans update HubSpot shipped recently pairs directly with this kind of time-aware automation.
Key Takeaway
Time in Current Stage is live, not historical. Use it for real-time escalation triggers. Use Cumulative Time in Stage for historical analysis and process reviews.
RevOps and Process Design
RevOps leaders who modeled custom object pipelines for non-deal processes now have the timing data to benchmark those processes properly. You can set stage SLAs, measure against them in reports, and surface the gap to leadership with real numbers.
This also makes custom objects a more credible alternative to Tickets for teams that stretched Service Hub into use cases it wasn't designed for. If your custom pipeline is tracking something that moves through defined stages and timing matters, you now have the instrumentation to run it properly.
For a broader look at how HubSpot's May 2026 releases are connecting data across hubs, see the May 2026 updates roundup on what the pattern actually means for RevOps teams.
Properties and Data Model
These six properties are read-only and system-generated. You don't configure them. You do need to think about which stages matter most for your analysis before you build reports around them, because each property is tied to a specific stage ID. Name your stages clearly before you start pulling data.
Who Should Care Most
This update is specifically for Enterprise tier portals. Within that group, here's who gets the most value:
- RevOps leaders who built custom object pipelines for post-sale, fulfillment, or operational workflows and need timing benchmarks to run QBRs with leadership
- Sales Ops and CS Ops managers who want SLA alerting on custom pipelines without building a custom integration or exporting data to BI tools
- HubSpot admins managing complex portals where multiple custom objects model distinct business processes, and timing data helps prove whether each process is working
- Growing B2B companies that use custom objects to mirror a complex service delivery model and need to track cycle time as a KPI
If you're on Professional tier, this isn't available to you yet. It's worth flagging to your leadership team as a reason to evaluate the Enterprise upgrade path, especially if you're already using custom objects in core operations.
George's Take
I've spent years watching smart teams build impressive custom object pipelines in HubSpot, only to manage them by gut feel because the timing data wasn't there. We'd see portals where someone had built a genuinely sophisticated post-sale process, twelve stages, clean automation, good property structure, and then they'd track progress by eyeballing the board and trusting their most experienced humans to flag when something felt slow. That's not a process problem. That's a data availability problem. And HubSpot just fixed it.
“You can't optimize a process you can't measure. Custom objects finally have the clock they've always needed. Now the question is whether your team knows how to read it.”
If your portal has custom object pipelines in place, don't wait to act on this. The data starts accumulating now. The teams that build their bottleneck reports this week will have a quarter of timing data before competitors who sleep on it have configured a single property.
Ready to make your custom object pipelines actually measurable? Book a strategy call with the Sidekick team and let's map out the reports and workflows that will make this update count in your portal.
Frequently Asked Questions
What are stage calculated properties for custom objects in HubSpot?
Stage calculated properties are six system-generated fields HubSpot automatically populates as records move through pipeline stages on custom objects. They track entry dates, exit dates, time in specific stages, and time in the current stage, giving teams timing data for reporting, views, and workflow triggers without any manual configuration.
Which HubSpot plans include stage calculated properties for custom objects?
Stage calculated properties for custom objects are available on Enterprise tier only, across Content Hub, Marketing Hub, Data Hub, Sales Hub, Smart CRM, and Service Hub. Professional and lower tiers don't have access to this feature as of the May 18, 2026 release.
How are stage calculated properties on custom objects different from those on Deals or Tickets?
The six properties work the same way across all object types. The difference is that custom objects previously lacked these properties entirely, while Deals, Tickets, and Projects have had them for years. This update closes that gap so any custom pipeline can now track stage timing with the same built-in precision.
Can I use stage calculated properties in HubSpot workflows for custom objects?
Yes. Time in Current Stage is the most useful workflow trigger. You can enroll custom object records when they've been in a stage longer than a defined threshold, then fire tasks, notifications, or status updates. This enables SLA alerting and escalation automation on any custom pipeline without a third-party integration.
What's the difference between Latest Time in Stage and Cumulative Time in Stage?
Latest Time in Stage tracks only the most recent visit to a specific stage. Cumulative Time in Stage adds up all time spent in that stage across every visit. If a record was moved back to an earlier stage and then forward again, the cumulative property captures the full total while the latest property shows only the most recent pass.
Do stage calculated properties on custom objects backfill historical data?
HubSpot begins populating these properties as records move through stages going forward from the release date. Historical stage movement that occurred before May 18, 2026 isn't retroactively calculated. Teams should start building reports and workflows now to accumulate meaningful data over the coming weeks and months.
