Geotab data export: what fleets can pull for analysis or licensing

What can a fleet export from Geotab?#

A fleet can export most of what its Geotab devices and apps record: trips and GPS logs, engine diagnostics and fault codes, hours-of-service logs, inspection reports, driver safety exceptions, fuel or charging data and the zones and rules the fleet configured. Which fields and how much history are available depend on the plan, the devices and the add-ins in use.

Each data family carries a different privacy or rights question, so map them before anyone starts downloading.

MyGeotab reports, the API or the Data Connector: which route fits?#

The right Geotab export route depends on whether you need a one-time archive, full-detail history or a continuing feed. Most fleets end up using more than one route, and the choice should follow the purpose rather than habit.

Check Geotab's current documentation and your reseller for specifics, because report options, API limits and connector tables change over time. Record which route produced each file so anyone using the archive later knows how it was built.

History limits to check before cancelling#

History limits are the first thing to check before cancelling or switching, because what you can export after a contract ends is rarely what you could export the day before. Ask these questions in writing and keep the answers with the contract file.

• 1How far back is each data type kept at full detail, and is older data summarized or deleted?
• 2Does access end on the termination date, or is there a read-only or export window afterward?
• 3Who holds the agreement: Geotab directly, or a reseller whose terms add conditions?
• 4Which hours-of-service and inspection records must the fleet keep itself once the account closes?
• 5Do any add-ins or integrations store data outside MyGeotab, and does that data end with the subscription?
• 6Can the fleet export its rules, zones, groups and device assignments, which explain how the raw data was produced?

Getting the history out: an order of operations#

Getting Geotab history out works best in a fixed order that protects the hardest-to-replace records first. Configuration goes before data, because rules and groups change the meaning of everything recorded under them.

Store the exports in plain formats your team can read later, such as CSV or Parquet files with a short data dictionary, rather than inside a tool whose access also ends with a subscription.

• 1Inventory: list data types, date ranges, vehicles, drivers and add-ins in use.
• 2Configuration: export groups, rules, zones and device assignments before anything else changes.
• 3Compliance records: pull HOS logs and inspection reports and store them where retention duties can be met.
• 4Bulk history: use the API in date ranges for trips, logs, diagnostics and exceptions, checking counts as you go.
• 5Linking: keep vehicle and driver IDs consistent with your dispatch, ERP and maintenance systems.
• 6Verification: compare monthly totals against MyGeotab reports before the account closes.

Which Geotab data needs a privacy or rights decision?#

Geotab data that identifies or tracks a person needs a privacy decision before any use beyond running the fleet. That covers driver names and IDs, location trails that show where a driver goes after hours in a take-home vehicle, personal conveyance periods and safety events tied to an individual.

Rights matter too. The fleet's agreement with Geotab or its reseller sets what the fleet may do with exported data, and driver notices or union agreements set expectations about use. Customer site locations in zones and stop data can also reveal who your customers are.

For licensing, most packages keep vehicle-level patterns and milestone events, replace driver and customer identities with tokens, coarsen or remove location near homes and leave personal conveyance periods out entirely.

Illustrative: a building products distributor switches telematics providers#

Illustrative: a fictional building products distributor runs a private fleet of delivery trucks on Geotab through a reseller and plans to switch providers when the contract ends. The fleet manager assumed history would stay available afterward; the COO asks for the reseller's answer in writing first.

The team exports configuration, then HOS logs and inspection reports, then several years of trips, diagnostics and exceptions through the API in monthly batches. Each batch is checked against MyGeotab report totals, and trips are linked to delivery orders in the ERP by route and date.

Later, the distributor scopes a package showing how delivery stops, unload times and fault codes relate to late deliveries. Driver identities are tokenized, take-home trips outside working hours are removed and customer sites become site types.

What is useful for licensing, and how SourceX handles it#

Geotab history is most useful for licensing when it is linked to the work it supported: delivery orders, dispatch decisions, maintenance work orders and customer exceptions. Raw GPS points alone rank lower than trips joined to the jobs they served, because the decisions sit in the joined records.

Under the SourceX Enterprise Data Value Framework, fault codes linked to repair work orders and late deliveries carry more domain expertise and AI utility than raw location logs, which are easier to reproduce and carry a heavier privacy burden.

SourceX begins with a fit check that asks only about systems, years of history and available joins. SourceX does not host large telematics archives; they stay on the fleet's own servers or travel on encrypted drives. Once a package is approved, its SourceX Evidence Packet lists the data's origin, the driver and location treatments, the permitted use and who released it.