School ERP
Overcoming Staff Resistance When Launching a New School ERP
Most school ERP projects that fail do not fail on technology. They fail because staff quietly keep the old registers. Here is why teachers and office staff resist new software, and a launch plan that turns sceptics into users.
The Onflows team3 min read

The software is bought. The data is imported. The training session is done. Three months later, the class teachers still mark attendance in the paper register and someone types it in at the end of the week. The accountant keeps the old ledger "just in case". The ERP exists, but the school runs on paper.
That is how most school software projects fail. Not with a crash, but with quiet non-use.
Why staff resist
Resistance is rarely stubbornness. It usually has a reason:
- "It takes longer." If marking attendance takes three minutes on the software and one on paper, the paper wins.
- "I don't trust it." Staff who have lost work to software before keep a paper backup.
- "Nobody asked me." A system chosen without the people who use it feels imposed.
- "I'm not good with computers." Often unspoken, and often the real reason.
- "It's another thing." If the old register is still required, the software is extra work.
A launch plan that works
1. Involve users before buying
Let two or three teachers and the accountant try the shortlisted systems. Their objections in a demo are cheaper than their objections after launch. See how to choose the right school management software.
2. Start with one module that saves time
Do not launch everything at once. Pick the module that saves staff the most effort. Attendance is often a good first module: if it takes under a minute and teachers stop carrying registers, they see the benefit in a week.
3. Pilot with willing classes
Two or three classes with enthusiastic teachers. Fix the problems they find. Then expand, with the pilot teachers as helpers.
4. Train by role, briefly
A class teacher needs to know three things, not thirty. Short, role-specific training, a video they can rewatch, and a one-page guide beat a three-hour session.
5. Remove the old way
Set a date after which the paper register is no longer collected. As long as both exist, the paper wins.
6. Office hours
A fixed time each week when someone helps with questions in person. Many people who will not ask in a meeting will ask one-to-one.
7. Show the results
After a month, show staff what changed: attendance known by 9:30, receipts in seconds, no end-of-term retyping. People keep doing things they can see working.
The leadership part
If the principal still asks for paper reports, staff will keep making them. Leaders must use the system themselves and ask for information from it.
Where Onflows fits
Onflows gives each role its own home screen and help guides, with walkthrough videos for each persona, so training is short and repeatable. You can switch modules on as you are ready. We cover the wider transition in how to smoothly transition your school to a new ERP.
Frequently asked questions
How long does adoption take?
Most staff are comfortable within a term if the first module saves them time.
What about staff close to retirement?
Pair them with a colleague. Make sure the essentials take as few steps as possible.
Should we make it mandatory?
Eventually, yes, by removing the paper alternative. But only after the pilot has shown it works.
See the help guides and role homes in Onflows, or create your school.
Topics: School ERP, Implementation, Teachers, Choosing school software, Benefits of school erp software