Human Minds. Amplified by AI.

Legacy Application Modernisation

A ten-year-old Java application.
Rebuilt in about two weeks.

330+ screens rebuilt and compared
with the original

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.

~2 weeks

from the first migration commit to a release candidate in team testing.

62

end-to-end processes checked on both systems, including database rows, e-mails and Excel exports.

76 → 31

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.

Every layer moved off end-of-life software

AreaBeforeAfter
Language and runtimeJava 7Java 25
FrameworkSpring Roo 1.3, Spring 4.3Spring Boot 4.1
ServerTomcat 7 as a WAR fileEmbedded server in a container image
PersistenceHibernate 5.1Hibernate 7
PasswordsReversible encryption, passwords sent by e-mailArgon2id hashing, reset by mailed link, lockout, CSRF protection
ViewsJSPX pages with Tiles, 317 filesThymeleaf templates, 332 files
DeliveryNo container, no pipeline, manual deploymentDocker images, automatic HTTPS, CI pipeline, backups with tested restore, metrics and a runbook

Read the full case study →

Modernising a working system means proving nothing broke

Run both, compare everything

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.

Fix security while moving

Weak password storage, injectable query filters and over-exposed data were closed as part of the move, with checks that attack both versions.

Engineers stay accountable

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.

Could your application move the same way?

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].