First, know your two non-negotiables
Everything in an ELD switch bends around two regulatory facts. Get these right and the rest is logistics.
- Six months of records. Carriers must retain records of duty status and supporting documents for six months. That obligation survives the switch, and it is yours, not your old vendor's. If the only copy of last quarter's logs lives in a portal you are about to cancel, you have a problem.
- No gap in logging. Every driver must be on a compliant logging method every day. During a cutover that means the old device, the new device, or properly prepared paper logs, with no day where a truck runs on none of the above.
Your leverage with the old vendor disappears the moment you give notice. Export everything first.
Step 1: Export your history before you say a word
Before anyone calls the incumbent to negotiate or cancel, pull your data out. Six months of duty-status records at minimum, and ideally the full history: logs, edits and annotations, unidentified driving records, IFTA mileage by jurisdiction, DVIRs, and GPS history if you use it for anything downstream.
Download it in whatever formats the system offers and store it somewhere you control. Then spot-check it. Open a handful of drivers and confirm the export actually contains the days it claims to. Vendors' bulk exports are the least-tested feature they ship, and the worst time to discover a hole is after the account is closed.
Step 2: Read your contract before you cancel
The exit terms you agreed to at signing now decide your timeline and cost. Three things to find in the document, in order of how often they surprise people:
- The renewal date and notice window. Many ELD contracts auto-renew for a full year unless cancelled inside a 30 to 60 day window. If you are near the window, your switch date may have just chosen itself.
- Early termination fees, and whether they are charged per device or per account. Get the payoff number in writing and weigh it against what the new provider saves you. Paying two months of overlap is often cheaper than waiting out a renewal.
- Hardware terms. Leased devices usually must be returned within a set period, in working condition, at your shipping cost. Owned devices are yours, but they are useless with another provider, so plan on recycling them.
Step 3: Stand the new system up in parallel
Never schedule the old system's shutdown for the day the new one starts. Overlap them. Two to four weeks of running both, even if only on part of the fleet, converts every unknown about the new system into a known while you still have a working fallback.
During the parallel window, treat the new system as the one that has to prove itself:
- Install on a pilot group first, five to ten trucks, including your oldest vehicles and your least patient drivers.
- Confirm engine data is actually syncing: engine hours, odometer, and power-up events, per truck, not just for the fleet on average.
- Have a driver run a roadside transfer drill on the new device, both transfer methods, with someone playing the officer.
- Run one full payroll and one IFTA-relevant week off the new system's data and reconcile it against the old one.
- Only then schedule the fleet-wide install, in batches, with a person on each yard shift who has done it before.
The parallel window is cheap insurance. The failure mode it prevents, discovering a gap after the old system is dark, has no cheap fix.
Step 4: Cut over drivers, not just devices
The hardware swap takes minutes per truck. The part that actually determines whether week one is calm is the driver-facing change: a new app, a new login, a new place to certify logs, a new malfunction procedure.
Keep the training short and concrete. One session per driver group covering login, duty-status changes, certifying the day, the roadside inspection screen, and what to do if the device malfunctions. Print the new provider's malfunction instructions and put a copy in every cab, because that document is what a driver needs on the worst possible day, and it is required to be there.
- Update each cab's document packet: instruction sheet, malfunction procedure, and a supply of blank paper logs.
- Set a hard date after which the old app is deleted from driver phones, so nobody logs into the wrong system out of habit.
- Tell your safety and dispatch teams which system is authoritative for which dates. Mixed-source weeks confuse audits later.
If your provider was revoked, compress the same plan
When FMCSA removes a device from the registered list, carriers get a short runway, historically eight days from the notice, to replace it. The sequence above still applies, it just runs on a compressed clock: export immediately, skip the leisurely pilot, and lean on paper logs as the bridge if hardware can't arrive in time.
Drivers can run paper records of duty status temporarily during a documented malfunction or replacement window, but paper does not scale and enforcement patience is finite. A provider that can ship preconfigured devices overnight and activate them the day they arrive is worth a premium that week.
The cutover-day checklist
- Historical data exported, verified, and stored somewhere the old vendor can't touch.
- Written cancellation sent inside the notice window, with the confirmation saved.
- New devices installed and syncing engine data on every truck.
- Every driver logged in, trained, and carrying the new in-cab documents.
- Old devices collected for return or recycling, old app removed from phones.
- A named person watching unidentified driving events daily for the first two weeks, because they spike during every cutover.
