- MapA roadmap in phasesWe assessed the IBM i estate and proved the approach on one module first.
- ConvertAI-assisted refactoringAgents sped up the code conversion, and engineers validated every change.
- RebuildBrowser screens and servicesReact screens, Java services, and an API layer replaced the green screens.
- RunOld and new side by sideLegacy modules kept running until the new ones were ready, with data moved from DB2 to SQL.
A global logistics provider moves off IBM i in stages The old screens keep running until each new one is ready
Global logistics
Bookings and billing move to the browser, one module at a time
The core worked, but it couldn't change Bookings, documents, and billing ran on IBM i, built in Synon CA 2E
Green screens slowed people downThe way people used the systems hadn't changed in decades.
Few people could change the codeEvery update needed IBM i skills that were hard to hire.
Most of the code had no documentationThe business rules lived in the code and in a few heads.
Operations couldn't stopA risky cutover on live shipping systems wasn't an option.
We replaced one module at a time Each new module went live beside the one it replaced
Bookings and billing now take fewer hand-offs Teams work in the browser while the rest of the core moves
- KeptBusiness logic written downOne repository holds the rules the old code carried.
- ReusedShared partsWeb and service components built once, for every module.
- AdoptedTeams trained on the new screensHands-on training and change support for each release.
- NextThe next modulesThe roadmap moves the rest of the core one step at a time.
Book a working session on IBM i modernization
We'll tell you which module to move first, and what keeps running meanwhile.