United Kingdom · Greater London
TaxiCloud vs Cordic — London.
Switching from Cordic to TaxiCloud in London: Transport for London (TfL) compliance, parallel-run plan, no dispatch disruption.
A Cordic → TaxiCloud migration in London is a standardised 4–8 week process: 2 weeks of data export from Cordic, 1–2 weeks of parallel-run, 1–2 weeks of staff training, then a clean cut-over. Transport for London (TfL) reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
Cordic → TaxiCloud, London-specific.
Hand-written cutover plan for the Cordic → TaxiCloud migration in London. Migration window: 14 working days.
- Data export
- Cordic London export is the most labour-intensive of the five legacy systems. Driver, vehicle, customer, and booking history export via Cordic's on-premise database snapshot plus a manual TfL operator return audit reconciliation pass. Allow 5-7 days for the export pipeline alone.
- Parallel run
- 14-day extended parallel-run because Cordic's polling-based console means dispatchers need explicit retraining on WebSocket tempo. Heathrow and Gatwick peaks both inside window; cutover the following Tuesday morning.
- Risks to manage
- Cordic on-premise database schema variance across customer instances — verify schema version before scheduling export.
- TfL monthly return cycle straddling cutover.
- Wins post-cutover
- WebSocket dispatch removes Cordic's 10-15 second polling lag entirely.
- TfL monthly return automation replaces Cordic's manual finance-team workflow.
FAQ
Cordic → TaxiCloud in London.
- Why switch from Cordic to TaxiCloud in London?
- London operators on Cordic typically move when they need Transport for London (TfL)-specific features the current platform doesn't ship, when consolidation across affiliate bases is hard to operate, or when pricing for the local fleet size becomes uneconomic. TaxiCloud is calibrated for London specifically — see the city detail for the regulator-aware features that matter.
- How long does a Cordic → TaxiCloud migration take in London?
- A typical London Cordic migration runs 4–8 weeks: 2 weeks of data export, 1–2 weeks of parallel-run with both systems live, 1–2 weeks of staff training, then full cut-over. We do not require any disruption to live dispatch during the switchover.
- Can we keep our Cordic driver app phone numbers in London?
- Yes. Driver phone numbers, vehicle plates, and rider account history all migrate. The cut-over keeps every rider's saved address, every driver's payout setup, and every corporate account's billing configuration.
Ready when you are
Dispatch on autopilot.
14-day free trial. No card. Cancel anytime.
47 fleets joined this month · Talk to sales
