Migrate from Gazoop taxi dispatch software to TaxiCloud.

Gazoop migrations are typically driven by three pressure points: Gazoop's pricing has tracked upward 12-18% annually for the last three renewal cycles, the dispatch console's UI is recognisably 2014-era and dispatchers report fatigue compared to modern alternatives, and Gazoop's AI features are rule-based-with-ML rather than generative — there is no Copilot equivalent that surfaces explainable recommendations to the dispatcher. Operators evaluating modern alternatives most often pilot TaxiCloud on their dispatch-board UX segment first, where the modern interface impact is most visible to ops floor staff.

Gazoop's data export path is straightforward but takes longer to map cleanly than Cordic or iCabbi. Drivers (with licensing and vehicle assignment), vehicles (with inspection records), customer accounts (with booking history and saved-card metadata), pricing rules (with airport tariffs and surcharges), and a 12-month historic booking archive export via Gazoop's reporting API. Corporate-account expense-code mappings often need manual review during cutover — Gazoop stores expense codes as free-text fields rather than structural objects, so operators with substantial corporate books should plan an extra day for expense-code normalisation.

The Gazoop parallel-run window typically runs over a Wednesday-to-Sunday cycle to absorb the corporate-account expense-code review across two business days. The 8-day total cutover excludes the prior Friday-Sunday weekend; data export runs Monday, configuration Tuesday, expense-code normalisation Wednesday-Thursday, integration testing Friday, parallel-run Saturday-Sunday-Monday, cutover Tuesday morning. Driver onboarding to the new app rolls out terminal-by-terminal across the same window.