Switching Dance Studio Software Without Losing Enrollment History

Dance studios switching software mid-season risk tuition billing gaps that take weeks to untangle — the order of migration steps matters more than the timeline. The studios that migrate cleanly do three things: export everything before canceling, run billing in parallel for one cycle, and notify families twice before go-live.

Why Do Dance Studios Switch Software?

The three most common triggers are pricing, billing flexibility, and class management depth.

Jackrabbit Dance and Mindbody are the dominant platforms in the dance studio market. Both have real strengths — Jackrabbit's dance-specific enrollment management and Mindbody's brand recognition. Both also have pricing structures that escalate with studio size and feature add-ons that turn a $100/month plan into a $250/month reality.

Studios switch when that pricing stops making sense, when they need a feature the platform doesn't support natively, or when the operational friction of workarounds becomes unsustainable.

What Data Must You Export Before Migrating?

Seven categories. Export all of them before canceling your current subscription.

Student records. Name, contact info, emergency contacts, enrollment date, class assignments, and any medical notes or performance flags. This is the irreplaceable core of your student database.

Transaction history. Every payment, pack purchase, tuition charge, and refund for at least the last 24 months. Needed for dispute resolution and financial reporting.

Class attendance logs. Per-student attendance records. Needed for milestone tracking, loyalty programs, and any attendance-based billing models.

Pack balances. Outstanding class credits for every student. These are liabilities on your balance sheet — a student with 6 remaining classes on a 10-pack is owed those classes regardless of which platform you're on.

Recurring billing details. Every active subscription, charge amount, billing date, and payment method token. Note: payment tokens don't transfer between processors. Families with saved cards will need to re-enter payment info in the new system.

Enrollment contracts and terms. Any signed agreements, photo release forms, or policy acknowledgments. Export as PDF or CSV depending on what your current platform supports.

Communication history. Email logs and notes from parent interactions. Not always available for export, but worth checking.

What Is the Correct Migration Sequence?

The 6-Step Dance Studio Migration Sequence:

Step 1: Build the new system. Configure class types, schedules, room capacities, tuition structures, and pack products in the new platform. Do not touch billing yet.

Step 2: Import student records. Upload your exported CSV. Verify that names, contact info, enrollment dates, and class assignments all import correctly. Spot-check 10% of records manually.

Step 3: Notify families. Send the 2-week advance notice explaining the switch, what changes, and what families need to do.

Step 4: Set up recurring billing in the new system. Configure recurring tuition charges for every active family. Do not process any charges yet.

Step 5: Parallel run. For one full billing cycle, both systems are live. Process the billing cycle in the old system as normal. Verify the new system would have produced identical charges. Resolve any discrepancies.

Step 6: Cut over. Process the next billing cycle only in the new system. Cancel recurring billing in the old system. Send go-live confirmation to families.

How Do You Handle Recurring Tuition During the Switch?

Recurring tuition is the highest-stakes element of the migration. A billing gap — where a family doesn't get charged when they should — erodes trust immediately. A double charge is worse.

The safest approach: confirm every active recurring billing record in the new system before processing a single charge. Run a test batch of $0.01 charges to verify processor connectivity if your platform supports it. Then process your first real cycle.

Families whose saved payment methods don't transfer will need to re-enter card details. This is unavoidable when switching payment processors. Send a targeted email to that subset of families specifically — not a generic blast — explaining exactly what they need to do and by when.

What About Enrollment History and Student Records?

Enrollment history is not just sentimental data — it drives milestone recognition, loyalty program triggers, and any attendance-based policy enforcement.

When importing to a new platform, flag students by enrollment start date in addition to their current class schedule. Many platforms will show a student's "joined date" based on when they were created in the system — which will be your migration date, not their actual enrollment date. Override this manually during import or add a custom field for "original enrollment date."

For the dance studio loyalty program milestones to function correctly, you need the actual enrollment date, not the platform-creation date.

How Do You Keep Families Confident During the Switch?

Communication is the primary trust lever. Three messages:

Message 1 (2 weeks out): "We're switching to a new studio management platform. Here's why and what's changing for you." Focus on benefits — better booking experience, improved app, clearer billing statements. Don't apologize for switching.

Message 2 (3 days out): "Here's what you need to do before [go-live date]." Specific actions: create your account, download the app, verify your payment method. Include a link and a deadline.

Message 3 (go-live): "We're live on the new system. Here's how to book your next class." Brief, practical, positive.

Any family who doesn't complete the required action by go-live gets a personal follow-up from staff — not another automated email.

For related context on building the broader operational structure around your software, see the dance studio operations playbook. For membership and pricing structure decisions that affect how you configure the new platform, see the dance studio membership pricing guide.

How Long Does Staff Training Take?

Plan for two weeks of supervised operation, not a one-day training session.

Core functions — class check-in, enrollment, billing inquiry — take 2–3 hours to learn. Advanced functions — reporting, pack management, communications — take another 2–3 hours. After that, real-world use reveals the questions that classroom training doesn't.

The most effective training structure: one structured walkthrough of core functions, then supervised live use for two weeks with a senior staff member available to answer questions in real time. Do not train on a Friday before a Monday go-live.