Switching ELD or telematics provider: get historical data out first

Why does the export have to come before the switch?#

The export has to come before the switch because the old provider's duty to keep and serve your data usually shrinks once the contract ends. Many agreements limit access after termination, and some providers delete account data after a period set in their terms, so the window can close before anyone notices a gap.

Hardware adds a second deadline. In-cab displays, cameras and gateways often go back to the provider or get swapped truck by truck, and anything stored only on a device leaves with it. Plan exports around the device swap schedule, not just the contract end date.

Attention is the third reason. Once the rollout starts, dispatch, safety and drivers are learning the new system. Exports done in a calm planning phase get checked; exports done during cutover get rushed.

The pre-cancellation export checklist#

The pre-cancellation checklist covers ten record families, from hours-of-service logs and inspection reports to video, integrations and account settings. Work through it in order and check each export against the dashboard before ticking it off.

Prefer record-level files over summary reports. A CSV of every duty status change, with driver and vehicle IDs and edit history, can be checked and reloaded later; a PDF of weekly totals cannot. Save the provider's field definitions with each export, because column names rarely explain themselves once the account is gone.

• 1Hours-of-service logs for every driver, including edits, annotations, unassigned driving events and malfunction or data diagnostic events.
• 2Supporting documents tied to duty status, such as fuel receipts, bills of lading and dispatch records, wherever they are stored.
• 3Driver vehicle inspection reports with defects and the repairs that closed them.
• 4Engine fault codes, diagnostics, odometer and engine hours history by vehicle.
• 5IFTA mileage by jurisdiction and the fuel purchase records behind it.
• 6GPS breadcrumb history and geofence events, if dispatch or claims rely on them.
• 7Safety events, driver scorecards and coaching notes.
• 8Event video and its metadata, starting with clips tied to accidents, claims or disputes.
• 9Integration settings: which TMS, maintenance and payroll systems pull data, and how.
• 10User lists, driver and vehicle ID lists, and screenshots of account configuration.

How should the switch be sequenced?#

The switch should be sequenced in four phases, with data work leading each one: before notice, between notice and the device swap, during the swap, and after cutover. Tie each phase to a named owner so exports do not fall between safety, IT and finance.

The last phase is the one fleets most often skip. Do not ask the old provider to delete anything until your archive has been checked against the manifest, because a deletion request cannot be undone.

• 1Before notice: read the termination and data clauses, get the export deadline in writing, pull claim-linked video and run a first full export.
• 2Between notice and device swap: export the remaining record families by quarter, build the driver and unit crosswalk, and start the new provider on a first group of trucks.
• 3During the swap: confirm drivers can show recent duty status, return devices against a checklist, and note any data held only on hardware.
• 4After cutover: run a final export covering the last days on the old system, check it against the manifest, then request deletion confirmation.

Which retention rules apply to the records you export?#

Retention rules for ELD records come mainly from federal hours-of-service regulations, which require motor carriers to keep records of duty status and supporting documents for a minimum period and to produce them on request. The periods and document categories are set in FMCSA rules and can change, so confirm them with whoever owns safety compliance instead of trusting the provider's default settings.

Other duties sit alongside. Inspection and maintenance records fall under federal vehicle maintenance rules, fuel tax records under IFTA, and anything tied to a claim may be under a litigation hold. Insurers and customer contracts can ask for longer retention than the regulations do. Treat each period as a floor and write down who confirmed it.

What to ask the old provider in writing#

The old provider should confirm in writing what happens to your data after termination. A short written answer from the account team settles questions that a support ticket often leaves open, and it gives you a record if a gap appears later.

How do you keep drivers and dispatch running during the change?#

A parallel run keeps drivers and dispatch running: install the new provider on a first group of trucks while the old one stays active, then move the rest once logs, dispatch integration and driver training are proven. Drivers still need to show recent duty status at roadside after their truck changes over, so agree with your safety lead how prior logs will be available on swap day.

Map identifiers before the move. Driver IDs, unit numbers and vehicle groups in the old system rarely match the new one, and a simple crosswalk table saves real effort when someone later joins old fault codes to new ones for the same truck.

Owner-operators need their own line in the plan. Some run their own ELD accounts or carry devices under their lease, so confirm which accounts the carrier controls before exporting anything.

Illustrative: a regional tank carrier changes telematics providers#

Illustrative: a fictional tank truck carrier decides not to renew its telematics contract. The COO reads the agreement and finds that export access ends soon after the term, so the switch plan starts with data, not devices.

The safety director pulls claim-linked video first, then exports logs, supporting documents, inspections and fault codes by quarter, each with a manifest. IT builds a crosswalk of driver and unit IDs, and one terminal runs both systems before the rest of the fleet moves.

Later, an auditor asks for logs from before the switch and the carrier produces them from its own archive. When leadership asks whether maintenance history could interest AI developers, a metadata-only review scopes fault codes, defects and repairs with driver identities removed, and leaves video and location traces out.

How SourceX treats fleet records after a provider switch#

SourceX treats fleet records from a provider switch like any other archive: the first step is a metadata-only fit check, and nothing is shared during that assessment. Records that link a signal to an outcome, such as a fault code linked to the work order that fixed it, tend to matter most.

If the fleet proceeds, the work follows the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The Rights step covers the provider agreement and driver notices, Preparation removes driver identities and coarsens locations, and the SourceX Evidence Packet documents the scope the fleet approved.