VAMOS Taxi Software Migration Checklist

Buyer preparation guide. This checklist does not guarantee that every source system can export every field.

1. Data access and ownership
- Confirm who owns driver, vehicle, rider, account, booking, zone, tariff, and payment data.
- Request complete exports in documented CSV or API formats.
- Record unavailable fields and any vendor export fees.

2. Operational inventory
- Drivers and compliance documents
- Vehicles and service classes
- Zones, tariffs, surcharges, and account rates
- Future and recurring bookings
- Corporate and hospitality accounts
- Payment processor and payout configuration
- Existing integrations and webhooks

3. Validation and pilot
- Reconcile record counts and sample data.
- Configure dispatch rules and permissions.
- Train dispatchers and a pilot driver group.
- Test booking, allocation, payment, cancellation, support, and reporting flows.

4. Cutover and rollback
- Choose a low-volume cutover window.
- Keep the current system available during the agreed overlap period.
- Define go/no-go checks, named decision owners, and a rollback point.
- Confirm customer and driver communications.

5. After launch
- Monitor booking completion, pickup ETA, payment exceptions, driver availability, and support requests.
- Reconcile financial reports before ending the overlap period.
- Document lessons and remaining integrations.

Updated: 8 October 2026