The Samsara Power BI 6-month limit, and how to get your full history
Samsara's official Power BI connector only reaches back about 6 months. If you need a full year — or several — of trips, HOS or safety data, that wall stops your report cold.
The 6-month limit lives in Samsara's official Power BI connector, not in your data — the history is still there in your account. To get past it, read the Samsara API directly with your own token, page through the full available history, flatten the nested JSON into rows, and refresh on a schedule. That's exactly what Fleet Export does: you paste your own Samsara token, it handles the pagination, rate limits and flattening, and lands clean rows in a Power BI dataset (or Google Sheets, QuickBooks or CSV) without a single line of Python.
Why the 6-month limit happens in the first place
The Samsara Power BI connector is built for dashboards, not deep history. To keep refreshes fast and payloads small, it scopes the data it returns to a rolling recent window — in practice the last 6 months or so. The records older than that aren't deleted; the connector just won't hand them to Power BI.
That's fine for an operational view of this quarter. It falls apart the moment you need a year-over-year safety trend, an annual idling or fuel summary, or a full-history dataset for a finance review. The data exists in your Samsara account — it simply isn't reachable through the connector.
Why you can't just 'pull more' from the API by hand
The obvious fix is to skip the connector and call the Samsara API yourself. In theory you can read as far back as your account allows. In practice, getting that into Power BI cleanly is a real engineering job:
- Pagination. History comes back in pages behind cursors. Miss a cursor and you silently drop rows — and never notice until a number looks wrong.
- Rate limits. Pull a year of trips too fast and you get throttled. A naive loop needs proper backoff and retries to finish at all.
- Nested JSON. Samsara responses nest vehicles, drivers, events and timestamps several levels deep. Power BI wants flat rows, so something has to flatten that structure reliably.
- Refresh. A one-time pull is stale tomorrow. You need it to re-run on a schedule, not be re-coded every month.
This is why teams end up with brittle hand-rolled scripts or an expensive consultant just to move numbers into a spreadsheet.
The workaround: read the API, flatten, schedule
Fleet Export is a single-purpose data pipe that does the awkward part for you. You connect with your own Samsara API token, pick the endpoints you care about — HOS, trips, idling, fuel, safety events — and it:
- Pages through the full available history, not just the last 6 months, following every cursor to completion.
- Backs off against the documented rate limits and retries failures, so a large pull actually finishes.
- Flattens the nested JSON into clean, tabular rows that Power BI can load directly.
- Refreshes on the schedule you set, so the dataset stays current without you touching code.
Your token stays yours and your data flows into your destination. Nothing is resold, and Fleet Export never sits between you and your Samsara account.
Connector vs API-by-hand vs Fleet Export
| Samsara Power BI connector | Hand-rolled API script | Fleet Export | |
|---|---|---|---|
| History depth | ~6 months only | Full (if coded right) | Full available history |
| Handles pagination | N/A | You build it | Yes |
| Handles rate limits | N/A | You build it | Yes |
| Flattens nested JSON | Partial | You build it | Yes |
| Scheduled refresh | Yes | You maintain it | Yes |
| Needs a developer | No | Yes | No |
Get your full Samsara history into Power BI
Paste your own Samsara token and Fleet Export handles the pagination, rate limits and flattening — full history, on a schedule, no Python. Get started in minutes.
Enter your work email to get started
Uses your own API token. Works with Samsara, Geotab and Motive.
FAQ
Why does Samsara's Power BI connector only show 6 months?
The connector scopes its data to a recent rolling window — about 6 months — to keep refreshes fast. Your older history still exists in your Samsara account; the connector just won't return it.
Can I get more than 6 months of Samsara data into Power BI?
Yes, by reading the Samsara API directly with your own token instead of relying on the connector. Fleet Export does this for you — paging through the full history, flattening the JSON, and landing clean rows in Power BI on a schedule.
Is my Samsara API token safe with Fleet Export?
You connect with your own API token and the data flows into your own destination — your Power BI dataset, Google Sheet or CSV. Fleet Export doesn't resell your data or sit between you and Samsara.