A utility’s core system for customers, field work and billing had run on premises for 15+ years on Struts 1, WebLogic and Oracle. Without access to the client’s environment, we assessed it, proved the move to Spring Boot in code and mapped the route to the cloud.
One codebase runs customers and contracts, field work, billing and collections, stock and equipment, a large set of printed forms and a nightly batch. The client asked what state it was in, whether modernizing it was feasible, what it would cost, in what order, and how it should reach the cloud.
Drawn new for this page. No screens or data from the client's systems.
The client sends only a source export and specifications; there is no access to its environment. We build a mirror of the legacy stack, move a slice from the old framework to Spring Boot, and compare every output with the old system: screens, database writes and report files must match.
The as-is stack we assessed, and the target the proof of concept and the cloud strategy point to.
Provisioned our own servers mirroring the client’s stack (Red Hat Enterprise Linux, WebLogic, Oracle) from the specifications and the source export, for analysis, performance baselines and regression tests.
Module inventory and dependency map (one core module carries most of the inbound references), static and security scans, a risk heatmap and priority matrix, and the client’s list of issues analysed alongside the hidden ones we found.
Rebuilt the missing design documents and extracted the business rules from the source code, accelerated with AI under an approved, masked-data process.
Moved a slice from Struts actions and JSP to Spring Boot and Spring MVC on a current Java release without changing behaviour, checked against a golden baseline of the old system’s screens, database writes and report files.
Current-state capture; functional, non-functional and migration requirements; a weighted AWS and Google Cloud comparison (Oracle licensing, total cost, data residency, compatibility with the Java estate); and a roadmap tied to the proof of concept.
Modernize the application where it runs today, then move it to the cloud.
Today the system runs on premises on Struts 1 and JSP, Java 8, Oracle WebLogic and Oracle Database, built with Ant from Subversion. Step one modernizes the application where it runs: Spring Boot on Java 21, a container image, Maven, Git and CI/CD, with a golden baseline proving the old and new behave the same. Step two moves it to the cloud: AWS or Google Cloud, Multi-AZ, infrastructure as code, Oracle with the licence brought or managed, and PostgreSQL evaluated.
Every product and practice in this work, named so an engineer can check it.
Slice by slice. Each slice moves from Struts actions and JSP to Spring Boot and Spring MVC, and a golden baseline compares its screens, database writes and report files with the old system automatically before it is accepted.
We advise two steps: modernize the application first, on infrastructure you already know, then move it to the cloud. Doing both at once multiplies the risk and blurs the cause of any problem.
Yes. From a source export and specifications we build a mirror of the stack, then run the analysis, the performance baselines and the regression tests there.
Tell us what you run and what is getting in the way. You get a reply within 24 hours.
