Four things decide it: data export quality, whether stored cards transfer, what your exit clause costs, and whether the new platform discloses its payment margin in writing.
What Actually Decides Whether You Should Switch
Take them in that order, because the first two can kill the move before pricing matters at all. Data export is the first veto. Ask what fields you get, in writing, before you sign anything with a new vendor. Client names, emails, and a sales history are the easy part. The hard part is contract terms, remaining package balances, visit history, membership start dates, and any freeze or hold status. If those don’t come out in a structured file, someone on your staff rebuilds them by hand from screenshots, and every unclaimed class credit you miss is a refund conversation later.
Stored payment credentials are the second veto, and they’re the one most owners discover during cutover week. A card on file inside a platform’s own payment processing isn’t sitting in your account waiting to be downloaded. That’s a negotiation between two payment companies, not a setting in your software. Either both sides agree to do it or your members re-enter their cards, and a re-entry campaign always loses some percentage of your recurring base.
Only then does money enter the picture, and the monthly software fee is the least interesting number on the page. A studio running a meaningful monthly card volume can pay more in undisclosed processing margin than in subscription fees.
The five sections that follow work through each of these in sequence, with the specific questions to put in writing before you commit.
Get Your Data Out Before You Shop
Pull a full export before you talk to a single sales rep. You’ll evaluate demos better when you know what you actually hold, and you’ll find out early which records live somewhere you can’t reach without asking support.
| Record type | Usual export path | What breaks if it’s missing |
|---|---|---|
| Clients and contact details | Self-serve CSV | Nothing, if emails and phone formats survive the import |
| Membership terms and start dates | Self-serve, often without the original contract text | Renewal dates and price locks reset; you rebill people wrong |
| Class-pack and series balances | Partial; expiration dates often drop | Members show zero credits and stop trusting the new system |
| Visit and attendance history | Self-serve, sometimes date-limited | Retention reporting starts from zero; instructor pay disputes |
| Sales and payment history | Self-serve for transactions; card tokens never transfer to you | Refunds, chargeback evidence, and year-end reconciliation |
| Signed waivers and agreements | Support request; often per-document, not bulk | An unwaived member on day one |
| Staff schedules and pay rules | Partial; pay formulas usually rebuilt by hand | First payroll run after cutover |
| Marketing consent status and timestamps | Support request in many cases | You inherit the obligation without the proof |
Two rows deserve a calendar entry. Waivers and consent timestamps are the ones that require a human on the other end, so request them in writing, date-stamp the request, and keep the reply. Do it while billing is still active. (16 CFR 425.1)
The Payments Question Nobody Asks Until Cutover Week
Your software choice also decides whether you are moving card processing or just changing the front end. Some platforms bundle their own processor. Others let you bring one. With bundled processing, the migration is also a processor change, so stored cards and autopay credentials become the risk item, not the class calendar.
Ask the new provider whether it supports a vault migration from your current processor, who initiates the transfer, what approval your current processor requires, how long the handoff usually runs, and what happens to members whose tokens do not land in the new vault. You need the fallback before cutover: a retry plan, a card-update page, and member outreach that points to the right form the first time. Keep your renewal terms and cancellation terms attached to that re-entry flow, because material terms in an auto-renewing negative option plan must be disclosed clearly and conspicuously. (16 CFR 425.1)
Don’t assume token services travel with the cards. Ask whether the destination vault will be enrolled for network tokens and Account Updater, who handles that enrollment after cutover, and how retries are managed while that setup is completed. If that work lags, month-one autopays turn into avoidable declines and front-desk cleanup. Our explainer on Account Updater and Network Tokens: Keeping Member Autopays Alive When Cards Expire shows why that sequence matters.
Then price the whole stack. Ask for interchange-plus, with the processor’s margin stated in basis points and cents per transaction, and use the effective rate on your last three statements as the baseline to beat. Separate software fees from processing fees, and separate processor fees from card-network fees. Every fee has a name and a source. If you can’t get both in writing, keep shopping. Confirm whether next-day funding is included or priced, and ask for the batch cut-off time in your time zone, because that is what decides when today’s dues become tomorrow’s deposit.
Before you add a surcharge or convenience fee to recurring dues, read Can Studios Surcharge Recurring Membership Payments? Card Rules, State Laws, and Disclosure Requirements. (16 CFR 425.1)
Read the Exit Clause of the Contract You’re Signing
You just spent weeks prying your records out of one vendor. Don’t sign a contract that makes the next exit worse. Find the auto-renewal language first, then the notice window in front of it, then whether notice counts only if it’s in writing to a named address or legal department. An email to your account rep often doesn’t stop a renewal.
Then price the way out. Ask whether early termination is a flat fee or the remaining months of the term billed as a lump sum, and get the answer in the contract rather than a sales email. Ask whether your data export on exit is a right you hold, in what file format, and whether it’s billed as a service.
Two more things decide how tangled the exit gets:
- Whether payment processing is a separate agreement with its own term and end date.
- Whether price increases are capped annually or left open.
Hardware deserves the same read. A card reader lease can outlive the software cancellation, which is why Gym Equipment Financing: Lease, Loan, or Buy Outright matters here too. Buy the tablets outright when you can.
Compliance You Carry With You
Your obligations to members don’t reset when the software does. Under the FTC’s negative option rule, failing to clearly and conspicuously disclose the material terms of a plan is itself a deceptive practice (16 CFR 425.1), and prenotification plans carry their own requirements around what the subscriber is obligated to do (16 CFR Part 425). We cover the mechanics in Gym Membership Auto Renewal After Click-to-Cancel: What Studios Must Get Right in 2026.
See Health Club Membership Statutes: The State Rules Your Agreement Has to Follow before you approve the new template. If the platform reflows your agreement text, you’ve issued a new agreement, and it needs a lawyer’s eyes before launch.
Bring the consent timestamps across. Without them you can’t prove when a member agreed or when they canceled, and that proof is what wins a dispute.
A Cutover Sequence That Doesn’t Drop a Billing Cycle
Pick your cutover date the day after a billing run settles, not the day before one. Mid-cycle switches split a month’s revenue across two systems, and every proration argument that follows lands on your front desk.
- Export members, contracts, package balances, and payment history, and store a copy outside both platforms.
- Run the vault migration, then reconcile token counts and get a named list of every card that didn’t transfer.
- Bill a small test cohort and confirm the deposit before the full run.
- Email members whose cards failed to migrate a direct update link, before the charge attempt.
- Rebuild waivers and require a signature at each member’s next check-in.
- Reconcile the first full run line by line against the last run in the old system and chase every missing charge.
Done looks like two billing runs that match member for member, with the gaps explained rather than discovered.
Put the notice date and the billing-run date on one calendar this week, then ask your prospective platform who runs the vault migration and what their exception report looks like.
Frequently Asked Questions
Can I keep my members’ saved credit cards when I leave Mindbody?
Sometimes, but you never touch the card numbers yourself. Whether it’s possible in your case turns on which gateway sits behind your current payments and whether that gateway will release tokens to a competitor. If the answer is no, you’re collecting cards again, and you want that discovered while you still have leverage rather than in cutover week.
How long does a wellness center software migration usually take?
The calendar is set by four things: the number of active recurring agreements you have to rebuild, how many years of class and purchase history you insist on carrying over, whether your new payments account is underwritten and approved, and whether you plan to run one billing cycle in parallel before you shut the old system off. A single-location studio with a few dozen memberships and no interest in historical reporting moves faster than a multi-site center with corporate billing and prepaid packages. Book the go-live for a quiet week in your schedule, not the week a new term or session starts. Then add slack for the underwriting step, because that one isn’t yours to control.
Do I have to get members to re-sign waivers after switching software?
The waiver itself stays valid, because it’s an agreement between the member and your business rather than something your software owns. What often breaks is the proof: the timestamp, the document version, and the record of who clicked accept. Export the signed waiver records with their metadata before you leave, and if your new platform can’t store that evidence in a retrievable form, re-signature at next check-in is cheaper than an unprovable waiver. Treat recurring-billing authorizations as a separate record with its own retention rules, since automatic-renewal arrangements are governed by federal negative option requirements independent of any liability release (16 CFR 425.1).