Your school may have one spreadsheet for admissions, another for school fees and a separate class list on a teacher’s laptop. These files can become difficult to keep consistent as records change.
Moving to school management software starts before anyone transfers a file. The important work is agreeing which records are correct, preparing them carefully and checking that the new system matches them. Here is a practical process for school owners, administrators and bursars.
1. Decide what moves first
Begin with a manageable scope. For example, move active students, their parent or guardian contacts, current classes and agreed fee balances. Decide separately whether previous results, attendance and older financial transactions are needed immediately.
Choose one person to coordinate the move. Ask the admissions officer to verify student records and the bursar to verify fees. A named reviewer should approve each set of records before transfer.
Set a cut-off date and time. Write down how new admissions, payments and corrections received after that point will be recorded and added, so nothing disappears between the old and new systems.
2. Keep a safe copy before changing anything
Save a dated, untouched copy of every source file in a school-approved location with restricted access. Check that the files open and that a second authorised person knows where to find them. Make changes in working copies, not the originals.
Keep a simple file list showing the owner, purpose and last verified date. If two files disagree, ask the responsible staff member to resolve the difference. Do not assume that the newest filename contains the correct figures.
3. Clean student and parent records
Use a consistent student identifier, such as the school’s admission number. Names alone are unreliable because two students may share a name, and the same name can be spelt differently.
Check duplicate entries, missing admission numbers, spelling, current class and whether each student is active or has left. Confirm that parent or guardian contacts are linked to the correct child. Siblings may share a contact; that does not make the children duplicates.
Keep phone numbers and identifiers as text in the working spreadsheet so leading zeros are preserved. Formatting cannot recover zeros already lost: check the original record. Agree a clear date format, and verify ambiguous dates rather than guessing.
Use one meaning per column and consistent class names. “JSS 1”, “JSS1” and “Junior Secondary 1” should not accidentally become three separate classes. Flag missing information for follow-up instead of inventing values.
4. Agree classes, fees and opening balances
Prepare the academic session, term, class names and fee categories before transferring student records. Separate current charges, previous balances, payments, discounts, waivers and credits so the same amount is not counted twice.
An opening balance is the amount carried into the new system at the agreed cut-off. For example, if a student was charged ₦80,000 and paid ₦50,000 before that date, the outstanding amount is ₦30,000, assuming no other adjustments.
Confirm how the new system represents that balance. Do not load ₦30,000 as an opening debt and then add the original ₦80,000 charge again without the matching payment history.
Have the bursar approve each student’s balance and the class totals against the school’s ledger or verified records. Record the cut-off date and keep explanations for disputed amounts and credits. Resolve differences before live billing.
5. Confirm the transfer method and test one class
Ask the provider which transfer method and fields are supported. Map each source column to its intended destination; do not assume any Excel file can be uploaded.
For Smart EduSphere, the admin guide documents student bulk enrolment using the current enrolment-screen template. Keep its headers unchanged, use one student per row, follow the template’s required values, save as UTF-8 CSV and review the upload preview and errors. After valid rows are imported, correct and re-upload rejected rows only.
That student process does not establish a fee-balance import route. Agree how prior arrears, credits and payment history will be represented with the onboarding team.
Start with one class in a test area where available. Include representative cases such as siblings and a part payment. Use fictional records for demonstrations and approved, restricted environments for live records.
Confirm correction or rollback steps and prevent test activity from sending real messages or creating unintended bills.
6. Reconcile what arrived
A successful transfer message is only the start of checking. Compare the source and destination student counts, then match students by identifier. Check that no child is missing, duplicated or assigned to the wrong class.
Review parent links and contact details. Compare every opening balance and reconcile totals by class and for the whole pilot. Matching totals alone can hide errors where two students’ balances have been swapped.
Keep a discrepancy list showing the record, issue, correction and reviewer. Recheck corrected records. Do not repeatedly transfer the same file unless the provider has explained how existing records and duplicates are handled.
Expand to other classes only when the pilot’s records and balances have been checked and the responsible staff have signed off.
7. Train staff and make the switch
Train staff on the tasks they actually perform: finding a student, updating an authorised contact, recording a payment and checking a report. Use a short practice exercise rather than relying only on a presentation.
Agree who may view or change each type of record. Use individual accounts where available and avoid shared passwords. Share files only through an approved route with the people who need them, not a general staff or parents’ group.
Ask the provider about access controls, backups, recovery and returning the school’s data if the service ends. Check the school’s privacy and retention requirements before deciding what to transfer or keep.
At the agreed switch-over, capture and reconcile changes since the cut-off. Identify one official place for new entries. Keep the old spreadsheets as restricted reference copies according to the school’s retention plan, rather than maintaining two competing live records.
Start with a controlled move
The aim is to carry accurate, useful records into a system staff can use confidently. A checked pilot, clear responsibilities and a reconciled opening position give the school a stronger starting point.