Skip to content
Logo von nextlevels
Request a project

Free · 2 minutes · no sign-up

Legacy Check: Is your old system a risk?

The old system runs – until it doesn't. The legacy check shows in six questions how big the risk really is: technically (framework, version, updates) and organizationally (maintenance, operations, documentation).

You get a risk score from 0 to 100 and a recommendation for the modernization path that fits your situation: refactor in place, gradual replacement (strangler) or a rebuild.

Six questions about your system

1. Language & frameworkWhat does the system run on?
2. VersionHow far is the system from the current release?
3. Last updateWhen was the code or its dependencies last touched?
4. Who maintains it?Who could safely roll out a change today?
5. Hosting & operationsWhere and how does the system run?
6. DocumentationWhat is written down?

Your risk score

Answer the six questions – the score updates with every answer.

More on the approach: Software modernization & legacy migration

How we score

Every answer adds 0 to 3 risk points; the sum of all six questions is normalized to 0 to 100. The weighting is deliberately equal: a discontinued framework is as dangerous as a system only one person understands.

Rating

  • Low risk: 0–33 points
  • Medium risk: 34–60 points
  • High risk: 61–100 points

Two floors

Good detail answers must not average away fundamental problems. Therefore:

  • Discontinued technology without reliable maintenance: this raises the risk to "high" regardless of the other answers.
  • Without active maintenance the risk is at least "medium" – no matter how good the technology is.

How the path is derived

  • Refactor: Technology current or only slightly dated – the risk sits in maintenance, operations or documentation.
  • Strangler: Framework and version clearly outdated together, but the system is maintained and documented well enough to replace it step by step.
  • Rebuild: Framework discontinued plus a version without support, no maintenance or no documentation.

Frequently asked questions about the legacy check

When does software count as "legacy"?
Not by age but by maintainability: when updates are risky, the knowledge depends on one person or the framework no longer gets security updates, a system is legacy – even if it is only five years old.
What is the difference between refactor, strangler and rebuild?
Refactor modernizes in place: updates, tests, documentation, without swapping the architecture. Strangler puts a facade in front of the old system and replaces it area by area while it keeps running. Rebuild builds the system anew and migrates the data – sensible when the technology is discontinued and nobody can operate it safely anymore.
Does an old system have to be replaced right away?
No. A high risk means secure first: check backups, lock down access, document knowledge, close vulnerabilities. Only then does it become clear which path is economical. A running system is an advantage, not a flaw.
What happens to my answers?
The check runs entirely in your browser. Your answers are neither stored nor sent to us; we only count anonymously how often the check is completed and which rating comes out.

Let's talk about your old system

We look at code, operations and team situation and tell you honestly whether refactor, strangler or rebuild is the right way – and what it costs.

Profile picture of Slawa Ditzel, Executive Partner
Slawa Ditzel
Executive Partner
info@next-levels.de +49 (0) 2161 539 71 60