Human Minds. Amplified by AI.
Legacy Application Modernisation
A business web application on Java 7, Spring Roo and Tomcat 7 was moved to Java 25, Spring Boot 4.1 and container images. Same data, same screens, same behaviour — verified against the original.
from the first migration commit to a release candidate in team testing.
end-to-end processes checked on both systems, including database rows, e-mails and Excel exports.
dependencies, now with vulnerability scanning. Password storage, query filters and access rules hardened in the same move.
The client is anonymised. The application is in team testing and has not yet replaced production; cutover follows testing. Timing is calendar time from commit history and includes waiting periods. Timelines are assessed for each application.
| Area | Before | After |
|---|---|---|
| Language and runtime | Java 7 | Java 25 |
| Framework | Spring Roo 1.3, Spring 4.3 | Spring Boot 4.1 |
| Server | Tomcat 7 as a WAR file | Embedded server in a container image |
| Persistence | Hibernate 5.1 | Hibernate 7 |
| Passwords | Reversible encryption, passwords sent by e-mail | Argon2id hashing, reset by mailed link, lockout, CSRF protection |
| Views | JSPX pages with Tiles, 317 files | Thymeleaf templates, 332 files |
| Delivery | No container, no pipeline, manual deployment | Docker images, automatic HTTPS, CI pipeline, backups with tested restore, metrics and a runbook |
The original stayed live as the reference. An automated harness compared screens, API responses and access rules, then diffed database rows, e-mails sent and generated Excel files.
Weak password storage, injectable query filters and over-exposed data were closed as part of the move, with checks that attack both versions.
AI assists the repetitive development and testing. Engineers direct the process, review each component and approve the result. Your code and data can stay inside your environment.
Book a 30-minute legacy assessment. Tell us which stack you run and roughly how large the application is, and we'll come back with a view on scope, verification and migration path. Prefer email? [email protected].