Skip to content
Artrilogic
Opinion piece

Upgrade or rebuild? The honest tests we apply.

Most modernisation engagements work as a series of bridges. Some do not. Here is how we tell the difference, and why we will occasionally recommend a full rebuild even though it is the harder sale.

01

The default

Bridges almost always win.

Most legacy estates contain hard-won business logic that the original author has long since left the building. A rebuild claims to recreate that logic. In practice it recreates the parts the team remembers and quietly drops the parts they did not. The dropped parts then surface six months after go-live as “edge cases” that were never edge.

Wrap the existing system. Bridge to the modern stack via APIs or MCP servers. Migrate the painful slices on a schedule the team can absorb. This is what we recommend most of the time, and it is rarely the most expensive option on the table.

02

The exceptions

When we recommend a rebuild anyway.

Three conditions, and at least two of them have to be true at once.

  • The data model is so distorted by accumulated workarounds that bridging would lock the workarounds in.
  • The business model has fundamentally changed (acquisition, new regulator, new market) and the system is now solving a problem nobody has.
  • The platform is genuinely unsupported (not “Microsoft has stopped marketing it”, but “there is no security patch path and the vendor is gone”).

When at least two of those are true, a rebuild is not optional, it is overdue. The remaining work is to scope it honestly and resource it without theatre.

03

The honest test

What we ask before we recommend either.

“If we do nothing for two more years, what specifically breaks, and who pays for it?” If the answer is vague, the modernisation is not yet load-bearing for the business. Wait until it is, then act with conviction.

“What does the team that runs this think?” If the people closest to the system want to keep it and the people farthest from it want to replace it, the right answer is almost always closer to the first group.

“Whose roadmap are we trying to align with?” If the answer is a vendor's, pause. If it is a regulator's, prioritise. If it is your own, that is the only one that matters.

Want to talk this through against your specific estate?

The opinions above are general. Your estate is specific. A modernisation assessment puts honest numbers on which path fits.