Moving your school off registers and Excel: a 30-day plan

The hard part of adopting school software is almost never the software. It is the fortnight where your office is running two systems, your staff are unsure which one is authoritative, and a parent is standing at the counter while somebody works out where the receipt book went.

This is a plan for getting through that fortnight with the least disruption. It assumes a school of a few hundred to a couple of thousand students with a small office team, which is the common case.

Before you start: pick the right month

This matters more than anything else in this article.

Do not switch during fee week. The start of term is when your office has the least slack and the highest cost of a mistake. Every rollout that goes badly wrong went badly wrong in fee week.

The right window is a vacation. For schools in the Kashmir valley, the extended winter break is close to ideal — the office has capacity, there is no queue at the counter, and staff can be trained without being pulled away every ten minutes. For Jammu division and most of India, the summer break serves the same purpose.

If you cannot wait for a vacation, pick the quietest month mid-term and accept that it will take longer.

Week 1 — Clean and export what you already have

You are not starting from nothing. Your records exist; they are just distributed across a register, a spreadsheet and somebody’s memory.

Day 1–2: Find the authoritative student list. There is usually one Excel file that is more correct than the others. Find it, and decide it is the source of truth. Do not attempt to merge four versions.

Day 3–4: Clean it. This is the genuinely tedious part and it cannot be skipped:

• One row per student, one column per field. No merged cells.
• Split combined columns — “Name (Class)” becomes two columns.
• Standardise class names. 5A, V-A, Class 5 A must all become one form.
• Check phone numbers are complete and correctly formatted. These become parent logins, so errors here surface later as support calls.
• Remove students who have left, into a separate sheet — you will import them as archived records.

Day 5: Export staff and fee structure. A staff list with designations and salary, and your current fee structure written out per class with amounts and frequency.

The single best predictor of a smooth rollout is the quality of the spreadsheet you start with. An afternoon spent cleaning columns saves a fortnight of correcting records later.

Week 2 — Import and configure

Day 6–7: Import students and staff. Your vendor should do this, and it should be included. You upload the CSV, map your columns to theirs, preview exactly what will be created, and confirm. If a vendor asks your staff to type records in manually, treat that as a serious warning sign.

Day 8–9: Configure classes, sections and subjects. Straightforward, and mostly it is checking that what came in from the import is right.

Day 10: Configure fee structures. Give this real attention. Get the fee heads right — tuition, transport, admission, examination — with the correct frequency for each. Set up your concessions and discounts as discounts rather than adjusted amounts, so they survive an audit.

Day 11–12: Set up admin users and permissions. Decide who sees what before anyone logs in. The fee clerk gets the fee counter. The exam coordinator gets exams. Only the owner and principal get everything. Retrofitting permissions after staff have grown used to seeing everything is an awkward conversation.

Week 3 — Run the fee counter in parallel

This is the week that determines whether the rollout sticks.

Day 13–15: Train the office team properly. Not a demonstration — sit them down and have them do the tasks. Record a payment. Issue a receipt. Find a student. Check a defaulter list. The people who will use it daily must have used it before you depend on it.

Day 16–20: Run both systems. Every payment gets recorded in the software and in the register. Yes, it is double work for a week. Do it anyway.

At the end of each day, reconcile: does the software’s total match the register’s total? For the first two days it will not, and the discrepancies will teach you what your staff are misunderstanding. By day four or five they should match every time.

When they match consistently for three consecutive days, the register is redundant. That is your objective evidence to switch, rather than a feeling.

Week 4 — Switch, then add attendance

Day 21: Stop the parallel run. The software is now authoritative for fees. Keep the register in a drawer for a month — you will not need it, but its presence is reassuring.

Day 22–25: Turn on parent communication. Start with fee receipts going out automatically, because that is the highest-value, lowest-risk message and parents are unambiguously pleased to receive it. Then enable the WhatsApp bot so parents can check dues themselves. Send one announcement to all parents explaining the new number and what they can do with it.

Day 26–30: Add daily attendance. Now, and not before. Attendance involves every teacher rather than a couple of office staff, so it is the change with the widest blast radius. Start with two or three willing classes for a few days, fix whatever comes up, then roll out to everyone.

What to leave for next term

Deliberately not in the first 30 days:

• Exams and results — do these in the run-up to your next exam cycle, when the workflow is fresh in everyone’s mind
• Payroll — move at the start of a month, once fees are stable
• Timetable — most useful at the start of an academic year

Trying to move all of it in one month is the most common way this goes wrong. Records and fees are 80% of the value and 30% of the disruption. Take that first.

The rule underneath all of this

Never let staff work in two systems for more than one week. Parallel running is a verification tool, not a way of life. Beyond a week, people quietly pick a favourite, the two diverge, and you end up with two half-correct sets of records — which is worse than either system alone.

One week of parallel running, a clear reconciliation test, then commit.

---

If you want help planning this for your school, book a walkthrough — we do onboarding, data import and staff training as part of the price, and for schools in Kashmir and Jammu we can do it in your office. You can also read why school ERP rollouts fail for the failure modes to avoid.