United Kingdom · South West England
TaxiCloud vs iCabbi — Bristol.
Switching from iCabbi to TaxiCloud in Bristol: Bristol City Council Hackney + PHV Licensing compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in Bristol 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. Bristol City Council Hackney + PHV Licensing reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
iCabbi → TaxiCloud, Bristol-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in Bristol. Migration window: 7 working days.
- Data export
- iCabbi Bristol export covers the standard record classes cleanly. Bristol City Council's CAZ-compliant-vehicle audit trail history needs explicit export — flag this on day one because Bristol enforces CAZ checks at every quarterly return.
- Parallel run
- Standard Tuesday-to-Saturday parallel-run. Bristol Airport BRS peak covers Friday-Saturday business + leisure return; cutover Monday morning.
- Risks to manage
- CAZ-zone compliance audit reconciliation across migration boundary — produce dual-source CAZ audit for the first month post-cutover.
- Bristol-to-Bath cross-border bookings under iCabbi multi-base config need explicit base-mapping.
- Wins post-cutover
- CAZ-compliance audit trail integrated into the booking record; council inspections produce evidence in one export.
- Bristol Green Fleet-style 100% EV positioning surfaces in the customer app immediately on cutover.
FAQ
iCabbi → TaxiCloud in Bristol.
- Why switch from iCabbi to TaxiCloud in Bristol?
- Bristol operators on iCabbi typically move when they need Bristol 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 Bristol specifically — see the city detail for the regulator-aware features that matter.
- How long does a iCabbi → TaxiCloud migration take in Bristol?
- A typical Bristol 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 Bristol?
- 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
