Shop for school software and you will meet three labels: LMS, SIS and ERP. Vendors stretch each label to cover more ground, so the same feature can appear in all three. Schools then end up with grades entered in two places, parent phone numbers that differ between systems, and nobody sure which record is correct.
This guide defines each type of system, shows where they overlap and gives you a simple way to decide what your school actually needs.
What an LMS does
A learning management system (LMS) is where teaching and learning happen. Teachers build courses, publish lessons, set assignments and quizzes, mark work and give feedback. Students learn, submit work and see their results. In schools, parents follow progress there too.
- Courses, lessons and learning materials
- Assignments, quizzes and exams
- Marking, rubrics and feedback
- A gradebook for coursework
- Discussions and messaging
- Links to live classes and timetables
Its daily users are teachers and students. You judge an LMS by whether teaching and learning get easier.
What an SIS does
A student information system (SIS) is the system of record for students. It holds who each student is, what they are enrolled in and what their official results are.
- Admissions, applications and enrolment
- Student and family records
- Class lists, sections and timetables
- Official attendance
- Final grades, transcripts and GPA
- Reporting to ministries, accreditors and boards
Its daily users are the registrar, student affairs and school administration. In several countries, schools must also report into a government platform, such as Noor, the Saudi Ministry of Education's system for school data, attendance and exam results. Whichever system holds your official records must be able to produce what those platforms need.
What a school ERP does
ERP stands for enterprise resource planning. In education, the term usually means software that runs the business side of a school: finance, fees, staff, purchasing and operations. Many “school ERP” products also include SIS functions, and some bundle a basic LMS.
- Fee schedules, invoices, payments and receipts
- Staff records, contracts and payroll
- Purchasing, assets and inventory
- Transport, canteen and library
- Financial reporting
Its daily users are finance, HR and operations staff. You judge an ERP by whether the school runs efficiently and the accounts are right.
Where the three overlap
Most confusion comes from five areas that more than one system claims:
| Area | LMS | SIS | ERP |
|---|---|---|---|
| Grades | Coursework marks and gradebook | Official final grades and transcripts | Rarely involved |
| Enrolment | Access to courses | Admission and official enrolment | Fees triggered by enrolment |
| Parents | Progress and messages | Contact details and family records | Invoices and payments |
| Attendance | Presence in live classes | Official attendance register | Staff attendance |
| Payments | Rarely involved | Sometimes fee status | Core function |
The rule that prevents most problems: every piece of data needs one owner, the system where it is created and corrected. Other systems may display it, but they should not compete to be the source of truth. Overlapping features are fine; two owners for the same data are not.
Signs your current setup is not working
- Teachers enter the same grade in two systems, and the two sometimes disagree.
- The office exports a spreadsheet from one system every week to upload it to another.
- Parents need separate logins for grades, messages and fee payments.
- Nobody can say with confidence which phone number or address for a family is current.
- Producing transcripts at the end of the year takes days of manual checking.
- A new student attends classes for days before appearing in every system.
One or two of these is normal friction. Several together usually mean that data ownership was never decided, and adding another system will make things worse unless you decide it first.
Connected systems or one platform?
There are two broad ways to cover teaching, records and finance.
Specialist systems, connected
You choose the strongest product in each area and connect them through integrations.
- Strengths: depth in each area, and the freedom to replace one part without replacing everything. This suits large institutions with specialist teams.
- Costs: integrations to build and maintain, more vendors and contracts, and data that drifts apart when a sync fails quietly.
Standards reduce the effort. 1EdTech's OneRoster standard covers class rosters and gradebook exchange between systems, and LTI lets external tools open inside an LMS. Ask vendors which standards they support today, which are certified and which are only planned.
One platform
A single platform covers teaching and academic records, and sometimes fees.
- Strengths: one sign-in, one set of data and nothing to synchronise. Final grades flow into transcripts without retyping, and training and support are simpler.
- Costs: depth can vary between modules, one part is harder to swap out, and you depend more on a single vendor.
The pattern many schools settle on
A common middle path is an LMS that also handles academic records, from coursework through final grades, transcripts, the parent portal and admissions, connected to separate accounting and HR software. Teaching and academic records share one set of data, while finance stays in tools built for accountants.
Plan the data flow before you buy
Before talking to vendors, draw a simple map of your data on one page. List the main records down the side, such as students, families, staff, courses, enrolments, coursework grades, final grades, attendance, invoices and payments. For each one, write which system creates it, which systems need to read it and how often it changes.
This map turns vague discussions into concrete questions. If enrolments are created in admissions but needed in the LMS within the hour, you need a real-time integration or a single platform, not a nightly spreadsheet. If final grades must reach a ministry system every term, someone must own that export. Vendors who can answer against your map are far more useful than vendors who answer from their brochure.
How to decide
| If your situation is | Consider |
|---|---|
| A small or new school with no SIS and a small office team | An LMS that also covers academic records, admissions and parent communication |
| A school with an SIS that works well | A dedicated LMS that connects to it through CSV, an API or OneRoster |
| A large university with registry systems and many faculties | A specialist SIS and LMS, connected by standards |
| A group running several schools or campuses | A platform that runs each school with separate data and reports across all of them |
| An online school with self-paced courses | An LMS strong on course building, mentoring and records from enrolment to transcript |
| Employee training in a company | An LMS connected to your HR system; an SIS is not needed |
How this looks in universities and companies
The same three categories exist outside schools, under different names.
- Universities usually call the SIS a registry or student records system. It handles programme structures, credit hours, academic standing and graduation audits, which are more complex than in schools. The LMS handles course delivery, and the two are normally connected so that course enrolments flow from the registry to the LMS and final grades flow back.
- Companies rarely need an SIS. The equivalent system of record is the HR system, which holds employees, departments and managers. The LMS assigns training, tracks completion, issues certificates and reports mandatory training back to HR.
The principle is the same in every setting: decide which system owns each piece of data, then connect everything else to it.
Questions to ask before you buy
- Which system will own each type of data: students, enrolment, grades, attendance and fees?
- Where will teachers enter grades, and how do final grades reach transcripts?
- What happens to records when a student changes section mid-term?
- Which integrations exist today, which are on a roadmap, and who maintains them?
- Can we export all our data in standard formats at any time?
- How many separate sign-ins will staff, students and parents need?
- Which reports must we submit to authorities, and which system produces them?
For a complete vendor questionnaire, use our LMS RFP checklist.
Common mistakes
- Buying an ERP for its finance features and accepting the weak LMS bundled with it. Teachers feel the difference every day.
- Entering grades in two places “for now”. Temporary double entry tends to become permanent.
- Forgetting parents. If family contact details live in one system and messaging in another, messages go to old numbers.
- Comparing module checklists instead of workflows. Two products can both list “transcripts” and work in completely different ways.
- Underestimating integration upkeep. Every connection needs an owner, monitoring and a plan for when one side changes.
Where Ilmoria fits
Ilmoria is an LMS that covers the academic side end to end: course building, assessments, the gradebook through to final grades and transcripts, certificates, the parent portal, admissions, and student invoices and receipts. It connects to other systems through CSV import and export, with a REST API and webhooks on enterprise plans. See how it works for K-12 schools.
Want to see this guide applied to your institution? We will walk you through it on Ilmoria.
Book a demo