White-glove migration · 10 days
Migrate from Autocab taxi dispatch software to TaxiCloud.
Autocab migration in 10 days: drivers, vehicles, customers, pricing rules, coverage zones, and historic bookings imported clean. Parallel-run weekend included on Pro and above.
Migrating from Autocab to TaxiCloud takes 10 business days end-to-end. Our white-glove team imports every record from your existing tenant, configures the compliance reports for your authority, and runs a parallel-run weekend so dispatchers train on live data before cutover. Available on Pro (£149/month) and above as part of onboarding.
What we import
Every record, mapped.
Autocab
Drivers + licensing data
TaxiCloud
Driver records with licence expiry tracking
Autocab
Vehicles + inspection records
TaxiCloud
Vehicle records with inspection deadline calendar
Autocab
Customer database
TaxiCloud
Customer accounts with booking history preserved
Autocab
Pricing rules + coverage zones
TaxiCloud
First-class pricing rule and geofence objects
Autocab
Historic bookings (24-month window)
TaxiCloud
Booking archive, searchable + reportable
Autocab
Corporate accounts + travellers
TaxiCloud
Account-pay records with expense codes intact
Migration timeline · 10 days
Off Autocab, on TaxiCloud, on schedule.
White-glove migration runs on a fixed timeline. Every step has a clear output, a clear owner, and a clear handoff. No surprises, no console-dark window.
Day 1
Audit + scope
Migration team reviews your current dispatch setup, exports list, integrations, and compliance reports. Output: signed migration plan with cutover date.
Day 2-3
Configure tenant
TaxiCloud tenant configured to match your operating reality — coverage zones, council-licensing reports, pricing rules, customer-app branding.
Day 4-5
Import data
Drivers, vehicles, customers, pricing rules, historic bookings imported. Integration tests run against Stripe, PayPal, Twilio, FCM.
Day 6-7
Parallel-run weekend
Small driver subset runs live on TaxiCloud alongside your existing platform. Dispatchers train against real bookings; we monitor side-by-side.
Day 8+
Cutover live
Full fleet flips to TaxiCloud. Migration team on standby for the first 72 hours. Onboarding manager assigned for the first 90 days on Pro Max+.
Migration FAQ
Switching from Autocab, answered.
- How long does migration from Autocab take?
- Typical cutover is 10 business days end-to-end. The timeline includes audit, tenant configuration, data import, integration testing, parallel-run weekend, and live cutover. Available on Pro (£149/month) and above as part of onboarding — no separate setup fee.
- What does the parallel-run weekend look like?
- A small driver subset (typically 10-20% of fleet, often the airport or executive segment) runs on TaxiCloud alongside your existing platform. Dispatchers train against real bookings; we monitor side-by-side. Operators decide cutover go/no-go based on the live data, not slideware.
- What data gets imported?
- Drivers with licensing data, vehicles with inspection records, customer database with booking history, pricing rules, coverage zones, corporate accounts with expense codes, and a 24-month historic booking archive. Pro Ultra extends the historic window to 7 years for regulatory and insurance use cases.
- What happens if integration tests fail?
- We do not cut over until integration tests pass. The migration plan signed at Day 1 includes the full integration list (Stripe, PayPal, Twilio, FCM, Google Maps, your custom integrations). If something fails during testing, we extend the migration window — never cut over with broken integrations.
- Can I roll back to {{competitor.name}} after cutover?
- Yes. The first 30 days post-cutover include rollback support. Your Autocab tenant is kept available (read-only for compliance) for 90 days post-cutover. Most operators do not roll back, but the option exists. After 90 days, the rollback path closes formally; we have not had an operator request rollback past the 30-day window.
Ready when you are
Dispatch on autopilot.
14-day free trial. No card. Cancel anytime.