How do I import guests, bookings or staff from a CSV?
Use the four-step Data import wizard to bring guests, bookings or staff over from another system — up to 10,000 guests or bookings in one file.
Bring your existing guests, bookings or staff into ResoFlow with the wizard at Settings → Data import — four steps: Upload, Mapping, Preview, Import. Moving from an old system? Import your guest list and your booking history from it here.
Guest imports come with Plus and above, and with every paid Gift Cards, Loyalty, Events or Order & Pay product; booking imports need a venue plan (a venue with products only doesn't see the Bookings tile). The staff import comes with Complete only. Only Owners and Admins see this page.
Run an import
- Go to Settings → Data import and pick a tile: Guests, Bookings, Staff Members or — when gift cards are on — Gift cards.
- Click the upload box (Click to upload your CSV or Excel file) and choose your file — a .csv, or an Excel .xlsx file as it is (the first sheet is read; there's no need to save it as CSV first). A guests or bookings file can hold up to 10,000 rows (a staff file up to 500) and 8 MB, and must include a header row. A big file is brought in 500 rows at a time, with a progress bar and one result at the end; for more than 10,000, split the file, or ask our team to bring it across for you. Not sure what the file should look like? There's a sample-template download link under the upload box (its wording names the data type — "Download a sample guests template", and so on) — it downloads a ready-made CSV with the right columns and example rows to copy.
- Mapping — match your CSV columns to ResoFlow fields. The wizard auto-matches columns with recognisable names; fix any it missed. Files that look like a Quandoo export are recognised and pre-filled automatically — and if yours isn't, the Importing from another booking system? row lets you pick Quandoo and click Apply the column mapping. The same row covers OpenTable, ResDiary, Collins (DesignMyNight), TheFork and SevenRooms — see Files from OpenTable, ResDiary, Collins, TheFork or SevenRooms below. Required fields are marked — guests need an Email (plus a name column); bookings need Date, Time (HH:MM) and Party Size; staff need Full Name, Username and Role. Dates can be 28/10/2026, 2026-10-28 or 28 Oct 2026 (the format ResoFlow's own bookings export uses, so you can export, tidy up in a spreadsheet, and re-import). When your file has a Date (or Birthday) column, the Mapping step asks Dates in this file are — Day first (28/10/2026), the UK way and the default, or Month first (10/28/2026) — once for the whole file. Times can be 19:30, 19:30:00, 9:30 or 7:30 pm. Click Preview data.
- Preview — check the first 10 rows look right. If any row has a problem, Rows with a problem lists every one of them with its row number (matching your spreadsheet — row 1 is the headings) and the reason, so you can find a bad date on row 340 without hunting. If some rows are missing required fields, click Remove N rows with blank required fields to drop them.
- Importing bookings, the Preview step checks the file's tables against your floor plan (see Tables in your bookings file below), and has the box Don't send reminders for these bookings. Imported bookings never send a confirmation, and ones that have already happened send nothing at all; bookings still to come get your usual reminders unless you tick it (do, if your old system is still running and reminds guests itself).
- Click Import N records to start the import. When some rows have a problem, the button says Skip these rows and import the rest instead: everything else comes in now, and the skipped rows are listed again on the results screen so you can fix them and import just those later.
- Wait on the results screen — don't close the window while it says Importing your data…. When it finishes you'll see exactly what happened: how many records imported, a Skipped rows list naming each skipped row and why (for example "Row 7 — invalid time"), and an Imported with adjustments list for rows that needed a tweak (a shortened note, say). If the import stops with Import failed and says some rows may already have been imported (the connection dropped, or it stopped part-way), check your guests or bookings before trying again; if it says nothing was imported, nothing was.
Undo this import. For 7 days after a guests or bookings import, Undo this import (on the results screen, and under Recent imports on the Upload step) takes it back out. You confirm with your password, and it removes only what that import added that nobody has changed since — anything edited, seated, booked or paid stays and is listed with the reason.
A booking that's already here is never brought in twice. Before writing anything, the bookings import checks your diary: a row whose old-system reference (the Booking Ref column) is already on a booking is skipped, and so is a row with the same date, time, guest email or phone and party size as a booking you already have. A row that repeats an earlier row of the same file is skipped too. The results screen lists every one under Already here — not imported again, with its row number and the reason. So it's safe to import a fresh export, an overlapping file, or the same file again — and if you upload an identical file, ResoFlow still asks "This file has been imported before" first, so you know.
Files from OpenTable, ResDiary, Collins, TheFork or SevenRooms
On the Mapping step, the Importing from another booking system? row has a list of systems — Quandoo, OpenTable, ResDiary, Collins (DesignMyNight), TheFork and SevenRooms. Pick the one your file came from (it's already picked if you told us at sign-up, or if the file looks like that system's export) and click Apply the column mapping: the matches below fill in one go, and you can still change any of them. Nothing is written until you've seen the preview and pressed Import.
These five systems don't publish their export's column names, so their matches come from what each one does publish — not yet from a real export file. That's why a file from one of them is never matched by itself: the row says "This looks like a TheFork export — not applied yet" (or whichever system it is), and after you apply it a Check each match. note asks you to check every field and the preview. If a column isn't matched, pick it by hand.
Once applied, the import also reads the file the way that system writes it:
- A date and time in one column (ResDiary's visit date and time, TheFork's meal date, say) is split into the booking's date and time. A time written with a time zone is read in your venue's own time zone.
- The system's booking statuses become ResoFlow's. For example: Booked, Recorded, Left Message or Unconfirmed (the guest hasn't reconfirmed yet) → Confirmed; Pending, Requested, New or In Progress → Pending; Arrived or Seated → Seated; Done, Finished, Left or Complete → Finished; No Show → No-show; Cancelled, Refused, Rejected or Lost → Cancelled. On Collins, Complete means the booking went ahead as agreed, so it comes in as Confirmed. A status the import doesn't know is listed with the row's reason.
- A party size written with a word ("4 covers") is read as the number.
- The system's own booking number comes across as the booking's reference, so you can match a booking back to the old system.
The marketing column in these files (an opt-in, a newsletter or a marketing permission) is never matched to Said yes to offers by itself — see Marketing consent below. A yes kept by TheFork can cover a whole group of venues, so a guest may have said yes at another venue in the group.
Tables in your bookings file
The bookings import checks your file's Table column against your floor plan before anything is imported. If the file names tables that aren't on it yet ("Snug", "T14"), Tables not on your floor plan lists each one with how many of its bookings are still to come, and the import waits until you've sorted them: click Add them on the floor plan (it opens in a new tab, and the preview checks again as soon as you've added them), use the Match button when ResoFlow spots a close match ("Match T14 to Table 14"), or tick Import without these tables to bring those bookings in with no table on purpose. A booking whose Table cell names several tables ("Table 7, Table 8") keeps every one of them as one joined booking, so none of them can be sold twice.
Telling guests their booking has moved
Guests with a booking still to come got their confirmation from your old system, so its link is the one they'd use to change or cancel — and a cancellation there never reaches ResoFlow. When a bookings import brings in bookings still to come, the results screen offers one short email to those guests (ticked, with See the email to preview it): "Your booking is still in our diary", with their booking's new link to change or cancel. Click Send to N guests (you confirm with your password, as it emails many guests at once), or Not now. It's sent once per booking, never for bookings already past or cancelled, and guests with no email address are left out (the screen says how many). It's a message about a booking they already have, not marketing. Their reminder before the visit says the same in one line, unless you turned reminders off for those bookings. Your set-up's "Moving from …" checklist ticks Tell guests with a booking still to come once it's sent.
Their history with you (visits, tags and dietary)
a guest list from SevenRooms, ResDiary, OpenTable or another system usually has Visits, Last visit, Tags and Dietary columns, and they can come across (a Seating preference column too). Each is optional and matched on the Mapping step. Visits and the last visit show on the guest's profile and on their bookings as visits before ResoFlow, added to the visits ResoFlow counts — so a regular is never shown as "First time visiting". A guest who came from your old list is also never sent the first-visit welcome email. Tags are added to the guest's own tags (the ones you filter Guests by — they come with Plus and above; on a plan without them the tags are left out and the results screen says so), never replacing any; several tags in one cell are separated by commas. Dietary and Seating preference fill the guest's profile, and a blank cell never clears what's already there. A Visits cell must be a whole number and a Last visit a date, or the row is listed with the reason. Spend columns aren't brought across: money taken in another system isn't ResoFlow's to report.
Moving from another system, step by step (links, Google and the old contract)
On Your set-up, the Coming from another system? step is a checklist for the whole move, named for the system you're leaving — the one you picked when you signed up (no answer then? it asks here, and you can change it). Six steps, in order:
- Bring your guest list and 2. Bring your bookings — the importer opens from the step, and each ticks itself once an import has brought something in.
- Tell guests with a booking still to come — ticks itself once you've sent the "booking has moved" email from the bookings results screen.
- Swap every booking link — your website's button, Google (add your ResoFlow link and remove the old system's — Google keeps showing its "Reserve a table" until that system takes it down, so ask them when you cancel), Instagram and Facebook, Apple Maps and Tripadvisor, and your printed QR codes. Tick each as you go.
- Run both, or switch over — see below.
- Cancel your old system in time — give its renewal date and click Set a reminder: five weeks before, a notification on the bell reminds you to give notice (many contracts renew each year and need 30 days' notice). Remove the reminder takes it away.
Every tick is yours — ResoFlow can't see your other system — and Done on each step ticks it by hand.
Running both systems for a while
Keeping the system you're leaving for a while (for its diners, say)? Bring in the bookings it takes, every few days, so your ResoFlow diary has every table. After your first bookings import, the Upload step shows Running your old system alongside? with your last bookings import, and a Bring in new bookings button:
- Click Bring in new bookings and choose its new export. Your column matches from last time are kept, so it goes straight to the Preview (if a column's heading has changed, you match it once on Mapping).
- Don't send reminders for these bookings starts ticked here — the other system reminds its own guests. Untick it if you want ResoFlow's reminders instead.
- Click Import. Only bookings that aren't here yet are added. A booking already brought across that was cancelled there since is cancelled here too, and its table is free again; one that moved (a new date or time) or whose party size changed is changed here too. ResoFlow sends the guest nothing about either — they made the change there, which told them.
- The results screen lists each one under Changed to match your old system. A booking your team has changed here since it was brought across (seated, edited, or with a payment on it) is never changed by a file — it's listed under Changed in your old system — left as it is here, with why, for you to sort out by hand.
It only works for bookings that carry that system's reference (the Booking Ref column), and only for bookings still to come. An ordinary import (not through Bring in new bookings) never changes a booking that's already here.
Marketing consent and loyalty balances
Marketing consent: another system's newsletter or marketing column (Quandoo's Newsletter, or an OpenTable, ResDiary, Collins, TheFork or SevenRooms opt-in, say) is never matched to Said yes to offers automatically — that yes may have been to the old system, not to you — and the Mapping step says so. To bring a real yes across, add a Said yes to offers column to your file (the sample template has it; map it on the Mapping step) and put Yes against each guest who agreed to hear from you — for example on a sign-up form. The preview step then has the box "I have permission to upload these guests’ details, and the ones marked “Said yes to offers” agreed to hear from us". With it ticked, only the guests marked Yes can get your marketing, and their yes is recorded on their profile. Everyone else — and every row if the box isn't ticked — is imported as not asked: they get no marketing (including the loyalty round-up email) until they choose themselves, for example by booking and leaving the offers box unticked. A No or a blank cell counts as not asked, and a cell ResoFlow can't read (say "maybe") is listed under Imported with adjustments. An import never changes a choice a guest has already made, and guests who have said no stay that way; if an earlier import left someone as not asked, a later import that marks them Yes (with the box ticked) records their yes. Imported guests who said yes get their first campaign 100 at a time: the first 100 get it straight away, and the rest wait with the campaign's held rest and go by themselves on a later morning, once fewer than 4 in 100 of those first emails have bounced (an old list full of dead addresses pauses your marketing instead, and the ResoFlow support team will go through it with you). Imports preserve existing booking history and loyalty records, including changes made while the import is running.
If our team brought your guest list across for you (the free set-up), the guests your old list marks "Said yes to offers" come across waiting for you: only you can say you have their permission, so until you do they're not asked and get no marketing. Your Guests page then shows a card — for example "212 guests said yes to offers in your old system" — with the same sentence as the importer's box. Tick it and click Confirm 212 guests (the number is yours) to record their yes, with your name and the time, as the evidence; or click Leave them as not asked. A guest who has chosen for themselves since, or said no before, stays exactly as they chose. Only an Owner or Admin can confirm, and ResoFlow's team can't confirm it for you.
Switching from another loyalty scheme? While your loyalty scheme is active (loyalty comes with Pro and Complete, or the standalone Loyalty product), the guest Mapping step offers an optional Loyalty Balance column. Map it to bring your members' stamps or points across: each balance creates that guest's membership (or tops up an existing one) and is recorded as a staff adjustment in the activity log, so the movement is always traceable. No join bonus is given — a migration isn't a new join. Values must be whole numbers (0 or more; an invalid value rejects that row), and a blank cell means the guest isn't a member. The success screen confirms how many loyalty balances were applied.
Birthdays: the optional Birthday column takes a day and month — 28 Jul or 07-28 — or a full date (1990-07-28 or 28 Jul 1990). Only the day and month are kept: a year in the file is dropped, never stored. A birthday the wizard can't read is shown as a row error — it's never silently dropped.
Gift cards from your old system
If guests hold gift cards from the system you're leaving, bring them across with the Gift cards tile (it shows when gift cards are on for your venue). The file needs a Code and a Balance for each card — what's left on it, like 25.00 — and can carry an Expiry date and a Holder email. Each card keeps its old code, so a guest's card still works when your team redeems it, at your booking page's checkout and on your gift card balance page — and your team can find it by typing its old code into Search or do anything. A code shorter than 10 letters and numbers is too easy to guess online, so it works only at your venue: your team finds and redeems it in the Scanner and on the Gift cards page as usual, while your balance page and every online checkout say "Please use this card at the venue" — after the import, the results screen says how many of your cards that applies to. A card with no expiry date gets your usual gift card expiry from today; a card that has already expired, has nothing left on it, or whose code is already in ResoFlow isn't brought across (the results screen lists each one with the reason).
Nothing is sent when you bring them across, and the cards are marked Brought across on your Gift cards page. Afterwards, a card with a Holder email gets your usual reminder about 30 days before it expires (while Expiry reminder emails is on), and the "£X used, £Y left" email after it's used (while Balance update emails is on) — never the balance reminders. Their balances count only in what guests are still owed — never as gift cards sold, takings, fees or VAT in any report or summary email. Each card's history starts with "Balance brought across from the previous system". A card brought across counts towards your plan's live gift card limit like any other.
Staff imports: the credentials file
A PIN is auto-generated for each imported staff member. On the success screen, click Download credentials CSV before leaving the page — the PINs are shown once and never stored in plain text, so this is your only chance to download them. Hand each person their PIN; they'll be asked to choose a new one on first sign-in. Delete the file once distributed.
Tips
- Imported guests appear in your directory immediately; imported bookings land on the dates in the file. An imported booking shows what came across from the old system (its reference, what it was booked through, what was paid there and any extras) near the top of the booking's Overview, and a booking already paid in the old system carries a small Paid elsewhere chip (or Paid on OpenTable, when the file names it) — that money is with the old system, so take it off the bill at the venue.
- An Excel .xlsx file is read as it is: date cells come in as dates and time cells as times, whatever Excel shows. Only the first sheet is read, so put your data there.
- Any .csv your old system or spreadsheet saves is read as it is — one Excel saved on Windows keeps its accents (Zoë, Siobhán), and one separated by semicolons or tabs instead of commas is read too.
- Roles in a staff CSV must match your role names (built-in like manager/host, or a custom role's name). You can't bulk-import an owner.
Related: How do I export my data? · How do I add a staff member? · How do I find and manage my guest list? · How do I switch from Quandoo to ResoFlow?