Import your data from a CSV or Booklux

Moving from Booklux, Anolla or a spreadsheet? Settings → Import loads your existing data from CSV files. Every import is checked in a dry run before anything is written, and a committed import can be rolled back.

#Before you start

• Create your resources and services first. Booking imports match rows to them by name.
• Export your data from the old system as CSV. The column names follow Booklux exports, so a Booklux export needs little or no editing. From another system, rename your columns to match the template.
• Import in this order: Clients first, then everything that refers to clients.

#What you can import

booklux_id is the client's ID in your old system. Any unique value works if you are not coming from Booklux. Other rows find their client through it.

#Get a template

Under Template CSVs, click the template for the kind you need, for example Clients template. It opens the header row in a new tab. Save it as a .csv file and fill it in, or compare it with your export.

#Import a file

1. Under Upload a CSV, choose the Kind.
2. Pick your file under CSV file and click Upload. A new job appears in Job history with the status uploaded.
3. Click Dry run. Nola reads every row and shows a summary: rows, OK, warnings, errors and duplicates in the file. The first 10 errors and warnings are listed by row number.
4. Fix any errors in your file, upload it again and repeat the dry run. Commit stays disabled while there are errors.
5. Click Commit. Nola shows how many rows were created, updated, skipped or failed.

#What to expect

• Clients that already exist with the same booklux_id are updated, not duplicated. Birthday, address, card number and PIN go into the client's notes. group becomes a tag and newsletter_optin sets marketing email consent.
• Wallet balances, passes and bookings are only created for clients who already have a Nola account linked to their client record. Other rows are skipped with the message "Client has no linked Nola account yet". Once those clients have signed up, run Dry run and Commit on the same job again to pick them up.
• Bookings fail if the resource name does not match a resource in Nola. Without a service column, Nola uses your first active service.
• Class attendees need a training group whose name matches class_name. Otherwise the row is skipped.

#Roll back an import

A committed job has a Rollback button. It removes the bookings, booking series, client passes and memberships, and class enrolments that the job created. Clients and wallet credits are kept, because they may already have new activity. Imports and rollbacks are recorded in the audit log.

#Related

• Clients
• Resources and hours
• Services
• Client wallets