HubSpot stores every datetime field as UTC milliseconds since the Unix epoch. The connector preserves that — OData exposes those values as Edm.DateTimeOffset with UTC offsets, and Power BI imports them as UTC datetimes.
Why it happens #
This is HubSpot’s storage model, not a connector choice. The HubSpot API returns the same UTC milliseconds for everyone, regardless of the viewer’s timezone. The HubSpot web UI converts to your local timezone for display only; the underlying value is UTC.
How to localize in Power BI #
Power BI lets you convert datetime columns to a local timezone in the Power Query editor:
- Open the dataset in Power Query (Transform Data).
- Right-click the datetime column → Transform → Time Zone → To Local Time (or pick a specific zone with To Time Zone → …).
- Apply.
If your report is shared with viewers in multiple timezones, consider leaving the datetime as UTC and letting the viewer interpret it — or use a slicer that lets each viewer pick their zone.
Related #
- Filter Rows — filtering by UTC datetimes.
