Ravi spent eleven years on a bank's loan-processing system: Java 8, an old application server, and a set of batch jobs nobody else dared touch. When his team was reduced, he assumed that knowledge was worthless outside that building. A former colleague, now at an IT services firm, disagreed: "We have three clients with systems just like that. They need someone who isn't scared of them." Ravi spent six weeks upgrading an open-source app across two LTS versions, wrote a calm two-page report, and used it in every conversation.
Speaking as someone who has seen many of these careers: the developers who are good at modernisation are rarely the flashiest. They are patient, they test first, and they write things down.
The modernisation field guide
The Unsupported Version. Apps still running on old Java releases. Oracle's roadmap (updated 20 Oct 2026) lists LTS releases 8, 11, 17, 21 and 25, with Java 29 the next planned LTS in September 2027. Approach: hop LTS to LTS, tests green at each stop.
The Framework Fossil. Old Spring, Struts or EJB code. Approach: upgrade in steps; automated refactoring tools such as OpenRewrite (open source, "large-scale automated source code refactoring") handle much of the mechanical change.
The Untested Core. Critical code with no tests. Approach: characterisation tests — record what it does today, then change it.
The Monolith. One big deployable. Approach: not always split it. Sometimes a modular monolith is the right answer. If splitting, use the strangler pattern — route parts of traffic to new services behind a stable interface.
The Batch Job at 2 a.m. Undocumented, essential. Approach: document inputs, outputs and timing before touching it.
The Licensing Question. Real, important, and not ours to answer. Oracle JDK 25 is listed under a free-use licence; other vendors publish their own terms. Each organisation's legal team decides.
The Business Stakeholder. Wants it modern, cheap and done by quarter end. Approach: a before/after report with honest risks and effort.
The modernisation skill tree
Root: strong Java, testing habits → Upgrade branch: LTS hops → build-tool upgrades → OpenRewrite recipes → framework major versions → Structure branch: characterisation tests → refactoring → modular boundaries → strangler pattern → Platform branch: containers → CI/CD (automated build and release pipelines) → cloud deployment basics → observability → Advisory leaf: estate assessment → effort estimates → roadmap writing
The four-panel comic
A short illustrated strip, with full alt text. Panel 1: An elderly, cardigan-wearing Java service sits in a server room, sipping tea. Caption: "LoanService, est. 2012." Panel 2: A bright young API (application programming interface) knocks: "Hi! The mobile app needs your data. In JSON. Today." Panel 3: LoanService peers over its glasses: "I speak SOAP and batch files, dear." Panel 4: A modernisation developer stands between them with a small adapter and a test suite: "You two are going to get along fine." Both smile. Static images; a gentle reminder that the job is translation, not demolition.
A proof project for modernisation roles
Upgrade an open-source Java app across at least one LTS hop with OpenRewrite, keep the tests green, and write a two-page before/after report: starting point, changes, breakages, results, remaining risks, effort.
How a modernisation engagement usually runs
Assess — inventory apps, versions, frameworks, test coverage. Prioritise — by risk and business value, not by age alone. Pilot — upgrade one representative app and measure effort. Scale — apply what you learned, often with automated recipes. Hand over — documentation, runbooks, training for the team that stays.
Who moves into modernisation
Java developers with long codebase experience, production support engineers who know legacy systems, and architects who prefer hands-on work.
Where the work is, India and beyond
India: IT services modernisation practices, banks, insurers and GCCs. Global: consultancies and cloud partners; assessment contracts. Work authorisation is outside our scope.
Your realistic 90 days
Java developers, especially from services firms on old Spring, J2EE or Struts stacks, come here. Banks and insurers are upgrading Java and moving monoliths to cloud, with AI helping refactor. Your starting artefact is a legacy module you maintained.
Assumes 2–3 hours a day alongside job applications, a laptop and a phone, and free plans only. Every step has a smaller version and a way to pause. Use them. It runs in three blocks of 30 days, each ending with a signal that you're on track. A signal is not a promise of a job or income.
What AI changed in your old tasks
| You used to… | Now you… |
|---|---|
| Patched a Java 8 monolith | Upgrade to Java 21 and Spring Boot 3 |
| Built WARs for app servers | Containerise and deploy |
| Read old code alone | Use AI assistants to explain and refactor, then verify with tests |
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | Describe a legacy module you maintained (no client code) | Description |
| 2 | Clone an old open-source Spring app (e.g. spring-petclinic history) | Repo |
| 3 | Write characterisation tests for 3 flows | Tests |
| 4 | Upgrade Java and Spring with OpenRewrite recipes | Build passes |
| 5 | Use a free AI assistant to refactor one class; review diffs | Diff notes |
| 6 | Dockerise and run locally | Container runs |
| 7 | Save 8 'Java modernisation', 'Spring Boot migration' postings | 8 links |
Days 1–30: An upgrade case
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Publish repo with migration log | about 14 hours across 3 weeks | Repo | Tests + upgrade. | It is fine to hold “publish repo with migration log” until next month. |
| Share with 4 Java leads | about 2 hours | 4 | Share with 2 Java leads. | You can defer “share with 4 Java leads” when energy returns. |
Signal by day 30: A lead asks about OpenRewrite.
Days 31–60: Cloud deploy
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Deploy to a free tier (Render/Fly) and add health checks | about 8 hours | Live | Container only. | It is fine to hold “deploy to a free tier (Render/Fly) and add health checks” when energy returns. |
| Apply to 10 Java/Spring roles | about 5 hours | 10 | Apply to 5 Java/Spring roles. | OK to shelve “apply to 10 Java/Spring roles” till a lighter week. |
Signal by day 60: A screening call.
Days 61–90: Interview depth for java modernisation roles
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Revise Java 17/21 features and practise 2 system-design prompts | about 6 hours | Notes | 1 prompt. | OK to shelve “revise Java 17/21 features and practise 2 system-design prompts” for a fortnight. |
| Ask 2 ex-architects for referrals | about 1 hour | 2 | Ask 1 ex-architect for referrals. | It is fine to hold “ask 2 ex-architects for referrals” till a lighter week. |
Signal by day 90: A technical round.
Job-hunt moves that matter for this route
- Search 'Java modernisation', 'Spring Boot', 'legacy migration' on Naukri.
- BFSI GCCs and services firms have big migration programmes.
- Tests before refactors — say so in interviews.
Where the openings are, and what to type
Also worth a weekly look: Instahyre, Cutshort, Wellfound, and iimjobs or hirist for senior roles. Upwork and Contra if you want freelance work.
IT services firms and banks upgrading old Java estates to current LTS versions and Spring Boot. Naukri carries many migration and 'Java upgrade' posts; LinkedIn adds GCC roles.
- LinkedIn search string:
("Java modernization" OR "Spring Boot migration" OR "Java 21" OR "legacy modernization") AND Java - Naukri / foundit keywords: Java migration, Spring Boot upgrade, legacy application modernisation Java
Worries people bring to this route
- Is 40+ too old for Java hiring? Old codebases need people who remember why the old code looks that way.
- A gap on the CV. Upgrade a public Java 8 project to a current LTS and publish the dated diff and notes.
- Degree filters. Services firms often use skills tests; prepare for those.
- English in design reviews. Migration plans are checklists and risk tables.
- Family worries Java is dying. Banks still run huge Java estates that need upgrading. That's this route.
- Short runway. Standard Java developer roles accept the same project.
Modernisation route pay
We haven't verified pay data for modernisation roles.
Watch for these scams
Placement-guarantee "modernisation architect" courses, recruiter fees, OTP or UPI PIN requests. Official domains only. Report: cybercrime.gov.in / 1930 (India), ReportFraud.ftc.gov (US).
Senior questions about modernisation
Is it just maintenance? No — it's risk management with code. Done well, it lets organisations keep running safely. Will AI tools replace this? They speed up mechanical change. Deciding what's safe to change, and proving it, stays human work. Our view.
Quiz · Related: SRE / production support · MuleSoft
The upgrade, as a comic strip
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
Quick quiz: does this path fit?
Answer each, then press Check. Every answer explains itself.
Make your Path Card
A shareable reminder of where you're heading. The day count starts the first time you open this page; quest XP comes from your log above.
Scam check before you apply anywhere
- Real job and gig platforms are free to join. Never pay a "joining" or "training" fee.
- Never share an OTP or UPI PIN — no genuine employer needs them.
- Use official domains only; type the address yourself.
- India: report at cybercrime.gov.in or call 1930.
- US: report at ReportFraud.ftc.gov.
Small steps, every day.
Each quest has a smaller version for hard weeks, and a pause button. Nothing is lost.
Keep exploring
Sources
Checked 23 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).
| What we checked | Where |
|---|---|
| Spring Boot | spring.io |
| OpenRewrite | docs.openrewrite.org |
| Java roadmap | oracle.com |