Replace taxi dispatch software without losing sight of bookings

Replace taxi dispatch software in six steps

1. Export customers, drivers, accounts and all future bookings from the old system.
2. Set up the new system with your brand, fares and vehicle types.
3. Test real bookings and common exceptions end to end.
4. Train dispatchers and drivers, and install the new driver app.
5. Switch on a quiet day and keep the old system read-only as a fallback.
6. Cancel the old contract once bookings and payments are reconciled.

Write down the failures the new system must solve

Collect real examples from today: a request nobody took, unclear driver availability, a fare dispute with no record, or too much retyping. Record the booking channel, what staff did and the result you need instead.

Use those cases in each dispatch software demo. Compare a normal booking and a problem case in every system. A new screen doesn't mean the problem is fixed.

Inventory data, accounts and upcoming work

List the data you use: drivers, vehicles, customers, future bookings, fares, trip history, payments and company accounts. Ask your current supplier what you can export, and in what format.

For each one, note who owns it, the fields you need, where it goes, how you'll check it and how long you can keep it. Check you can access your domain, app store accounts, payment provider, maps and messaging. Never send customer or driver records through a contact form. Agree a safe way to share them.

Data migration into Hoppvia is available on the Enterprise plan. Do not assume an export from another platform can be imported unchanged.

Map the workflow before mapping the files

Match booking statuses, driver availability, fares and staff access to the new system. Note any differences. For example, "assigned" in your old system may not mean the same as an offer waiting for a driver.

In Hoppvia, a ride stays unassigned until a driver accepts the offer. Test acceptance, declines and unanswered requests with the dispatch team. Test any import with sample data before you move real records.

Record the outcome with the software evaluation checklist and list how your fleet needs to work.

Prepare a cutover sheet with a named owner

Agree when new bookings move to the new system and what happens to future bookings already taken. Give staff one place to check which system owns each booking, so no ride is dispatched twice.

• Record open and future bookings and their responsible team.
• Confirm driver access, training and support contacts.
• Verify the live provider connections and agreed payment flow.
• Assign responsibility for customer messages and app changes.
• Define when the old system becomes read-only or remains available for reconciliation.

Note the switch time and any work still open. Agree the steps with your software and operations leads.

Define rollback before the first live shift

Agree when to pause the switch. For example, if drivers can't get offers or staff can't find open bookings. Name the person who decides and the support channel used during the shift.

Write down how you'd handle new bookings if you had to switch back. A backup file alone is not a plan. Keep access to the old system until the new one is working.

Ask for an explicit migration scope

Ask for a plan that lists exports, data matching, imports, testing, training, account changes and anything not included. Keep software costs separate from provider fees and the months you pay for both systems.

Hoppvia publishes flat yearly plans. Data migration and custom integrations are quoted on Enterprise. Bring how you work today, your number of drivers and your data list to a demo. The implementation guide has a handover checklist.

Frequently asked questions