How to switch from Mindbody to a new studio software in 2026

If you're reading this, you've probably decided — or are close to deciding — to leave Mindbody. The decision is rarely impulsive; it usually follows a few specific events: the annual contract renewal landed with a price increase, the marketplace commission accumulated into a meaningful annual cost, support took two weeks to answer a question that should have taken an hour. This post is the step-by-step playbook for executing the switch in five to ten business days, written by the person building one of the operator-friendly alternatives.

The short version is in the Short answer callout at the top of this page. The long version, with the per-step detail and the constraints to watch, is below.

The six steps, in order

The migration follows a consistent shape regardless of which platform you're moving to. The variations are mostly in how the receiving platform handles imports and in the per-tool quirks of your destination.

Step 1: Pull the Mindbody export

From your Mindbody operator dashboard, go to Reports and pull the standard CSV exports for: client list with profile data, class booking history, active memberships with current period and pause status, class packs with credits remaining, intake forms (and completion status per client), email opt-in status, and (if you've been running the marketplace) marketplace-attributed booking flags.

Most studios get the full set of files in under thirty minutes. The standard exports are free. If you've heard about the four-hundred-pound complete-record export scenario — that applies when you request a deep historical archive that includes year-over-year intake form versions and detailed financial transaction logs. For a migration, the standard exports are sufficient.

If you're not sure which reports map to which data, your destination platform's migration team will walk you through the exact menu paths. The five tools most studios migrate to (Junocal, Momence, Mariana Tek, Walla, OfferingTree, Acuity) all have documented import flows from Mindbody.

Step 2: Send the export to the new platform

How this works depends on the platform. Operator-friendly platforms (Junocal, OfferingTree, Arketa) typically handle migrations directly through the founder or a small migration team — you upload the CSVs through a secure portal or email them to a dedicated migration address, and a person reviews the import before it goes anywhere.

Larger platforms (Momence, Walla, Mariana Tek) typically run their imports through partner consultants or an internal migration team. The handoff is similar: secure upload, dry-run review, sign-off.

The pattern that matters: a person should review your data before it goes into the production system. Automated imports without human review tend to surface edge cases at the worst time (the cutover weekend). The platforms that do this well always stage the import first.

Step 3: Dry-run the import into staging

The staging environment is where you verify the migration before it goes live. Most operator-friendly platforms run the import into a sandbox version of your studio first, with the production environment untouched. You log in, look at the data, and sign off on anything that looks wrong.

Specific things to verify in the dry-run:

• Client list. Counts match. Profile fields look right. No duplicate clients from a CSV-parsing edge case.
• Active memberships. Each member's current period start and end date is correct. Pause status (if anyone is on pause) carries across with the resume date.
• Class pack credits. The credits remaining match what Mindbody shows today.
• Intake forms. Completed-status flags carry across. Forms tied to specific services are still tied to those services.
• Email opt-in. Critical. Spot-check ten clients who are confirmed unsubscribed in Mindbody — they should be unsubscribed on the new platform. Spot-check ten confirmed opted-in clients — they should be opted-in.
• Booking history. Spot-check the last few weeks of bookings. Counts match. Attendance status (attended, no-show, late cancel) carries across.

This is the most consequential step in the whole migration. Most studios spend two to four hours on the dry-run review. Take your time.

Step 4: Configure the new platform

Independent of the data migration, you'll set up the new platform's configuration: studio branding (logo, colours, photos), class types and their per-service rules (price, capacity, cancellation policy, intake form, pick-a-spot toggle), instructor accounts and access permissions, the booking page theme and copy.

This can happen in parallel with the dry-run review. Most studios do this in evenings during the migration week.

Step 5: Pick a Sunday and cut over

The cutover is when the new platform goes live for new bookings. Most studios pick a Sunday evening because:

• The schedule for Monday morning is already set
• New bookings overnight are minimal
• The studio has time to verify everything is working before Monday-morning classes
• If something needs a fix, there's a few hours before clients arrive

The cutover itself is typically two to four hours of coordination. The new platform's migration team runs a final data sync (to capture any bookings or membership changes between Step 3 and now), updates the public booking-page URL, and switches the routing. Your old Mindbody booking page either redirects to the new page or shows a "we've moved" message.

For platforms that support custom-domain mapping, the URL change can be invisible to clients. For platforms that don't (or for switches where you accept the new URL), set up a redirect from the old domain and send a cutover email to clients.

Step 6: Run a few classes, then cancel Mindbody

The post-cutover week is verification. Run your Monday-morning classes on the new platform. Check that the staff PWA shows the right rosters. Confirm Stripe is processing payments correctly and payouts hit your account on schedule. Watch for any client confusion in the support inbox.

Most studios cancel their Mindbody subscription at the end of the current Mindbody billing period — not immediately at cutover. This gives a buffer in case something needs to be re-imported. Mindbody continues to be accessible (in read-only mode for most studios) for the remainder of the paid period.

If you were inside an annual contract, the cancellation either: triggers the early-termination buyout (if you chose that path), or just non-renews at the end of the term (if you timed the cutover to the contract end).

The constraints to watch

Five things commonly trip up Mindbody-to-new-platform migrations.

The annual contract timing

Mindbody's standard contract runs twelve to twenty-four months with auto-renewal. The auto-renewal window is typically thirty to sixty days before the term ends. If you miss the window, you're locked in for another year.

The defensive pattern: set a calendar reminder one hundred and twenty days before your Mindbody contract end date. That gives you sixty days to evaluate alternatives, run a trial, and complete the migration before the renewal window closes. If you're starting your evaluation inside the renewal window (last sixty days), you can still migrate, but you may need the early-termination buyout to avoid the auto-renewal.

The marketplace listing

You can keep the Mindbody marketplace listing running while your operations move to the new platform. The twenty-percent commission on app-discovered bookings continues to apply to those bookings; bookings made directly on the new platform's branded booking page carry no commission.

Most studios drop the marketplace listing after sixty to ninety days. UK studios tend to drop it faster because marketplace penetration is lower in the UK and the commission isn't compensating for meaningful new-client discovery. US studios in dense urban markets sometimes keep it longer.

The decision is yours. The commission keeps applying as long as the listing is up.

The Stripe handover

If Mindbody is currently processing your payments through Mindbody-branded processing (rather than direct-to-Stripe), the handover to a Stripe Connect Standard platform involves connecting your Stripe account to the new platform via OAuth. If you don't already have a Stripe account, you create one through Stripe-hosted onboarding (typically ten to twenty minutes if you have your business details ready).

From the cutover date, new charges flow through your Stripe account directly. Mindbody continues to handle residual charges (refunds for prior bookings, dispute responses for older transactions) until those cycle out, which is typically a few weeks.

Your new Stripe relationship starts fresh in terms of risk score, dispute history, and lender visibility. For most studios this is fine — Stripe's onboarding is well-calibrated for new merchants. If you were depending on a long Stripe history for Stripe Capital eligibility or other financing, you may want to plan around that.

Email opt-in status

This is the field most often lost in migrations. If your destination platform doesn't carry opt-in status across, your post-migration mailing list resets to zero opted-in clients, and you have to re-collect consent from each one before you can resume marketing email. For a studio with two thousand active clients, that's a months-long project.

Before signing with a new platform, ask explicitly: does opt-in status migrate from Mindbody as a first-class field? Get the answer in writing. The platforms that do this well make it a default; the platforms that don't tend to lose it through an "edge case" in the import.

The dry-run review (Step 3 above) is when to verify this. Spot-check at least ten unsubscribed clients and ten opted-in clients to confirm the status transfers.

The on-demand video library (if you have one)

If you've built an on-demand video library on Mindbody, the migration is more involved. Mindbody hosts video natively, and the binary files may or may not be retrievable through the export. Studios with meaningful video libraries (twenty or more videos) typically need to either re-upload to Vimeo, YouTube, or Uscreen during the transition, or move to a platform that handles video natively (Momence has the strongest native video product).

If video is twenty percent or more of your revenue, the migration plan needs to address video specifically before you commit to a destination platform.

How long the whole thing actually takes

Most one-to-five-instructor studios complete the switch in five to ten business days, measured from the day you pull the first Mindbody export to the day Monday-morning classes run on the new platform. The variance is mostly in the dry-run review (how thorough you want to be) and the cutover scheduling (which Sunday works for your studio).

The work distribution across that timeline:

• Day 1: Export pull, send to destination platform. (Half day of your time.)
• Days 2-3: Staging import + dry-run review. (Two to four hours of your time; most of the work is on the platform's side.)
• Days 3-5: Studio configuration (branding, services, intake forms, instructor accounts). (Spread across evenings; total maybe four to six hours.)
• Day 6 (Sunday): Cutover. (Two to four hours of coordination.)
• Days 7-10: Monday-morning verification, watching for issues, cancelling Mindbody at billing-period end. (Maybe two hours total.)

Total operator time: roughly twelve to twenty hours over a ten-day window. Not bad for a structural decision that pays back in lower monthly cost and a better operator experience for years.

The decision points before you start

Before you pull the Mindbody export, two decisions matter.

First, which platform are you migrating to? The five with automated Mindbody migration importers are typically Junocal, Momence, Mariana Tek, Walla, and OfferingTree. The right one depends on your studio shape — see Best Mindbody alternative for pilates studios for the comparison logic, or the individual comparison pages (vs Mindbody, vs Momence, vs Mariana Tek, vs Walla).

Second, what's your timing relative to your Mindbody contract? Are you inside the auto-renewal window? Inside the last six months of the term? Mid-contract with a year to go? The contract timing shapes whether you parallel-run, buy out, or wait — and it shifts the migration calendar.

Both of those decisions take an evening or two with a notepad. Once they're settled, the migration is mostly execution.

If you want to walk through the specifics of your studio and your contract situation, 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 20% marketplace commission problem, and the /migrate page with the per-source-tool playbook.