When the system you run on is one nobody can change.
It was built years ago, by someone who has since moved on. It still takes the orders or runs the schedule. But every change takes a month, it only works in the office, and one person is the reason it still runs.
How you know it's time.
- Simple changes take weeks, or never happen.
- One person or one outside contractor is the only one who can touch it.
- It runs on a server or software version that no longer gets security updates.
- Staff retype its data into newer tools, and remote staff can't reach it at all.
It isn't anyone's fault.
Old systems hold years of business rules nobody wrote down, which is exactly why they're hard to replace. A full rewrite promises a clean break but changes everything at once, and the old system keeps changing while the new one is built. So most companies wait, and the risk grows quietly.
What the work looks like.
-
1
Decide what really needs replacing
Some systems should be wrapped or left alone. We look at what is actually holding you back before recommending a rebuild.
-
2
Learn the hidden rules
We sit with the people who use it and the person who knows it best, and read its data, so the odd rules that matter get carried across on purpose.
-
3
Replace one piece at a time
Each piece of work moves to the new system in its own step, starting with the one that hurts most. Every step is useful by itself.
-
4
Run old and new side by side
Both systems handle the same work until the results match and your team trusts the new one. The old system stays available, read-only, until it's safe to switch off.
Common questions.
Should we rewrite it from scratch?
Rarely. Rewrites take longer than planned and change everything at once. Replacing it piece by piece is usually safer. Our guide on modernizing a legacy system covers the trade-offs.
Our system is a Microsoft Access database. Is that different?
Somewhat. Access is still supported in Microsoft 365, and sometimes the right fix is to keep it and move the data to a proper database server. When it needs replacing, see replacing a Microsoft Access database.
What happens to our old data?
Active records move to the new system after we clean and map them, and rehearse the move on a copy until the totals match. Older records can go to a searchable archive.
What if nobody understands how it works?
That's common. Running old and new side by side shows any hidden rule as a mismatch, before it costs anything. We also write down what we learn, so you're never dependent on one person again.
Does this sound like your team?
Tell us what's going on. A few sentences is plenty.