Every vendor will tell you how long onboarding takes. Almost none of them tell you what actually happens during it — which days are busy, which days are quiet, and where your team needs to show up versus where the vendor is doing the heavy lifting in the background. That gap is why so many providers go into a NEMT software switch nervous about disruption they don’t need to worry about, while missing the parts that actually do need their attention.
Before Day One: What Should Already Be Settled
By the time an actual switch begins, the contract should be signed and a few things confirmed: which broker integrations are being set up first, who on your team is the point of contact, and what your current data looks like — active trips, driver records, standing appointments — so it can be migrated rather than re-entered by hand.
Days 1–2: Data Migration and Core Setup
This part happens mostly without your team lifting a finger. Driver records, vehicle information, and historical or standing trip data get imported into the new system. Your job during this stretch is mostly answering questions and confirming that what’s been migrated actually matches your operation — not doing the heavy data entry yourself.
Days 3–5: Broker Integration Setup
This is where timelines vary the most, because it depends on the broker, not just the software vendor. Some broker API connections activate in a day. Others require the broker’s own IT process to approve and configure, which can add time outside anyone’s direct control. A vendor who’s upfront about which of your specific brokers fall into each category — instead of giving you one generic number — is giving you a realistic picture instead of a sales-friendly one.
Days 5–7: Dispatcher and Driver Training
This is the part that actually requires your team’s time and attention. Dispatchers need to get comfortable with the new interface, ideally by running real trips in a training environment rather than a generic demo. Drivers need the new app on their phones and a walkthrough of how status updates and signatures work. The quality of this week matters more to a smooth transition than almost anything else on the timeline — rushed training here is where switches go sideways later.
Week 2: Running in Parallel
Many providers run the old and new systems side by side for a short stretch, scheduling real trips in both to catch discrepancies before fully cutting over. This adds a little short-term overhead but meaningfully lowers the risk of a missed trip or billing gap during the transition. Skipping this step to save a few days is one of the more common regrets providers report after a rushed switch.
After Cutover: The First Full Billing Cycle
The real test isn’t day one of dispatch — it’s the first full billing cycle on the new system. This is where you find out whether claims are generating correctly, whether broker integrations are pulling trip data cleanly, and whether anything from the migration didn’t carry over the way it should have. A good vendor stays closely involved through this cycle rather than considering onboarding “done” the moment the dispatch board goes live.
What This Means for Planning Your Own Switch
The honest version of a timeline isn’t a single number — it’s a week that requires almost nothing from your team, a week that requires real attention from dispatchers and drivers, and a final stretch where the new system proves itself against your actual billing. Providers who plan around that shape, rather than around a marketing timeline, go into a switch with realistic expectations and far less disruption than they feared.
RoutingBox walks new customers through this exact structure, with a dedicated Customer Success Manager staying involved through that first full billing cycle rather than handing off the moment dispatch goes live.
See a Realistic Timeline for Your Fleet
If you’re considering a switch and want to know what it would actually look like week by week for your specific brokers and fleet size, schedule a demo with RoutingBox and ask for the real onboarding breakdown, not the marketing version.
