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.

Method

Seven phases, module by module

The seven phases repeat for every module, so the new system grows while the old one keeps operating.

Seven phases, module by moduleSeven-phase cycle: discover, specify, migrate data, build, interface, verify and cut over; it starts again with the next module. The client decides at three points: signs the rule in phase 2, accepts parity in phase 6 and authorizes the date in phase 7.1Discover2Specify◆ You sign the rule3Migrate data4Build5Interface6Verify◆ You accept parity7Cut over◆ You authorize the dateNext module◆ Client decision point
1

Discover

Inventory of the real system: objects, data, integrations and rules.

2

Specify

Current behavior is written down as a verifiable specification.

3

Migrate data

Data moves to the new schema with its identifiers preserved.

4

Build

The module is implemented against the specification.

5

Interface

The user interface is rebuilt on top of already-verified operations.

6

Verify

The new module is compared against the current one and differences are documented.

7

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.

Route-based cutover, no downtimeA single entry point splits traffic between the legacy and the new system at three moments: at the start 100% legacy; halfway 45% legacy and 55% new; at the end 100% new.StartSingleentry point100 %Legacy systemNew systemHalfwaySingleentry point45 %55 %Legacy systemNew systemCloseSingleentry point100 %Legacy systemNew system

AI agents

How we use AI agents

How we use AI agentsFour steps: signed specification, the agent implements, tests per clause and human review.1Signed specificationThe client signs what it must do2The agent implementsCode from the specification3Tests per clauseEvery clause has its test4Human reviewA person reviews and approves

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

Each migrated module can run as a task on an IA Factory line: it is specified, built test-first, goes through parallel reviews and is validated against the behavior of the original system before a person merges it. It is the same method —specification before code and mandatory human review— delivered as a service.

Evidence

We did it on our own system

Migration of SISCON's management system off GeneXus

15
calendar weeks
0
days of operational downtime
581
API operations delivered
1,277
automated tests
782
changes merged with review

Complete exit from the proprietary environment and data migration with identifiers preserved.

Migration analysis of a rail logistics and transport system

2,009
objects in the legacy inventory
159 · 1,238 · 155
tables · columns · foreign keys in the real schema
54
composite primary keys

The existing documentation underestimated the real size of the system. That is why the first step is to measure.

How to start

Three steps, no commitment to migrate

1

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.

2

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.

3

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.

Ready to measure your system?
Tell us which system you want to leave behind and we will show you what it looks like in a measured sample.