How do you move existing class credit balances into a new system without losing anyone's sessions?

Freeze the numbers before you touch anything

The first step is to pick a cutover date and stop making changes in the old system after that point except for actual check-ins. Export every member's balance, expiry date, and pack type as of that moment. If your old system is a spreadsheet, that means saving a dated copy that nobody edits. If it is another tool, that means an export you can open and read line by line.

Before importing, reconcile the export against what you believe to be true. Compare the total outstanding credits to your last known figure, and look for negative balances, duplicate member records, and people with credits but no expiry date. Every anomaly you fix before import is one fewer confused member after it. Related: How can a studio set a class credit expiry policy that feels fair to members and to the business?

Keep reading: How can a small studio start selling class credit packs without creating a bookkeeping headache?, Why do class credit balances drift out of sync and how can a studio keep them accurate?, How can a studio set a class credit expiry policy that feels fair to members and to the business?. See how CreditLoopr helps you class credit packs and session balance tracking.

Map the old fields to the new ones honestly

Systems differ in how they represent credits. One may store a pack as a single row with a count, another as individual credit records, a third may attach credits to a class type. Write down how each old field maps to the new one, and note anything that does not map cleanly, such as packs with mixed credit values or credits that were granted as goodwill rather than purchased. Related: How can a small studio start selling class credit packs without creating a bookkeeping headache?

For credits that do not map cleanly, decide a rule and apply it consistently. A common approach is to import each remaining credit as a single unit tied to the original purchase date and expiry, and to tag goodwill credits separately so they do not show up as revenue. Resist the urge to tidy balances during migration; adjust them afterward with a note, so the audit trail stays honest. Related: Why do class credit balances drift out of sync and how can a studio keep them accurate?

Run both systems side by side for a short window

Even a careful import benefits from a parallel run. For a week or two, record check-ins in both the old and new systems and compare balances at the end of each day. Differences will point you to import errors, class types that were mapped incorrectly, or staff who are still checking people in from memory. Related: Why should a studio owner always know how many class credits are still outstanding at any time?

Tell your front desk staff what to do when the two systems disagree: trust the new one, note the discrepancy, and flag it for review. Do not let staff quietly fix balances in either system without a record. The point of the parallel run is to find problems, not to hide them.

Tell members what changed and give them a way to check

Send members a short note before cutover explaining that their balances are moving, that nothing changes in terms of what they own, and how they can check their balance in the new system. Include their current balance in that note if you can. Members who verify their own numbers are your best migration testers.

After cutover, expect a small number of "this is not right" messages and treat each as a data point, not a complaint. Keep the old export accessible for a few months so you can look up any balance as of cutover day. Once the questions stop, archive the old data somewhere safe and move on.