See what Kairo would import before you sign up.

Drop the bookings export from your current system. Kairo runs the same column rules its importer uses and shows which columns map, which clients, drivers, vehicles and jobs it would create, and what would not come across. Kairo reads the file once, in memory, and keeps nothing from it.

CSV or Excel (.xlsx), up to 4.5 MB

Kairo reads the file in memory for this one request, then discards it. It does not store the file or send it anywhere else. It logs the system it recognised and the number of columns, nothing more.

How it reads your file.

Three passes, the same ones the signed-in importer makes on the mapping step.
  1. 1Recognises the system

    A Dever bookings export carries a Booking Class column. That marker switches the importer into Dever mode, where the Vehicle column holds registrations. Everything else goes through the generic rules.

  2. 2Places each column

    The importer tries exact header names first, the ones that are safe in any export, then reads the wording of anything still unplaced: a column called Collection becomes the pickup, Reg becomes the registration. Kairo marks what neither pass can place so you can map it by hand.

  3. 3Counts the records

    From the mapped rows Kairo would create or match clients, accounts, partners, contacts, drivers and vehicles, then one job per row, with identical rows skipped. The counts here are the counts the import wizard would show.

What leaves your browser, and what does not.

Kairo parses the file in memory and discards it when it sends the response back. It does not write the file to disk, put it in a database or pass it to another service. The check runs with no account and no workspace, so it cannot touch anyone's data, including yours if you already have a trial.

Kairo logs two things: the system it recognised and how many columns the file had. If you ask for the full report, your email and the headline counts (columns, jobs, clients, drivers, vehicles) go to Kairo's leads mailbox so someone can follow up. No cell, header or file name goes with them. Kairo refuses files over 4.5 MB before reading them.

Bring a real file.

One historic export tells you more about a migration than any feature table. When the report looks right, the switching page explains how Kairo agrees the records, rebuilds the rate card and runs a parallel week before the old system goes.