Article · 8 min read

Can you switch dispatch platforms without losing forward bookings?

Yes — and the operators who lose bookings all skip the same three steps.

By the Limozoft team · Last reviewed 2026-10-19

We've migrated dozens of operators off platforms they outgrew. Which means we've also seen the export files that didn't work and the customer data that didn't survive the move. Almost every failed migration failed on forward bookings, not on historical data.

Step 1 — Export before you give notice

Request your full data export while you are still a paying customer in good standing. Ask for trips, customers, corporate accounts, rate cards, drivers, vehicles and — critically — all reservations with a pickup date in the future, with no export window cap.

Step 2 — Audit the forward book

Sort future reservations by date. Anything beyond 90 days out is where systems silently truncate. Count them, then count them again in the import file. If the numbers differ, stop and fix the export before going further.

Step 3 — Rebuild rate cards, don't import them

Corporate rate cards, hourly minimums and zone tables rarely map cleanly between platforms. Rebuild them by hand and price-test ten historical trips in the new system against the old invoices. A 4% pricing drift across a corporate account is a lost contract.

Step 4 — Handle saved cards honestly

Card tokens belong to the payment processor, not the dispatch vendor. If both platforms sit on the same processor, request a token migration. If not, plan a re-authorisation email to account holders — and send it before cut-over, not after a declined charge.

Step 5 — Parallel run for 7 to 14 days

New bookings go into the new system only, from day one
Existing forward bookings stay visible in both
Dispatchers work the new board; the old one is read-only reference
Drivers get both apps installed, with a stated switch date

Step 6 — Cut over on a Tuesday

Never cut over on a Friday, never before a holiday weekend, never on an event date. Tuesday morning gives you three business days of vendor support before the weekend load. Our 5-day migration playbook has the day-by-day version.

The 10-point cut-over checklist

Forward booking counts reconciled
Rate cards price-tested against 10 old invoices
Corporate contacts and net terms verified
Driver accounts active and logged in
Vehicle and licence expiry dates carried over
Payment processor live and tested with a real charge
Booking engine pointed at your own domain
SMS/WhatsApp templates approved and sending
Old platform set to read-only, not cancelled
Historical CSV archived off-platform

Frequently asked questions

Can you switch dispatch platforms without losing forward bookings?+

Yes. Export future reservations first, import them into the new system, then run both platforms in parallel for one to two weeks with a hard cut-off date after which all new bookings are entered only in the new system.

How long does a dispatch software migration take?+

Five to fifteen days for most fleets under 50 vehicles: two days of export and mapping, three days of parallel running, then cut-over on your quietest weekday.

What usually goes wrong in a migration?+

Forward bookings beyond the export window, saved card tokens that cannot transfer between processors, corporate account rate cards, and driver logins switched over mid-shift.

Should I migrate historical trip data?+

Migrate the last 24 months for reporting continuity and archive the rest as CSV. Moving ten years of trips slows the cut-over and rarely gets queried.