How to export your client list from Mindbody

Exporting a client list is only the first part of a migration. A studio also has future commitments, balances, consent records and financial history that must be accounted for separately.

Mindbody account versions and permissions differ. Use the labels visible in your dashboard and the official Subscriber Data Export guidance rather than relying on a screenshot or menu path from another studio.

Step 1: define the required data

Create a migration inventory before downloading anything:

• client identity and contact details;
• communication and marketing preferences;
• future classes, appointments and courses;
• attendance and cancellation history needed operationally;
• active packs, remaining credits and expiry dates;
• memberships, status, renewal dates and pauses;
• forms, waivers and responses that must be retained;
• financial, tax, refund and dispute records;
• notes or clinical records with separate retention obligations;
• recurring payment methods and mandates.

The destination may not support every source object. Mark each item as import, archive, rebuild, re-authorise or not required.

Step 2: export the client report available to your account

Use an authorised owner or staff login and locate the client or customer reporting area. Select the complete population required for migration, including inactive records where they must be retained. Export in the format the account offers, commonly CSV.

Do not promise that the file always contains a fixed list of fields. Open it and record:

• row count;
• headers and definitions;
• date and timezone formats;
• stable client identifier;
• blank, duplicated and malformed values;
• encoding and delimiter;
• consent-related columns and provenance.

Keep an untouched original and work on a copy.

Step 3: export operational records separately

A client list usually cannot encode the studio's entire operational state. Pull the available reports for future bookings, attendance, pricing options, memberships, forms and transactions. Use the stable client identifier to link them where possible.

If the dashboard reports do not contain required history or fields, use Mindbody's official Subscriber Data Export process and ask support what the account can receive. Confirm scope, format, timing and any cost in writing.

Step 4: treat consent as evidence, not a checkbox

An email-related field may mean marketing consent, transactional-email eligibility, an account setting or a legacy status. Do not relabel it without understanding the source definition.

For UK and EU contacts, the migration should preserve the lawful basis and evidence the studio relies on. Unknown or missing status must not be converted to subscribed. Keep suppression and unsubscribe records.

Step 5: separate records from payment authority

Customer names, membership status and transaction history can appear in data files. Reusable card credentials and bank-debit mandates cannot be safely exported as ordinary CSV values.

Ask both payment providers:

1. Which account owns the customer and payment method?
2. Can the destination connect to that same account?
3. Can existing mandates be reused under the original authorization?
4. Which clients must re-enter payment details?

Do not schedule recurring billing until this is resolved.

Step 6: dry-run and reconcile

Import a representative sample into a safe destination environment. Check:

• client count and deduplication;
• future booking count by date and service;
• pack balances and expiries;
• membership states and next billing dates;
• consent and suppression values;
• required archived records;
• records rejected by validation.

Produce a reconciliation table and have the operator sign it off. A successful file upload is not proof of a complete migration.

Step 7: secure and retain the files

Exports may contain personal, health and financial information. Use an approved encrypted transfer, restrict staff access, record recipients and delete working copies according to the studio's retention policy. Do not email unencrypted exports casually.

What Junocal can and cannot promise

Junocal can review the files available to the studio and explain which current destination fields can be mapped. It cannot guarantee that Mindbody exposes every desired field, that clinical records become Junocal objects or that payment mandates transfer. Junocal is not an EHR or HIPAA product.

Bottom line

Export the client list, but plan the migration around all operational records. Verify the actual columns, preserve consent evidence, use the official export-request process when needed, reconcile a dry run and treat recurring payment authority as a separate workstream.