MIGRATION AND MODERNIZATION AT SCALE · CODE AND APPLICATIONS

Modernize COBOL, Visual Basic 6, Access or Oracle Forms.Your business stays.

COBOL and mainframe, Visual Basic 6, Access, Oracle Forms or PL/SQL, or a stack you want to unify (Java, C#, Python, Node, PHP or Go): we rebuild it in the language you choose, with your team and your AI, orchestrated. The same business rules, with parity measured on your real data.

Legacy · COBOL, VB6, Access and FormsThe host is switched offOne stackParity measured case by case

Request a demo

Automatic demonstration · Tap your code and see what comes out, where it can go and what stays.

Legacy system migration and application modernization:the clock and the bill

There is no core to respect here: the whole program is migrated. What stays is your business, the rules and the data, which are the reference for case-by-case parity. The clocks have already rung: COBOL on the host, Visual Basic 6, Access and Oracle Forms are legacy, and what costs money is keeping them alive.

End of support

Four technologies with no future and a database full of logic

Visual Basic 6 has had no support for years; it runs as long as Windows tolerates it.
Access and Oracle Forms are legacy: Microsoft and Oracle take their users elsewhere, and the screens do not survive a database migration.
COBOL on mainframe does not expire, but every year fewer people know it and the host costs more per MIPS.
PL/SQL and T-SQL have no date; the problem is the business logic buried in the database, tied to that engine and its licence.

What you pay

The host, the database and the people who are left

The mainframe by MIPS and its licences, which go up every year for the same work.
The database licence you cannot change because the logic lives inside, in procedures and packages.
The two or three people who understand that code, and the risk that they leave. And in modern stacks, the cost of maintaining five languages instead of one.

What staysand what goes

Your business stays: the rules and the data. Every case, every calculation and every screen is documented before anything is rewritten, and afterwards we check that the new one gives the same result, case by case, on your real data.

The code that runs it goes: batch programs and JCL, CICS transactions and 3270 screens, VB6 and Access forms, Forms screens, PL/SQL procedures and packages. And the host, the database or the file on a PC that held them up.

You choose the target language: Java, .NET, Python or TypeScript, or your data platform for what is calculation on data. Also from one modern language to another, to keep a single stack.

Which language do you want it in:five destinations, you choose

A language never goes to itself. The criterion is the stack your team already has, not ours.

Java · Spring Batch

From COBOL to Java: the natural destination for batch

Services and batch in Java, the standard for business processes. Spring Batch picks up COBOL batch and JCL; the services take over what the transactions did.

C# · .NET

From Visual Basic 6 to .NET: the same vendor

If your shop is Microsoft, everything in .NET: VB6 forms and logic, Access forms, and also COBOL or Forms if the team is .NET.

TypeScript · Node

Web screens instead of terminals and forms

3270 screens, Forms and Access as a web application, with users and permissions, against the same database or the new one.

Python · data platform

What is calculation on data, close to the data

Processes and calculations in Python, and PL/SQL procedures and Access tables to the SQL and processes of your data platform: Databricks, Snowflake or Fabric.

How to modernize a legacy applicationin four steps, case by case

1Code inventoryWith read-only access: programs, copybooks, JCL, forms, packages and what depends on what. What runs, what has not run for years and which business rules are inside.
2Document what it doesReverse engineering: functional and technical documentation of each program, taken from the code, not from anybody’s memory. What is dead is not migrated: it is switched off.
3Rebuild with your orchestrated AIDevelopment instances that rewrite, test and document each program in the chosen language, with the same method. Your team decides and validates.
4Cut-over with measured parityThe new and the old run in parallel on your real data and are compared case by case. The host is switched off when the last process matches.

The rules

Business rules and data stay
What does not run is not migrated
Process by process, no big bang
You choose the language

Technology by technology:what goes out and where it ends up

One summary per technology. In the chart above you have each piece and its path: tap your code or follow the link.

Legacymainframe

Migrating COBOLto Java or .NET, and switching off the host

Your business rules and your data stay, with measured parity. The host and its MIPS cost are switched off.

What goes out

Batch and JCL → Spring Batch, the natural destination for COBOL batch; or .NET; or the data platform if it is calculation
CICS transactions and 3270 screens → Java or .NET services, and web screens in TypeScript instead of green terminals

See the paths for COBOL

Legacyno support

Migrating Visual Basic 6to .NET, from the same vendor

Your business rules and your data stay. Nothing from VB6: it has no support.

What goes out

VB6 forms and logic → C# · .NET; or a web application in TypeScript; or Java if it is your team’s stack

See the paths for VB6

Legacya file on a PC

Migrating Accessto a web application with a real database

Your data and what your forms do stay, in an application that does not depend on a file on a PC.

What goes out

Forms, queries and macros → a web application in TypeScript, with users and permissions; or .NET
Tables → a real database on your data platform, with backup and access control

See the paths for Access

LegacyOracle

Migrating Oracle Formsweb screens against the same database

Your Oracle database stays, if you want to keep it. The Forms screens go out.

What goes out

Forms screens → web screens in TypeScript or Java, against the same database
PL/SQL logic of the screens → Java or .NET services

See the paths for Forms

Logic in the database

Migrating PL/SQL and T-SQLbusiness logic leaves the database

Your tables and your data stay. The business logic leaves the database, and with it the tie to that engine and its licence.

What goes out

Procedures and packages → the SQL and processes of your data platform; or Java or Python services

See the paths for PL/SQL

Modern stack

Migrating Java, .NET, Python, Node, PHP or Gofrom one language to another, for a single stack

Your business rules and your data stay: same result, in the language that unifies your stack. Five languages cost more than one.

What goes out

Services, batch, applications and scripts → the language you choose among Java, .NET, Python and TypeScript; a language never goes to itself
Python scripts and processes that are calculation on data → the notebooks and processes of your data platform

See the paths for the modern stack

Frequently asked questions about Code and applications

Can COBOL be migrated to Java without stopping the host?

Yes. Batch and JCL go to Spring Batch and CICS transactions to Java services, with web screens instead of 3270 terminals. The new and the old run in parallel on your real data and are compared case by case; the host is switched off when the last process matches.

What is a Visual Basic 6 application migrated to?

To C# and .NET, from the same vendor, or to a web application in TypeScript, or to Java if it is your team’s stack. VB6 has no support; your business rules and your data stay.

How is an Access database migrated?

Forms, queries and macros go to a web application with users and permissions, and the tables to a real database on your data platform, with backup and access control. It stops depending on a file on a PC.

What does modernizing a legacy application with orchestrated AI mean?

Inventorying the code with read-only access, documenting what it does by reading it from the code, rebuilding it in the language you choose with development instances that rewrite, test and document with the same method, and cutting over process by process with measured parity. Your team decides and validates.

How much code does a single personon your team understand today?

In a demo we show you the whole journey on a sample legacy application: the inventory, the documentation taken from the code, the rebuild and the case-by-case comparison. So that you can see what it would look like with yours.

Request a demo See the four scopes

We also migrate: ERP and CRM · Data integration and platforms · Dashboards and analytics · systems migration