Moving From Registers and Excel to School Software: A Step-by-Step Checklist

Many schools in India still run on admission registers, fee receipt books, attendance registers and a few Excel files maintained by one office clerk. It works until that clerk goes on leave, a parent disputes a fee balance, or the management wants a report in a hurry. School software can fix these problems, but only if the switch is planned. Schools that buy software and skip the planning often go back to registers within a few months.

This checklist walks through each step, from deciding whether you are ready to reviewing the first month. It applies whichever software you choose. If you have not chosen a vendor yet, read our guide on how to choose a school ERP first.

Step 1: Check your readiness

Answer these questions honestly before you start:

• Who owns the project? Name one person, often the correspondent, principal or office manager, who will make decisions and follow up.
• Is there time? Avoid starting in the busiest weeks, such as admissions season or exam weeks. The start of a term, or a quieter month, is easier.
• Do you have devices and internet? At least one reliable office computer, a printer for receipts if needed, and a stable internet connection with a backup such as a mobile hotspot.
• Are staff willing? Talk to office staff and teachers early. Explain what will get easier for them, not only what management will gain.
• Is your data available? Locate current student lists, fee records and staff details. If they are scattered across registers, plan time to compile them.

Step 2: Choose your modules

School software usually offers many modules. Do not switch on everything on day one. Pick what solves your most painful daily tasks first.

Step 3: Clean your student data

This is the most important step and the one most schools rush. Prepare one spreadsheet with one row per current student. Use consistent formats throughout. A typical template looks like this; your vendor may provide its own format.

Cleaning checklist:

• remove duplicate rows and students who have left;
• check every mobile number has 10 digits;
• make class and section names identical in every row;
• fill missing dates of birth from the admission register;
• ask class teachers to verify their class list against the attendance register.

Collect only the data you need. Our guide on student data privacy for schools explains why less data means less risk.

Step 4: Import the data

1. Import a small test batch first, such as one class.
2. Check that names, dates and phone numbers appear correctly in the software.
3. Fix format problems in the spreadsheet, not one by one in the software.
4. Import the rest of the school.
5. Compare totals: number of students per class in the software must match your registers.
6. Import staff records next, then set up classes, subjects and fee structures if not already done.

Keep the original registers and spreadsheets safely. Do not destroy any paper records; schools must preserve admission registers and similar records as per education department rules.

Step 5: Carry forward fee balances

Fee balances cause the most disputes, so handle them with care.

• Set up the fee structure first, by class and fee head, as decided by management. Our school fee structure guide can help.
• Choose a cut-off date. All receipts up to that date go into the opening balance; all receipts after it are entered only in the software.
• Prepare an opening balance list for every student: total due, total paid and balance as on the cut-off date.
• Have the accountant and the correspondent or principal check and sign this list.
• Enter opening balances and check a sample of students against receipt books.
• If a parent disputes a balance, check the receipt book and correct the entry with a note, rather than deleting records.

For more on fee processes after go-live, read school fee collection best practices.

Step 6: Set up staff roles and logins

Give each person their own login with access only to what they need. Never share one admin password among staff.

Decide who can edit or cancel receipts and who can give concessions. Limit these permissions to one or two senior people.

Step 7: Train your staff

• Train by role. Fee clerks do not need exam training, and teachers do not need fee training.
• Keep sessions short and practical. Each person should complete real tasks during training, such as issuing a test receipt or marking attendance.
• Write a one-page cheat sheet for each role with the five most common tasks.
• Name one "super user" in the office who can answer basic questions before calling the vendor.
• Plan a second short session a week after go-live, when real questions have come up.

Step 8: Run both systems in parallel, briefly

For a short period, often two to four weeks, continue the old method alongside the software for critical tasks like fees and attendance. Each day, compare totals: fee collected, students present. Fix any differences. Once totals match consistently, stop the old method. A parallel run that goes on for months doubles everyone's work and staff lose interest, so set an end date in advance.

Step 9: Roll out the parent app

Parents need clear instructions, not just a download link.

1. Inform parents in advance through a circular and the class teacher, explaining what the app will show: attendance, fees, homework, circulars.
2. Share simple step-by-step instructions, ideally with a short demo at a parent meeting.
3. Make sure the parent's registered mobile number is correct, because most apps log in with it.
4. Keep a help desk at the office for the first few weeks for parents who struggle.
5. Continue other channels for parents who do not use smartphones.

Our guide on parent communication for schools has more ideas.

Go-live checklist

• All current students imported and totals match registers.
• Fee structures and opening balances entered and signed off.
• Every staff member has an individual login with the right role.
• Receipt format, school name and logo checked on a printed sample.
• Backup and data export options understood.
• Vendor support contact and hours shared with the office.
• Parents informed about the change and the parent app.
• Old system end date announced to staff.

First-month review

After about a month, hold a short meeting with office staff, a few teachers and the vendor. Review:

• tasks that are faster now, and tasks that still take too long;
• errors found in data, and whether they have been fixed at the source;
• how many parents are using the app, and why others are not;
• whether any staff are still keeping private Excel files or registers, and why;
• which modules to add in the next phase.

To see how these steps work in practice, you can book a school ERP demo and walk through the process with real data.

Frequently asked questions