Migrating from Limo Anywhere to Ridxo: A 14-Day Plan

Days 1–3: export and clean

• Export reservations, customers, corporate accounts, rates and fleet records to CSV
• De-duplicate customers on email and phone — most fleets carry 5–15% duplicates
• Flag accounts with unusual rate agreements for manual review
• Send the folder to onboarding; we return an import preview

Days 4–6: rebuild rates, accounts and users

Rate rules are where migrations go wrong, so they get their own three days. We load your point-to-point, hourly and airport rates, surcharges, waiting time and tolls, then price twenty historical jobs in the new system and compare the totals to the old invoices. Any variance over a dollar gets investigated before we move on.

At the same time we set up dispatcher, driver and accounts users with the right permissions, and configure your confirmation emails and SMS templates.

Days 7–9: test with real work

• Run five live jobs end to end: book, dispatch, driver app, complete, invoice
• Include one airport pickup with flight tracking and one farm-out
• Have the dispatcher who will actually use it run the console, not the owner
• Log every friction point; fix or accept each one in writing

Days 10–12: parallel running

New bookings go into Ridxo; existing future reservations already imported stay where they are and are worked from Ridxo as well. Keep the old system readable but stop entering new work into it. Two systems for three days is annoying; a rushed cutover that loses a wedding job is worse.

Days 13–14: cutover

• Point your booking site and QR codes at the new web booker
• Publish the branded passenger app and message existing clients with the download link
• Switch payment processing over and run one live card transaction
• Downgrade the old account to read-only for 90 days before cancelling

What goes wrong, and how to avoid it

The three recurring failures are unpriced rate exceptions discovered mid-week, drivers who never installed the app, and a corporate client whose invoice format changed without warning. Handle all three in advance: price twenty historical jobs, make app install a paid ten-minute task at a driver meeting, and send each account client a sample invoice before the first real one.