Switching dance studio software does not have to mean rebuilding your studio one record at a time. In many cases, families, students, classes, enrollments, balances, and available financial history can move into the new system. Even when a studio has no perfect database export, a published schedule or PDF may be enough to rebuild the class schedule quickly.
The key is to plan the migration before canceling the old software. Find out what information exists, what the new provider can import, how the records will be checked, and what must happen separately with payment processing. This guide gives studio owners a practical path from the first export to opening registration in the new system.
On this page The quick answer What can move Starting with a PDF schedule The migration plan How to check the import Frequently asked questionsThe quick answer: start with whatever information you have
Do not begin by assuming everything must be typed again. The best available source may be a complete database export, a group of spreadsheets, access to the former software, downloaded reports, or a PDF schedule. Each source can be useful.
Full export or database
This can provide the broadest set of family, enrollment, account, and historical records.
CSV or Excel reports
Standard student, class, enrollment, balance, attendance, and transaction reports can be mapped into the new system.
Old-system access
Read-only access or saved reports can help fill gaps and explain how fields and account totals should be interpreted.
PDF or web schedule
Class names, teachers, days, times, and season dates can provide enough structure to create an online schedule.
Send a representative sample to the new provider before committing. A useful migration assessment should explain what can move, what needs review, what may not transfer, the likely timing, and whether any unusual work will cost extra.
What dance studio data can usually be moved?
The answer depends on what the old system can provide and how its records are organized. A studio should ask about each category separately rather than accepting a vague promise to “move your data.”
| Information | What to look for | What to verify afterward |
|---|---|---|
| Families and students | Names, contacts, family relationships, birth dates, emergency information, and notes | Household links, duplicates, missing contacts, and date formats |
| Classes and seasons | Class names, teachers, rooms, days, times, dates, tuition, capacity, and age or level rules | Times, instructors, conflicts, pricing, registration status, and season boundaries |
| Enrollments | Active rosters, future enrollments, waitlists, withdrawals, and available history | Student counts, class placement, start dates, and inactive records |
| Account balances | Outstanding charges, credits, unapplied payments, and opening balances | Family totals, credit signs, past-due amounts, and the cutover date |
| Financial history | Charges, payments, refunds, credits, adjustments, and available transaction details | Totals by period, recent deposits, refunds, and how imported history is labeled |
| Attendance and notes | Attendance exports, medical notes, account notes, documents, and communication records | Privacy, record ownership, dates, and whether the history remains searchable |
Not every studio needs every historical record inside the new system. Sometimes the best result is to import the active operational information and preserve older records in a secure archive. Decide what staff must use every day, what must remain available for reference, and what should be retained for accounting or legal reasons with guidance from the studio's professional advisers.
A PDF schedule may be enough to open registration
A schedule that lists class names, teacher names, days, and times contains more useful structure than it may appear to. If the studio also knows the season's starting and ending dates, Dance Studio Manager can use AI-assisted extraction to create draft class records from the schedule. A person then reviews the result and completes details such as tuition, room, capacity, registration status, and age or level limits.
AI is useful here because it reduces repetitive entry; it does not remove the need for review. Teachers with similar names, overlapping rooms, unusual tuition rules, multi-day classes, and exceptions still need a studio owner or staff member to confirm them. The goal is a fast first version followed by a short, controlled correction process.
If payments are not ready yet, a studio can also decide whether to allow registration before collecting payment. That is a business decision, not a requirement of the migration.
Financial history and saved payment methods are different
Financial history includes charges, payments, credits, refunds, balances, and transaction dates. Those records can often be imported when the old provider supplies usable exports or access. They are ordinary business records, although the fields and totals still need to be reconciled carefully.
A saved card or bank account is different. Modern payment systems commonly use processor-controlled tokens instead of exposing the underlying card number to the studio software. The PCI Security Standards Council explains that acquiring token systems are proprietary rather than based on one universal token format. As a result, saved payment methods may be transferable in some arrangements but not in others.
Never send card numbers in a migration spreadsheet
Ask the new software provider to review the processor, gateway, merchant account, and token arrangement. If a supported transfer is not available, families may need to add their payment methods again through the new system's secure payment flow.
Do not cancel the old processor or merchant account simply because the class schedule is ready. Confirm the final billing date, refunds, deposits, recurring-payment responsibilities, token-transfer status, and the date the new processor will begin charging.
A practical dance studio software migration plan
- Inventory the records you use.
List families, students, classes, enrollments, waitlists, attendance, balances, credits, payment history, notes, waivers, documents, and reports. Mark each item as active operations, useful history, or archive-only.
- Export before giving notice.
Download every available CSV, spreadsheet, report, statement, document, and schedule while access is normal. Record the date and filters used for financial reports.
- Send a small sample first.
A representative student file, class file, account report, and schedule can reveal field problems before the full import begins.
- Agree on the field mapping.
Confirm how families, siblings, seasons, class levels, active statuses, balances, credits, and historical transactions will appear in the new software.
- Create and review the initial import.
Import the operational records, compare counts and totals, identify exceptions, and correct the mapping before the final cutover.
- Choose a cutover point.
Decide when staff will stop changing the old system and start using the new one. If activity continues in both systems, identify exactly which final changes must be brought across.
- Test real studio workflows.
Create a registration, enroll siblings, apply a discount, review a family balance, take attendance, send a message, and run the reports staff will need first.
- Keep the old records available temporarily.
Retain read-only access or a secure archive long enough to reconcile the first registration and billing cycle and answer unexpected historical questions.
How to check that the migration worked
A successful import is not defined by the absence of an error message. Compare the new system with the source using a written checklist:
- Total family and student counts
- Sibling and guardian relationships
- Active enrollment and waitlist counts
- Class times, rooms, teachers, capacity, tuition, and season dates
- Total outstanding balances and credits at the agreed cutover date
- Several individual family ledgers, including unusual cases
- Recent payments, refunds, and processor deposits
- Recurring-payment schedules and saved-payment-method status
- Staff permissions, parent access, and registration availability
Use totals to find broad problems and individual records to find mapping problems. For example, matching the total balance does not prove that every credit belongs to the correct family.
How long does a dance studio software migration take?
The technical import may be much faster than the complete business transition. For many DSM migrations completed in 2026, the initial import was ready within about one business day after the studio supplied usable information. A clear PDF schedule can be converted into an initial online schedule within minutes. Larger, incomplete, or highly customized databases need more time.
After the first import, allow time for review, corrections, processor setup, staff testing, and family communication. Presenting that work separately is more useful than promising that every studio will be completely live in one day.
What does DSM charge for migration?
Dance Studio Manager completes most routine migrations at no additional charge. If the source is exceptionally large, incomplete, inconsistent, or requires custom reconstruction, we explain the extra work and any cost before proceeding.
We can work from common spreadsheet and database formats, exports from another system, reports, old-software access, or a schedule published as a PDF or web page. See our DSM data import and export service for accepted formats and a concise service overview.
You do not need a perfect export
Show us what you have before you decide
Send us a sample export, report, or schedule. We will review it and explain what can move, what needs confirmation, and what the likely migration process would look like.
Frequently asked questions
Can I switch dance studio software without re-entering every student?
Usually. Family, student, class, enrollment, balance, and historical records can often be imported from a database export, CSV, spreadsheet, report, or access to the former system. The exact result depends on what the old provider makes available and how the records are organized.
Can a dance studio schedule be imported from a PDF?
Yes. A clear PDF or published schedule containing class names, teachers, days, and times can be used to create draft class records. Season dates and details such as tuition, capacity, rooms, and age or level rules should then be confirmed by the studio.
Can saved credit cards move to new dance studio software?
Sometimes, but not through an ordinary data export. Availability depends on the processors, gateways, merchant accounts, token arrangements, permissions, and provider cooperation. If a supported token transfer is unavailable, families will need to enter their payment methods again securely.
How long should I keep access to my old studio software?
Keep read-only access or a secure archive through at least the initial reconciliation and billing period, and longer when accounting, tax, legal, or operational requirements call for it. Export records before canceling because access and report availability can change after termination.
Does Dance Studio Manager charge a data migration fee?
Most routine DSM migrations are completed at no additional charge. If a source is exceptionally large, incomplete, inconsistent, or requires custom reconstruction, DSM explains the work and any cost before proceeding.
Sources and scope
- PCI Security Standards Council: acquiring tokens, issuer tokens, and payment tokens
- PCI Security Standards Council: Data Security Essentials for Small Merchants
- Jackrabbit Dance: current data-migration overview
- ProgramChamp: current migration and saved-payment-method explanation
Scope: Last reviewed August 22, 2026. Migration results depend on the quality and availability of source records, provider cooperation, payment-processing arrangements, and the studio's requirements. Timings describe common DSM experience, not a guarantee for every database. Do not transmit unprotected payment-card data in spreadsheets or ordinary email.