Migration readiness
Your old system stays live until Kairo has run a real week.
A switch is more than importing rows. Kairo agrees the records, tests the rates, prepares the team and validates live work before you retire the old system.
Get a migration assessmentKairo counts clients, drivers, vehicles, forward bookings and account balances and writes them into the checklist.
Kairo checks rebuilt rates against historic jobs to confirm they return the agreed figures.
Source files, credentials, approvals and team availability must be complete before the delivery clock starts.
Kairo runs beside the current system for a live week before signed handover.
Kairo writes the scope before work begins.
A migration has three decisions.
Each decision produces an artefact you can inspect before moving on.
- 1Can the source be read?
Confirm the system, files, record counts and any access needed to retrieve the agreed data.
Output: source and exception list - 2Does Kairo behave correctly?
Rebuild the agreed rates and use historic jobs to verify that real work prices as expected.
Output: verified sample and checklist - 3Is the operation ready to cut over?
Train the office and drivers, run a parallel live week, then sign the handover or resolve the remaining exceptions.
Output: signed handover and rollback/export test
What a migrated booking looks like.
The same record from quote to invoice, moving on its own.
Turn an enquiry into a complete, priced journey.
Enter the route, passenger and vehicle class once. Kairo applies the account rate and sends a branded quote the client can accept in one tap.
Four things Kairo agrees before any date.
The records that move, what a sample can prove, how the parallel week runs, and what happens to the old system.
The same booking, priced twice: one system forks a new version at every hand-off, the other keeps one record end to end.
The categories in scope are clients, account billing terms, drivers, vehicles, tariffs and rate cards, and open and historic bookings and invoices. Kairo counts each category from the source system and agrees it in writing before import, so the checklist reflects what your operation actually holds rather than a generic template.
Kairo's CSV and Excel importer can load a representative export and rebuild rate cards against a set of historic jobs, which proves that the file format is readable and that the rebuilt rates return the figures you already charged. It cannot prove that your book holds every rate variation, or that every historic booking will import cleanly, until the full data set has been through the same check.
Both systems stay live at the same time. You enter new bookings in Kairo only, and Kairo reconciles each day's sheet against the current system before it closes, so you catch any discrepancy the same day rather than discovering it after you switch off the old system.
Retiring the old system does not mean losing the record. Once you sign off the parallel week, Kairo keeps the imported data live and you cancel or downgrade the old subscription; Kairo keeps a read-only export of the previous system so you can still look up historic bookings and invoices later. Operators who want this run for them rather than self-managed can choose the Managed Launch service, £495 one-off, described on the Managed Launch page.
Start with the system you run today.
Vendor-specific pages explain the operating-model trade-offs and published evidence. They do not assume a direct migration is possible until Kairo checks the source data.
Choose who owns the migration work.
The Kairo subscription is separate from the optional Managed Launch service.
Use the onboarding flow and importer yourself.
Kairo carries out the written migration checklist.
You import and validate them.
Kairo reconciles agreed records and verifies rate samples.
No purchased training, parallel week or guaranteed date.
Office training, driver setup and a parallel live week.
No setup-service charge.
£495, one-off.
Bring a sample before you bring the operation.
Use one historic booking, a rate-card sample and the source export you expect to rely on. Kairo will return a written view of the migration scope and exceptions.