Home › Blog

Moving Your Student List From Spreadsheets and Chat Into a Booking App

Young Woong Moon · working golf lesson pro, developer of ProField · November 7, 2026

For the first two years of teaching, my entire student roster lived in three places at once: a Google Sheet with names and remaining lesson counts, a KakaoTalk thread per student for scheduling, and my own memory for anything that fell through the cracks of the other two. It worked, in the sense that nothing caught fire. It also meant every "how many lessons do I have left?" question from a student sent me digging through a spreadsheet I hadn't opened in four days, hoping I'd remembered to update the last session.

The actual switch to a real system was something I kept putting off, because I assumed it meant re-entering forty students by hand and praying I didn't mistype someone's remaining balance. It took under an hour once I actually sat down to do it. Here's the plan I'd give any coach who's stuck at that same "I know I should switch but haven't" stage.

1. Why this is harder to start than it is to finish

The spreadsheet-and-chat setup isn't broken enough to force a change, and that's exactly the trap. Nothing fails loudly — a student's balance is just quietly off by one lesson, or a reschedule lives in a chat thread you'll forget to check. The cost shows up as small, constant background tax: every booking question takes a lookup, every new student is one more row to remember to update by hand. The actual migration work is small; what's large is the fear of losing data mid-switch, which is really a planning problem, not a technical one.

2. Two coaches, two very different starting points

A tennis coach with 22 students across three sheets. One sheet for group lesson attendance, one for private lesson packages, one just for payment tracking, because she'd added each as a separate problem over two years. Her blocker wasn't the data — it was that she didn't trust any single sheet to be complete, so she kept all three "just in case." The fix wasn't technical; it was deciding, once, which sheet was the source of truth before moving anything.

A piano teacher with 15 students, all tracked by memory and a paper notebook. No spreadsheet at all — he simply remembered who'd paid for how many lessons, which worked until he hit his first bad week and had two separate students genuinely disagree with him about their remaining balance. He had the opposite problem from the tennis coach: not too many sources, but zero source he could point to and settle an argument.

3. Pick your cutover day, and treat the sheet as frozen after it

The mistake that causes real data loss isn't the migration itself — it's running the old system and the new one side by side indefinitely, updating both "just to be safe," until they quietly disagree. Pick one day. Before that day, the spreadsheet is the truth. After it, the app is the truth and the spreadsheet is a read-only backup you keep for a month, then archive. Don't keep editing both.

4. The step-by-step move

  1. Pick your source of truth first. If you have multiple sheets like the tennis coach above, reconcile them into one list before you touch any app — names, remaining lesson counts, and whatever pricing or package type each student is on.
  2. Paste the whole list in at once. Don't add students one at a time through a form. A roster you can paste in from an old spreadsheet or a chat export, student by student, turns a 40-student migration into a few minutes of copy-paste instead of an evening of data entry.
  3. Enter each student's real remaining balance, not zero. This is the step people skip because it feels tedious, and it's the one that actually matters — a student whose balance resets to zero in a new system will notice immediately, and it undermines trust in the whole switch.
  4. Run one real overlap week. Keep the old spreadsheet open and compare it against the new system after each lesson that week. This is where you catch the one student whose count was already wrong before you migrated, while it's still cheap to fix.
  5. Freeze the spreadsheet. Once the overlap week checks out, stop editing the old sheet. Keep it as a static backup, not a second source of truth.

5. Students don't need to notice anything changed

You don't need to announce a migration to students who book by text and always will. The students who never open an app should feel zero difference — you still text them a time, you just record it in one place instead of a sheet. Nothing about moving your own records requires every student to adopt anything. A short, low-key message covers the ones who do ask:

"I've moved my lesson scheduling into one system so I never lose track of anyone's remaining lessons — nothing changes on your end, just keep booking the way you always have."

And for a student who specifically asks to self-book going forward:

"Sure — I'll send you an invite link. It takes two minutes and your current lesson balance carries over exactly as it is, nothing resets."

6. Before vs. after the move

Spreadsheet + chatOne system
"How many lessons do I have left?"You open a sheet and scroll to find the rowIt's on the student's profile, current as of their last booking
Source of truthWhichever sheet you updated most recentlyOne record, updated the moment a lesson is booked or cancelled
Adding a new studentNew row, new chat thread, remember both existAdded once, tracked the same way as everyone else
Risk of a mistyped balanceHigh — manual entry, no cross-checkLow — deducted automatically when a lesson is booked
Student switches to self-booking laterRe-enter them from scratchInvite code links existing history, nothing resets
This is the exact gap I built ProField around. You can paste in a list of students from an old spreadsheet or a chat thread to add many at once, entering each one's real remaining lesson count rather than starting everyone at zero. From there, bookings, cancellations and package deductions are tracked automatically whether you're booking on a student's behalf or they're booking themselves. If a student later wants to self-book, a personal invite code connects their existing balance and history to their new account — nothing is lost in the switch.

A quick checklist before you move

1) Pick one sheet as the source of truth if you have more than one. 2) Paste your whole list in at once instead of typing students one by one. 3) Enter real remaining balances, not zero. 4) Run one overlap week checking the old sheet against the new system. 5) Freeze the spreadsheet once it checks out — don't keep updating both.

Try a lesson app built by a coach

Bulk-add your student list · automatic lesson-pack tracking · your own cancellation deadline · video feedback — free to use

App Store Google Play Use it on the web

FAQ

Do I need to move every student at once, or can I do it gradually?

Move the roster all at once, but let actual app use happen gradually. Add every current student to the system in one sitting so your lesson-pack numbers are in one place, then invite students to self-book at whatever pace makes sense — some the first week, some months later, some never.

What happens to a student's remaining lessons when I move them over?

You enter whatever balance they actually have left when you add them, so nothing resets to zero. If that student later installs the app through a personal invite, the same balance and booking history carry over to their account instead of starting fresh.

How long should the spreadsheet-to-app changeover take?

For most solo coaches, the data entry itself takes under an hour if you paste the list in rather than typing each student one at a time. The part that takes longer is the overlap week where you double-check the old sheet against the new system before you stop touching the sheet for good.

Read next