Skip to content
Syndik8

Import bookings from a CSV

Move bookings from any other booking system into Syndik8 by uploading a CSV and telling Syndik8 which columns hold the booking data.

Before you start

Section titled “Before you start”
  • You must be an admin or the owner of the syndicate.
  • Export the bookings from your current system as a CSV. The parser accepts ISO 8601 dates, dd/MM/yyyy HH:mm, and a handful of other common formats — see generic CSV format for the full list.
  • Start Date/Time and End Date/Time are the only required fields. Member name, member email, aircraft registration, notes, and flight time are optional.
  • If your CSV happens to be a genuine Goboko export, the wizard will detect it and skip the column-mapping step — see import bookings from Goboko.

Steps

Section titled “Steps”
  1. Open the syndicate and go to Settings → Import Data.
  2. On step Upload CSV File, tap Choose File and pick your export. The screen reports Generic CSV detected — map columns below and a row count.
  3. On step Map Columns, pair each Syndik8 field with a column in your CSV using the dropdowns:
    • Start Date/Time — required
    • End Date/Time — required
    • Member Name, Member Email, Aircraft Registration, Notes, Flight Time — optional Leave unwanted CSV columns unmapped; they are ignored.
  4. On step Match Import Entries, confirm each unique person in the CSV. Each entry resolves to an existing member, an invite to send (if you enter an email), or an aircraft-maintenance booking. There is no automatic maintenance detection on this path — mark rows as maintenance yourself if your source system used a sentinel name.
  5. On step Match Aircraft, confirm each unique registration maps to an existing asset. If the syndicate has only one asset, every row auto-matches that asset regardless of what your CSV’s registration column says.
  6. On step Review Import, read the summary — bookings to create, skipped rows, duplicates from a prior import. Tap Import N Bookings to commit.
  7. The wizard runs the import and lands on Done.

If it goes wrong

Section titled “If it goes wrong”
  • The wizard will not move past Map Columns. Both Start Date/Time and End Date/Time must be mapped. Check that at least one column in your CSV holds each value and pick it from the dropdown.
  • Bookings are an hour off during BST. CSV rows without a timezone offset are treated as UTC. If your source system stored local times without an offset, look for an ISO variant with Z or +01:00 in the export. Otherwise the times will land an hour off during British Summer Time.
  • Rows are being skipped at parse time. Dates that do not match any of the supported formats are silently dropped. Open the CSV in a spreadsheet, check the column types, and re-export if needed.
  • Member matching keeps failing. Members are matched first on exact email (case-insensitive), then on exact display name. If neither matches and the row has no email, the row is skipped. Either invite by email on the matching step, or adjust the source data to carry the member’s account email.
  • The file is being treated as Goboko. That is intentional — if your CSV is UTF-16 with the Goboko header, it routes through the Goboko path automatically. You do not need this guide; use import bookings from Goboko.

See also

Section titled “See also”