Black Friday
Skip to documentation content

Booking Operations

Import and export bookings with CSV

Pro's booking CSV workflow supports controlled migration and operational export. An import changes booking data and inventory; a CSV file is not a database backup and does not prove a gateway payment or customer consent.

Pro’s booking CSV workflow supports controlled migration and operational export. An import changes booking data and inventory; a CSV file is not a database backup and does not prove a gateway payment or customer consent.

Prepare a small test file

Use the CSV screen’s current template rather than inventing columns. Required headers are external_reference, room_code, quantity, check_in, check_out, adults, guest_name, guest_email, total_amount and currency. Keep ISO dates, room codes and monetary values consistent with the target hotel.

The parser limits a file to 5 MB and 1,000 rows. Preserve a stable, unique external reference for each source booking. Optional status and financial columns are validated; they are not unrestricted instructions to mark a reservation Paid.

Preview, then import

  1. Back up the target database and use a disposable environment for the first rehearsal. Use authorized Pro staff access.
  2. Upload the .csv file and inspect validation errors with their original row numbers. The preview shows the first 25 rows, so also review the full result counts.
  3. Correct rejected data before confirmation. Positive paid/refunded amounts additionally require payment-management permission and supporting historical evidence.
  4. Confirm the owned preview. Commit rechecks capacity and availability for every row; existing references are skipped.
  5. Read imported, skipped and failed counts and inspect the affected bookings. Resolve failed rows individually, retaining references for already imported rows.

Imports can have mixed row outcomes. Re-uploading with different references can create duplicates; do not assume a whole batch was rolled back because some rows failed. Historical imports do not send booking or invoice emails.

Export and protect the result

Apply the intended filters and export only what staff need. CSV may contain guest contact details, internal notes and financial references; store it in a restricted location and follow the hotel’s retention procedure. Do not email production exports as test fixtures.

Imported Room Policy text can be snapshotted, but imported data does not establish an online acknowledgement. Imported paid amounts do not create provider-owned transactions eligible for automatic refunds. Undoing a migration needs a reviewed restore or correction plan, not deletion of financial rows.

Was this article helpful?

Your feedback helps us improve the documentation.