How to switch taxi dispatch software without losing bookings

Deciding to switch taxi dispatch software is the easy part. Actually doing it without dropping bookings, confusing drivers, or losing customers? That’s where most operators get nervous. And honestly, that nervousness is justified. A bad migration can cost you thousands in missed jobs and driver churn.

But here’s the thing: operators across the UK switch dispatch systems every week, and the ones who plan it properly don’t lose a single booking. This guide walks you through exactly how to do it, step by step, based on what we’ve seen work for real taxi and private hire companies.

Why operators switch taxi dispatch software

Before getting into the how, it helps to understand the why. Most operators don’t switch because they’re bored. They switch because something is broken or too expensive.

Common reasons include:

Long-term contracts with annual price increases
Clunky interfaces that slow dispatchers down
Poor driver app reliability
Expensive hardware requirements
Lack of modern features like AI call handling or web booking
Slow or offshore support when things go wrong

If any of those sound familiar, you’re not alone. We’ve covered the specific differences between major providers in our complete guide to choosing taxi dispatch software, which is worth reading before you commit to any new system.

Step 1: Audit your current system before you switch taxi dispatch software

You can’t plan a clean migration if you don’t know what you’re migrating. Spend a day documenting everything your current system handles.

What to document

Total number of active drivers and vehicles
Account customers and their billing arrangements
Recurring bookings (school runs, hospital contracts, corporate accounts)
Phone system integration (SIP trunks, IVR setup, phone numbers)
Driver compliance documents stored in the system
Zone and fare configurations
Any API integrations with third-party platforms

Write all of this down. Seriously, use a spreadsheet. The operators who skip this step are the ones who discover three weeks after going live that their airport zone pricing didn’t carry over.

Export your data early

Most dispatch systems let you export customer lists, driver records, and booking history as CSV files. Do this now, even if you haven’t chosen your new provider yet. Some older systems make data export deliberately difficult, and you don’t want to discover that the day before your contract ends.

If your current provider is Autocab, iCabbi, or TaxiCaller, we’ve written specific comparison guides that cover data portability:

Step 2: Choose your new dispatch system (and test it properly)

Don’t just watch a demo and sign up. Actually test the system with real scenarios from your operation.

Questions to ask during evaluation

Can you import our existing customer and driver data?
How long does setup take from sign-up to going live?
Is there a contract, or can we leave if it doesn’t work out?
What happens to our phone numbers? Can we port them?
Do drivers need new hardware, or does the app work on their current phones?
What does onboarding support look like?

Setup time matters more than most operators realize. Some systems take weeks to configure. Others, like CAB-X, can get you live within 24 to 48 hours because there’s no hardware to install and the system is cloud-based. That speed difference can be the difference between a smooth cutover and a painful two-week period of running two systems.

Run a parallel test

If your new provider allows it, set up the system and run test bookings alongside your existing platform for a few days. Create test drivers. Put through test jobs. Check that fare calculations match your expectations. This catches configuration issues before they become real problems with real customers.

Step 3: Plan your cutover date carefully

Timing your switch taxi dispatch software migration is critical. Pick the wrong day and you’ll be troubleshooting during your busiest period.

Best practices for timing

Avoid switching on a Friday night or Saturday. If something goes wrong, you want business hours available for support.
Tuesday or Wednesday morning is usually ideal for UK operators. Booking volumes are lower mid-week.
Avoid switching during school run contract start dates, major local events, or holiday periods.
Give yourself at least two weeks between choosing your new system and going live. Rushing creates mistakes.

Communicate the switch date internally first

Your dispatchers need to know before your drivers do. Schedule a 30-minute walkthrough of the new dispatch portal with your office team at least a week before cutover. They should feel comfortable with the basic workflow: creating a booking, assigning a driver, editing a job. If your dispatchers aren’t confident, your cutover day will be chaotic.

Step 4: Migrate your data cleanly

Data migration sounds technical, but for most taxi operators it comes down to three things: customers, drivers, and pricing.

Customer data

Export your customer list from your old system. At minimum, you need names, phone numbers, email addresses, and any account billing details. If your new system supports CSV import, this can take minutes. If you have corporate accounts with specific pricing rules, document those separately and configure them manually in the new system.

Driver and vehicle data

Export driver names, phone numbers, badge numbers, vehicle registration details, and license expiry dates. Compliance documents like DBS checks, insurance certificates, and council licenses should be re-uploaded to the new system. This is tedious but important. Missing a license expiry because you didn’t migrate compliance data properly creates a real liability risk.

Fare and zone configuration

This is where operators most commonly make mistakes. Don’t assume your new system uses the same fare structure logic as your old one. Walk through every fare scenario: metered fares, fixed prices, zone-to-zone pricing, airport runs, out-of-area charges. Test each one with a sample booking before going live.

Step 5: Get your drivers on the new app

Driver adoption makes or breaks a dispatch software switch. If drivers can’t or won’t use the new app, nothing else matters.

How to handle driver onboarding

Start communicating with drivers at least one week before cutover. Send a clear message explaining:

Why you’re switching (be honest about the benefits)
When the switch happens
What they need to do (download the new app, log in with provided credentials)
What changes for them day-to-day

Keep it simple. Most drivers care about three things: can they see and accept jobs quickly, does the navigation work, and does the app drain their phone battery. Everything else is secondary.

Run a driver training session

In-person is best if you can manage it. Even 20 minutes in your office showing drivers how to go online, accept a job, navigate to pickup, and complete a trip will prevent 90% of day-one issues. If in-person isn’t practical, a short video walkthrough sent via WhatsApp works surprisingly well.

One thing we’ve noticed: systems with simpler driver apps have dramatically higher adoption rates. If a driver can figure out the app without training, that’s a good sign. Complex apps with too many screens cause frustration and resistance. The CAB-X driver app was specifically designed to be usable without formal training, which matters when you’re asking 50 or 100 drivers to switch overnight.

Step 6: Handle your phone system transition

Your phone number is your business. Customers have it saved, it’s on your cards, it’s on Google. Don’t lose it.

Number porting

If your current dispatch system controls your phone number through their SIP integration, you need to port that number to your new provider or to an independent SIP trunk provider. Start this process early because number porting in the UK can take 5 to 10 business days depending on the carrier.

Temporary forwarding

If porting isn’t complete by cutover day, set up temporary call forwarding from your old number to a new one connected to your new dispatch system. This ensures zero missed calls during the transition period.

Consider AI call handling

If you’re switching systems anyway, it’s a good time to consider AI-powered booking systems that can answer calls, take bookings, and route overflow automatically. This reduces the pressure on dispatchers during the transition period and beyond.

Step 7: Go live and monitor everything

Cutover day. Here’s your checklist.

Morning of go-live

Confirm all drivers are logged into the new app and showing as available
Process a test booking end-to-end before taking real calls
Verify your phone number is routing to the new system
Have your old system accessible (but not active) as a reference
Keep your new provider’s support number on speed dial

First 24 hours

Stay in the office. Or at least stay available. The first day is when small configuration issues surface. A fare that’s calculating wrong. A zone boundary that needs adjusting. A driver who can’t log in because they typed their email wrong. None of these are catastrophic, but they need quick fixes.

Have one person dedicated to monitoring the dispatch portal and another handling driver questions. If you’re a smaller operation, ask your new provider’s support team to be on standby. Good providers will do this. If yours won’t, that tells you something.

First week

Review daily booking numbers against your old system’s averages. Are you processing the same volume? Are response times similar or better? Check your missed booking rate. If it’s higher than before, dig into why. Usually it’s a dispatch configuration issue, like auto-assign radius being too narrow, or drivers not having notifications enabled.

Step 8: Handle forward bookings from your old system

This is the detail that catches people out. If a customer booked a trip two weeks ago for a date after your cutover, that booking lives in your old system. It won’t magically appear in the new one.

How to handle this

Before cutover, export all future-dated bookings from your old system
Re-enter them into your new system manually, or import them if your new provider supports it
Double-check recurring bookings like school contracts and corporate accounts
Verify that the customer will receive the correct confirmation from the new system

For operators with hundreds of forward bookings, this is the most time-consuming part of the migration. But it’s non-negotiable. Missing a pre-booked airport run because it was stuck in your old system is exactly the kind of thing that loses customers permanently.

Step 9: Decommission your old system

Don’t cancel your old system on day one. Keep it accessible in read-only mode for at least two weeks after cutover. You may need to reference old booking records, customer details, or driver documents that didn’t migrate cleanly.

Once you’re confident everything is running smoothly on the new platform:

Download a final data export from the old system for your records
Cancel your subscription or give contractual notice
Confirm that your phone number port is complete and the old provider no longer has control
Remove old driver app instructions from any onboarding materials

Common mistakes when operators switch taxi dispatch software

We’ve seen dozens of migrations over the years. Here are the mistakes that keep showing up.

Rushing the switch

Operators who try to switch taxi dispatch software in a single day without preparation always hit problems. Give yourself two weeks minimum from decision to go-live.

Not testing fares

Assuming your new system will calculate fares identically to your old one is dangerous. Always run test bookings through every fare scenario before going live.

Ignoring driver communication

Sending a text message on cutover morning saying “download this new app” doesn’t work. Drivers need context and time. One week’s notice is the bare minimum.

Forgetting forward bookings

Already covered above, but it’s worth repeating. Forward bookings are the number one cause of lost jobs during a migration.

Not having a rollback plan

Things can go wrong. Have a plan to revert to your old system for 24 hours if the new one has a critical issue. This means keeping your old system active (not cancelled) through the first week.

What a clean migration looks like

When done right, your customers won’t even know you switched. They’ll call the same number, book through the same channels, and get picked up on time. Your drivers will have a new app on their phone that they figured out in ten minutes. Your dispatchers will have a cleaner screen with less clicking.

The cost comparison between providers often shows that operators save money after switching, especially when moving away from systems with hardware costs or long-term contracts. But the real win isn’t just financial. It’s operational. A system that works the way your business actually operates means fewer errors, faster dispatch, and happier drivers.

If you’re considering a switch and want to see how quickly you could get up and running, get in touch with the CAB-X team. Most UK operators go live within 24 to 48 hours, with full data migration support and no setup fees. No contract lock-in either, so if it doesn’t work for your operation, you’re not stuck.

Frequently Asked Questions

How long does it take to switch taxi dispatch software?

With proper planning, most UK operators can switch taxi dispatch software within two weeks from decision to go-live. The actual system setup can take as little as 24 to 48 hours with cloud-based providers like CAB-X, but you should allow extra time for data migration, driver training, and phone number porting.

Will I lose bookings when switching dispatch systems?

Not if you plan properly. The key is exporting all forward-dated bookings from your old system and re-entering them into the new one before cutover. Also ensure your phone number is ported or forwarded so no customer calls are missed during the transition.

Do my drivers need new phones or hardware for a new dispatch system?

Most modern cloud-based dispatch systems run on standard Android and iOS smartphones. Drivers typically just need to download a new app. No specialist hardware or PDA devices are required with providers like CAB-X.

Can I keep my existing phone number when switching dispatch software?

Yes, in most cases you can port your existing phone number to your new provider or to an independent SIP trunk. The porting process in the UK usually takes 5 to 10 business days, so start early. Temporary call forwarding can cover any gap.

What data can I migrate from my old taxi dispatch system?

You can typically export and migrate customer contact details, driver and vehicle records, fare and zone configurations, corporate account details, and forward-dated bookings. Most systems allow CSV exports, though some older providers make this more difficult.

How to switch taxi dispatch software without losing a single booking