Migration guide · 9 min read

How to migrate from LimoAnywhere in under 5 days.

A day-by-day playbook, written by the team that runs the imports.

By the Limozoft team · Last reviewed

The single biggest reason operators stay on LimoAnywhere long after they've outgrown it isn't the software — it's the fear of a bad migration. Losing a reservation, losing a corporate account, losing card-on-file tokens. All fixable. All avoidable. Here is exactly how we do it in five business days.

This playbook assumes a fleet of 5–75 vehicles. Larger fleets follow the same pattern but Day 2 (mapping) usually expands to 2–3 days.

Day 1 — Data export from LimoAnywhere

Kick off with a full CSV export from LimoAnywhere's admin panel. You'll pull reservations (24 months), customers, corporate accounts, vehicles, drivers, rate cards, zones and affiliate lists. Our migration engineer sits with your office manager on a shared call — the export itself takes about 90 minutes.

We simultaneously kick off a Stripe account-to-account token transfer so that card-on-file tokens carry over. That process runs in the background for 24–48 hours and doesn't block anything else.

Day 2 — Field mapping and rate-card translation

This is where migrations usually go wrong on cheap platforms and where we spend the most time. LimoAnywhere's rate structures — hourly, transfer, hourly-as-directed, zone, flat, per-mile with minimum — all map cleanly to Limozoft's dynamic pricing engine, but the field names differ. Our engineer builds the mapping file, you review it, we lock it.

By end of day you have a sandbox Limozoft tenant with your full data loaded and every rate card producing the same quote as LimoAnywhere for a test set of 25 trips.

Day 3 — Sandbox parallel run

Your dispatchers spend one full shift running trips in the Limozoft sandbox in parallel with LimoAnywhere. Same jobs, same drivers, side-by-side. This is the day the team goes from skeptical to sold — the real-time dispatch console is usually where the switch clicks.

Any last-mile fixes (a rate card, a zone boundary, a corporate account net-term setting) get logged and fixed in-flight.

Day 4 — Driver and dispatcher training

Drivers install the new driver app the day before cutover. Onboarding takes 8 minutes per driver — most fleets run it as a 30-minute morning huddle. Dispatcher training is a 90-minute live session followed by shadowing.

We also brand and submit the passenger app to the App Store and Play Store — those reviews take 3–7 days and usually clear before your public cutover.

Day 5 — Cutover

8:00 AM: booking widget on your website flips to Limozoft. 8:05 AM: LimoAnywhere is set to read-only. Reservations in flight finish on the old system; new bookings land in Limozoft. Your migration engineer stays on Slack for the full day.

By end of day, you're fully live. LimoAnywhere stays available for 90 days as a read-only historical archive.

What it costs

The migration itself is included — no setup fee, no per-record fee. You pay only the standard monthly plan starting the day you go live. Most operators save 40–60% versus their old LimoAnywhere invoice plus SMS, dispatch add-ons and per-booking fees.

Considering other platforms too?

Smart. Also look at our comparisons with Yelowsoft, Cabsoluit and MyLimoBiz. We publish the honest feature-by-feature breakdown even where competitors win.

Frequently asked questions

How long does a real LimoAnywhere migration take?+

For fleets under 50 vehicles, five business days is realistic. Day 1 is a data export, Day 2 is mapping, Day 3 is a sandbox parallel run, Day 4 is dispatcher and driver training, and Day 5 is cutover. Fleets over 100 vehicles typically take 7–10 days because of corporate-account and rate-card complexity.

Will my reservations, customers and corporate accounts move over?+

Yes. Limozoft imports reservations (past 24 months by default, longer on request), customers, corporate accounts with net terms, vehicles, drivers, rate cards, zones, affiliates and saved locations. Card-on-file tokens migrate through Stripe's account-to-account flow.

Do I have to run both systems in parallel?+

Only for one to three days. We recommend a short parallel where new bookings still land in LimoAnywhere while your dispatchers shadow them in Limozoft. Once you're comfortable, you flip the booking widget on your website and stop taking new work in LimoAnywhere.

What breaks during the cutover?+

Nothing that matters. Passenger apps keep working during the switch, drivers install the new app the day before cutover, and dispatchers use both consoles for the 24-hour handover. The most common surprise is stale rate cards — that's why Day 2 mapping matters.

How much does the migration cost?+

Zero. Migration is included on every Limozoft plan. There is no setup fee, no per-record fee and no professional-services minimum. See the full pricing on our pricing page.

Ready to run your 5-day migration?