How to export your client list from Mindbody

If you've decided to leave Mindbody — or you're just doing the due diligence work of confirming that you can leave when you decide to — this is the step-by-step guide to pulling your data out as a clean set of CSVs. Total time: roughly twenty to thirty minutes for the full set of exports. The work is well-documented inside Mindbody and the exports are free. The only constraints worth knowing are which fields export cleanly, which ones don't, and where to verify each.

The short version is in the Short answer callout at the top of this page. The long version, with the per-report detail and the field-by-field notes, is below.

The full export set, in order

A complete Mindbody export for migration purposes is five separate reports plus your storefront/branding configuration. They all live under the Reports section of your operator dashboard, though some versions of Mindbody place them under slightly different menu names.

1. Client list

Menu path: Reports → Client List.

Filters to set: All Clients (active and inactive). Date range: All Time. Status: All. Most studios pull both active and inactive because clients sometimes reactivate, and you want a complete record on the new platform.

Fields included by default: first name, last name, email, phone, address (where collected), gender (where collected), date of birth (where collected), client ID (Mindbody's internal identifier), status (active / inactive / etc.), sign-up date, last visit date, email opt-in status, SMS opt-in status, the values of any custom fields you've configured.

Action: Click Export to CSV. The file downloads as Client_List_[date].csv. For a studio with two thousand active and inactive clients, the file is typically two to three megabytes.

Time: Roughly five minutes including filter setup.

2. Class booking history

Menu path: Reports → Class History (or Sales → Class History in some versions).

Filters to set: Date range: All Time (or the longest available range your Mindbody version exposes, which is typically the last two to three years). All instructors. All class types.

Fields included: booking ID, class name, instructor name, class date and time, client name, client ID (matches the client-list export), attendance status (attended, no-show, late cancel), booking source (direct, marketplace, app), payment status, price charged.

Action: Click Export. For a studio with two or three years of bookings, the export is a few hundred thousand rows and downloads as a ZIP containing one or more CSV files (Mindbody splits large exports across multiple files).

Time: Five to ten minutes depending on the studio's history depth.

3. Active memberships

Menu path: Reports → Membership Sales (or Membership Roster in some versions).

Filters to set: Status: Active. (Or Active + Paused if you want to include paused memberships, which most studios should for a migration.) Date range: All Time.

Fields included: membership type, client name, client ID, current period start date, current period end date, pause status, pause resume date (if paused), renewal type (auto-renew, manual), price, payment frequency, payment method on file.

Action: Export to CSV. Typically a smaller file — a couple of hundred rows for most studios.

Time: Two to three minutes.

4. Pricing options / class packs

Menu path: Reports → Pricing Option Sales (or Pack Sales — Mindbody's naming varies by version).

Filters to set: Status: Active (i.e., packs with credits remaining or not yet expired). Date range: All Time.

Fields included: pricing option type (drop-in, four-pack, ten-pack, etc.), client name, client ID, credits purchased, credits remaining, expiry date, price paid, purchase date.

Action: Export to CSV.

Time: Two to three minutes.

5. Intake forms

Menu path: Reports → Forms (or Settings → Forms in some versions).

Filters to set: All forms. All clients.

Fields included: form name, client name, client ID, completion status, completion date.

Note: The export typically gives you the form template (the questions, in a separate Settings export) and the completion log per client (who has filled out which form and when). The actual answer values may or may not export — this depends on how the form was configured. For most migrations, what matters is the completion status per client (so the new platform knows which clients have a current intake on file).

Action: Export to CSV.

Time: Five minutes.

6. Storefront configuration

This isn't technically an export — your storefront branding (logo, colours, photos, about copy, social links) doesn't come out as a CSV. But you'll want a record of the configuration before you start setting up the new platform.

Action: Take screenshots of your current storefront pages. Save your logo and any custom photos. Note your brand colours (hex codes if you have them, otherwise eyeball them from screenshots). Save any copy you've written for the studio description, the class descriptions, and the about page.

Time: Ten to fifteen minutes if you want to be thorough.

What's in each field — the migration-critical notes

A few fields deserve extra attention because they're the ones that commonly trip up migrations.

Email opt-in status

The standard client-list export captures the email subscription status field correctly. The risk is on the receiving side: not all destination platforms preserve the field through the import. Some platforms have an "edge case" in their importer that marks all clients as unsubscribed on entry — which means your post-migration mailing list resets to zero opted-in clients, and you have to re-collect consent from each one.

Before sending your export to a new platform, ask explicitly: does opt-in status carry across as a first-class part of the import? Get it in writing. The dry-run review on the receiving platform is when to verify. Spot-check at least ten clients confirmed unsubscribed in Mindbody — they should be unsubscribed on the new platform. Spot-check ten confirmed opted-in clients — they should be opted-in.

Client ID matching across exports

The client ID is the field that links the booking history, the memberships, and the packs to specific clients. The destination platform's importer uses this ID to associate the records correctly. If the IDs in one export don't match the IDs in another, the migration breaks at staging.

The standard Mindbody exports use a consistent client ID across all reports, so this usually isn't an issue. If you've ever merged duplicate client records in Mindbody, the surviving record's ID is what's in the exports — the deleted IDs are gone. This is normally what you want, but worth verifying in the dry-run.

Booking attendance status

The attendance status (attended, no-show, late cancel) in the booking-history export is what the new platform uses to calculate per-client retention, attendance rates, and no-show patterns. If your Mindbody configuration was using non-standard status values (some studios customise this), the migration may need a mapping step. The dry-run will surface this.

Membership pause status

For any member currently on pause, the export should include both the pause-start date and the auto-resume date. If only one of these is in the export, the new platform may resume the membership immediately at the migration date rather than honouring the original resume date. Verify by spot-checking a few currently-paused members in the dry-run.

Custom field migration

If you've configured custom client fields in Mindbody (anything beyond the standard name / email / phone), those fields export but the receiving platform may or may not have a slot for them. Operator-friendly platforms typically let you map custom fields to custom-field slots in the new platform. Larger platforms sometimes flatten or drop them. The dry-run review is when to verify the custom-field mapping.

What doesn't export

A few things don't come out cleanly in the standard exports.

On-demand video library content. If you've built a video library on Mindbody, the binary files are hosted by Mindbody and don't export with the CSV. You'd need to download each video manually through the Mindbody admin UI, or re-upload to Vimeo, YouTube, or Uscreen during the migration. For studios with a meaningful video library, this is the migration step that takes the longest.

Custom reports and dashboards. Any analytics or reporting configurations you've built in Mindbody live in the Mindbody UI and don't export as code. You rebuild equivalent reports on the new platform.

Marketplace-attribution rules. The marketplace-attributed booking flags export as part of the booking history (you can see which bookings were attributed to the marketplace), but the rules Mindbody uses for attributing bookings over time (the attribution window, the rules for renewing attribution on returning clients) are platform-specific and don't migrate. The new platform either has no marketplace (operator-friendly platforms) or has its own attribution model.

Stripe Capital eligibility / lender history. Your Stripe history stays with your Stripe account, but if it was a Mindbody-mediated Stripe relationship (i.e., Mindbody was the merchant of record), you don't have your own Stripe history. The new platform will use Stripe Connect Standard if it's operator-friendly, which means you create or activate your own Stripe account — and that account starts fresh in terms of risk score and lender visibility.

After the export

Once you have the five CSV files (plus your storefront configuration), the export is done. The next step is the import on the receiving platform's side — typically a secure upload, a staging review, and a sign-off before the data goes into the production system.

The full migration playbook is in How to switch from Mindbody to a new studio software in 2026, which covers the six-step process end-to-end. The export described above is Step 1.

If you're running the export to confirm you can leave Mindbody before you commit to switching, you can stop after the export — keep the files in a safe location and you have a backup of your studio's data independent of any platform. Studios that want a regular off-platform backup of their data run this export quarterly.

If you have questions about a specific quirk in your Mindbody configuration or how it'll map to a new platform, hello@junocal.com gets a real reply from a real person, usually within a few hours. Related reading: the annual contract trap in studio software, the /migrate page with the tool-by-tool playbook, and the broader Best Mindbody alternative for pilates studios buyer's-guide comparison.