Skip to content
Dirac Core

Free tool

How risky is it to migrate your system?

Six one-tap questions. At the end you see the risk by dimension, the approach we'd suggest and what we'd do first. No sign-up: your answers never leave your browser.

Question 1 of 6
Is the system's technology still supported?

How the assessment works

Each answer adds risk to one of five dimensions: technology, integrations, system knowledge, data and business continuity. Each dimension goes from low to high, and the overall risk depends on how many end up high and how much risk is spread across them.

The approach comes from simple rules: if the technology is no longer supported, we suggest rewriting in phases; if it holds up but data or integrations are at stake, migrating in phases; otherwise, stabilizing first. These are the same questions we start a real technical review with.

Signs a legacy system is risky to migrate

  • 01Nobody on the team dares to deploy a change on a Friday.
  • 02The documentation is whatever one person remembers.
  • 03Other companies connect to its API and you're not sure which ones.
  • 04There are no automated tests: every change is checked by hand, or not at all.
  • 05Being down for more than a few minutes costs the business customers.

How we did it in our largest migration

The platform of a real estate network in Spain, serving hundreds of thousands of requests a day with dozens of third-party integrations, moved to the client's own cloud with a 2 h 54 min cutover: 31 checks passed, zero data lost, and 24 of 25 integrations kept working without their owners changing anything.

See our migration and modernization service

Frequently asked questions

Do you store my answers?

No. The assessment runs in your browser and sends nothing: the result only lives in the link you choose to share.

Why doesn't it give a price or a timeline?

Because they depend on what each company needs to migrate. The assessment tells you where to start; scope, price and timeline go into a fixed proposal after the technical review.

Does it work if the system is a vendor product, not our own?

As guidance, yes. With off-the-shelf software the question is usually how to get out with your data, and we cover that in the technical review too.

Who defined the rules?

We did, based on the migrations we've delivered. They're explained above exactly as they're applied, no black boxes.