Getting started

Migrating from legacy dispatch

The staged path off FastTrak, Limo Anywhere, iCabbi, or spreadsheets — without a risky big-bang cutover.

11 min read · updated

What imports, and how

The import pipeline accepts exports from common dispatch systems and normalized CSV for everything else. Records are validated, deduplicated, and staged for review before anything touches your live organization — you approve the mapping, not the tool.

  • Customers and corporate accounts, with billing terms.
  • Future bookings, standing orders, and recurring schedules.
  • Rate cards, zones, and surcharge rules.
  • Driver records and vehicle compliance data.

Parallel running

Most fleets run Renaro alongside the old system for one to two weeks: dispatchers mirror a slice of real work, drivers get comfortable with offers, and owners compare settlement output against the legacy reports. Because imports are idempotent, you can re-sync future bookings right up to cutover night.

Cutover night

Cutover is a checklist, not a leap: freeze the legacy system after the evening peak, run the final booking sync, flip your phone and web channels to Renaro, and dispatch the first night with both boards open. The next morning's daily close is your first ledger-backed report.

  • Rollback stays available until you retire the legacy licenses.
  • Passenger tracking links work from the first migrated booking.
  • Your comparison baseline: the last legacy month vs. the first Renaro month.