Migrate

How to migrate

Migration is a cutover, not a rebuild. Keep selling on the old system until the catalog, guest records, and upcoming reservations are in scheduld and staff have practiced the day-of workflow.

migrate

Migration is a cutover, not a rebuild. Keep selling on the old system until the catalog, guest records, and upcoming reservations are in scheduld and staff have practiced the day-of workflow.

Open Settings → General settings → Data Import. Import in this order: Items, Customers, then Bookings, then Products, Assets, Gift Vouchers, Memberships, and Waivers as needed.
Download the CSV template for each type, map your old columns, set defaults for required fields, preview, validate, then import. Imported bookings do not send guest emails.
Create at least one location, set timezone and currency, and publish items with live availability before you share a booking URL.
Staff can take reservations in Bookings and POS while you learn the product. If Stripe and Square are not connected, test payments in the app, staging, and demo mode are allowed and do not charge a card.
Connect Stripe (online cards) and optional Square hardware under Settings → Integrations before you take live guest payments. Cash, pay on arrival, and staff-recorded payments still work without a processor.
Point your website, Google listing, and confirmation emails to the new booking-site URL on go-live day. Keep the old system in read-only mode for a short overlap so you can look up legacy reservations.
When an OTA such as GetYourGuide, Viator, Tripadvisor, Klook, or Booking.com is connected, those reservations appear in Bookings, Payments, and Reports with that OTA named in the Source column. Direct website sales show as Booking site. Phone, walk-in, and desk reservations show as Staff booking. The Source column is hidden by default — turn it on from Columns.

Tips

Import a small sample file first, confirm names and times, then import the rest.
Do not connect live Stripe or Square until staff have completed a test booking, a cash POS sale, and a refund in staging or demo.
If a row fails validation, fix the CSV and re-import only the failed rows rather than duplicating the whole file.