Migration planning, testing and go-live support
Switch Taxi Dispatch Software Without Treating It Like a Simple Login Change
Changing dispatch software is an operational project. A taxi business cannot simply turn off one system and hope the replacement works on Monday morning. Dispatch, pricing, driver records, passenger booking, account work, staff permissions and reporting can all depend on the existing setup. CabTaxi's switching process starts by understanding those dependencies and agreeing what data can realistically be migrated.
The switching process
The objective is to configure and test the new environment before go-live and to agree what data can realistically be migrated from the current platform.
- 1. Discovery - document booking channels, dispatch rules, fleet size, pricing, branches, account work and critical integrations.
- 2. Configuration - set up company structure, user access, drivers, vehicles, pricing and required workflows.
- 3. Data review - identify available export formats and agree what can be imported or recreated. Migration is never promised before the source data is inspected.
- 4. Testing - test representative bookings from creation to completion, including driver and passenger flows.
- 5. Training - train dispatch and admin users and the people responsible for driver rollout.
- 6. Go-live plan - agree timing, responsibility and escalation routes for launch.
- 7. Early-life support - monitor the agreed launch issues and prioritise blockers.
Questions to ask before switching any taxi platform
Before committing, an operator should be able to answer these questions about data, integrations, pricing and support with every provider under consideration.
- Can you export your driver, vehicle, account and booking data?
- Which third-party services are connected to the existing system?
- Which pricing rules are business-critical?
- Which functions are used every day versus rarely?
- Who needs access and what should each role see?
- What is the minimum test that proves the new system can operate safely for your business?
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 data from my current system?
Migration depends on the data that the current system can export and the quality and format of that data. CabTaxi should review the available source before confirming scope.
Will I need to retrain dispatchers?
Any system change requires some training. The goal is to train the relevant roles on the workflows they actually use rather than overwhelming staff with every feature.
Can we test before going live?
A representative workflow test is recommended before go-live so booking, dispatch, driver and other critical processes can be validated.
Related pages
Compare CabTaxi and Other taxi's
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.
