Student information system (SIS)

How this works in a running school

The student information system is the record everything else depends on, which makes its quality disproportionately important. If the same student exists twice, if a guardian is linked to one sibling and not the other, or if enrolment history is overwritten each year rather than retained, every downstream module inherits the problem and reporting becomes unreliable in ways that are hard to trace.

This is also why migration effort concentrates here. Loading students is straightforward; deduplicating them, reconstructing guardian relationships, and deciding what historical data to bring across is the work that determines whether the first year of reporting is trustworthy.

What to check when evaluating it

• Whether each student has a stable identifier that survives class changes, name changes, and re-enrolment.
• Whether guardians are first-class records linked to multiple children, rather than fields on a student.
• Whether enrolment history is retained per academic year instead of overwritten.
• How a student who leaves and returns is handled, and whether history reconnects.
• What the deduplication tooling looks like, since your source data will contain duplicates.
• Which fields are mandatory, and whether that matches what your office can realistically collect.

What it costs to get wrong

Errors here propagate everywhere and are hard to unwind. A duplicate student created during migration will appear in one class register and not another, receive one set of fee invoices, and carry half an academic history. By the time the pattern is noticed, months of attendance and marks have been recorded against both records and merging them means deciding which history is real. Time spent deduplicating before migration is the highest-return work in the whole project.

Student information system (SIS): common questions

What data belongs in a student information system?

Identity and contact details, guardian relationships, enrolment and class history, attendance, assessment results, fee position, and documents collected during admissions.

Anything that must be answerable about a student a year after the fact belongs here rather than in a departmental spreadsheet.

Is a student information system the same as a learning management system?

No, and they are complementary. A student information system holds the administrative and academic record: who the student is, what they are enrolled in, and how they performed.

A learning management system delivers course content, assignments, and classroom interaction. Many schools run both, integrated at the roster level.

How long should student records be retained?

This is set by your jurisdiction and often by your accrediting body, and it is frequently longer than schools expect for academic transcripts.

Establish the requirement before migration, because it determines what historical data must be brought across rather than archived.