United Kingdom · Tyne and Wear
TaxiCloud vs iCabbi — Newcastle.
Switching from iCabbi to TaxiCloud in Newcastle: Newcastle City Council Hackney + PHV Licensing compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in Newcastle 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. Newcastle City Council Hackney + PHV Licensing reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
iCabbi → TaxiCloud, Newcastle-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in Newcastle. Migration window: 7 working days.
- Data export
- Newcastle iCabbi export covers Newcastle City Council quarterly return audit cleanly. Tyne crossings booking-route taxonomy (north vs south Tyne) needs explicit mapping during import to preserve Newcastle Night Fleet-style night-economy operating clarity.
- Parallel run
- Night-economy pattern means parallel window should cover at least two Friday and Saturday late-evenings. 22:00-04:00 dispatcher tempo on TaxiCloud validated under load before cutover.
- Risks to manage
- Night-economy surge-band timing has Newcastle-specific Friday-Saturday-evening peaks — calibrate surge bands explicitly during week one.
- Sunderland cross-boundary bookings under iCabbi multi-base need explicit Sunderland Council fare-rule mapping.
- Wins post-cutover
- Newcastle Night Fleet-style night-economy operators get sub-second dispatch on TaxiCloud's WebSocket console vs iCabbi's 8-12 second polling.
- Newcastle City Council quarterly return automation; on-time arrival reporting first-class.
FAQ
iCabbi → TaxiCloud in Newcastle.
- Why switch from iCabbi to TaxiCloud in Newcastle?
- Newcastle operators on iCabbi typically move when they need Newcastle 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 Newcastle specifically — see the city detail for the regulator-aware features that matter.
- How long does a iCabbi → TaxiCloud migration take in Newcastle?
- A typical Newcastle 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 Newcastle?
- 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
