Every stage is a decision, not a date

An adaptable framework

These are the stages a migration usually goes through. The order, the overlap and the dates depend on your operation, and they are agreed with you after discovery.

Stage	What it establishes	Format
1. Understand the operation	Your workflows, booking channels, fleet structure, commercial rules and dependencies, with your management, IT, dispatch and finance teams.	On site and remote
2. Address launch-critical gaps	The features and integrations your operation needs before launch, and an agreed scope for any work they require.	Joint scoping
3. Configure	Pricing, zones, fleets, accounts, permissions and dispatch rules; data migration, payments and integrations prepared and tested internally.	Joint project work
4. Onboard in phases	Dispatchers and drivers prepared around your real scenarios, including peak hours and unusual bookings, in the languages they use.	On site where useful
5. Test and run in parallel	The agreed workflows validated with a small pilot group and the results reconciled, with both systems running side by side where that is appropriate.	Closely supported
6. Release the rider app in phases	Your own branded rider app, released when operational readiness and customer communication are in place.	Coordinated launch
7. Go live	The agreed cutover, with clear responsibilities on both sides and a documented fallback.	Joint decision
8. Hypercare and stabilisation	Users supported, issues resolved and configuration refined before the longer-term growth programme.	Ongoing

Dates come out of discovery

Until we understand your current system, your data and your integrations, any date would be a guess. Discovery produces an agreed timetable, with responsibilities and dependencies on both sides, and only then do we commit to it.

Every stage ends with a joint review

Our team leads the work and reports what has been tested, what remains open and what the next decision is. You approve the next step, or we adjust or pause together. Your IT lead can raise concerns at any point and have them recorded and answered.

People, not just technology

A migration can be technically right and still be slowed by how quickly drivers, dispatchers or riders take to the change. Training, communication and support are planned for each group, and readiness criteria cover people as well as systems. See drivers and dispatchers.