How to Migrate from Old School Software Without Losing Data
The reason most schools stay on software they dislike is not loyalty, it is fear: years of student records, fee history and results sitting in a system they do not trust but cannot afford to lose. That fear is reasonable and the risk is manageable. Here is how a migration actually runs, and what to verify before anyone switches anything off.
Before anything else: can you get your data out?
Ask your current vendor for a full export today, before you start any conversation about switching. What comes back tells you everything. A usable export arrives as Excel or CSV per entity, covering students, guardians, fee ledgers, staff and results. If the answer is a PDF, a screenshot, a delay, or a fee, you have learned something important about who actually controls your records, and it is a reason to leave rather than a reason to stay.
What actually needs to move
Not everything is worth migrating, and pretending otherwise makes projects fail.
- Students and guardians, with contact numbers and the family links between siblings
- Classes, sections, and the current enrolment of each student
- Fee structure, plus outstanding arrears per student. This is the one that must be exact.
- Fee payment history, at least for the current academic year
- Staff records and salary structures
- Past results, usually the last two or three years rather than everything
- Documents and photos where they exist
Get the arrears right, or nothing else matters
Every other field can be corrected quietly later. An arrears figure cannot, because a parent will notice within days and the school's credibility goes with it. Reconcile outstanding balances to the rupee before go-live, have your accountant sign off on a sample of at least twenty families across classes, and keep the old system readable until that reconciliation has survived one full fee cycle.
Migrating from paper registers
Many schools are not moving from software at all, they are moving from registers. The practical approach is to enter current students and current arrears first, get the school running, and backfill history afterwards if it is genuinely needed. Do not let a plan to digitise ten years of registers stop you starting; most of that history is never queried again.
A migration timeline that works
Sequence matters more than speed.
- Export everything from the old system and keep an untouched copy offline
- Map fields to the new system and agree what will not be migrated
- Do a test import into a sandbox, then check a sample against the old system by hand
- Reconcile arrears and have finance sign them off
- Train staff on the new system before go-live, not after
- Go live between terms, never during admission season
- Keep the old system readable, not editable, for at least one full fee cycle
Who should do the work
If migration is quoted as an extra cost, treat that as part of the price. Vendors confident in their onboarding include it, because a botched migration costs them the customer. eSchools migrates students and families, fee history and arrears, classes, staff and past results from spreadsheets, registers or another system as part of onboarding, at no extra charge. Whoever you choose, make sure a named person owns the reconciliation.
Frequently asked questions
Can we migrate data from our old school software?
Yes, in almost all cases. Students, guardians, classes, fee structures, arrears, staff and past results can be migrated from another system, spreadsheets or paper registers. The main constraint is whether your current vendor will give you a usable export, so request one before you commit to switching.
When is the best time to switch school software?
Between terms, and never during admission season. Go live when the office is quiet enough to verify data and learn the new system, and keep the old system readable for at least one full fee cycle as a fallback.
What if our data is only in paper registers?
Enter current students and current arrears first so the school can start running on the new system, then backfill historical records only if you genuinely need them. Waiting to digitise years of registers before starting is the most common reason schools never start at all.