Understand the software your business depends on—then move beyond it, without betting the company.
RPG, COBOL, SAS, VB6 or anything else your business runs on: we help you understand it and keep it alive, then plan the way out. Migration Blueprint maps the estate, dependencies and risks before anyone commits. Migration CodeCraft transforms the system in controlled increments and validates each one against the behavior of the original.
A legacy system does not fail all at once. It gets more expensive to keep, harder to integrate, riskier to expose, and less attractive to work on. Incompatibility, security gaps and performance bottlenecks quietly start deciding what your company can and cannot do next.
What a legacy system is costing you
High maintenance costs
Old systems demand constant fixes for software or hardware that drain budget.
Lack of flexibility
Your current setup makes integration, scaling and going to the cloud slow and expensive—sometimes practically impossible.
Security risks
Older platforms leave you exposed to modern threats and to compliance failures.
Talent drain
Developers do not want to spend their careers on outdated technology, which makes both hiring and retention harder every year.
The true cost of delaying
- Missed growth opportunities. Outdated software slows innovation and makes it harder to adapt to market changes. While competitors adopt automation and scalable platforms, the estate sets the ceiling on what you can offer.
- Team frustration and burnout. Developers maintain fragile code instead of building; business users fight slow processes and daily workarounds. Over time that frustration turns into turnover, and turnover takes the domain knowledge with it.
- Risk of falling behind. Every delay compounds. The system gets larger, the people who understand it get fewer, and the migration you postpone becomes the migration you have to do under pressure.
The point of a migration is not new technology. It is getting the knowledge locked inside the old system out, intact, and into something your team can keep changing.
How we work
Two offers, in sequence. The Blueprint is what makes the migration estimable; CodeCraft is how it gets delivered. You can stop after the Blueprint and take it to anyone—including your own team.
Migration Blueprint
A structured assessment of what you actually have before anyone commits to moving it. We parse the real codebase—not the documentation—and map modules, dependencies, dead code and the risky corners, then set out a migration strategy with a realistic scope.
Migration CodeCraft
Automated translation to a contemporary language, tuned until the output is code your developers would have written. We transform the system in controlled increments and validate each increment against the behavior of the original, so the migration is verifiable at every step rather than at the end.
Everything in this practice
The practice is wider than the two offers above. If you already know which platform or which language you are dealing with, start here.
RPG & IBM i modernization
The platform we know best: RPG to Java, RPG to Python, Synon / CA 2E, and the RPG Language Engine underneath all of it.
Languages covered
Which source and target languages we support, and what we have already built parsers and transpilers for.
Parsers and transpilers
The machinery a migration is made of. We build custom parsers, license the ones we already have, and write the transpilers on top.
Ready-to-go RPG to Python
A packaged migration path for teams whose target is Python and who want to start from something that already exists.
The book
Migrating RPG Code to Modern Languages
FEDERICO TOMASSETTI & GABRIELE TOMASSETTI
A practical playbook for teams modernizing IBM i applications: how to read the estate you have, how to decide what moves and what stays, and what actually goes wrong between RPG and a modern language. It is the book we wanted to hand to clients at the start of a project, so we wrote it.
If you want to know how we think about migrations before you talk to us, this is the longest and most honest version of the answer.
Why Strumenta
- We build the tools, not just the projects. Parsers, transpilers and language engines are our own product line. A migration here is not a team of consultants reading code by hand—it is tooling built for your codebase, and you can see it work before you commit.
- Battle-tested at scale. Our RPG Language Engine is battle-tested on more than 30 million lines of production RPG code from IBM i (AS/400, iSeries) systems.
- Breadth across languages. Since 2015 we have worked with 70+ clients in 20+ countries across six continents, on 24 languages and more than 10 industries.
- Open foundations. Our language-engineering libraries—Starlasu—are Apache-2.0 and public. There is no proprietary intermediate representation holding your migration hostage.
- The estate comes first. We will not quote a migration we have not measured. That is what the Blueprint is for, and it is why the price for the agreed scope does not move afterwards.
You can also read what our clients say in the case studies and the testimonials.
Start with the estate, not with the estimate.
Tell us what you are running and what is pushing you to move. We will tell you plainly what we would do, what it would cost, and whether the migration is worth doing at all right now.
