Modernization
Portfolio assessment: decide what to modernize first
When there are several legacy systems, the first mistake is starting with the most visible one. We measure each application and give you a decision per application and a wave plan.
The problem
Many applications, a single budget
Duplicate systems, applications almost nobody uses and critical ones with no documentation. Without a measured inventory, the order of modernization is decided by perception and the budget goes to what was not a priority.
How we do it
From the inventory to a wave plan
Measured inventory
Each application is measured: size, technology, data, integrations, users and dependence on people or licenses.
A decision per application
Retire, keep, move to the cloud, open through APIs, rebuild or absorb into an ERP, based on business value and technical risk.
Wave plan
Applications are ordered in waves that balance early benefit, dependencies and your team's capacity.
Estimates on what was measured
Each wave is estimated on the real inventory, not on assumptions.
Illustrative scenario
A company with a dozen legacy applications
Imagine a company with a core system in GeneXus, several Visual Basic modules, a couple of Java applications on in-house servers and critical spreadsheets.
- The inventory shows that two applications duplicate functions the ERP already covers: they are retired.
- The Java applications are moved to containers without rewriting them.
- The core system is opened through APIs while its module-by-module migration is planned.
- The Visual Basic modules go into the second wave, once the core system is stable.
Illustrative scenario: A hypothetical example to explain the method: it does not describe a client or a measured result.
What you keep
A portfolio map and a plan
An inventory per application, a recommended decision with its rationale and a wave plan with estimates. You keep it even if you execute with another provider.
Frequently asked questions
How is it different from the diagnostic?
The diagnostic goes deep into one system; the portfolio assessment compares several applications to decide the order and type of modernization for each.
What do you need from my team?
The list of applications, the structure of their databases and a business owner per application. No real data is needed.
Do I have to modernize everything that is assessed?
No. The assessment may recommend retiring or keeping several applications and focusing the budget on a few.
Next step
Start with a measured sample: 5 to 10 screens of your system turned into a verifiable specification, with tests and an inventory of differences.