United Kingdom · Merseyside
TaxiCloud vs Autocab — Liverpool.
Switching from Autocab to TaxiCloud in Liverpool: Liverpool City Council Hackney + PHV Licensing compliance, parallel-run plan, no dispatch disruption.
A Autocab → TaxiCloud migration in Liverpool is a standardised 4–8 week process: 2 weeks of data export from Autocab, 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
Autocab → TaxiCloud, Liverpool-specific.
Hand-written cutover plan for the Autocab → TaxiCloud migration in Liverpool. Migration window: 9 working days.
- Data export
- Autocab Liverpool export via IGO partner-data export plus Liverpool City Council quarterly return audit. Cruise-terminal pre-booking flow audit history needs separate CSV pull.
- Parallel run
- Cruise-ship docking day (Saturday-Sunday) inside parallel window. Validate Liverpool Cruise Direct-style pre-booking flow on TaxiCloud under cruise-day load. 9-day window typical.
- Risks to manage
- Cruise-day pre-booking flow has Autocab-specific surge-band timing — re-configure surge bands explicitly during week-one calibration.
- Autocab dispatcher workflow retraining curve.
- Wins post-cutover
- Cruise-terminal pre-booking flow on WebSocket dispatch removes polling-lag complaints common during Saturday cruise-day peaks.
- Liverpool City Council quarterly return automation.
FAQ
Autocab → TaxiCloud in Liverpool.
- Why switch from Autocab to TaxiCloud in Liverpool?
- Liverpool operators on Autocab 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 Autocab → TaxiCloud migration take in Liverpool?
- A typical Liverpool Autocab 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 Autocab 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
