Skip to content

A practical guide for principals, finance teams and IT leads

How to choose school ERP software for an international rollout

Start with the work your school must complete each day: admit a student, mark attendance, issue a receipt, communicate with parents and publish a report card. Use the same sample workflows to evaluate every school management system. This checklist is published by EduGradUP, a software vendor; it is not an independent ranking of vendors.

By EduGradUP · Updated

1. Agree the requirements before comparing prices

Ask the people who will use the software to demonstrate their current process. Separate required workflows from features that would be useful later.

1. Agree the requirements before comparing prices
RequirementWhat to reviewConfirm before rollout
Student information systemAdmissions, guardians, student records, class changes and academic-year history.Can the office import and export the required fields without losing the relationship between siblings and guardians?
Curriculum and assessmentTerms, subjects, grading scales, transcripts and report cards.Can the vendor reproduce your actual report format and show any required ministry or board export?
Fees and paymentsFee schedules, instalments, concessions, receipts and refunds.Can a payment be reconciled to a student, including gateway fees, tax and settlement currency?
Language and parent accessThe languages and devices staff and families actually use.Can a parent read a notice and find a receipt on their own phone in the required interface language?
Multiple campusesBranch reporting and separate school access.Can group leaders see branch summaries while school staff retain only the access they need?

2. Verify privacy, access and hosting with evidence

Request the hosting region, data processing agreement, subprocessor list, retention and deletion process, backup policy and incident contacts. Have your school's responsible adviser review the terms against local requirements. A generic compliance badge or a country name on a website is not sufficient evidence.

3. Price the full first year and renewal

Compare the written total in a stated currency: subscription, onboarding, migration, training, required customisation, payment processing, SMS or WhatsApp, support and taxes. For a school planning for 500 students, ask every vendor to price the same student count, campus structure and message usage. Record what changes if enrolment grows and what is charged again at renewal.

3. Price the full first year and renewal
RequirementWhat to reviewConfirm before rollout
Subscription and school sizeAnnual cost for the agreed student count, campuses and required modules.Is billing per student, per school or by an enrolment band? Confirm currency, included users, taxes and the effect of growth.
Setup and transitionData preparation, migration, report customisation, onboarding and staff training.Which items are included, which are one-time charges and which need a separate statement of work?
Ongoing use and supportMessage usage, payment processing, support hours and any additional integrations.List the usage rates, provider charges, renewal terms and any support commitments in the written quote.

4. Move student records and fee balances from Excel

Keep a copy of your original registers and make an import plan before changing systems. EduGradUP includes bulk Excel student import and fee opening-balance import. Begin with a small sample without personal data, map identifiers and required fields, and check sibling and guardian links. After a pilot import, compare student totals and outstanding balances with the source records; agree how historical attendance, exam results and old receipts will remain accessible.

5. Run a small acceptance pilot

Use synthetic students and a sample fee schedule. Test an admission, attendance entry, corrected payment, refund, parent notice, report card and data export. Record who approves each result and resolve gaps before importing live student data. Agree a migration plan, staff training and a rollback decision with the vendor.

6. Check EduGradUP against your shortlist

EduGradUP combines an SIS with fees, attendance, exams, report cards, parent apps and branch dashboards. Its shipped interface languages are English, Hindi, Marathi, Tamil, Telugu and Urdu. Confirm the fit of your curriculum, payments, hosting and support requirements during an international demo.

Frequently asked questions

What is the difference between school ERP, SIS and LMS?
A student information system (SIS) focuses on student records. School ERP extends into administration such as fees, staff and operations. A learning management system (LMS) focuses on teaching, coursework and assessments. Ask which workflows are included and which require integrations.
Should we compare school software using a per-student price?
Compare the total annual cost at your expected enrolment and number of campuses. Include migration, messaging, payment processing, customisation, support, taxes and renewal terms, whether the subscription is per student or per school.
What should an international school test before buying an ERP?
Test your student import, curriculum and report card, fee receipt and refund, parent communication, staff permissions and data export. Confirm the hosting location, payment availability and contract requirements for your country.
How can a school compare software costs for 500 students?
Ask each vendor for the same student count, campuses, modules and expected messaging usage. Compare subscription, setup, migration, training, support, processing fees and taxes in a stated currency. Then compare the renewal total and what changes when student numbers grow.
What should we check when replacing Excel with a school ERP?
Agree an import template and stable student identifiers, check duplicate rows and guardian links, and reconcile opening fee balances against the original ledger. Pilot the process with a sample and agree access to historical records before importing live data.