How an RPG-to-Java Migration Actually Works
We structured our offer around a simple idea: you should see real results on your own code before committing to a large engagement. That is why we start with a Pilot, and continue only if you are satisfied.
Migration Pilot
A real program from your codebase, correctly translated to Java, with tests. Fixed price: EUR 3,000. If it doesn't give you concrete value within 15 days, we refund in full.
Migration Flow
The full migration, done in short structured iterations. Feedback from each iteration is incorporated into the next — and applied consistently to what came before.
Migration Pilot
The Migration Pilot is the low-risk entry point. We start from a real program in your codebase — typically up to 2,000 lines of code — analyse the dependencies that matter to translate it correctly, and deliver a working Java version supported by tests.
The goal is not to produce a generic demonstration. It is to give you a concrete result on your own system: a realistic basis for evaluating the quality of the translation, the approach we use, and whether this kind of migration is feasible for your codebase as a whole.
At the end of the Pilot, you have a translated program, a test suite, and a clear picture of what the broader migration would involve. You can use that to make an informed decision — with no pressure to continue.
15-day money-back guarantee
If within 15 days of delivery you conclude that the Pilot did not give you concrete value in evaluating the migration, notify us in writing with your reasons and we will issue a full refund. No negotiation.
What you receive
-
Working Java translation
The selected program, correctly translated and compiling.
-
Dependency analysis
A map of the relevant dependencies we identified and handled.
-
Test suite
Tests that validate the Java output behaves as the original RPG.
-
Migration assessment
Our honest view of what the broader migration would involve.
EUR 3,000
Fixed price. No scope creep. Full refund available within 15 days.
Each iteration delivers
Scope definition upfront
You know exactly what will be translated before we start.
Translated code + tests
Clean Java output and a test suite for the migrated modules.
Feedback opportunity
Review quality, naming, patterns, and technical decisions.
Retrospective application
Feedback is applied to earlier code — the migration stays consistent.
Progress visibility
Test coverage, quality indicators, and documentation as needed.
Migration Flow
Once the Pilot is complete and you are satisfied with the result, we continue the migration in short, structured iterations. At the start of each iteration, you receive a clear definition of what will be translated. At the end, you receive the translated code, the tests, and the opportunity to review and give feedback.
That feedback is incorporated into the following iterations — and, where appropriate, applied consistently to code that was already migrated. This means the migration improves over time rather than drifting into inconsistency as the project grows.
Throughout the process, we provide visibility: progress tracking, quality indicators such as test coverage, and generated documentation when it is useful. The result is a migration that is transparent, adaptable, and aligned with how modern software development actually works.
Why iterative?
A large codebase migrated in one long project tends to drift: decisions made at the start no longer reflect what was learned along the way. Short iterations with feedback loops produce more consistent, higher-quality output — and give you meaningful checkpoints throughout.
Uncertain about the full migration? Start with the Pilot.
The Migration Pilot is designed specifically for organisations that want to see real results before committing to a large project. It answers the questions that matter: how does the translated code look, how are edge cases handled, and does our approach work for your codebase?
Low financial risk
EUR 3,000 with a 15-day refund policy. You are not committing to a six-figure project before you have seen results.
Real code, not a demo
We work with an actual program from your codebase — not a synthetic example. The Pilot result is directly representative of what the full migration will produce.
A concrete decision basis
At the end of the Pilot, you have enough information to make a well-founded decision about the Migration Flow — including a realistic cost and timeline estimate.
Common questions
See what migration looks like on your own code.
The Migration Pilot takes a real program from your codebase — up to 2,000 lines — translates it to Java, and delivers it with tests. You evaluate the result before committing to anything further.
Start with a Migration PilotEUR 3,000 fixed price. 15-day money-back guarantee. We respond within 2 business days.