United Kingdom · Cambridgeshire
TaxiCloud vs iCabbi — Cambridge.
Switching from iCabbi to TaxiCloud in Cambridge: Cambridge City Council Hackney + PHV Licensing compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in Cambridge 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. Cambridge City Council Hackney + PHV Licensing reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
iCabbi → TaxiCloud, Cambridge-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in Cambridge. Migration window: 7 working days.
- Data export
- Cambridge iCabbi export pulls cleanly. Stansted Airport STN feeder-route audit history needs explicit export; Cambridge-Biomedical-account dictionary (matter numbers, project codes) should be reviewed before import.
- Parallel run
- Standard Tuesday-to-Saturday parallel-run. Cambridge term-time cycle drives demand pattern; cutover outside Michaelmas and Lent intensive periods.
- Risks to manage
- STN cross-boundary fares under iCabbi multi-base need explicit Essex County Council fare-rule mapping.
- Cambridge Biomedical Cars-style account dictionary needs early review against modern dispatch expense-code format.
- Wins post-cutover
- Cambridge Biomedical Cars-style university-and-biomedical-contract operators get integrated account-level expense-code dictionaries (first-class TaxiCloud).
- STN airport-feeder pre-positioning via AI Copilot replaces iCabbi manual dispatcher workflow.
FAQ
iCabbi → TaxiCloud in Cambridge.
- Why switch from iCabbi to TaxiCloud in Cambridge?
- Cambridge operators on iCabbi typically move when they need Cambridge 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 Cambridge specifically — see the city detail for the regulator-aware features that matter.
- How long does a iCabbi → TaxiCloud migration take in Cambridge?
- A typical Cambridge 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 Cambridge?
- 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
