Switching Martial Arts Software Without Losing Data (or Families)

The real risk isn't the software — it's the billing transfer

Student records move in a CSV. What actually goes wrong in migrations is recurring billing: hundreds of card-on-file agreements that either transfer between processors or have to be re-entered by every family. A re-enrollment campaign always loses cards — families procrastinate, cards have moved, and 5-15% of autopay quietly stops.

If both platforms use Stripe, ask about a Stripe-to-Stripe customer migration — card tokens can transfer between accounts without families lifting a finger. If your current platform uses a proprietary processor, plan a managed re-capture campaign with a deadline and a kiosk prompt, and start it before you cut over, not after.

Inventory what must move — and what's trapped

Before choosing a destination, export everything from your current system and see what you actually get. Belt history and attendance records are the common casualties — many platforms export current rank but not promotion dates, or member lists but not attendance. Know what's trapped before you decide whether it matters.

• Students and families: names, contacts, emergency info, household grouping
• Belt/rank history with promotion dates — ask specifically; 'current rank' is not history
• Active billing: plan, price, renewal date, and card-on-file per family
• Attendance history (or accept a clean start and archive the export)
• Waivers: signed PDFs export from most platforms; re-signing via kiosk on the new system is the clean fallback

Run two weeks in parallel

Import your roster into the new system and run check-ins on it for two weeks while billing continues on the old platform. This proves the roster is complete, gets staff and students used to the new kiosk flow, and surfaces data problems while the old system is still authoritative. Cut billing over at a month boundary — mid-cycle proration across two systems is where double-charges come from.

Set a hard decommission date for the old platform and take a final full export the day before it ends. You will want that archive exactly once, two years from now.

Tell parents less than you think you need to

Families don't care about your software; they care whether their payment changes and whether check-in still works. One short message covers it: what's changing, what they need to do (usually nothing, or 'the kiosk looks different Monday'), and who to ask. Save the detailed announcement for the rare case where families must re-enter payment details — that one deserves a deadline, a reason, and a reminder sequence.

MyDojang migrations start with a CSV importer for rosters, ranks, and families, Stripe-to-Stripe billing transfer where the source platform allows it, and a full-featured free trial long enough to run the parallel period properly. Our comparison pages show exactly what you'd be moving to, feature by feature.