PageSourceSearch

https://resoflow-prod.web.app/assets/switching-from-resdiary-cMXmxcd6.js

js resoflow-prod.web.app collected 2026-10-03 12:37:54 UTC 4,890 bytes, 2 lines download raw bytes

1!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{};e.SENTRY_RELEASE={id:"1.0.0"};var o=(new e.Error).stack;o&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[o]="8e93421c-6f36-47ab-88a7-b771f88c2fcd",e._sentryDebugIdIdentifier="sentry-dbid-8e93421c-6f36-47ab-88a7-b771f88c2fcd")}catch(t){}}();const e="__RESOFLOW_HELP_BODY__",o="Moving from ResDiary to ResoFlow takes three steps: get your data out, import it, and switch your booking links over. There's no deadline pressure — run both systems side by side while you settle in if you like.\n\n## Step 1 — Export your data from ResDiary\n\nAsk ResDiary (or your account manager there) for a CSV export of your **customer database** and, if you want history, your **reservation records**. Your customers' details are your venue's data — ResDiary processes it on your behalf — so you're entitled to take it with you when you leave. Check your contract's notice period at the same time, so your ResDiary subscription doesn't renew after you've moved.\n\n## Step 2 — Import it into ResoFlow\n\nImports run from the wizard at **Settings → Data import** — four steps: **Upload**, **Mapping**, **Preview**, **Import**. Customer and booking imports are *Available on Plus plan and above* (and included with a paid Gift Cards, Loyalty, Tickets or Order & Pay product), and only Owners and Admins see the page.\n\n1. Pick a tile — **Customers** for your customer list, **Bookings** for your reservation history — then click the upload box (**Click to upload your CSV file**) and choose the file. Maximum 500 rows per file; if your export is larger, split it in a spreadsheet and run the wizard more than once.\n2. On the **Mapping** step, the wizard matches your CSV columns to ResoFlow fields automatically wherever the column names are recognisable — check each one and map by hand any it missed. Required fields are marked: customers need an **Email** (plus a name column); bookings need **Date** (`2026-07-28` or `28 Jul 2026`), **Time (HH:MM)** and **Party Size**. Click **Preview data** when the mapping looks right.\n3. **Preview** shows the first 10 rows. Fix anything flagged (or click **Remove N rows with blank required fields** to drop empty rows), then click **Import N records**.\n4. Wait on the **Import complete** screen — don't close the window while it says **Importing data…**.\n\n### What imports\n\n- **Customers**: email (required), name, phone, allergies, birthday, notes and VIP status. A customer whose email already exists in your directory is **merged**, never duplicated.\n- **Bookings**: date (required — `2026-07-28` or `28 Jul 2026`), time (required, HH:MM), party size (required), plus customer name, email, phone, status, duration, notes and table.\n- **Loyalty balances**: if you ran a loyalty scheme and your ResoFlow loyalty scheme is active (loyalty comes with Pro and Complete, or the standalone Loyalty product), the customer Mapping step offers an optional **Loyalty Balance** column — map it to bring members' stamps or points across. Each balance is recorded as a traceable adjustment, and no join bonus is given.\n\n### What doesn't import\n\nResDiary's own diary settings (opening hours, tables, policies), its reports, and anything sold through its add-ons — outstanding gift vouchers included — can't be brought across automatically. You set your venue up in ResoFlow directly (the setup checklist walks y
1ou through it), and any vouchers you've already sold stay your venue's to honour; speak to support if you'd like advice on handling them.\n\n> [!NOTE]\n> ResoFlow reads dates as `2026-07-28` or `28 Jul 2026`, and times as HH:MM. If your export uses DD/MM/YYYY, open it in Excel or Google Sheets, change the date format to one of those, save and re-upload — the Preview step will flag any rows that still don't parse.\n\n## Step 3 — Share your new booking link\n\nYour public booking page (it looks like `…/book/your-restaurant`) is live once your setup essentials are done. Replace your ResDiary booking links and widgets with it on your website and social profiles — the walkthroughs at **Settings → Get more bookings** cover Google, Apple Maps, Instagram, Facebook, TikTok and WhatsApp — or embed the booking widget on your own site. New bookings land in your dashboard in real time, and there are no per-guest fees on any ResoFlow plan.\n\nRelated: [How do I import customers, bookings or staff from a CSV?](import-csv) · [How do I take my first booking?](take-your-first-booking) · [How do I share my online booking page?](share-your-booking-page) · [How do I find and manage my customer list?](customer-directory)";export{e as __helpBodySentinel,o as default};
2//# sourceMappingURL=switching-from-resdiary-cMXmxcd6.js.map

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.