Modernization
Leave GeneXus without stopping operations
We migrate GeneXus systems module by module, with verified parity and reversible cutover. We did it first with our own management system.
What you recover
What your system already knows how to do
The model and the rules
Business logic living in the model is extracted as a specification you sign off.
The schema
Tables, columns and relationships are documented from the real database.
The data
Migrated with identifiers preserved.
The interface
Screens are rebuilt on top of the specification, not blindly copied.
What you leave behind
What you no longer have to carry
- The code generated by the platform.
- The license lines associated with GeneXus.
- The dependency on a generator for every change.
Own case
15 weeks, 0 days of downtime
We left GeneXus with SISCON's management system: 15 calendar weeks, 0 days of downtime, 581 API operations and 1,277 automated tests, with data migrated with identifiers preserved.
Frequently asked questions
Does the system have to stop during the migration?
No. We migrate module by module and a single entry point splits traffic between the legacy and the new system until the final cutover.
What do I get at the end?
The new system, the specification behind it and the tests that verify parity. The code is yours from day one.
How is the scope estimated?
With a measured sample: 5 to 10 screens turned into a verifiable specification, before quoting.
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.