United Kingdom · Merseyside
TaxiCloud vs iCabbi — Liverpool.
Switching from iCabbi to TaxiCloud in Liverpool: Liverpool City Council Hackney + PHV Licensing compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in Liverpool 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. Liverpool City Council Hackney + PHV Licensing reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
iCabbi → TaxiCloud, Liverpool-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in Liverpool. Migration window: 7 working days.
- Data export
- iCabbi's Liverpool export covers driver, vehicle, customer, and Liverpool City Council quarterly return audit cleanly. Cruise-terminal pre-booking flow audit history needs a separate CSV pull from iCabbi's events API.
- Parallel run
- Parallel window should cover at least one cruise-ship docking day (typically Saturday-Sunday at Liverpool Cruise Terminal) so the team validates Liverpool Cruise Direct-style pre-booking flow on TaxiCloud under load.
- Risks to manage
- Cruise-day pre-booking flow has iCabbi-specific surge-band timing — re-configure surge bands explicitly during week-one calibration.
- Liverpool John Lennon LPL airport feed contract billing needs explicit account-level mapping during import.
- Wins post-cutover
- Cruise-terminal pre-booking flow under WebSocket dispatch removes the polling-lag complaints common during Saturday cruise-day peaks.
- Liverpool City Council quarterly return automation; on-time arrival reporting visible to council on request.
FAQ
iCabbi → TaxiCloud in Liverpool.
- Why switch from iCabbi to TaxiCloud in Liverpool?
- Liverpool operators on iCabbi typically move when they need Liverpool 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 Liverpool specifically — see the city detail for the regulator-aware features that matter.
- How long does a iCabbi → TaxiCloud migration take in Liverpool?
- A typical Liverpool 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 Liverpool?
- 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
