The DIQ Go-Live Method
The switch is a product feature, not a project
Changing software is the part everyone dreads, so we built the move into the product: an agent that reads your files, a board where nothing imports without your approval, compliance clocks rebuilt from your real dates, and a checklist that tracks you to live.
- 1
The migration agent reads what you already have
Upload the files you run on today — fleet rosters, driver lists, insurance schedules, fuel and expense sheets, load history, broker and customer lists — as XLSX or CSV, plus PDFs and photos of documents like COIs, CDLs, medical cards and registrations. The agent maps your columns to DIQ fields and normalizes the values ("Reefer", state names, two-digit years), so messy headers are its problem, not yours.
- 2
Nothing imports without your approval
Everything the agent proposes lands on a review board as a draft. Records like trucks, drivers, trailers, policies and customers you can fix right on the board — remap a column, edit a value, tick rows in or out. High-volume sheets (past loads, fuel, expenses) commit as a reviewed batch: clean rows import, problem rows stay behind for you to fix in the sheet. Either way, nothing becomes a record in your account until you commit it — the same approve-first rule that governs all of DIQ’s AI.
- 3
Your compliance clocks come back to life
Expiry dates in your sheets and on your documents — CDL, medical card, registration, annual inspection, insurance, IFTA, and any other renewal date column on your truck, trailer or driver sheets — are rebuilt as renewal clocks attached to the driver, truck or carrier they belong to. Anything the agent can’t match with certainty is left for you, never guessed. From day one, the Renewal Radar and dispatch-readiness lights run on your real dates instead of an empty account.
- 4
A go-live checklist that knows what’s left
A checklist on your dashboard is computed from your account’s actual state — carrier verified against FMCSA, fleet in, driver pay set, first rate con read by AI, first load dispatched, cost per mile set, first invoice created. It always shows the next step, nudges about once a day, and disappears once every step is done.
How the rest of the product protects your data: Security & architecture →
The 14-day go-live target
We work every new account against a 14-day go-live target: from first sign-in to a migrated, running operation — fleet and history in, clocks live, real loads dispatched and invoiced. That number is a target, not a guarantee. Every operation’s paperwork is different, and we won’t print it as a promise until enough real onboardings have proven it — when they have, this page will show the numbers. What we can say today: the method above ships in the product, and the import is an upload-review-commit pass, not a scheduled implementation project. The dispatch track has no free trial — it starts with a paid 30-day pilot (your first month, at your plan’s normal price), and that pilot includes a 20-minute onboarding call after signup. This method is the agenda.
What this page doesn’t claim
There’s no direct TMS-to-TMS integration yet — if you’re leaving another system, export your data to CSV or XLSX and the same method applies. Until you pick a plan, trial accounts are capped at a small evaluation fleet — pick your plan during the trial and your real limits apply. And the 14-day figure stays labeled a target until real onboardings have proven it. We publish what the product does, not what we hope it will do.
See the method in your own account
Create your account — the first step of the checklist is waiting on your dashboard.