United Kingdom · Lothian
TaxiCloud vs iCabbi — Edinburgh.
Switching from iCabbi to TaxiCloud in Edinburgh: City of Edinburgh Council Licensing compliance, parallel-run plan, no dispatch disruption.
A iCabbi → TaxiCloud migration in Edinburgh 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. City of Edinburgh Council Licensing reporting continues uninterrupted; rider, driver, and corporate account history is preserved.
Cutover narrative
iCabbi → TaxiCloud, Edinburgh-specific.
Hand-written cutover plan for the iCabbi → TaxiCloud migration in Edinburgh. Migration window: 7 working days.
- Data export
- iCabbi's Edinburgh export pulls cleanly via the partner API including City of Edinburgh Council quarterly return audit history. Validate the 1-of-3 council reporting variants Edinburgh uses against TaxiCloud's pre-configured CoEC return template during day-one configuration.
- Parallel run
- Edinburgh's festival-season operating tempo means the parallel-run should avoid the August Fringe period. Standard Tuesday-to-Saturday parallel-run with cutover the following Monday works outside festival; inside festival, extend the window to 10 days.
- Risks to manage
- Edinburgh Hackney plate-distinction between taxi and PHV needs explicit dictionary mapping during data import.
- Waverley + Haymarket station ranks have iCabbi-specific dispatcher overrides that don't directly translate — document the override logic before cutover.
- Wins post-cutover
- City of Edinburgh Council quarterly return generates in 8 minutes vs the 4-5 hour spreadsheet iCabbi customers typically run.
- Festival-period surge bands configurable inside the dispatch console rather than via iCabbi support ticket.
FAQ
iCabbi → TaxiCloud in Edinburgh.
- Why switch from iCabbi to TaxiCloud in Edinburgh?
- Edinburgh operators on iCabbi typically move when they need City of Edinburgh Council 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 Edinburgh specifically — see the city detail for the regulator-aware features that matter.
- How long does a iCabbi → TaxiCloud migration take in Edinburgh?
- A typical Edinburgh 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 Edinburgh?
- 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
