When you switch school management software, your core records (students, families, teachers, and schedules) can usually be moved to the new system, but billing details, payment methods, and communication history each need a specific plan. A good migration is planned around those details, timed outside your busiest season, and tested before families ever see the change.
For a growing school, the fear of switching is reasonable. Your current system holds years of student records, family relationships, recurring lessons, balances, and makeup credits. It holds the trust of hundreds of families who expect their lesson to be on the calendar next week and their card to be charged correctly. Losing or scrambling any of it isn’t an inconvenience. It’s a retention problem.
That fear keeps a lot of schools on software they’ve outgrown. The schools that switch successfully aren’t the ones with the least data. They’re the ones that know exactly what’s moving, what needs attention, and who’s responsible at each step. This guide walks through all three.
What Moves, What Needs Care, and What Usually Stays Behind
Not all data migrates the same way. Most systems can export core records cleanly, while anything tied to money or to a specific vendor’s tools takes more planning. Here’s how the main categories typically break down.
| Data | What usually happens | What to check |
|---|---|---|
| Students, families, and contacts | Exports cleanly as a spreadsheet and imports into the new system | Family links (siblings, split households, who pays) survive the import, not just names |
| Teachers and staff | Moves with profiles; availability and pay rates often need to be re-entered | Pay rates, locations, and room assignments are confirmed before payroll runs |
| Recurring lessons and class rosters | Can be rebuilt in bulk from exported schedules | Every recurring slot, teacher, and room matches before families can self-book |
| Programs, tuition plans, and discounts | Usually recreated in the new system rather than copied | Sibling discounts, semester plans, and prorations produce the same totals |
| Account balances and credits | Carried over as opening balances | Outstanding balances, prepayments, and makeup credits reconcile to the penny |
| Billing and payment history | Often archived as a report rather than imported line by line | You can still access past invoices for disputes and taxes |
| Stored payment methods | Can typically be transferred securely, most easily between systems on the same processor (see below) | Which cards will transfer, and how you’ll reach any families whose cards don’t |
| Messages and call history | Rarely moves between systems | You keep an export of past conversations you may need |
| Phone number | Can often be ported to a new provider | Who owns the number today and how long a port takes |
The pattern is consistent: the closer the data is to money or to families’ trust, the more it deserves a named owner and a check before go-live. Multi-location schools should run each check per location, since shared teachers and rooms are where mismatches hide.
The Two Details Most Switching Guides Skip
Families’ payment methods
Card numbers aren’t stored in your school software the way names and addresses are. They’re held securely by a payment processor, which is why you can’t simply export them to a spreadsheet. Even so, stored cards can typically be transferred securely to a new system, and it’s usually simplest when both systems use the same processor, such as Stripe. Some setups take more work, and occasionally a few families may need to re-enter their payment details.
Ask about this early, because it shapes your whole family communication plan. For any families who do need to re-enter cards, give them a simple link, a clear deadline before the first billing date on the new system, and reminders by both text and email. Handled well, it’s a two-minute task for each family. Handled as an afterthought, it becomes a wave of failed payments in your first month.
Your phone number and conversation history
Your school’s phone number is on your website, your Google listing, flyers, and years of families’ contact lists. If you’re consolidating phone, text, and email into your new platform, you’ll want to keep that number. Phone numbers can often be ported from one provider to another, but it takes time and paperwork, and you need to confirm who owns the number today.
Past text and call history usually doesn’t transfer between systems, so export anything you may need before you switch off the old tools. Going forward, a switch is a good moment to stop splitting family conversations across a personal cell, a separate texting app, and email. Having every call, text, and email on one family record means anyone at the front desk, at any location, can pick up where a colleague left off.
A Switching Timeline That Protects Your Families
Every school is different, but successful switches tend to follow the same phases. The biggest variable is timing: avoid switching in the middle of your heaviest enrollment window, and dance schools in particular should avoid the run-up to recital season, when costume fees, rehearsal schedules, and ticketing are all in motion.
- Plan. Pick a go-live date between billing cycles and outside your busiest season. Name one person on your team as the owner of the switch, and write down your key decisions before setup starts: cancellation and makeup policies, pricing, billing cadence, due dates and late fees, and sibling discounts. Unclear policies are one of the most common reasons go-live dates slip.
- Export and clean. Pull your data from the current system and clean it before it moves. Merge duplicate families, close out inactive students, and fix contact details. Migrating messy data just moves the mess.
- Import and rebuild. Load students, families, and teachers, then rebuild recurring lessons, classes, tuition plans, and discounts in the new system.
- Reconcile. Compare balances, credits, and next month’s invoices side by side across both systems. Spot-check a sample of families, including your most complicated accounts.
- Train your team. Get teachers and front-desk staff comfortable before families arrive. Your team should be able to answer “how do I…” questions confidently on day one.
- Invite families. Send portal invitations, collect payment details if needed, and explain what’s changing and what isn’t.
- Run both briefly, then switch off. Keep read-only access to the old system for at least one billing cycle, so you can answer any question about past charges.
A school with a few hundred students and clean data can often move through these phases in a few weeks. Larger and multi-location schools should plan for more time, mostly in the reconcile and rebuild steps.
Questions to Ask Before You Switch
“Switching is easy” isn’t an answer. A vendor who has done this many times should be able to answer each of these specifically:
- Who does the data import: my team, your team, or both?
- What exactly do you import, and what do I need to rebuild by hand?
- How do you carry over balances, prepayments, and makeup credits?
- Can my families’ payment methods transfer, or will they need to re-enter them?
- Can I keep my school’s phone number?
- How long does a migration typically take for a school my size, with my number of locations?
- Will I have a named person helping me during the switch, and how do I reach them?
- What does support look like after go-live, when a billing question comes up on a Saturday?
If you can, ask to talk to a school of similar size that switched in the last year. Ask them what surprised them. That one conversation will tell you more than any demo.
Telling Families and Teachers
Families don’t need to know how the migration works. They need to know what changes for them, what doesn’t, and what (if anything) they need to do. Keep the message short:
- What’s changing: a new, easier portal for schedules, payments, and messages.
- What’s not changing: their lesson day, time, teacher, and tuition.
- What to do: log in by a specific date, and confirm payment details if needed.
- Who to ask: one name and one number for questions.
Send it by both text and email, a few weeks before go-live, with a reminder a week out. Tell teachers first, so they can answer questions in the lesson room with confidence. When families hear a calm, consistent message, a software switch reads as a school investing in their experience.
The Bottom Line
Your data is more portable than it feels. Student, family, and schedule records move well. Balances, payment methods, and your phone number need a plan, an owner, and a check before go-live. Schools that treat migration as a project, not a weekend task, switch without losing families’ trust, and they stop paying the hidden cost of software they’ve outgrown.
How Opus1 helps: Opus1 was built by music school owners for growing music and dance schools, including multi-location schools with shared teachers and rooms. Our guided onboarding lays out exactly what our team handles and which decisions are yours, with a dedicated specialist guiding you week by week from kickoff through build, training, and go-live. If your current system runs on Stripe, moving families’ stored cards is typically simple, and Opus1 Voice supports porting your existing school phone number. After launch, live phone and chat support stays with you. See how schools like Grow Your Gift Conservatory of Music made the switch in our customer stories.
Opus1 is the all-in-one management platform for growing music and dance schools. Admin Less. Inspire More. Book a demo →
