Two different Deal close dates for same deal for different users

CRM & Sales CRM
1

As the title suggests,
two of our users one in CDT and one in EDT are seeing two different deal close dates on the same deal. This is creating reporting and tracking issues while them being just 1 hour apart.
Ideally, I believed each user sees the date as the same indifferent to their time zones. What am i missing?
Is it because of the automation/integration or is valid for manual deal close date tagging too?

2

This is a known issue in HubSpot. The Deal Close Date property is stored as a timestamp (including time and date) in UTC, but the user interface displays it based on each user’s local time zone. This can cause the same deal to appear with different close dates for users in different time zones, especially if the close date is set to midnight or the end of the day.

Key points:

  • HubSpot stores all date/time properties in UTC.
  • When a user views a date, HubSpot converts it to their local time zone.
  • If a deal close date is set to 2024-08-25 (with no specific time), HubSpot may interpret this as 2024-08-25 00:00:00 UTC. For a user in CDT, this could display as 2024-08-24 19:00:00, and for a user in EDT, as 2024-08-24 20:00:00, potentially showing as the previous day.
  • This issue affects both manual and automated/integrated updates to the close date.

This is not caused by your automation or integration alone; it is a core behavior of how HubSpot handles date/time fields.

What you can do:

3

@AAhmad564 wrote:

What you can do:

  • When setting close dates, try to set the time to noon UTC (e.g., 2024-08-25 12:00:00 UTC) to minimize the risk of date shifting across time zones.

@AAhmad564 how exactly would one set the close date to a time of the day when the deal close date is not a date time property but only accepts dates without times?

4

You are right @karstenkoehler
There is no way to set the time of day for the close date via the HubSpot UI or workflows as of now. This is a frequently requested feature, but not yet available.

But is only possible if you are using the API, where you can provide a full datetime value.
If you have developer resources, you can use the API to set the close date with a specific time (e.g., noon UTC) to minimize time zone issues. Otherwise, you are limited to the default behavior.

5

Hi @RKumar15,
Thank you for posting to the Community!
I’d like to tag in some of our Top Contributors to take a look here -- @Anonymous @JenBergren and @Jonno_Price Do you have any suggestions on this?
Cassie, Community Manager