Switching Shuttle Software in 2026: A 10-Day Migration Checklist
Most operators stay on the wrong platform because switching feels risky. It is not — it is a 10-day project with a fixed checklist. This guide gives the day-by-day plan, the exact data to export, and the two mistakes that cause lost bookings.
Days 1–2: Export everything before you talk about cancelling
Vendors rarely block exports, but access ends the day billing does. Pull CSVs now:
- All bookings for the last 24 months (for reporting continuity)
- Future bookings — this is the critical set
- Customer list with email, phone and consent status
- Routes, stops, pickup points and pricing rules
- Vehicles with seat counts, and driver contacts
Days 3–4: Rebuild routes and pricing in the new system
Rebuild rather than force-import structure. Route and pricing models differ between platforms, and 20 routes take about two hours to enter cleanly — far less than debugging a bad import for a week.
Days 5–6: Load future bookings and run a parallel week
Enter every future booking into the new system while the old one still runs. Both boards should show identical departures. This parallel period is what removes the risk.
Day 7: Onboard drivers
Drivers need 20 minutes: install the app, accept a run, mark on-board and completed, and check in a passenger. Do it in person at a shift change if you can.
Day 8: Switch payments and test a live card
Connect the payment account, take one real $1 booking, refund it, and confirm the payout lands. Never go live on an untested payment path.
Day 9: Point the booking links at the new system
Update the website button, Google Business Profile link, email signatures and any QR codes. Keep the old booking page live but redirected for 30 days.
Day 10: Cancel the old subscription — after payouts clear
Wait until the last payout from the old platform has settled and the last legacy booking has travelled. Then cancel and archive the exports.
The two mistakes that cost bookings
Both are avoidable with the plan above:
- Cancelling the old platform before future bookings are re-entered — those riders arrive to nothing
- Skipping the parallel week, so the first real busy morning is also the first day on the new board
How to choose what you switch to
Judge the replacement on the same criteria that made you leave:
- Leaving a marketplace over commission? Confirm 0% per-booking fees in writing
- Leaving Moovs or Limo Anywhere over shared rides? Test per-seat capacity in the demo
- Leaving a spreadsheet? Prioritise the driver app and automatic rider messaging
- Leaving a custom build? Prioritise included updates over one-off development
See it running
Compare directly on the Moovs comparison or the Limo Anywhere comparison, then book the live demo.
Frequently asked questions
How long does it take to switch shuttle software?
For a 3–20 vehicle operator, 10 days end to end, including a parallel week. Shuttle.Software itself is configured and live in 3–5 working days.
Will I lose my future bookings?
Not if you export future bookings first and re-enter them before cancelling the old platform. That single step prevents almost every migration failure.
Can I import my customer list?
Yes — customers import from CSV with email, phone and consent status. Keep consent flags intact so marketing messages stay compliant.
Should I migrate historical bookings?
Keep them as an archived CSV export for reporting. Importing years of history into a live board adds noise without operational value.
Is there a setup fee to switch?
Shuttle.Software charges a one-time $299 setup that includes route, pricing and vehicle configuration, then $99/mo flat with 0% commission.
Ready to move?
Shuttle.Software is $99/mo flat with a one-time $299 setup and 0% booking commission — live in 3–5 working days.
Explore More →Or explore the full shuttle booking software product page →