Key points
- Write down your school's real problems and who will use the software before you look at any vendor.
- Separate must-have modules from nice-to-have ones so a long feature list does not decide for you.
- Ask every vendor the same questions about data ownership, export, backups, support, training and the full cost over three years.
- Insist on a demo that uses a small sample of your own data, not the vendor's ready-made demo school.
- Plan a phased rollout over several weeks, starting with student records and fees, and avoid going live in the middle of exams or admissions.
Buying school ERP software is one of the few decisions that touches every person in a school: the office clerk, the accountant, class teachers, the principal, parents and sometimes drivers. A poor choice leaves you with software nobody opens after the first month.
This checklist is written for owners, correspondents and principals of private and budget schools. It does not recommend any particular product. It helps you decide what you need, compare vendors fairly and avoid the common traps.
Step 1: List your problems before you shop
Most schools start by watching demos. That is backwards. A demo shows what a vendor wants to show. Start instead with a short meeting of the people who do the daily work, and write down answers to these questions:
- What takes the most time today? For many schools it is fee receipts, due lists, attendance registers, report cards or answering parent phone calls.
- Where do mistakes happen? Duplicate receipts, wrong concessions, missing transport fees, marks entered twice.
- What do parents complain about? Not knowing the balance due, late information about holidays, lost circulars.
- What does management want to see? Daily collection, pending dues by class, staff attendance, admission enquiries.
Rank the list. The top three or four problems are what the software must solve. Everything else is a bonus.
Who will actually use it
Write down each user group and their comfort with computers and phones. If most teachers are not confident with technology, a simple mobile app for attendance and marks matters more than an advanced dashboard.
Set a realistic budget
Decide on a budget range for the first year and for later years. School software is usually priced per student per year, as a flat annual fee, or as a one-time licence plus yearly maintenance. Also budget for things outside the licence: SMS or WhatsApp message charges, payment gateway charges, a printer for receipts, and staff time for data entry.
Step 2: Decide must-have and nice-to-have modules
Vendors often compete on the number of modules. More modules do not help if your staff only need five of them. Use a simple table like the one below and mark each row for your own school. The split shown is a reasonable starting point for a typical private school, not a rule.
| Module | Typical priority | Why it matters |
|---|---|---|
| Student records and admissions | Must-have | Every other module depends on accurate student data. |
| Fee collection, receipts and due reports | Must-have | Usually the biggest source of office work and disputes. |
| Student attendance | Must-have | Daily task; parents expect quick absence alerts. |
| Exams, marks and report cards | Must-have | Must match your board's grading pattern. |
| Parent communication (app, SMS or WhatsApp) | Must-have | Reduces phone calls and lost circulars. |
| Staff records and staff attendance | Usually must-have | Needed for payroll and substitution planning. |
| Timetable | Nice-to-have for small schools | Very useful once you have many sections and shared teachers. |
| Transport and bus tracking | Depends | Essential if you run buses; irrelevant if you do not. |
| Payroll | Depends | Some schools prefer to keep payroll with their accountant. |
| Library, inventory, hostel | Nice-to-have | Add later if the core modules are working well. |
Check that report cards support your board. State board schools in Telangana and Andhra Pradesh commonly use formative and summative assessments, which we explain in CCE, FA and SA grading explained. CBSE schools follow a different structure. Ask the vendor to show a report card in your exact format.
Step 3: Questions to ask every vendor
Ask all shortlisted vendors the same questions, in writing if possible, so you can compare answers side by side.
Data ownership and export
- Who owns the data we enter? Is this written in the agreement?
- Can we export all student, fee and marks data to Excel or CSV at any time, without asking support?
- If we stop using the software, how long do we have to take our data, and in what format?
- Where is the data stored, and who on your team can see it? Our guide on student data privacy for schools lists more points to check.
Backups and security
- How often is data backed up, and how many days of backups are kept?
- Has a restore ever been tested? How long would it take?
- Can we give each staff member their own login with limited permissions, so a teacher cannot edit fee records?
- Is there an activity log showing who changed a receipt or a mark?
Support and training
- What are your support hours and days? Is support available during the first weeks of the academic year, when you need it most?
- How do we contact support: phone, WhatsApp, email, ticket?
- How much training is included, and is it in person or online? Can new staff be trained later?
- Will you help import our existing student and fee data, and is that included in the price?
Costs
- What is the total cost for three years for our current student strength?
- Are SMS, WhatsApp messages, app listing, extra users or extra branches charged separately?
- How much can the price increase at renewal?
- Is there a setup, customisation or data migration fee?
Apps and payments
- Are parent, teacher and staff apps available on Android and iPhone? Are they listed under the school's name or the vendor's name?
- Which payment gateway is used for online fee payment? Who holds the merchant account, the school or the vendor? Where does the money settle, and how quickly?
- Do online payments automatically create receipts and update dues, or does someone have to match them manually?
Red flags to watch for
- No way to export your own data, or export only on request for a fee.
- Prices that change depending on how quickly you sign, or a quote that is not in writing.
- Long contracts with heavy advance payment before you have used the software in real conditions.
- A demo that only uses a perfect sample school and avoids your actual fee structure.
- Vague answers about backups, such as "the server is safe" with no details.
- No references from schools similar to yours in size and board.
Step 4: Run a demo on your own data
A demo on your own data shows problems that a generic demo hides. Prepare a small test pack before the session:
- Pick two classes and take 15 to 20 student records each, including a few tricky ones: siblings, a student with a concession, a transport student, and a mid-year admission.
- Write down your real fee structure for those classes, including instalments and late-fee rules. Our fee structure guide can help you organise it.
- Ask the vendor to set these up in a trial account, then have your own office staff do the following, not the salesperson:
- Collect a part payment and print a receipt.
- Apply a sibling concession.
- Generate the due list for one class.
- Mark attendance for one class from a phone.
- Enter marks for one test and print a report card.
- Send a test message to a parent.
- Time each task and note where staff got confused.
- Ask for the trial login for a week so staff can try again without the vendor watching.
Step 5: Plan the rollout
Most failed ERP projects fail at rollout, not at selection. Avoid switching everything at once. A phased plan works better, and timing matters: try not to go live in the middle of admissions, board exams or the first fee collection week.
| Phase | Suggested duration | What happens |
|---|---|---|
| Preparation | 1 to 2 weeks | Clean student lists, confirm fee structure, decide user roles and logins. |
| Data import | About 1 week | Import students, parents, classes and opening fee balances. Check totals against your registers. |
| Office go-live | 2 to 3 weeks | Fees and student records move to the software. Keep a parallel register for the first few days only. |
| Teacher go-live | 2 to 4 weeks | Attendance first, then marks entry. Short hands-on training per group. |
| Parent go-live | After the above | Launch the parent app or messages once data is accurate, so parents do not see wrong dues. |
| Review | After one term | Check what is used and what is not. Retrain or adjust settings. |
The durations are a guide only. A school with one office person and 300 students may move faster; a multi-branch group will take longer. Name one internal person as the project owner who has authority to make decisions and is the single point of contact with the vendor.
If you are planning a wider move away from paper, our digital school checklist covers devices, internet and staff readiness.
If you would like to see how one system handles these checks, you can book a free demo of Nipun Schools and bring your own sample data.
Frequently asked questions
Is cloud-based school software safe for student data?
It can be, if the vendor keeps regular backups, uses secure logins and limits who can see data. Ask for specifics on backups, access control and activity logs rather than general assurances, and make sure you can export your data at any time.
When is the best time to switch to a new school ERP?
Many schools prefer to set up during the summer break, before the new academic year, so fee collection starts cleanly in the new system. Avoid switching during admissions, exams or the first fee collection week.
Should a small school buy ERP software at all?
Even a school with a few hundred students can save time on receipts, due lists and parent messages. Start with only the core modules: student records, fees, attendance and communication. Add others later if needed.
How long does it take staff to learn a school ERP?
It depends on the software and on staff comfort with technology. Office staff usually need a few days of practice on daily tasks. Teachers mostly need to learn attendance and marks entry, which should take less than an hour if the app is simple.
What should be in the agreement with the vendor?
At minimum: the price and what it includes, renewal terms, data ownership, your right to export data, what happens to data if you leave, support hours and response times, and who holds the payment gateway merchant account.
