Your legacy code, migrated module by module—and yours to keep.
Migration CodeCraft is the migration itself: automated translation of your existing system into a modern language, delivered in increments you can deploy and test as they arrive, with full ownership of the result and no lock-in.
A rewrite asks you to stop the world, rebuild for two years, and hope the behavior survives. Migration CodeCraft does the opposite: your application is broken down into modules, each module is translated by our tooling and delivered with the runtime library it needs, and you deploy and test it in a real environment while the rest of the system keeps running.
The business logic is preserved because it is translated, not reinterpreted. The work is transparent because you see it arrive one module at a time, and you say what is wrong while it is still cheap to change.
How it works
Every Migration CodeCraft engagement begins with a Migration Blueprint, and then repeats the same short loop until the system is across.
The preparatory step that lays the groundwork. The application is analyzed and broken down into discrete modules, and each module is planned into a specific delivery, deployment and testing sequence—so progress is incremental and manageable instead of one risky release. It is also where you and we agree on what the migrated system should look like.
With the Blueprint guiding the sequence, the work unfolds module by module. For each one you receive two things: the translated code, and the runtime library that supports it. You can deploy and test that module immediately, without waiting for the whole system.
You deploy the translated module and test it against your expectations. The feedback from this phase is what keeps the migration honest: inconsistencies surface early, while they are still one module wide.
We act on the feedback and deliver updated versions of the affected modules. We also refund any lines of code you are not happy with—a rare guarantee in this industry, and the clearest way we know to put our confidence on the line.
You receive full ownership of all migrated code, no strings attached. We retain ownership of the runtime library, but you get its source code and a comprehensive license to use it however you want, now or later—with no ongoing license fees and no obligation to keep us for support.
What you own at the end
The point of the exercise is independence, not a new dependency. We would rather you were free to leave and chose to stay.
No lock-in, in writing.
You get complete access to the migrated code and to the runtime library, so you can keep evolving the system on your own. We keep the right to reuse parts of the runtime library on other projects; you keep the right to maintain, modify and extend yours without recurring fees or contractual dependency on us.
The goal is not to create reliance. It is to deliver freedom through thoughtful engineering.
Why Migration CodeCraft
Automated code translation
Our tools convert legacy code into modern, structured code while preserving business logic and functionality—so behavior is carried across rather than re-derived from documentation nobody trusts.
Cost and time efficient
A streamlined, automated migration process instead of an expensive, multi-year manual rewrite that has to be maintained twice while it runs.
Future-proof software
Moving to a modern programming language makes the system easier to maintain and enhance—and makes it possible to hire developers who already know it.
The two systems run side by side
Each module goes live when it is ready, next to the parts still running on the legacy platform, instead of on one cut-over date. The migrated code is therefore tested under real load and real data while there is still something to fall back to.
Clarity and collaboration, not a black box. A shared blueprint of the target system, code delivered module by module, your feedback at the center—and full ownership of the result.
Terms
Fixed price, guaranteed for a year. The scope comes out of the Migration Blueprint, so the price is based on your actual system rather than on an estimate made before anyone read the code.
Where it starts
With the Migration Blueprint. It maps your application into modules and sets the delivery sequence, and it is what makes a fixed price possible. If you want to see which source languages we handle, the languages we cover page has the current list, and RPG & IBM i covers the platform we work on most.
How a fixed price survives a large codebase
A fixed price on a migration is only honest if the scope was measured rather than guessed, and if the cost of the work does not grow with the size of the estate the way a team billing hours does. Three things carry it, and none of them is confidence.
- The scope is counted before it is priced. The Blueprint’s Code Insights report lists the constructs and built-in functions your code actually uses, the modules it divides into, and the code that is never reached. Volume is not what makes a migration expensive; unknown constructs and dead code priced as live code are. Both are known before the number is written.
- The translation is done by a licensed engine, not assembled for you. The same parsers we sell on their own do the reading: the RPG engine has been exercised on more than 30 million lines of production RPG and carries 718 automated tests, the COBOL engine 681, including all 459 programs of the NIST COBOL-85 conformance suite. A rule applied by a machine costs the same on the last module as on the first.
- The risk of being wrong sits with us. The price is fixed and guaranteed for a year, and we refund any lines of code you are not happy with. That guarantee is only affordable to us because of the two points above — which is the honest reason we can offer it and a supplier pricing off a line count cannot.
What we will not fix a price against is a codebase we have not read. That is the entire reason the Migration Blueprint comes first and is priced separately.
Federico’s book on migrating RPG
Launched in October 2025, Migrating RPG Code to Modern Languages is a practical playbook for teams modernizing IBM i applications—the same thinking that Migration CodeCraft puts into practice. Learn more about the book.
Ready to move your system across?
Tell us what you are running and what you want to run instead. We will tell you honestly whether a migration is the right answer, and what the Blueprint would need to look like.
