United Kingdom · West Yorkshire
TaxiCloud vs iCabbi — Leeds.
Switching from iCabbi to TaxiCloud in Leeds: Leeds City Council Hackney + PHV Licensing compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in Leeds 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. Leeds City Council Hackney + PHV Licensing reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
iCabbi → TaxiCloud, Leeds-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in Leeds. Migration window: 7 working days.
- Data export
- Leeds iCabbi export pulls cleanly across driver, vehicle, customer, and Leeds City Council quarterly return audit. Verify the 2025 LCC reporting-column update against TaxiCloud's pre-configured Leeds template during day-one configuration.
- Parallel run
- Standard Tuesday-to-Saturday parallel-run. Leeds Bradford LBA peak coincides with Friday-evening business return; the parallel window covers the peak before Monday cutover.
- Risks to manage
- Cross-boundary bookings between Leeds, Bradford, and York councils need explicit per-council fare-rule mapping during config.
- Corporate-account base in Leeds (KPMG, EY regional teams) typically run matter-number formats that need dictionary review.
- Wins post-cutover
- Per-council fare-rule first-class configuration replaces iCabbi's manual override workflow.
- Leeds Corporate Cars-style Magic-Circle-satellite account onboarding flow scales cleanly on TaxiCloud's account-level expense-code dictionaries.
FAQ
iCabbi → TaxiCloud in Leeds.
- Why switch from iCabbi to TaxiCloud in Leeds?
- Leeds operators on iCabbi typically move when they need Leeds City Council Hackney + PHV Licensing-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 Leeds specifically — see the city detail for the regulator-aware features that matter.
- How long does a iCabbi → TaxiCloud migration take in Leeds?
- A typical Leeds 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 Leeds?
- 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
