Skip to content
People & access5 minute tutorial

Import a roster from another system

Review and import people from Mindbody, Zen Planner, Gymdesk, Kicksite or your own spreadsheet.

On this page
  1. Before you start
  2. 1. Mindbody
  3. 2. Zen Planner
  4. 3. Gymdesk
  5. 4. Kicksite
  6. 5. Another system or my own spreadsheet
  7. 6. Review and approve
  8. Troubleshooting

Available now

This workflow is available in the web product.

Before you start

  • An authorized roster CSV, up to 2 MB and 2,000 people. Managers stage and review; owners approve.
1

Mindbody

Open Client Directory and include the intended active and inactive clients. Exact controls can vary.

Export to Excel, then save the person worksheet as CSV in a spreadsheet app.

Check headers and scope before upload. Contact your vendor if your screen differs.

2

Zen Planner

Open reporting and find the report listing all students or people.

Include the intended statuses and contact fields, then export as CSV.

Some versions use New Report > All Students > Export. These exact labels are not verified in primary help. Contact your vendor if your screen differs.

3

Gymdesk

Open Settings > Members > Import / Export / Merge.

Export full customer data and save the CSV.

Review members, visitors and leads before importing. Contact your vendor if your screen differs.

4

Kicksite

Open the Student List or Prospect List.

Export one roster as CSV, with stable IDs, names and status or stage.

Review the scope and headers before upload.

5

Another system or my own spreadsheet

Save one person per CSV row.

Include a stable ID, first and last names (or Last, First), and status.

Map supported fields manually and review every person.

6

Review and approve

Saved cards and payment methods are not in these exports. Billing schedules, attendance history, signed documents, and family links do not transfer here. Link families separately. Importing people does not bill or email them. Program and rank text does not create enrollments or promotions. This preset recognises usual columns. Review the mappings and every person in the preview. Vendor names describe the file source and do not imply affiliation.

Open Settings > Data imports. Choose the source, upload a CSV, correct the mappings, and choose the numeric date order. Unknown statuses must be corrected before staging. Review every person before owner approval. Exact vendor headers remain unconfirmed.

Data imports →

Troubleshooting

If something looks wrong

What if a column is not recognised?

Map it to a supported field or choose Do not import. Leave guardian and relationship columns unmapped. Ask your vendor about export controls that differ.

Keep going

Reviewed July 27, 2026.