Guide
Getting off spreadsheets without losing a term
Most schools adopting software are not starting from nothing. They have years of records in spreadsheets, registers and one clerk's memory. How that migration is handled decides whether the rollout works.
Clean before you migrate
Importing messy data produces a messy system, and the mess is harder to fix once it is spread across modules. The most common problems are duplicate students, inconsistent class naming, missing admission numbers and phone numbers stored in several formats.
Fixing these in the spreadsheet first is far quicker than fixing them afterwards, and it is work your staff can do without waiting for the vendor.
- One row per student, with duplicates removed
- Consistent class and section naming throughout
- A unique admission number for every student
- Phone numbers in one format, ideally with country code
- Dates in one format
Migrate in the right order
The order matters because later records depend on earlier ones. Students cannot be assigned to classes that do not exist, and fees cannot be assigned to students who are not there.
Set up structure first, then people, then the operational data that references them.
- Academic year, classes, sections and subjects
- Students with their guardians
- Fee structures, then each student's charges and payment position
- Transport routes and stops, then student assignments
- Staff records and departments
- Documents, once the records they attach to exist
Decide how much history to bring
The instinct is to import everything. It is usually the wrong call. Historical attendance and marks from previous years take substantial effort to migrate and are rarely consulted afterwards.
A pragmatic line: bring current students with their current fee position and documents, keep prior years in their existing form as archive, and start clean from the current academic year. If a historical record is needed later, the archive is still there.
Run parallel briefly, not indefinitely
A short overlap where fees are recorded in both the old register and the new system builds confidence that the figures agree. Two weeks is usually enough.
Running parallel for a term does the opposite: staff treat the new system as extra work, the registers stay authoritative, and adoption never happens. Set the switch-off date before you start.
Expect the mid-term joiners to be the problem
Whatever else goes smoothly, the awkward cases will be students who joined mid-term, students on concessions granted informally, and students whose transport arrangement changed and was never written down.
These are worth identifying deliberately before migration rather than discovering them one at a time afterwards. Ask the accounts clerk — they will know exactly who they are.