Migrating to a new school ERP

An ERP is only as trustworthy as the records inside it. When a school moves from registers and spreadsheets to a connected system, every inconsistency in the old data comes along for the ride, and it shows up on day one as a wrong fee balance, a duplicate student or a parent who never receives an alert.

The good news is that data problems are predictable. This checklist walks through what to fix before go-live, and in what order.

Start by listing where information actually lives today. Typical sources include:

• Admission register and enquiry sheets
• Fee registers, receipt books and accountant spreadsheets
• Attendance registers
• Marks sheets kept by individual teachers
• Staff files and salary sheets
• Transport, hostel and library lists

For each one, note who owns it, how current it is and whether it disagrees with another source. Disagreements between the admission register and the fee register are the most common and the most costly.

Decide, before importing anything, which fields make up one authoritative student record and where each will come from. A sensible baseline:

• A unique admission number that never changes or gets reused
• Name and date of birth as they appear in official documents
• Class, section and roll number for the current academic year
• Parent or guardian names with a verified primary mobile number
• Sibling links, category and fee category
• Transport or hostel assignment, where relevant

Choosing the source of truth for each field up front ends most arguments later.

Set aside time to fix the problems that appear in almost every school's data:

• Duplicates: the same child entered twice under slightly different spellings
• Name and date mismatches between admission records and fee records
• Broken sibling links, which cause wrongly applied discounts or missed family-level reminders
• Invalid or shared phone numbers, including numbers that belong to a former driver or an old contact
• Class and section drift, where students who were promoted or shifted are still listed in the old section
• Staff duplicates and missing designations or joining dates

A simple approach: export each list, sort it, and have the owner review flagged rows in a short, scheduled session. Cleaning by committee for weeks rarely works. Cleaning with a deadline does.

Not every historical record needs to live in the new system. A useful rule of thumb:

• Migrate: the current academic year's students, staff, structures, fee schedules and opening balances
• Archive, but keep accessible: older years' registers and receipts, stored as scanned or exported files
• Retire: duplicate lists, personal copies and abandoned templates

Importing many years of messy history usually adds risk without adding value.

Data depends on other data, so sequence matters:

1. Academic year, classes, sections and subjects
2. Fee heads, fee structures and concession categories
3. Staff and roles
4. Students and guardians
5. Opening balances (dues and advances) as of a fixed cut-off date
6. Transport, hostel and library assignments

Never sign off on a migration by eyeballing a few screens. Check totals:

• Number of students per class matches the register
• Total outstanding dues in the system matches the accountant's closing figure
• A sample of students, taken across classes and fee categories, matches paper records line by line
• Every active staff member has a role, and no former staff member has one

Record the sign-off and who gave it. If a number does not reconcile, fix the source, not the total.

Choose a cut-off date, ideally at the start of a month or term, and run old and new side by side for a short, defined period. Set an end date for the parallel run in advance. Without one, dual entry becomes permanent.

• Starting the import before the fee structure is agreed
• Letting several people edit the "final" spreadsheet at once
• Skipping the opening balance reconciliation
• Treating migration as an IT task rather than a shared task between the office, the accounts team and the academic coordinator

A clean migration is unglamorous work, and it is what makes everything afterwards feel effortless: attendance alerts that reach the right parent, fee reminders that carry the right amount, reports that agree with each other. Give the data a few weeks of attention and the ERP repays it for years.

Planning a move from spreadsheets? Learn how a connected Student Information System becomes the single record everything else builds on.