The hidden cost of staying on the wrong system

"It still works" is the reason businesses stay on outgrown software for years. And it is true: it does still work. That is exactly what makes the cost of staying on the wrong system so easy to ignore, because it never arrives as a single bill.

Where the cost hides

The cost of staying never arrives as an invoice, which is why it does not get counted:

• Every workaround is time, repeated weekly or monthly, for as long as you stay
• Every re-key is an error risk that surfaces at the worst moment
• Every spreadsheet is a decision made on data of unknown age
• Every "only one person knows how that works" is a risk you are carrying uninsured

None of it shows on a licence renewal. All of it shows in your team's week. For a closer look at one part of it, see why software costs keep rising when headcount stays flat.

Key PointThe cost of staying is real but invisible: it is paid in hours, errors and delayed decisions, not in invoices.

Why it compounds

This is the part that catches people out. The cost does not stay flat. It grows, for two reasons.

First, processes calcify around the limitations. Workarounds become "how we do things", get taught to new starters and acquire defenders. What began as a patch becomes policy.

Second, the eventual move gets bigger. There is more history, more integrations and more process to unpick, so the project feels more daunting each year. That makes it easier to postpone again, and the postponement makes it larger still.

Watch OutWaiting is not neutral. The longer you wait because moving feels too big, the bigger moving actually gets.

Working out your own break-even

You do not need a formal business case to get a usable number. For one month, estimate:

• Hours spent on manual workarounds that a better-fitted system would remove
• Hours lost to a month-end that a good close would not need
• The cost of one material error caused by re-keying or stale data

Annualise it, then compare it with a realistic one-off cost of moving plus any change in licence cost. The cost of staying recurs every year; the cost of moving is paid once.

When you price the move, include history. GOV.UK says a limited company must keep records for 6 years from the end of the last company financial year they relate to, so plan how you will keep the old data available.

Pro TipAsk what the move involves in practice. Microsoft's guide to importing data into Business Central shows the templates and configuration packages used to bring master data across, which helps you size the data work.

The counter-argument, honestly

Moving is not always right. If your problems are configuration rather than capability, fixing what you have is cheaper and faster.

If you are about to go through a major change, such as an acquisition, a restructure or a new market, waiting for a stable base can be sensible. The point is not that everyone should move. It is that "not now" should be a decision you make with the number in front of you, not a default you drift into.

If you do decide to move, our guides to how a safe Business Central migration works and Business Central pricing in the UK are the next step. Microsoft also offers a free 30-day trial of Business Central.

Frequently asked

How do we know we are not just bad at using our current system?

Ask whether the problems are about getting data out, which is setup, or about what the system can structurally hold, which is a ceiling. The first is fixable where you are.

Is it cheaper to wait until we are bigger?

Usually the opposite. More scale means more history and more process to migrate, so the move grows with you.

What is the minimum size for an ERP to make sense?

There is no clean threshold. Complexity matters more than headcount: a small business with stock and several currencies may need one before a much larger consultancy does. See when to move from Xero to ERP for the signs.

Can we phase it to spread the cost?

Often, yes. Finance first, then operations, is a common and sensible sequence.