What to ask before replacing a legacy system
Almost every organisation has a system that everyone complains about but nobody wants to touch. It’s slow, it’s awkward, and it holds years of important data. But it works, and replacing it feels risky.
That instinct is a sensible one. Replacing a core system is a big decision, and the organisations that get it right usually start by asking better questions, not by shopping for software.
Here are the ones worth asking first.
1. What does this system actually do for us?
Not what it was built to do, but what people rely on it for today. Systems collect extra jobs over the years, and some of those jobs are invisible until they stop working.
2. Who depends on it, and what would they miss?
Talk to the people who use it every day, not just the people who manage it. They usually know the workarounds, the shortcuts and the things that would break.
3. What is the real risk of leaving it as it is?
Sometimes it’s security, because the platform is no longer supported or updated. Sometimes it’s cost, because maintaining it takes more time every year. Sometimes it’s people, because only one person understands how it works. Knowing which risk matters most helps you decide how urgent this really is.
4. What data do we have, and what needs to come with us?
Years of records, files and history don’t disappear on their own, and they can’t be lost in the move. Understanding what you hold, and what you actually need to keep, shapes the whole plan.
5. Can we make the change without disrupting the business?
The best migrations are ones your customers and staff barely notice. Ask how the change will be staged, tested and rolled out, and what happens if something goes wrong.
6. What will we need from it in three years?
It’s tempting to replace what you have with something newer and identical. But if the organisation has grown, added locations, or wants to connect other systems or use AI, the new platform should be ready for that.
7. Who looks after it afterwards?
A new system is only as good as the support behind it. Ask who monitors it, keeps it secure and continues to improve it once the project is finished.
A simple way to use these questions
You don’t need all the answers before you speak to anyone. Even working through a few of them with your team will show you where the gaps are, and that makes any conversation with a technology partner far more productive.
The goal isn’t to rush into a replacement. It’s to be confident that whatever you decide is based on how your organisation really works.
If you’d like to talk it through, we’re always happy to help you think it over.
Related
Is a spreadsheet holding your organisation back?
Five signs your spreadsheet has become a risk, and what a better option looks like.
Learn more
How to upgrade a large platform without disrupting operations
Thousands of users, years of content and a growing security risk. Here is how a large platform can be upgraded with confidence.
Learn more
Where to start with AI when you're not sure what's possible
A practical way to start with AI. Look at where your team loses time, ask three simple questions and begin with a small pilot.
Learn more