How to switch from Mindbody to new studio software in 2026

A migration is successful when the studio can prove that future obligations, balances, consent and required history are correct in the destination. Going live quickly is secondary.

Junocal is one possible destination and this is Junocal's blog. The same controls apply whichever platform you choose.

1. Read the commercial terms

Collect the signed order form, current Mindbody terms, merchant agreement and any marketplace agreement. Record:

• subscription and add-ons;
• current term and renewal date;
• cancellation notice and approved method;
• promotion expiry;
• payment and marketplace terms;
• data access after cancellation;
• any stated export process or charge.

Mindbody's website terms provide defaults but allow other agreements to set applicable terms. Do not assume a universal annual contract, buyout percentage or notice period.

2. Define migration scope

Inventory:

• clients and contact preferences;
• future bookings, courses and events;
• attendance history required for operations or retention;
• class packs, credits and expiry dates;
• memberships, pauses and next billing dates;
• forms, waivers and responses;
• financial, tax, refund and dispute records;
• staff, rooms, locations and service catalogue;
• payment methods and mandates.

Classify each item as import, archive, rebuild, re-authorise or not required. The destination may not support an equivalent object.

3. Export from Mindbody

Use the reports visible to an authorised account owner. Keep untouched originals. If available reports do not cover the required data, follow Mindbody's official Subscriber Data Export guidance and ask support to confirm scope, format, timing and any fee.

Avoid fixed claims that a standard export is always free, complete or available in 30 minutes. Accounts and requests differ.

4. Map and clean

Build a field map from source to destination. Preserve stable identifiers and distinguish unknown values from false values. Particular care is needed for:

• communication and marketing consent;
• timezones and date formats;
• duplicate clients;
• pack balances and expiries;
• membership pause and renewal status;
• sensitive form data;
• historical notes with separate retention rules.

Do not convert clinical history into a generic booking note simply because the destination has no clinical record model.

5. Dry-run the import

Use a representative sample, then a complete rehearsal. Reconcile source and destination counts for clients, future bookings, active products and balances. Document rejected rows and manual changes.

The operator should approve a reconciliation report before the final sync.

6. Test real workflows

Test at least:

1. a new client purchase and booking;
2. pack and membership redemption;
3. cancellation and fee or credit outcome;
4. waitlist promotion;
5. form request and completion;
6. refund;
7. failed payment;
8. staff check-in and reporting.

If the destination is Junocal, also account for current gaps: private appointments are capacity one, charged in full and cannot redeem class-pack or membership credits; partial deposits and recurring appointment series are unavailable.

7. Plan payment re-authorisation

A CSV does not carry reusable payment credentials. Ask whether the same processor account can connect to the destination and whether existing customer objects and mandates can be used under their original authorization.

Segment members who need a new payment method. Do not assume a Stripe-to-Stripe, bundled-to-Stripe or Direct Debit transfer is automatic.

8. Communicate and cut over

After reconciliation passes:

• freeze configuration changes for the final export window;
• send clients the new booking link and action required;
• perform the final sync;
• verify the next live sessions and renewals;
• keep a rollback or manual attendance plan;
• redirect only domains the studio controls.

There is no rule that cutover must happen on Sunday or that Monday classes will be unaffected. Choose the lowest-risk operating window.

9. Preserve and close

Retain required financial, consent, form and clinical records securely. Confirm how historical access works after cancellation. Delete temporary migration copies according to the studio's retention policy.

Cancel only through the method required by the applicable agreement and keep proof.

Bottom line

The reliable migration sequence is contract review, inventory, export, mapping, dry run, reconciliation, workflow testing, payment planning, communication and controlled closure. Set the date from evidence in the actual account—not a generic five-day promise.