United Kingdom · East Sussex
TaxiCloud vs iCabbi — Brighton.
Switching from iCabbi to TaxiCloud in Brighton: Brighton & Hove City Council Hackney + PHV Licensing compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in Brighton 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. Brighton & Hove City Council Hackney + PHV Licensing reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
iCabbi → TaxiCloud, Brighton-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in Brighton. Migration window: 7 working days.
- Data export
- Brighton iCabbi export pulls cleanly. Brighton & Hove Council quarterly return audit history exports cleanly; Gatwick LGW airport-feeder contract billing needs explicit account-level mapping.
- Parallel run
- Parallel window covers at least one weekend night-economy peak. Brighton Friday-Saturday-evening 22:00-04:00 tempo on TaxiCloud validated before cutover.
- Risks to manage
- Night-economy surge-band timing has Brighton-specific weekend peaks — calibrate surge bands explicitly during week one.
- LGW airport-feeder contract billing under iCabbi's multi-base config needs explicit account-level fare-rule mapping.
- Wins post-cutover
- Brighton & Hove Council quarterly return automation; on-time arrival reporting first-class.
- LGW airport-feeder pre-positioning via AI Copilot replaces iCabbi manual dispatcher workflow.
FAQ
iCabbi → TaxiCloud in Brighton.
- Why switch from iCabbi to TaxiCloud in Brighton?
- Brighton operators on iCabbi typically move when they need Brighton & Hove 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 Brighton specifically — see the city detail for the regulator-aware features that matter.
- How long does a iCabbi → TaxiCloud migration take in Brighton?
- A typical Brighton 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 Brighton?
- 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
