Migrate from Cordic taxi dispatch software to TaxiCloud.

Cordic migrations are typically driven by three pressure points: Cordic's vehicle-class enforcement at dispatch is dispatcher-discretion rather than structural — premium S-Class bookings can be assigned to E-Class vehicles when a dispatcher misses the class flag — Cordic's compliance-report exports require manual reconciliation against UK council templates, and Cordic's customer app has lagged behind the rate of change in passenger-app expectations since roughly 2022. Operators evaluating modern alternatives most often pilot TaxiCloud on their executive or chauffeur segment first, where the vehicle-class enforcement gap is most visible.

Cordic's data export path is robust. Drivers (with licensing data and vehicle-class certifications), vehicles (with inspection deadlines and CAZ-compliance flags), customer accounts (with PO-level booking notes and expense codes), pricing rules (with executive-tier tariffs and airport surcharges), corporate-account billing rules, and a 24-month historic booking archive all export via Cordic's standard ops API. Our migration team has run six Cordic cutovers in the last year — every record class has a clean import path, and the executive-tier vehicle-class data is preserved as first-class TaxiCloud objects with structural enforcement at dispatch.

The Cordic parallel-run window typically runs over a Tuesday-to-Saturday cycle so dispatchers train against weekday corporate flows on Cordic-and-TaxiCloud in parallel before cutting over before Sunday airport-rush traffic. The 6-day total cutover excludes the weekend; data export runs Monday, configuration Tuesday, integration testing Wednesday, parallel-run Thursday-Friday, cutover Saturday morning. Executive Edinburgh's December 2025 Cordic migration followed this exact playbook with no fallback required.