Migration planning, testing and go-live support
Switch Taxi Dispatch Software Without Treating It Like a Simple Login Change
You can't just switch off one dispatch system and hope the replacement works fine come Monday morning. Dispatch, pricing, driver records, passenger booking, account work, and reporting can all depend on what's already in place. Switching taxi dispatch software properly starts with actually understanding those dependencies first.
The switching process
The process: discovery, documenting booking channels, dispatch rules, fleet size, pricing, branches, and critical integrations. Configuration, setting up company structure, user access, drivers, vehicles, pricing, and workflows. Data review, identifying what can genuinely be exported and imported, never promised before the source data's actually been inspected. Testing, representative bookings run start to finish, driver and passenger flows included. Training, for dispatch, admin, and driver rollout. A go-live plan with agreed timing and escalation routes. And early-life support monitoring launch issues as they come up.
- Discovery - document booking channels, dispatch rules, fleet size, pricing, branches, and critical integrations.
- Configuration - set up company structure, user access, drivers, vehicles, pricing, and workflows.
- Data review - identify what can genuinely be exported and imported. Never promised before the source data's actually been inspected.
- Testing - representative bookings run start to finish, driver and passenger flows included.
- Training - for dispatch, admin, and driver rollout.
- Go-live plan - agreed timing and escalation routes.
- Early-life support - monitoring launch issues as they come up.
Questions to ask before switching any taxi platform
Questions worth asking before switching any platform: can you export your driver, vehicle, account, and booking data? Which third-party services connect to your current system? Which pricing rules are genuinely business-critical? Who needs access, and what should each role actually see?
- Can you export your driver, vehicle, account, and booking data?
- Which third-party services connect to your current system?
- Which pricing rules are genuinely business-critical?
- Who needs access, and what should each role actually see?
Migration scope depends on the source system
Migration depends on the data that the current system can export and the quality and format of that data. CabTaxi reviews the available source before confirming scope.
A realistic migration plan is based on evidence, not reassurance. Where data cannot be imported cleanly, CabTaxi agrees with the operator what will be recreated, who is responsible and how the result will be checked before go-live.
Frequently asked questions
Direct answers to the questions operators ask most often about switch to cabtaxi.
Can CabTaxi migrate all my data?
Depends entirely on what your current system can export and the quality of that data, reviewed before scope is confirmed.
Will I need to retrain dispatchers?
Some training, yes, focused on workflows staff actually use.
Can we test before going live?
Yes, a representative workflow test is recommended first.
Related pages
Compare CabTaxi and iCabbi
A dated, sourced comparison of the two providers.
Compare CabTaxi and Autocab
A dated, sourced comparison of the two providers.
Founding Operator Programme
Assisted configuration and hands-on launch support.
See CabTaxi using your own workflow
Show us how bookings enter your business and how your dispatchers assign work. We will demonstrate the equivalent CabTaxi workflow rather than a generic feature list.
Email office@cabtaxi.co.uk or call 01293 974097.
