United Kingdom · Wales
TaxiCloud vs iCabbi — Cardiff.
Switching from iCabbi to TaxiCloud in Cardiff: Cardiff Council Hackney + PHV Licensing compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in Cardiff 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. Cardiff Council Hackney + PHV Licensing reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
iCabbi → TaxiCloud, Cardiff-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in Cardiff. Migration window: 7 working days.
- Data export
- Cardiff iCabbi export pulls cleanly. Cardiff Council's Welsh-language reporting requirement needs verification on TaxiCloud's pre-configured Cardiff template (TaxiCloud ships bilingual report headers ready).
- Parallel run
- Stadium-event days (Principality Stadium rugby and concert weekends) should fall inside the parallel-run window so the team validates event-mode surge handling under load before cutover.
- Risks to manage
- Stadium-event surge-band timing has Cardiff-specific Saturday-evening tempo — re-calibrate surge bands explicitly during week one.
- Welsh-language SMS template assets need import or new authoring during config.
- Wins post-cutover
- Stadium-event surge bands first-class-configurable rather than iCabbi-support-ticket; Cardiff Stadium Cabs documented the operating-tempo lift.
- Cardiff Council bilingual quarterly return generates in 8 minutes inclusive of Welsh-language report headers.
FAQ
iCabbi → TaxiCloud in Cardiff.
- Why switch from iCabbi to TaxiCloud in Cardiff?
- Cardiff operators on iCabbi typically move when they need Cardiff 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 Cardiff specifically — see the city detail for the regulator-aware features that matter.
- How long does a iCabbi → TaxiCloud migration take in Cardiff?
- A typical Cardiff 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 Cardiff?
- 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
