Why Schools Stay With School Management Systems They’ve Outgrown

From years of investment to concerns about migration, explore four reasons schools keep systems they’ve outgrown—and the questions worth asking about each.

A school can recognise that its management system is creating extra work and still decide to keep it.

Knowing where the problems lie doesn’t automatically make replacing it feel like a good idea.

Your team has learned to use it. Someone knows how to get the reports right. A migration sounds expensive, disruptive, and difficult to fit into an already busy year. And who can guarantee that the next system will be better?

Those concerns deserve proper answers. But they also deserve proper examination.

What keeps schools attached to systems they’ve outgrown—and do those reasons always hold up when you consider the cost of staying?

Reason #1: “We’ve already put so much into this”

Your current system represents more than a subscription fee.

Someone configured the records, built the templates, and worked out how to produce the reports your school needs. Staff attended training, learned through experience, and eventually became comfortable. Some of that work may have taken years.

So when someone suggests replacing the system, the obvious question is: Are we really going to do all of that again?

Replacing it can feel like admitting that effort was wasted. But the time already spent cannot be recovered by keeping the system longer. What matters now is how much work each option will require in the years ahead.

If staying means repeating the same manual tasks every term, that earlier investment may be drawing your school into further expense.

Ask:

• How much staff time goes into maintaining and working around the current system each term—and what does that time cost?
• What would a switch require, including staff time?
• Which existing processes and decisions could carry over?

A system should earn its place through what it enables today. But any proposal to replace it needs to account honestly for the work of getting there.

Reason #2: “Our team already knows how to make it work”

Most schools have someone who understands the system better than anyone else.

They know which export to use, which fields need checking, and why a report only works with a particular filter. Colleagues turn to them when something goes wrong. Their expertise keeps important work moving.

That person may be cautious about a replacement. They may defend a process that looks unnecessarily complicated to everyone else.

There are understandable reasons for that. They know what can go wrong. They have spent years solving problems that others barely see. And a change may unsettle a role in which they have become trusted and capable.

The workaround may be inefficient, but the knowledge behind it is valuable.

But how much of it is being used to compensate for the system?

If routine work depends on their intervention, the school has a bottleneck. That person also carries a burden: every question, exception, and deadline finds its way back to them. Taking leave becomes harder when nobody else can confidently cover the work.

Bring that person into the assessment early. Ask them to show where the system needs help, what each workaround achieves, and what a replacement must handle reliably. Give them a meaningful role in shaping the change and time to learn the new system.

Their experience can help the school make a better choice. And a better system should give them more room to use that experience beyond keeping routine tasks on track.

Reason #3: “What if the migration goes wrong?”

Keeping the current system has a familiar cost. Replacing it creates a visible decision with someone’s name attached.

What happens if records don’t transfer correctly? If staff cannot complete an essential task? If the change disrupts reporting or leaves families confused? The person recommending a switch may worry that every problem will come back to them.

Meanwhile, the extra work caused by staying is spread across the school and absorbed into ordinary routines: delays, corrections, dependence on individual staff, and time taken away from other work.

It helps to examine both sets of risks. What could go wrong during a switch? What already goes wrong—or requires constant attention—under the current arrangement?

A credible proposal needs clear agreement on the problems the change should solve, named owners across the affected teams, and staff time allocated to preparation, testing, and training.

Then ask how the migration risks would be managed:

• Who will check transferred data and test essential workflows?
• Which school deadlines must the implementation plan accommodate?
• What support will be available when problems arise?

Clear answers won’t remove every difficulty. But a practical plan, backed by the people who control the budget and workload, can make the change far more manageable than the vague prospect of “moving everything to a new system.”

Reason #4: “How do we know the next system will be better?”

Perhaps your school has heard ambitious promises before. Perhaps the current system also looked straightforward in a demonstration.

Now your team knows how much complexity can sit behind a polished interface. They are right to ask whether a replacement will solve the problem or simply introduce different limitations.

That scepticism can protect your school from another disappointing purchase—provided it leads to closer examination.

Start with the tasks that currently cause trouble. Ask a prospective provider to demonstrate those specific workflows using realistic school scenarios:

• Can staff produce the report they actually need?
• What happens when information changes halfway through a process?
• Where will staff still need to export, re-enter, or check data?
• What support will be available during implementation and afterwards?

Ask about limitations as directly as capabilities. Where possible, speak with a school with similar requirements about implementation, everyday use, and support.

You don’t need certainty that every task will be effortless. You need credible evidence that the replacement will address the problems driving your search.

Give staying the same scrutiny as switching

Competing priorities, staffing, or a difficult implementation window may affect when your school can switch. But postponing the change still has a cost.

If you decide to wait, give that decision a clear basis and a review date.

Record the current costs, the concerns about changing, and the evidence still needed. Agree on what would prompt another look: a recurring reporting problem, growing staff workload, or a requirement the system can no longer meet.

The question is whether your school has enough evidence to judge the cost of staying.

Count the recurring work. Involve the people who understand it. Turn migration worries into planning questions, and doubts about replacements into requirements that providers must demonstrate.

Your concerns may identify something that needs careful preparation. They may also rest on assumptions that no longer hold up.

Before committing another year to your current system, ask yourself: what will that year cost? And what evidence do you need to make a better decision?