Switching Pilates Studio Software: Migration Checklist

Most pilates studio software migrations fail because of one overlooked phase: card-on-file transfer and pack balance reconciliation. Get those two right and the rest of the migration is routine. Get them wrong and you're dealing with client complaints, billing disputes, and churn for weeks after cutover.

Why Do Pilates Studios Switch Software?

The three most common triggers are pricing, complexity, and the moment Mindbody's ecosystem stops fitting a boutique operation.

Studios switch away from Mindbody most frequently when they hit the pricing tier increase that comes with feature expansion. Mindbody's pricing scales with transaction volume and feature set in a way that surprises studios in their second or third year. A studio paying $129/month at launch can find itself at $349/month once they add online booking, marketing tools, and advanced reporting.

Studios switch away from newer platforms (Arketa, Walla) when the platform's roadmap doesn't align with their operational needs — usually around membership complexity or instructor pay tracking.

The move to a new platform only makes sense if you've identified what specifically is broken and verified the new platform actually solves it. Switching software for a vague sense of "better" is expensive. Switching because your waitlist doesn't auto-promote and you're losing 8% of reformer capacity every week is a specific, fixable problem.

What Should You Export Before Starting a Migration?

Export everything before touching the new platform. This is non-negotiable.

The critical exports:

1. Complete client list — name, email, phone, emergency contact, any notes
2. Active pack balances — client name, pack type, credits remaining, expiry date
3. Active membership list — client, plan type, billing date, payment method on file, freeze status
4. Booking history — last 12 months minimum, for client re-engagement and LTV tracking
5. Instructor schedule — recurring class assignments, substitution history
6. Revenue reports — monthly revenue by product type, for year-over-year comparison

The 28-Point Migration Checklist

Phase 1: Pre-Migration (Days 1–7)

1. Export all data (client list, pack balances, membership list, booking history)
2. Document all class types with capacity, duration, and room assignment
3. Document all pack products with price, credit count, expiry, and eligible class types
4. Document all membership tiers with price, billing cycle, class allowance, and freeze rules
5. List all instructor profiles, pay rates, and recurring schedule assignments
6. Pull active waitlists — notify clients that the waitlist will be rebuilt on the new platform
7. Audit all cards on file — identify which clients have active auto-billing (memberships)
8. Set a migration date (minimum 2 weeks out)
9. Notify clients 10 days in advance via email — explain what changes, what stays the same, and what they need to do
10. Select your go-live date based on a low-activity day (not Monday)

Phase 2: Platform Configuration (Days 8–14)

11. Create all class types with correct capacity and duration
12. Build recurring class schedule for the next 8 weeks
13. Configure all pack products with expiry rules and class-type restrictions
14. Configure all membership tiers with billing rules and class allowances
15. Set cancellation and late-cancel policy rules
16. Configure waitlist auto-promote timing and notification channel (SMS preferred)
17. Set deposit requirements per service type
18. Import client list — verify names, emails, and phone numbers after import
19. Manually enter pack credit balances from your export spreadsheet
20. Create instructor profiles and assign to class schedule

Phase 3: Parallel Running (Days 15–18)

21. Run both platforms simultaneously — old platform in read mode, new platform for all new bookings
22. Process test transactions (pack purchase, membership sign-up, class booking, cancellation)
23. Verify waitlist promotion fires correctly on a test class
24. Audit auto-billing members — confirm new billing is set up before canceling old billing
25. Send reminder communication to clients 3 days before full cutover

Phase 4: Cutover (Days 19–21)

26. Cancel old platform auto-billing for all members (new billing already active)
27. Mark old platform as inactive — disable new bookings
28. Confirm all active packs and memberships are visible and accurate in the new system

How Do You Handle Card-on-File Migration?

This is the step most studios underestimate. Card data is encrypted at the payment processor level and cannot be exported as plain card numbers.

Your options depend on your new platform's payment processor:

Option 1: Client re-entry. Send a proactive email asking clients to add their payment method to the new platform before the cutover date. Offer a small incentive (a free class credit) for clients who add their card by a deadline. Expect 60–70% completion before cutover; plan for the remainder to add at their next visit.

Option 2: Stripe card migration. If both your old and new platform use Stripe as the payment processor, Stripe offers a card migration program. Contact your new platform's support team to initiate. This is not available on all platforms or in all regions.

Option 3: Reauthorization at next billing. For memberships, send a link to re-authorize the new recurring charge. Most clients will complete this without issue if the communication is clear about why.

The risk of doing nothing: clients with expired billing information won't be charged, their memberships lapse, and you lose the recurring revenue. For studios with 40+ active memberships, this is a material financial risk.

For more context on pilates software options, read pilates booking software features and see how the platforms compare.

What Client Communication Do You Send During Migration?

Three messages: advance notice, cutover reminder, and confirmation.

Message 1 (10 days before cutover): Subject: "We're upgrading our booking system — here's what changes" Tell clients the go-live date, what they need to do (re-add payment method, re-download the app if relevant), and what stays the same (class schedule, pricing, pack credits).

Message 2 (3 days before cutover): Subject: "Action needed: add your payment method by [date]" For clients with active memberships or packs. Include a direct link to the payment method page. Be specific.

Message 3 (day of cutover): Subject: "We're live — here's how to book on [New Platform]" Send a short tutorial (screenshot or GIF). Include a support contact for questions.

What Can Go Wrong and How Do You Prevent It?

The four most common migration failure modes:

Pack balance discrepancies. A client claims they had 7 credits; the import shows 5. Prevention: export and screenshot pack balances from the old platform the day before migration. Keep the old platform accessible for 30 days post-cutover for reference.

Membership billing gaps. Auto-billing canceled on the old platform but not set up on the new one, resulting in a month of uncharged memberships. Prevention: complete new billing setup before canceling old billing, audit every auto-billing member individually.

Class type mismatch. Packs that restricted to "Reformer Pilates" on the old platform now accept any class because the class type names were entered differently. Prevention: test one pack redemption per class type before go-live.

Instructor schedule errors. Recurring classes assigned to the wrong instructor, wrong room, or wrong time. Prevention: have your lead instructor review the schedule in the new platform before cutover.

For a full comparison of Zatrovo against Mindbody including migration support details, see Zatrovo vs Mindbody. The profitable pilates studio playbook covers the operational context for why these platform decisions matter at different stages of studio growth.