Full platform rewrite
Migration to a new platform
Benefits
- Clean technology break
- Full system replacement
Limitations
- Very high costs
- Major functional risk
- Loss of business logic
- Vendor lock-in
Three possible approaches, with very different levels of risk and value.
Migration to a new platform
Opening up existing programs
New autonomous application layer
Four points to consider before starting a full migration.
Your IBM i represents decades of investment. Every RPG program reflects proven business processes and real know-how, refined over the years.
Most business logic is documented only in the source code. In a migration, these implicit rules are hard to reconstruct.
ERP migration projects routinely overrun their schedules and budgets. The operational risk is considerable.
The total cost of a rewrite includes training, parallel running and post-migration fixes, which are rarely anticipated.
IBM i remains the business back end, while .NET becomes the modern application layer. NTi Data Provider handles the exchange between the two.
Access existing data and reuse an existing RPG business program.
Processing managed by the new application.
New application deployed and independently maintainable.
A gradual transition from an IBM i ERP to .NET.
Deployment on Linux / Power.
No components installed on IBM i.
No service interruption during the modernization.
Tap into the largest talent pool on the market.
Your past investments become a competitive advantage.
The proven IBM i security model stays fully in force.
Every iteration delivers measurable value.
APIs, web and mobile, running on the infrastructure of your choice.
AUMERIAL combines its expertise with that of its partners to secure your application estate and prepare your IT for modern standards, with no turnkey migration imposed.
A review of your RPG/COBOL developments, a map of the business stakes, and a roadmap defined together.
Shared roadmapYour legacy code becomes reusable .NET components (assemblies, services, containers), deployable on Linux, Windows or Docker, with their original logic.
Reusable .NET componentsDaily monitoring, proactive handling of changes, fast response to incidents, and clear service levels.
Clear service levelsof IBM i professionals rank the IBM i skills shortage among their top concerns, now ahead of cybersecurity.
Source: Fortra, IBM i Marketplace Survey 2026ROI over three years for a composite organization running IBM i, with payback in under six months.
Source: Forrester TEI of IBM i (2023), commissioned by IBM, via IT JungleAnother question? Email us at contact@aumerial.com.
NTi Data Provider allows you to call your RPG, CLP, or even older 36 programs exactly as they exist today, from C# and .NET, without modifying your IBM i code.
Each program is executed natively on the IBM i, with the same parameters, the same libraries, and the same behavior as in 5250.
From .NET you can:
Your business logic remains 100% IBM i, but integrates immediately into a modern application, web or API, containerised or not. It is the simplest way to expose your RPG assets to the .NET ecosystem, without refactoring, without migration, without risk.
NTi relies exclusively on the security mechanisms of the IBM i:
All the rules remain those defined on the machine, without modifying your existing model. Modernisation happens on the .NET side, but security continues to be ensured by the IBM i, with the same level of reliability and control as your current applications.
Yes. NTi enables incremental modernisation: you keep your programs and DB2 data, then add new .NET modules as needed.
Concrete example:
You already have a CLIENTS file, an RPG program that validates and updates the data, and an interactive screen that calls this logic.
With NTi, you keep exactly this behaviour and build alongside it a modern web interface that uses that same RPG program to validate or save the data, without rewriting.
No. Nothing is installed on the IBM i.
NTi runs only inside your .NET application. You simply add a NuGet package to your .NET project, and it is the application that communicates natively with the IBM i, not the other way around.
Whether you run your app on a Windows server, a Linux system, a Docker container, or in the cloud, NTi always runs within .NET, never on the IBM i.
Result: instant deployment, no need to involve system teams, and a clean architecture where everything stays on the .NET side.
This is the daily reality for many IBM i teams. The programs exist, but their parameters, structures, or business rules are no longer documented.
.NET and NTi simplify this situation because each RPG, CLP or API call becomes explicit in the .NET code. You define your parameters, your types, your lengths, your buffers, and this definition becomes your documentation.
As you integrate your programs into .NET, you automatically rebuild clear documentation: which programs are called, with which parameters, in which order, and with what return values.
Even without historical documentation, your system becomes readable, manageable, and structured again. You give new life to your IBM i assets, supported by widely available and sustainable .NET skills.