White-glove migration · 6 days
Migrate from TaxiCaller taxi dispatch software to TaxiCloud.
TaxiCaller migration in 6 days: drivers, vehicles, customers, pricing rules, coverage zones, and historic bookings imported clean. Parallel-run weekend included on Pro and above.
Migrating from TaxiCaller to TaxiCloud takes 6 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.
TaxiCaller migration deep-dive
How we migrate TaxiCaller fleets to TaxiCloud.
TaxiCaller migrations are typically driven by three pressure points: TaxiCaller's UK-specific compliance content has historically lagged the Nordic and DACH content TaxiCaller anchors on, the customer-app rates around 4.0 versus 4.6 on TaxiCloud equivalent deployments — meaningful for operators where customer-app conversion drives bookings, and the dispatch flow is rule-based auto-dispatch rather than generative AI Copilot. Operators evaluating modern alternatives most often pilot TaxiCloud on their customer-app segment or NTA Ireland SPSV reporting segment, where the UK/IE-specific gap is most visible.
TaxiCaller's data export path is the cleanest of the five legacy systems. Drivers, vehicles, customers, pricing rules, and a 24-month historic booking archive all export via TaxiCaller's well-documented public API. Our migration team has run nine TaxiCaller cutovers in the last year — every record class has a clean import path. The 6-day total cutover is the shortest of the legacy migrations because TaxiCaller's data model maps cleanly onto TaxiCloud's first-class objects with minimal manual review.
The TaxiCaller parallel-run window typically runs over a Tuesday-to-Friday cycle. The 6-day total cutover excludes the prior weekend; data export runs Monday, configuration Tuesday, integration testing Wednesday, parallel-run Thursday-Friday, cutover Saturday morning. Harbour Cabs Dublin's November 2025 TaxiCaller migration to TaxiCloud followed this playbook with cutover completing on Saturday morning before Sunday Dublin Airport traffic — no fallback required.
- Export path
- TaxiCaller public API (well-documented) + CSV fallback
- Parallel-run window
- Tuesday-Friday cycle, cutover Saturday morning before Sunday airport traffic
What we import
Every record, mapped.
TaxiCaller
Drivers + licensing data
TaxiCloud
Driver records with licence expiry tracking
TaxiCaller
Vehicles + inspection records
TaxiCloud
Vehicle records with inspection deadline calendar
TaxiCaller
Customer database
TaxiCloud
Customer accounts with booking history preserved
TaxiCaller
Pricing rules + coverage zones
TaxiCloud
First-class pricing rule and geofence objects
TaxiCaller
Historic bookings (24-month window)
TaxiCloud
Booking archive, searchable + reportable
TaxiCaller
Corporate accounts + travellers
TaxiCloud
Account-pay records with expense codes intact
Migration timeline · 6 days
Off TaxiCaller, 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+.
TaxiCaller migration gotchas
Where TaxiCaller migrations bite, and how we handle it.
Gotcha
TaxiCaller's Nordic-first content does not match UK PHV or NTA Ireland SPSV templates
TaxiCloud resolution
TaxiCloud's council-licensing reports ship pre-configured for every UK PHV authority and the 2025-updated NTA SPSV format; Harbour Cabs Dublin generated their first NTA return in 8 minutes versus 4 hours on TaxiCaller.
Gotcha
TaxiCaller customer-app rating around 4.0 — passengers prefer modern alternatives
TaxiCloud resolution
TaxiCloud customer-app rates around 4.6 in equivalent deployments; iOS-first with native Android, designed on the Aurora design system.
Gotcha
TaxiCaller dispatch flow is rule-based auto-dispatch only
TaxiCloud resolution
TaxiCloud's AI Copilot surfaces explainable recommendations and drafts SMS in the passenger's booking language; dispatcher overhead drops 15-20% in pilot deployments.
Gotcha
TaxiCaller subscription includes long-term contract clauses
TaxiCloud resolution
TaxiCloud is month-to-month with one calendar month notice; no minimum-term commitment.
Migration FAQ
Switching from TaxiCaller, answered.
- How long does migration from TaxiCaller take?
- Typical cutover is 6 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 TaxiCaller 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.