United Kingdom · North East Scotland
TaxiCloud vs iCabbi — Aberdeen.
Switching from iCabbi to TaxiCloud in Aberdeen: Aberdeen City Council Hackney + PHV Licensing compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in Aberdeen 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. Aberdeen City Council Hackney + PHV Licensing reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
iCabbi → TaxiCloud, Aberdeen-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in Aberdeen. Migration window: 7 working days.
- Data export
- Aberdeen iCabbi export pulls cleanly. Aberdeen City Council quarterly return audit exports cleanly; energy-sector corporate-account dictionaries (BP, Shell, Total project codes) need explicit review.
- Parallel run
- Parallel window covers at least one Aberdeen Airport ABZ peak (helicopter-and-fixed-wing energy-sector workforce rotation typically Monday/Friday).
- Risks to manage
- Energy-sector workforce-rotation pickup windows have Aberdeen-specific timing — calibrate ABZ peak surge bands during week one.
- Cross-border bookings to Dundee under iCabbi multi-base need explicit fare-rule mapping.
- Wins post-cutover
- Aberdeen Energy Fleet-style energy-sector-contract operators get integrated project-code expense-code dictionaries (first-class TaxiCloud).
- ABZ helicopter-workforce-rotation pre-positioning via AI Copilot.
FAQ
iCabbi → TaxiCloud in Aberdeen.
- Why switch from iCabbi to TaxiCloud in Aberdeen?
- Aberdeen operators on iCabbi typically move when they need Aberdeen 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 Aberdeen specifically — see the city detail for the regulator-aware features that matter.
- How long does a iCabbi → TaxiCloud migration take in Aberdeen?
- A typical Aberdeen 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 Aberdeen?
- 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
