Moving chauffeur bookings out of spreadsheets
To move chauffeur bookings out of spreadsheets, keep an untouched export, clean the meaning of each field, map a small sample of real work first, then reconcile the imported records against the originals. Agree a transition date and one system of record, so new enquiries and changes are not split across two editable booking lists.
In this guide
1. Find the records you actually rely on
List the spreadsheets and other places your team uses for clients, vehicles, bookings, prices and payments. Identify which file is authoritative when two copies disagree.
Keep a read-only original export and note its date. Decide which future bookings and reference records need to move first. Historical files may have different structures and should not be mixed into the first trial import by accident.
- Name the owner of each source file.
- Keep an untouched export before editing.
- Separate future work from archived records.
2. Clean meaning, not just formatting
Give each booking a stable reference. Split pickup date, local time, pickup place and destination into clearly named fields. Keep passengers, bags, service and vehicle requirements explicit.
Check duplicates, missing dates and ambiguous status labels. A row marked done might mean the trip ran, the invoice was sent, or the customer paid. Resolve that meaning before mapping it to a new system.
- Use consistent date and time formats.
- Separate booking status from payment status.
- Review duplicate clients and repeated booking references.
3. Map a small sample first
Choose a few records that represent your work: a transfer, a return, a multi-stop journey and a partner job. Use the importer’s supported fields and review its preview before confirming.
Keep unmapped fields in the worksheet for follow-up. Do not silently put structured information into notes just to make the import appear complete. Some setup, documents or historical relationships may need a separate process.
Map each column, then check it
| Spreadsheet column | Field it becomes | Check before import |
|---|---|---|
| Date | Pickup date | One date format in every row, no text such as 'next Fri' |
| Time | Pickup time | 24-hour time, local to the pickup |
| From / To | Pickup and destination | One address per cell; stops listed in order |
| Pax | Passenger count | A number, never blank or 'a few' |
| Bags | Large and cabin bags | Two separate counts |
| Status: done | Booking status and payment status | Decide whether done meant ran, invoiced or paid |
| Notes | Follow-up list | Move structured details into their own fields first |
Illustrative column names. Map to the fields your importer actually supports and review its preview before confirming.
A four-record sample after the trial import
| Sample record | Result | Next step |
|---|---|---|
| Airport transfer | Accepted; date, time and price match the sheet | None |
| Return transfer | Accepted | Check that both directions are present |
| Multi-stop day | Accepted with the stops in a note | Enter the stops in order instead of leaving them in notes |
| Partner job | Rejected: pickup time missing | Fix the source row and try again |
Illustrative result. Count accepted and rejected rows, then open every accepted record before you import the rest.
- Match each source column to a supported destination.
- Check required fields and rejected rows.
- Keep an explicit list of information that did not transfer.
4. Reconcile the result in the new workspace
Count the accepted and rejected records, then open the imported bookings. Compare date, time, route, passenger, currency and value against the original sample.
Test the next operational step, not just the list view. Check whether the record can be quoted, assigned and found by the right person. Re-enter or review rates and access settings through their proper setup screens.
- Open several individual imported records.
- Confirm money and dates rather than trusting a total alone.
- Check driver, client and partner relationships where supported.
5. Choose one place for the next change
Agree a transition date and a person responsible for the final export. Decide where new enquiries and changes will be recorded during the move. Running two editable booking lists without ownership creates avoidable ambiguity.
Start with a manageable group of users, verify the first working day and retain the original archive according to your data policy. Keep unresolved issues visible until the team has checked them.
- Name the system of record after the transition.
- Brief the office and drivers on the new workflow.
- Keep a checked archive and a list of outstanding corrections.
Questions operators ask
How do I clean a booking spreadsheet before importing it?
Clean the meaning, not just the formatting. Give each booking a stable reference, split pickup date, local time, pickup place and destination into named fields, and keep passengers, bags and vehicle requirements explicit. Review duplicates, missing dates and ambiguous status labels, because a row marked done might mean the work happened, the invoice went out or the customer paid.
Should I import all my old bookings at once?
No. Map a small sample first: a few records that represent your work, such as a transfer, a return, a multi-stop booking and a partner job. Use the importer's supported fields and review its preview before confirming. Keep historical files out of the first trial import, since they may have different structures.
How do I check that a booking import worked?
Count the accepted and rejected records, then open several imported bookings and compare date, time, route, passenger, currency and value against the original sample. Test the next operational step too: check whether the record can be quoted, assigned and found by the right person, instead of trusting a list view or a total.
What happens to spreadsheet fields that do not map to the new system?
Keep them in your mapping worksheet for follow-up rather than pushing structured information into notes to make the import look complete. Keep an explicit list of what did not transfer. Some setup, documents or historical relationships may need a separate process, and rates and access settings belong in their proper setup screens.
How do I avoid running two booking lists during the switch?
Agree a transition date and name the person responsible for the final export. Decide where new enquiries and changes are recorded during the move, because two editable booking lists without ownership create avoidable ambiguity. Start with a manageable group of users, brief the office and drivers, and verify the first working day.
Take it into the working day
The spreadsheet migration checklist
Mark the items you have checked, or download a clean copy for your team.
Download PDF checklist0 of 15 checked. Your selections stay in this page only.
Put 4fleet to work
Try these checks in 4fleet
Explore the workflows that matter to your operation.
See 4fleet in action