How Do You Change School Management Systems? Part 1: Preparations

Changing your school management system can feel like a major undertaking, especially if it’s your first time leading a project like this. It’s not just about replacing software; it’s about rethinking how your school manages data, connects systems, and supports staff, students, and families.

Today, that challenge is even more complex. Schools are no longer choosing between simple administrative tools; they’re navigating a landscape of School Management System (SMS), School Information System (SIS), and Learning Management System (LMS) platforms, each with overlapping functionality and different roles across the school. Understanding how these systems fit together is often the first hurdle.

At the same time, expectations of technology vendors have shifted. Schools are no longer looking for software providers; they’re looking for long-term partners who can support them through change, growth, and ongoing innovation.

When Is It Time to Move On?

Most schools have invested heavily in their current system over many years. That investment can make it difficult to step back and evaluate whether the system is still the right fit.

This is where the sunk-cost fallacy, based on the work of Nobel Prize-winning psychologist Daniel Kahneman, comes into play. The sunk-cost fallacy describes the irrational tendency to continue a project, investment, or activity simply because time or money has already been invested. On an individual level, this can mean continuing to watch a terrible film just because you've already paid for your ticket. However, whilst you're only losing 90 minutes to a bad movie, the ramifications can be huge when the same thought processes impact major decision-making.

The fallacy can affect people at all levels, from politicians to business leaders, but fortunately, studies have shown that once you're aware of the effect, it becomes much easier to overcome. Check out this quiz to determine how susceptible you are to the sunk cost effect, which can help you be more aware of how it may impact your decisions.

Schools can continue investing in systems that no longer serve them, simply because of the time and effort already committed. However, past investments shouldn’t dictate future decisions, particularly when your system limits your ability to operate effectively.

In many cases, the issue isn’t just the software; it’s the relationship behind it.

Schools often experience:

• Delayed or undelivered roadmap features
• Limited training and onboarding
• Inconsistent support after implementation

Over time, this creates a growing gap between what schools need and what their system delivers.

Recognising the Signs

One of the clearest indicators is growth. As schools expand or evolve, legacy systems often struggle to keep up.

But increasingly, the trigger for change isn’t just functionality, it’s alignment.

Schools are asking:

• Does this system still support our long-term strategy?
• Is the vendor evolving with us?
• Are we getting value beyond the software itself?

Vendor ownership changes, shifting priorities, and a lack of investment in development can all contribute to systems falling behind.

Compliance is another growing pressure point. With evolving requirements such as Payday Super, schools need systems that can adapt quickly and reliably. If your platform cannot keep pace, it creates risk and additional administrative burden.

Understanding Your System Landscape

Before making any decisions, it’s important to understand what type of system your school is actually using.

Many schools operate across a mix of SMS, SIS, and LMS. While these systems can overlap, they serve different purposes. Check out this blog where we discuss these terms in detail and how they differ – SMS vs SIS vs LMS.

An SMS like TASS brings together finance, payroll, student data, and administration into a single platform, acting as a single source of truth. In contrast, SIS platforms focus primarily on student data, and LMS platforms support teaching and learning.

Without a clear structure, schools can end up with fragmented systems, duplicated data, and inefficient workflows. Recognising this early helps shape a more effective approach to change.

Getting Prepared Internally

Once you’ve identified that it’s time to explore a new system, preparation should begin before engaging with any vendors. The most successful projects start with strong internal alignment. This begins by identifying who will be involved and how decisions will be made. While Business Managers and IT teams are typically central to the process, it’s equally important to involve school leadership, administrators, and teaching staff. Each group interacts with the system differently, and their input helps ensure the final solution works in practice, not just in theory.

Rather than involving everyone in every decision, many schools take a structured approach by appointing representatives from key areas. This allows for meaningful input without slowing the process down. Targeted workshops or discussions with specific departments can also help uncover challenges and opportunities that might otherwise be missed.

Setting Timelines and Budget

With stakeholders defined, the next step is to establish a realistic timeline. Most schools underestimate how long this process can take. From initial research through to implementation, it’s common for a full project to span several months. Working backwards from your ideal go-live date, often aligned with school terms, helps ensure each stage is achievable. For example, a Term 4 launch in 2027 may require research and planning to begin as early as Term 1 in 2026.

Budget planning should also happen early. Beyond software licencing, schools need to consider implementation, training, and data migration. However, this should be weighed against potential cost savings, particularly where a modern SMS can consolidate multiple systems into a single platform, reducing administrative overhead.

Defining Goals and Priorities

With a clear understanding of your current environment, you can begin to define your project goals. These goals will guide your entire project, from vendor selection through to implementation and should reflect both your immediate challenges and long-term strategy. For many schools, priorities include:

• Consolidating systems

• Specific additional features or functions

• Easier integrations with APIs

• Time savings (i.e. through workflows and automation)

• Better value/cost savings

• Moving into the cloud

• Australia data residency

• Improved security or stability

• Community engagement through mobile apps for staff, parents, and students

• Data analytics and reporting on student performance

• Reliable and local customer service

• Security standards such as ISO 27001

Increasingly, there is also a focus on flexibility, ensuring the system can evolve alongside the school rather than becoming a limitation over time. Platforms like TASS support this through integrated functionality, automation, and APIs, enabling schools to build solutions tailored to their specific needs.

Identifying Risks Early

No major project is without risk, but identifying potential challenges early makes them far easier to manage.

• Staff availability is one of the most common considerations. Key stakeholders need to be involved throughout the project, and factors such as leave, leadership changes, or governance processes can impact timelines.

• It’s also important to consider other initiatives happening within the school. Large projects such as campus expansions or structural changes can compete for time and resources. Aligning these timelines helps ensure your project remains achievable.

• Some staff may be hesitant to adopt new systems, particularly if they are comfortable with existing processes. Involving these individuals early and maintaining clear communication throughout the project can significantly improve engagement. Our blog has valuable tips on how to navigate this period - Change management marathon.

• Finally, operational impact and data integrity must be carefully managed. Schools often choose to implement during quieter periods, such as holidays, to minimise disruption. Ensuring your chosen vendor has strong processes for secure data migration and validation is critical to maintaining confidence in the transition. Also, ensure that your final vendor can securely handle your data by verifying their certification against standards such as ISO 27001.

Preparing for a Modern System

Once you’ve identified the need for change, preparation becomes critical. This isn’t just about selecting new software; it’s about designing a better way of working. That includes:

• defining your system architecture (what sits where)
• identifying integration needs
• aligning stakeholders across the school
• setting clear project goals

Final Thoughts

Changing your school management system is not just a technical project; it’s a strategic decision.

It’s an opportunity to:

• Simplify your systems

• Improve data quality

• Reduce manual processes

• And, build a stronger foundation for the future

Hopefully, this breakdown helps to make the process of switching systems seem less daunting. Stay tuned for Part Two, in which we’ll explore how to evaluate vendors not just based on features, but on their ability to support your school as a long-term partner.