School ERP rollout — replacing the register, the fee book and the phone calls
A School Management Software rollout with the part that actually decides success: data migration and training by role. The software was the easy half; reconciling four years of fee records and getting the front desk comfortable took the planning.
- 4 years
- Of fee history migrated and reconciled
- 3 weeks
- From kick-off to go-live
- 2 roles
- Separate training tracks run
- Same day
- Attendance reaching parents
These figures are illustrative unless the client supplied measurement data. Replace them with measured values
before publishing — see the note at the top of content/portfolio.php.
The problem
The school ran student records in a register, fee collection in a bound receipt book, and parent communication through class WhatsApp groups. The office could answer any question asked of it, but only by hand — and the answer took twenty minutes.
Three things had to be true for the rollout to be worth it: fee outstanding had to be visible per student, attendance had to reach parents the same morning, and the office staff had to be able to run it without a developer on standby.
What we built
-
1
Configure to the school, not the reverse
Fee heads, class naming, grade scale, report card layout and permission roles were configured from the school's existing documents. No process was renamed to fit the software.
-
2
Data migration reconciled line by line
Student lists, guardian contacts and opening fee balances were imported and then reconciled against the receipt book with the accountant present. This was the single most valuable two days of the project.
-
3
Training split by role
The office and the teaching staff use almost disjoint parts of the system. One combined session would have spent half the time explaining screens the other group never opens.
-
4
A term boundary as the switch-over point
Going live mid-term invites a reconciliation problem. Switching at a natural boundary kept the opening balance honest.
-
5
Parallel running for the first week
The receipt book stayed in use for one week alongside the system, so the staff could verify the new numbers against the old process before trusting it.
Outcome
The system is now the record of truth, and the office answers "what does this student owe" from one screen instead of a receipt book. The transferable lesson is that a school ERP rollout is a data and training project that happens to include software — implementers who treat it as an installation are the ones whose customers stop logging in after two months.
What we would carry forward
- Reconciling opening balances with the accountant is the highest-value day of the project.
- Training split by role beats one thorough session for everyone.
- Never cut over mid-term if a term boundary is available.
Related
Other case studies: CalculatorBest · Loan Pipeline Dashboard
Free consultation
Have a similar problem?
Describe it in a few sentences and we will tell you what it would take — and whether we are the right people for it.
We reply within one business day. · No obligation