Plan the switch around your session start
The safest time for a school to go live on ERP is at the start of an academic session or, failing that, at the start of a term, once the office has a clean student list, a confirmed fee chart and trained staff. Going live in the middle of exams, the admission rush or the busiest days of fee collection is what causes most troubled rollouts.
This plan is for the principal, the office head and whoever coordinates IT at your school. It sets out five phases in order: data collection, setup, training, a parallel run and cut-over. How long each phase takes depends on your school's size, the state of your records and how much time staff can give, so the plan is built backwards from your own dates rather than from fixed weeks. Session start dates differ by board and state; many schools begin in April and others later, so check your session dates before fixing anything.
Work backwards from your go-live date
Fix the go-live date first, then place each phase before it. Leave spare time between phases, because data collection nearly always takes longer than expected.
| Phase | Main work | Owner at school | Finished when |
|---|---|---|---|
| 1. Data collection | Student, staff, fee and dues records gathered and cleaned | Office head | Every class teacher has signed off their class list |
| 2. Setup | Classes, sections, subjects, fee heads, users and permissions configured | Vendor, with the accountant | Test receipts and a test report card come out correctly |
| 3. Training | Office staff first, then teachers, then management | Principal schedules; vendor trains | Each user has done their own task on practice data |
| 4. Parallel run | Old method and new system used side by side | Accountant | Daily totals have matched for the agreed period |
| 5. Cut-over | Old registers closed; the system becomes the record | Principal | Principal signs off and the old method stops |
Phase 1: Collect and clean your records
Ask the vendor for its import template first, so data is collected in the right columns from the start. Then gather the following.
- Student details: admission number, full name, date of birth, class and section, roll number, parents' names, phone numbers and address.
- Transport details for students who use school transport: route and pickup point.
- Staff details: name, role, subjects and classes taught, and salary details if payroll is part of the plan.
- The fee chart: every fee head, the amount for each class, due dates, concession rules and the late fine rule.
- Opening dues: what each student owes on the day you switch, agreed and signed by the accountant.
Cleaning matters more than speed. Print each class list and ask the class teacher to correct spellings, add missing phone numbers and strike out students who have left. Fix duplicate admission numbers. A student entered wrongly now will appear wrongly on every receipt and report card afterwards.
Phase 2: Set up classes, fee heads and users
With clean data, the vendor configures the system: classes and sections, subjects for each class, fee heads with amounts and concessions, exam terms and grading, and a login for each user with the right permissions. Student and staff records are then entered or imported. If you are unsure how fee heads and concessions should be structured, our article on fee and attendance modules explains them.
Before moving on, test the setup with real cases. Collect a test fee for a student who has a sibling concession and uses transport. Check the due list for one full class. Enter sample marks and print a report card in your format. Confirm that a class teacher's login cannot open the fee screens. Every mistake caught here is far cheaper than one a parent finds.
Phase 3: Training in small groups, outside teaching hours
Train office staff first, because the fee counter is where a problem shows up first. Teachers come next, in small groups by role, at times that do not take them out of class: after school, on a staff meeting day or on a non-teaching day. Management training is short and focuses on reports and approvals.
- Office and accounts: fee collection, receipt cancellation, due lists, the day-end report, admissions and changes to student records.
- Class teachers: marking attendance, viewing their class list and entering marks.
- Exam in-charge: setting up exams, checking marks entry progress and publishing results.
- Principal and management: daily and monthly reports, concession approvals and user permissions.
Ask each person to do their own task on practice data during training rather than just watch. Name one staff member as the in-house helper whom others approach first. A one-page guide for each role, showing the three things that person does daily, is more useful than a long manual.
Phase 4 and 5: Run old and new side by side, then cut over
During the parallel run, every fee is entered in the system and also recorded the old way, and attendance is marked in both. At day end the accountant compares totals. Differences are investigated the same day, while people still remember the transaction.
Keep the parallel run short and clearly defined. Covering one full fee cycle and one month of attendance is a common choice. Running both methods for months tires staff and lets them go on trusting the register instead of the system.
Cut-over checklist
- Daily collection totals have matched for the agreed period.
- The accountant has checked the due list for every class.
- Every teacher has marked attendance independently on the system.
- Backups are running, and someone has confirmed they can be restored.
When these are met, the principal signs off, the old fee registers are closed with a final total, and the system becomes the official record.
Weeks to keep clear of go-live
Some weeks are a poor time for any change. Mark them on the school calendar before you fix dates.
- Exam and result weeks: teachers are busy with papers and marks, and a report card error is the most visible mistake a school can make.
- The admission rush: the office is already stretched with forms, enquiries and documents.
- The opening days of each fee cycle: the queue at the counter leaves no room for staff to learn new screens.
- Long vacations, for teacher training: the office can use a vacation for setup, but teachers are away, so their training has to happen before or after.
- Board practicals and inspections: staff attention is needed elsewhere.
The first month after go-live
Expect questions and small fixes. Keep a simple issue list with the date, the user, what happened and what was done, and review it with the vendor every week for the first month. Most entries will turn out to be training points rather than software faults, and they show who needs a short refresher.
Add optional modules only after the core is stable. Library, transport, homework posting, payroll and the parent app can each be introduced later as a small project of its own. Before you open parent logins, agree what the school will send through them; our guide on rules for parent communication covers this.
How MATROP implements its school ERP
For our school management ERP, MATROP follows the same order. We start with a requirement discussion about your current process, fee structure, exam pattern and modules. Then come setup and configuration of classes, sections, subjects, fee heads, users and permissions; student and staff data entry or optional import, with verification; admin and teacher training with practical use; go-live with support during the initial days; and ongoing support, updates and backups, with an optional AMC. We do not promise a fixed number of weeks, because the timeline depends on your data and your staff's availability, but we plan it with you around your session dates.
Sometimes the right advice is to wait. If the session has started and exams are close, plan for the next term boundary instead. If management has not finalised the fee structure, setup cannot be completed. If you have not chosen a product yet, begin with our guide on choosing school ERP software. Schools in and around Ranchi can also meet us at our office; you can find the address and hours on our contact page.
Questions people ask
Can a school switch to ERP in the middle of the session?
Yes, at a term or month boundary, provided the opening dues for every student are agreed and entered. Marks for terms already completed can be entered later or kept in the old records.
Do we have to enter previous years' records before going live?
No. Current students, staff, the fee chart and opening dues are enough to start. Older records can be added later or kept in the old files, depending on how often you need them.
What if a teacher keeps using the paper register after cut-over?
Find out why first; it is often a login problem or a gap in training. Give a short one-to-one session, and make it clear that only system attendance counts for reports from the cut-over date.
Who at the school should coordinate the rollout?
One person with authority, often the office head or a senior teacher, who can schedule training, chase data and take decisions with the principal. The vendor cannot do this role for you.
