United Kingdom · Greater London
TaxiCloud vs iCabbi — London.
Switching from iCabbi to TaxiCloud in London: Transport for London (TfL) compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in London is a standardised 4–8 week process: 2 weeks of data export from iCabbi, 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
iCabbi → TaxiCloud, London-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in London. Migration window: 8 working days.
- Data export
- iCabbi exports driver, vehicle, customer, and 24-month booking history via the partner API. London-specific TfL operator return audit history needs a separate CSV pull — flag this on day one with the iCabbi success team to avoid a 48-hour delay.
- Parallel run
- Run the parallel window Tuesday-to-Sunday so Heathrow Friday-evening peak and Sunday post-event Saturday-night recovery both hit on TaxiCloud while iCabbi remains live as fallback. Full cutover Monday morning, post-City-traffic re-test by Wednesday.
- Risks to manage
- TfL monthly return cycle straddling the cutover — schedule export of the in-flight period before switching the live channel.
- Corporate accounts on iCabbi PO-level expense codes need dictionary review against London Magic-Circle matter-number formats.
- Wins post-cutover
- WebSocket dispatch console removes the 8-12 second polling lag iCabbi London dispatchers report on Friday evenings.
- AI Copilot pre-positions drivers across LHR, LGW, LCY, STN, LTN automatically — multi-airport coordination collapses to one console.
FAQ
iCabbi → TaxiCloud in London.
- Why switch from iCabbi to TaxiCloud in London?
- London operators on iCabbi 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 iCabbi → TaxiCloud migration take in London?
- A typical London iCabbi 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 iCabbi 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
