Buying a trucking company: transferring ELD, telematics and dispatch data

Why do fleet records need their own closing workstream?#

Fleet records need their own workstream because they sit in several vendor systems, each tied to the carrier's identity and each governed by a separate contract. A purchase agreement that transfers trucks, trailers and customer relationships can still leave the buyer without the hours-of-service history, maintenance trail or dispatch archive it needs after closing.

Those records do real work after a deal. They answer compliance reviews and audits, support claims and litigation defense, show which lanes and customers made money, and carry the dispatch and exception history that AI developers may later want to license. Losing them in a rushed migration is hard to undo.

Start the workstream at the letter of intent. Ask for a system list, account owners and vendor contracts in the first diligence request, because vendor consents and export work can take longer than the legal documents.

Stock deal or asset deal: what changes for the records#

Deal structure decides who owns the records and who keeps the duty to retain them. In a stock purchase the carrier entity continues, so its accounts and obligations continue too. In an asset purchase the seller's entity keeps its history and duties unless the agreement moves copies and access to the buyer.

Registration and operating authority questions sit alongside the records. Confirm with transportation counsel how FMCSA treats the ownership change in your structure before assuming any account or number carries over.

System-by-system transfer checklist#

A transfer checklist works best when it names each system, its account owner and its export route. Run it during diligence, not after closing, so gaps show up while price and escrow are still open.

For each item, record whether history will be exported, migrated, kept live in the seller's account or archived, and who signs off. A named owner on both sides prevents the common gap where each party assumes the other ran the export.

Video deserves special attention. Camera platforms keep footage according to account settings: Samsara, for example, offers camera retention settings from 3 days to 4 years, with defaults that depend on region and sign-up date. Check the setting actually in force on the target's account, and save clips tied to open claims or litigation holds should be saved before any account change, with a log showing which events were preserved and why.

• 1ELD provider: account owner, administrator access, records of duty status, supporting documents and the backup copy.
• 2Telematics platform: GPS history, engine fault codes, driving events and the video retention settings in force.
• 3Dispatch or TMS, such as McLeod: loads, rate confirmations, customer and lane history, driver settlements and exception notes.
• 4Maintenance system: work orders, inspection reports, driver vehicle inspection reports and parts history.
• 5Safety and compliance files: driver qualification files, accident register and roadside inspection history.
• 6Drug and alcohol testing program: who holds the records and how restricted access will be handled.
• 7Fuel, tolls and tax: fuel card data and the records behind fuel tax and registration filings.

Retention duties that come with the fleet#

Retention duties attach to several of these record families, and a buyer should know which party carries each one after closing. Two examples show the range: records of duty status and supporting documents must be kept for six months from receipt under 49 CFR 395.8(k)(1), while 49 CFR 391.51 requires each driver qualification file to be kept for as long as the carrier employs the driver and for three years after. Other periods are set in FMCSA, DOT and tax rules and can change, so confirm current requirements with compliance counsel.

Where the seller keeps a duty, write an access clause into the purchase agreement so the buyer can obtain records it needs for claims or audits, and the seller can retrieve records it must still produce.

Contract clauses to read before signing#

Contract clauses in the target's vendor agreements decide how smooth the transfer will be. Read them in diligence and price the friction into the deal.

Start with assignment and change of control, which tell you whether the vendor must consent. Then read data ownership and export terms, including formats and any fees for bulk exports or historical video. Check termination terms for what happens to data when an account closes, and whether the vendor deletes history after a set period.

Finally, read any clause that lets the vendor use customer data for its own products or AI models. A buyer inheriting that clause inherits its consequences, including possible limits on licensing the same records elsewhere.

Illustrative: a regional carrier buys a smaller flatbed fleet#

Illustrative: a fictional regional carrier agrees to buy a smaller flatbed fleet through a stock purchase. The target uses a different ELD provider, a separate camera vendor and an older on-premise dispatch system.

During diligence, the buyer's COO builds a system checklist and finds that the camera vendor keeps video only for a limited window and that the dispatch system's license cannot be moved to new servers. The parties agree to keep the target's ELD and camera accounts live through a transition period, export dispatch history in full before the old system is retired, and tie an escrow release to completed exports.

After closing, every hours-of-service record and maintenance file is accounted for, and the dispatch archive, including years of exception notes, sits in the buyer's own storage.

Where SourceX fits after an acquisition#

SourceX fits after the records are secured. Acquired carriers often bring dispatch and exception histories that may be licensable, but inherited vendor terms, driver notices and customer contracts need a fresh rights review in the name of the entity that now holds them.

The SourceX five-step transaction runs that review in the Rights step, and the SourceX Evidence Packet records provenance across entities, so a buyer can show which company created each record and who approved its release.

Buyers who plan for this keep the option open. A dispatch archive exported with its notes, change history and customer references intact is far easier to scope later than one rebuilt from reports after the seller's systems are gone.