How to Switch From My Music Staff Without Losing a Single Lesson

The failure mode in a platform move is almost never lost data. It is billing: a family charged twice, or a family charged by neither system because the cutover landed mid-cycle.

Avoid it by treating the invoice run as the cutover event rather than the import. Import everything, verify balances against the old statements, then let the old system finish its current cycle before you raise a single invoice in the new one.

Run both in parallel for that one cycle. It feels redundant and it is the step that turns a risky migration into an uneventful one.

Recurring slots are the one thing worth entering by hand. Imported schedules carry forward every stale slot — the student who quit in March, the Tuesday hour that moved twice.

Rebuilding takes an hour or two and gives you a clean term with rooms attached, which is what enables conflict blocking afterwards. Studios that skip this step generally end up doing it anyway within a month.

Entering the instrument fleet is usually the longest task, because the information does not exist anywhere complete. Serial numbers live on labels, condition lives in someone's memory, and who currently has what lives in a text thread.

Budget an afternoon and treat it as an audit rather than data entry. Most studios find at least one instrument nobody can account for, which is itself the argument for keeping the record properly from then on.