Student records
The student record everything else is attached to
Admission through alumni, with guardians linked, bulk import for the first migration, and a year-end promotion you can preview before you commit.
What the student records module covers
Admission and enrolment
A student record, and an enrolment attaching them to a class and section for a given academic session.
Guardian links
Guardians as their own records, linked to students — which is what makes one parent login cover several children.
Bulk CSV import
The first migration off a spreadsheet, which is how every school's first day with an ERP actually starts.
Promotion with dry run
Year-end rollover previewed in full before it is committed. Promoting the whole school is not an action to find out about afterwards.
Alumni
Students who have left stay queryable, which is what makes issuing a transfer certificate two years later possible.
Campuses and sessions
Multiple campuses and academic sessions under one organisation, for trusts running more than one school.
Sessions are why the data model looks the way it does
A student is not in Class 8. A student has an enrolment that places them in Class 8 for the 2026–27 session. The distinction sounds pedantic until year-end, when a system that stored the class on the student has to overwrite it — and every attendance record, invoice and result from the previous year is suddenly attached to a student whose class says something else.
Promotion is therefore a bulk operation over enrolments, and it runs as a dry run first. The preview lists exactly who moves where, who is held back, and who is being marked as leaving. Promoting an entire school is not a thing to discover the shape of afterwards.
Alumni fall out of the same model. A student who has left keeps their record and their enrolment history, which is what makes it possible to issue a transfer or migration certificate, or answer a verification request, long after they have gone.
Bulk import matters more than it sounds. No school arrives with clean data in the right shape; they arrive with a spreadsheet. Import against classes and sections, with guardians, is the difference between adopting the system this session and adopting it next year.
Student records: common questions
Can we import our existing student data from a spreadsheet?
Yes. Bulk CSV import brings students in against their classes and sections, along with guardian details, which is normally how a school's first session on the system starts.
How does year-end promotion work?
As a bulk operation over enrolments, run as a dry run first. The preview shows exactly who is promoted, who is held back and who is leaving before anything is committed.
Can one organisation run multiple campuses?
Yes. Campuses and academic sessions both sit under an organisation, which is the arrangement a trust running more than one school needs.
What happens to students after they leave?
They remain as alumni records with their enrolment history intact, so transfer certificates, migration certificates and verification requests can still be handled years later.
See Student records against your own school's setup
Tell us your board, your class structure and how you collect fees today, and we will show you the parts that matter to you rather than a generic tour.