Switching Limo Software: A Migration Guide

The first mistake operators make is treating migration as an IT project. It isn't. It's an operations redesign with software underneath. Before you export a single record, write down the three or four things the new system should let you do that the old one couldn't. Faster quoting? Mobile-first dispatch? Automated invoicing? A real driver app?

Those answers determine which data you carefully migrate and which data you leave behind. If your new system has fundamentally different concepts — say, "rate cards" instead of free-text pricing notes — trying to one-to-one migrate will leave you with a mess that the new system can't reason about.

Export in this exact order. The order matters because each export depends on the integrity of the previous one.

1. Customers, with notes. This is your gold. Every customer record, every internal note, every preference (cold water, no ice, three minutes early, hates small talk). If the old system has a "do not service" list, get that too.
2. Account hierarchies. Corporate parents, sub-accounts, billing contacts, cost centres. This is the hardest data to recreate from memory; export it carefully.
3. Vehicles and drivers. Make, model, plate, VIN, capacity, any custom attributes. For drivers: license expiry, medical card expiry, hire date, any discipline notes.
4. Rate cards. Every active rate card, both retail and account-specific. This is where you'll discover that you have 47 active rate cards and only six of them are actually used. Use the migration as a chance to consolidate.
5. Future trips. Every booking dated today or later. This is the dataset that will make or break your first week on the new system.
6. Last 90 days of trip history. Enough for revenue continuity, recent customer call-backs, and any pending invoice disputes.
7. Older history as archive. Bring this in last, in bulk, as read-only reference data. Don't let it block your cutover.

Your CRM is only as good as the day you migrate it. Before importing, dedupe customer records ruthlessly. Most operators we audit have 20–35% duplicate customer records — the same person entered three times with slightly different email addresses or phone formats. Migrate the duplicates and you'll be living with them for years.

The cleanup checklist:

• Merge duplicate customers, keeping the most complete record.
• Standardise phone numbers to E.164 format (+1XXXXXXXXXX).
• Lowercase all email addresses.
• Strip historical "test" customers and old employee records used for trip-shifting.
• Fix any customer assigned to a corporate account that no longer exists.
• Archive vehicles and drivers no longer in service — don't migrate them as active.

This cleanup takes one to three full days for a typical mid-size operator. It's the highest-ROI work in the entire migration.

Cut over on a Monday after a slow Sunday. Not Friday — you don't want your support team away during the first 48 hours. Not month-end — you don't want billing complications layered on top.

The cutover sequence:

• Sunday 6pm. Old system goes read-only. No new bookings entered.
• Sunday 6pm – Monday 4am. Final delta export of any bookings made over the weekend, imported into the new system. Final reconciliation pass.
• Monday 4am. New system goes live. First driver shift starts on the new app.
• Monday – Friday. Both systems running, old in read-only. Any data discrepancy gets flagged and fixed in real time.
• Day +30. Old system fully decommissioned, archive exported to cold storage.

Keep the old system in read-only mode for 30 days as your archive and your safety net. The cost of an extra month of subscription is trivial compared to the cost of discovering on day 14 that one corporate account's recurring run didn't migrate.

Software migrations fail more often because of people than because of data. The dispatcher who has run the magnetic board for 15 years will be slower on the new system for the first two weeks, and they will hate you. That's normal. Three things help:

1. Train two weeks before cutover, not two days. Muscle memory needs reps.
2. Pair the slowest dispatcher with the fastest one for the first week. Pride and peer pressure beat training videos.
3. Don't change anything else for 60 days. No new pricing, no new vehicle types, no new drivers if you can avoid it. Stability everywhere except the software lets people focus on the change you actually wanted.

Operators who follow this playbook typically reach equivalent dispatcher productivity within three weeks and exceed old-system productivity by week six.

If you're already on another limo software — whether a legacy incumbent or a newer alternative — migration is a weekend, not a quarter. We'll import your customers, vehicles, and rate cards, and run a parallel test week so you don't risk live trips. Start with the features overview, then book a migration call.

Related reading: Switching Limo Software · Best Limo Software.