Legacy System Modernization
Leave your legacy system without stopping operations — and keep the code.
We did it on our own system. We show you yours in a measured sample.
We migrate systems module by module: each module is specified, rebuilt, verified against the current system and only then switched over. When rewriting is not the right call, we move the system to the cloud, migrate its database or open it through APIs. Your operation keeps running and the resulting code is yours from day one.
Entry points
Where do you want to leave from?
Leaving GeneXus or another proprietary low-code platform
You regain control of the code and stop depending on a proprietary environment and license.
Java or .NET systems with no written specification
Systems that work but that nobody can describe in full. We document them first, then migrate them.
Desktop or client-server systems
Visual Basic 6, PowerBuilder, Delphi, Oracle Forms, Access or FoxPro: we take them to the web module by module, coexisting with the current version.
COBOL, mainframe or IBM i (AS/400)
We document rules accumulated over decades, open the core through APIs and migrate what is worth migrating.
What to retire, absorb or rebuild when an ERP arrives
When NetSuite, SAP or another ERP comes in, we decide with data which modules are retired, which the ERP absorbs and which are rebuilt.
Documenting a system to tender it, audit it or maintain it
A verifiable specification of the system as it is today, useful for a tender, an audit or maintenance.
Types of modernization
Not everything gets rewritten
Each application calls for a different path. The assessment decides which one fits each case; the seven-phase method comes in when something has to be rebuilt.
Rebuild module by module
Specify, rebuild, verify and switch over module by module, with signed parity.
→Cloud and containers
Rehost or replatform to the cloud or to containers without rewriting the code.
→Database migration
Change engines with the schema measured and every table reconciled.
→APIs and a new interface
Open the system through APIs and give it a web or mobile interface without touching the core.
→Retire or absorb into an ERP
Decide with data which modules the new ERP retires or absorbs.
→Document the system
A verifiable specification of the system as it is today.
→Method
Seven phases, module by module
The seven phases repeat for every module, so the new system grows while the old one keeps operating.
Discover
Inventory of the real system: objects, data, integrations and rules.
Specify
Current behavior is written down as a verifiable specification.
Migrate data
Data moves to the new schema with its identifiers preserved.
Build
The module is implemented against the specification.
Interface
The user interface is rebuilt on top of already-verified operations.
Verify
The new module is compared against the current one and differences are documented.
Switch over
Operation moves to the new module, with rollback available.
Guarantees
- No module switches over without signed parity.
- Every switch-over is reversible in minutes.
- The code belongs to the client from day one.
Cutover
Not a single day of downtime
A single entry point splits traffic between the legacy and the new system, module by module, until the close.
AI agents
How we use AI agents
Specification before code
First we write what the system does; the code follows from that specification.
Agents implement against it
AI agents build the module against the specification, not against assumptions.
One test per clause
Every clause in the specification has an automated test that proves it.
Mandatory human review
A person reviews and merges every change. AI speeds things up; it does not decide on its own.
This is the agentic software development method applied to migration: here it lives as a method, not as a product.
IA Factory
Modernization as an IA Factory production line
Evidence
We did it on our own system
Migration of SISCON's management system off GeneXus
Complete exit from the proprietary environment and data migration with identifiers preserved.
Migration analysis of a rail logistics and transport system
The existing documentation underestimated the real size of the system. That is why the first step is to measure.
Full cycle
Before, during and after migrating
Before: portfolio assessment
If you have several applications, we decide with data what gets modernized first and how.
→During: modernization in waves
Each wave follows the path that fits it, with signed parity and reversible switch-over.
→After: operations and maintenance
Support for the new system, continuous improvements and knowledge transfer to your team.
→How to start
Three steps, no commitment to migrate
Measured sample, at no cost
5 to 10 screens of your system turned into a verifiable specification, with its tests and an inventory of differences.
3-to-5-week diagnostic at a fixed price
The real schema, a wave-by-wave plan, the estimate and the license spend that goes away.
Wave-by-wave migration
Quoted from the measured inventory, not from assumptions.
FAQ
Frequently Asked Questions
Do I have to stop operations to migrate?
No. We migrate module by module and none switches over without signed parity. In our own case it was 0 days of downtime.
Who owns the resulting code?
The client, from day one.
What if something fails at switch-over?
Every switch-over is reversible in minutes.
Do you work with technologies other than GeneXus?
Yes. The method starts from the system's schema and behavior, not from the language: it applies to Java, .NET, Visual Basic 6, PowerBuilder, Delphi, Oracle Forms, COBOL or IBM i. Our documented own case is GeneXus; for other technologies, the measured sample checks it on your system.
Does the system always have to be rewritten?
No. Depending on the application, it may make more sense to move it to the cloud or to containers, migrate only its database, open it through APIs or retire it. The assessment decides with data.
Where do I start?
With the measured sample, at no cost: 5 to 10 screens turned into a verifiable specification.
Related: ERP query agent — our ERP query agent product, in production in our own ERP.
Depending on your situation
Nine starting points
Migrate from GeneXus
What you recover and what you leave behind.
→Undocumented systems
The specification comes from the system itself.
→When a new ERP arrives
Retire, absorb, extend or rebuild.
→Client-server systems
Visual Basic 6, PowerBuilder, Delphi, Oracle Forms or Access, to the web.
→COBOL, mainframe and IBM i
Modernize without switching off what works.
→Cloud and containers
Modernize where your system runs.
→Database migration
Change engines without losing a single record.
→APIs and user interface
Open your system without rewriting the core.
→Portfolio assessment
Decide what to modernize first.
→