Help centre
Import bookings from a CSV, Excel file or itinerary
No connector? Drop in tomorrow's bookings as CSV or Excel, check every row before it goes in, or paste a multi-day itinerary.
Export tomorrow's bookings from your booking system as CSV or Excel, then drop the file in on Import CSV. DayRunner matches the columns, shows you every row before it goes in, and flags any row it can't read. It reads .csv, .xlsx, .xls and .xlsm.
Steps
Choose the file
Click Import CSV in the sidebar. Under Bookings: choose Spreadsheet or CSV, then pick your file. For a workbook with several sheets, pick one from Sheet.
Check the columns
DayRunner guesses which column is which. Fix any wrong ones in Maps to, and choose ignore for columns you don't need.
Check before importing
Set Dates in this file are to day/month (NZ) or month/day (US export). Fix or skip any flagged rows.
Import
Click Import N bookings. The mapping is saved, so next time it's one click. Then go to Day and press Plan the day.
Flagged rows
A row whose date, time, pax or status can't be read is flagged in red with the reason, for example Couldn't read the date "32/10" or "No time in this row". It isn't imported until you deal with it. You can:
- type the right date, time or pax straight into the row,
- tick Skip this row, or
- click Skip all N flagged to leave every flagged row out.
The summary at the top shows how many bookings, guests and flagged rows there are, and what's new, changed or to cancel compared with what's already in DayRunner. Grey notes, such as "Departs 05:30: check it's not a pm time", are worth a look but don't stop the import.
The fields DayRunner understands
| Maps to | What it is | If missing |
|---|---|---|
| Booking ref | Booking or order number | Made from the date, time, product and name. Map it if you have it, so re-imports update rather than duplicate. |
| Status | confirmed, cancelled, pending | Confirmed |
| Product | Tour name, exactly as in Setup | "Tour" |
| Date | 2026-11-02, 2/11/2026, 2 Nov 2026 | Default date (rows with no date column) |
| Time | Start time, 06:45 | Row is flagged |
| Lead guest name | Lead guest | "Guest" |
| Pax (guests) | Number of guests | Row is flagged |
| Children (added to pax) | Extra column for children | |
| Pickup location | Hotel or pickup point, as written in your stop order | Depot |
| Phone | Guest mobile with country code | No phone message drafted |
| Guest email | ||
| Source (channel) | Direct, Viator and so on | Direct |
| Notes | Special requests. "Child seat", "wheelchair", "vegetarian" and "gluten" are picked up. |
Bookings with the same date, time and product become one departure.
Download the template: bookings.csv.
No booking system? Paste an itinerary
For multi-day groups, choose Itinerary under Bookings:.
- Paste the itinerary or choose a
.txtfile. Each timed line becomes a departure. Each named venue becomes a supplier, with its reference on the confirmation list. Breakfast, lunch and dinner lines are marked as meals. - If the day headers have no dates, set Day 1 date (if the itinerary has none). Set Group pax if it isn't in the text.
- Check the table. Untick lines you don't want, and fix dates, times, suppliers or references in place.
- Leave Create as a tour ticked to get a tour with a day sheet for the guide.
- Click the create button. Lines without a date are not imported.
A "Guests:" line creates one group booking per departure. Without guest names, no bookings are created, but suppliers and confirmations still are.
Download the template: itinerary.txt.
Common problems
- Dates a month out. Set Dates in this file are to match your export. US exports are month first.
- Unknown product after planning. The product name in the file doesn't match Setup. See Decide before the day.
Tomorrow, sorted by 5pm.
Show us tomorrow in your booking system. We'll show you the same day in DayRunner.