Skip to main content
Data import brings your existing records into 1club from CSV files - usually when you move your gym over from another system or a spreadsheet. It runs as a four-step wizard: pick what you are importing, upload the file, review a validated preview, then execute. An AI analyzer can detect the record type and map your columns for you, so a file exported from another system usually imports without hand-editing the headers. You can import nine record types: members (contacts), accounts (households and companies), plans, memberships, charges, classes, bookings, invoices, and products. Files must be CSV and up to 10 MB.

When to use it

Use import to start on 1club with your history intact instead of re-keying members by hand. Nothing is written until you have seen a validated preview, only valid rows are imported, and re-running a file reuses existing members rather than duplicating them. Typical uses:
  • Migrating members with their memberships - a padel and tennis gym imports one members file that also creates each member’s session-based membership, with sessions already used, and adds children as household dependents.
  • Plans first, then the people on them - a martial-arts gym imports its belt-progression plans, then a members file that references those plans by name so each student lands on the right package.
  • Carrying over class credits - a Pilates studio imports one-time class-pack memberships with the pack size, so their remaining class credits carry over.
  • Bringing in past sales - a climbing gym imports its past day-pass charges, keyed by the member’s email.
  • Stocking the shop - a padel club exports its product list from its old till, with prices, VAT rates, barcodes, and quantities, and imports it as the shop’s catalog and opening stock.
See Worked example: migrating from a legacy system and Other vertical examples for the details.

The import wizard

Import lives under Settings > Data Tools > Import. The wizard has four steps, shown as a stepper across the top: Select Entity, Upload File, Preview, and Import. Because records reference each other, import them in dependency order. The wizard states it on the first step:
  1. Members (contacts)
  2. Accounts
  3. Plans
  4. Memberships
  5. Classes
  6. Bookings
  7. Invoices
Charges can be imported on their own or created as part of a chained member import. Products don’t depend on anything else and can be imported at any time. Before importing, make sure your Clubs, Areas, and Instructors already exist, because classes and bookings reference them by name or email.

Step 1 - Select entity

You have two paths on this step. AI-powered import. Upload a CSV into the AI card. The analyzer reads the headers and the first few rows, then proposes:
  • the detected record type, with a confidence percentage,
  • a short reasoning line explaining the detection,
  • a set of column-to-field mappings, shown as "Your Column" -> field chips.
If the detection looks right, continue and the mapping is applied automatically. If it is off, you can still pick the record type manually below. Manual selection. Choose one of the record-type cards: Members (Contacts), Accounts, Plans, Memberships, Charges, Classes, Bookings, Invoices, or Products. Each card shows a short description of what it imports. For Products, pick a Stock location (club). Quantities in the file are imported as opening stock for that gym; products without a quantity are imported without stock.

Step 2 - Upload file

If you uploaded through the AI card, your file carries over and the wizard notes it is already uploaded. Otherwise, upload the CSV here. Use Download Template to get a CSV with the exact expected column names for the selected record type; fill it in and upload it back. Only .csv files are accepted.

Step 3 - Preview

The preview validates every row against the selected record type without saving anything. You get three counts: Total Rows, Valid Rows, and Invalid Rows. Filter tabs let you view All, Invalid, Duplicates, or Valid rows, and each invalid row lists its specific validation errors. Rows that already exist, in 1club or earlier in the same file, are marked Duplicate and are skipped on import. For a large file the table shows a sample of rows, but the counts cover the whole file: every row is checked, and every valid one is imported. You can download the previewed rows (with their status and errors) as a CSV to fix them offline.
Invalid rows are never imported. Only valid rows are written when you execute, so a preview with invalid rows will import fewer records than the file contains. Fix the flagged rows and re-upload if you need all of them.

Step 4 - Import

Click Execute Import to write the valid rows to your organization. A large file is sent in batches, and the page shows how many rows are done; leave the tab open until it finishes. The results screen reports Total Rows, Imported, Skipped, and Errors, lists the first five row-level errors, and offers Download all errors (CSV) for the rest. Use Import Another File to start a fresh import. If a batch fails part-way, the import stops and tells you the row it stopped at. When the server declined the batch, nothing from that row onwards was written: fix the problem and run the file again. When the connection was lost, some rows from that point may already be in 1club, so check that range before re-running. For membership imports, executing first opens an Import Memberships dialog asking how their charges should be recorded:
  • Mark as paid - settles the charges. Choose the Payment method to record them against, from your manual payment methods (such as Cash).
  • Include signup fees - charges each plan’s signup fee alongside the membership. Leave it off when the joining fees were already collected in your previous system.

Field mapping and templates

Each record type has a fixed set of expected fields. The template download gives you those exact column headers. Useful conventions the importer follows:
  • Member name - use either name (a full name that is split into first and last) or firstName plus lastName. At least one is required.
  • Custom fields - for member imports, any column whose header starts with custom_ is treated as a contact custom field automatically. Do not map those to standard fields.
  • Tags - tags takes a comma-separated list, for example Open day, Lead. A tag that does not exist yet is created as a manual tag, so you do not have to set your tags up before importing. To tag a whole upload at once, put the same value in the tags column of every row.
  • Dates - accepted formats are dd.MM.yyyy, dd.MM.yyyy HH:mm:ss, yyyy-MM-dd, yyyy-MM-dd HH:mm:ss, and ISO-8601. A row with an unparseable date is flagged in the preview.
  • Charges default to paid, using your organization currency when none is given.
  • Bookings - each row books one slot for one customer. paymentStatus is paid or unpaid, and paymentMethod names how a paid row was collected. Leave totalPrice empty to price the slot from the area and instructor rate, or use 0 for a free or membership-covered booking. clubName can be left out in a single-club organization, and the club, area, class, and instructor columns accept a name (or an email for people).
  • Accounts - one row per member of a household or company account, naming an existing member by contactEmail (preferred) or contactName. accountType is household or company. role is owner, adult, or dependent for a household and admin or employee for a company; left blank, a household’s first member becomes its owner and everyone else an adult, and every company member is an employee. isPrimary (yes or no) picks the account’s primary contact, otherwise the first member is.

Product import

A product import brings in your shop catalog, for example an export from your previous till. The AI analyzer recognises common English and Bulgarian headers (such as Име артикул, Продажна цена, ДДС %, and Количество).
  • Stock location (club) - Choose a club on the first step. Quantities in the file become that club’s opening stock. Products without a quantity, or every product when no club is chosen, are imported without stock.
  • VAT rate - taxRatePercent is a percentage such as 20. Each rate is created once and then used at the point of sale, so a product is taxed at its own rate whatever its revenue account.
  • Category and brand - A category or brand that does not exist yet is created for you.
  • Revenue account - Matched by name to a revenue account you already have. If no account matches, the product is imported without one, for you to set later. An import never creates revenue accounts.
  • Cost price and SKU - costPrice feeds margin reporting, and sku is the product code alongside the barcode.
  • Duplicates - A product with a barcode matches an existing product with that barcode. Without a barcode, it matches on name and price, so the same item at two prices imports as two products. Matches are skipped, so you can re-run a file safely.
  • Active - isActive accepts yes or no (also in Bulgarian).
Importing products needs permission to create products, manage inventory, and manage billing (because it can create tax rates), which in practice means an Admin.

Chained member import

A member import is more than contacts. When the extra columns are present on a member row, the same row can also create related records in one pass:
  • A charge - transactionAmount, transactionDate, transactionDescription, transactionPaymentStatus, transactionType, transactionCurrency, transactionTaxAmount, transactionTotalAmount.
  • A membership - planName, membershipStartDate, membershipEndDate, membershipStatus, membershipPrice, membershipBillingFrequency, membershipAutoRenew, membershipSignupFee, plus session totals membershipMaxUses, membershipUsed, membershipUsesRemaining.
  • A wallet credit - wallet, a decimal amount credited to the member’s wallet.
  • Household dependents - two ways, never both on one row:
    • guardianEmail (preferred) - the row describes the child, with their own date of birth and gender, and guardianEmail is the parent’s email. The child is added to the parent’s household.
    • dependent - a comma-separated list of dependent names added under this member’s household. Use it only when your file has no row per child, because names alone give the children no date of birth or gender.

How duplicates are handled

Members are matched by email within your organization. If a row’s email already exists:
  • The existing member is reused, not recreated.
  • The charge, wallet credit, notes, tags, and custom fields on that row are skipped, so re-running an import does not double-charge or double-note anyone. This also means an import cannot add tags to members who are already in your organization - tag those from their profile instead.
  • A membership or dependents on that row are still attached to the existing member. This is how you deliberately import several rows for the same member (one per membership) or add family members to an existing account.
Memberships themselves are de-duplicated by member, plan, and start date, so the same membership row imported twice is not duplicated.

Worked example: migrating from a legacy system

Suppose a padel and tennis club is moving off an old spreadsheet-based system and exports a members file, members.csv, with columns like Full Name, Email, Mobile, Join Date, Plan, Membership Start, Total Sessions, Sessions Used, and Kids.
  1. Go to Settings > Data Tools > Import.
  2. Drop members.csv into the AI-powered import card. The analyzer detects Members (Contacts) and proposes a mapping such as "Full Name" -> name, "Mobile" -> phone, "Join Date" -> createdAt, "Plan" -> planName, "Membership Start" -> membershipStartDate, "Total Sessions" -> membershipMaxUses, "Sessions Used" -> membershipUsed, and "Kids" -> dependent.
  3. Confirm and continue to the Preview. Two rows are flagged: one has Join Date as 31/13/2023 (an impossible date) and one is missing an email. The counts read 48 valid, 2 invalid.
  4. Download the invalid rows, fix the date and add the missing email in your source, and re-upload. The preview now reads 50 valid, 0 invalid.
  5. Execute. Because these rows carry a plan and a start date, each member is created together with a session-based membership, and any names in the Kids column are added as household dependents under the parent. Session usage imports so remaining sessions are correct from day one.
Because members were matched by email, running the same file again would reuse every member rather than creating duplicates, and would only add memberships or dependents that were not already there.

Other vertical examples

  • Martial arts gym - import a plans.csv first (belt-progression memberships with maxUses per grading block), then a members file that references those plans by planName so each student lands on the right package.
  • Pilates and yoga studio - import class-pack memberships with membershipBillingFrequency set to one_time and membershipMaxUses for the pack size, so class credits carry over.
  • Climbing gym - import transactions.csv of past day-pass sales keyed by contactEmail, leaving paymentStatus blank so they default to paid in your organization currency.

Tips and best practices

  • Let the AI analyzer go first. It maps most legacy exports correctly, and you can still override the record type manually.
  • Import in dependency order (members, accounts, plans, memberships, classes, bookings, invoices) so references resolve.
  • Set up clubs, areas, and instructors before importing classes and bookings, which reference them by name or email.
  • Use the preview as a linter. Download the invalid rows, fix them in your source file, and re-upload rather than editing inside 1club.
  • Re-running is safe for members. Email matching means a second run reuses members and only adds missing memberships or dependents.
  • For member imports, prefix custom columns with custom_ so they map to contact custom fields automatically.
  • Tag the batch as you import it. Add a tags column with the same value on every row (for example the source or campaign the list came from) so you can filter and message that group afterwards. Tags only apply to members the import creates, so do this on the first run.

Troubleshooting

Data export

Export your records back out to CSV.

Members overview

Contacts, custom fields, and how imported members behave.

Memberships

The membership catalog and checkout that chained imports create against.

Plans

Plans that membership imports reference by name.