Decision tree: what kind of modernisation suits you?
Do you enjoy deep code work more than meetings? → Yes → Prefer automation or hand-crafting? → Automation → Upgrade engineer: bulk version and framework upgrades using tools such as OpenRewrite. → Hand-crafting → Refactoring specialist: breaking up tangled code, adding tests, improving structure. → No, I like planning → Comfortable with cloud and infrastructure? → Yes → Migration lead: moving apps to containers and cloud platforms. → No → Modernisation assessor: reviewing estates, estimating effort, writing roadmaps.
All four exist within IT services and consulting practices.
The modernisation checklist
Ticking all Eight fills the bar. Three in week one is a solid start.
⏳ Version Time Machine
A horizontal timeline from Java 8 to Java 25 with a small time-machine icon you drag along it. At each LTS stop, a card pops up with one friendly "what changed for everyday code" note (for example, var for local variables arriving after 8, records and text blocks by 17, virtual threads in 21) and the support status from Oracle's roadmap as of 23 Oct 2026. The far right shows "Java 29 — planned LTS, Sept 2027" in dotted outline. A fixed, human-checked set of notes.
Java time machine
Support dates worth knowing
From Oracle's roadmap (updated 20 Oct 2026): Java 17 Premier Support to September 2026 and Extended to September 2029; Java 21 Premier to September 2028; Java 25 Premier to September 2030. Oracle JDK 25 is offered under a free-use licence. Other vendors publish their own OpenJDK support dates. Licensing choices are a legal matter for each organisation; we don't advise on them.
The proof project: a before/after upgrade
- Pick an older open-source Java app with tests.
- Get the tests running on its original version; record the baseline.
- Use OpenRewrite recipes to move it to a newer LTS (and Spring Boot version, if used).
- Fix what automation can't.
- Write a before/after report: what changed, what broke, time taken, risks left.
That report is the deliverable modernisation clients actually buy.
Writing the before/after report
Keep it to two pages. Starting point: versions, framework, test count and pass rate, build time. What changed: the recipes you ran, the manual fixes, the libraries replaced. What broke and why: honest notes — a reflection-based library, a removed API, a date-format change. Results: tests green, build time, any performance notes you actually measured. Risks left: what you'd test more before production. Effort: hours spent, split into automated and manual.
Assessors and hiring managers read these reports for one thing: does this person understand risk? A calm, specific report answers yes.
Phrases to describe your experience
"Upgraded a 120k-line Spring application from Java 8 to 17, keeping all 900 tests passing" (use your real numbers). "Wrote characterisation tests before refactoring a payment module." These lines matter more than any title.
Where modernisation work is
India: IT services firms with application modernisation practices, banks and insurers with large Java estates, and GCCs running platform upgrades. Global: consulting firms and cloud partners; contract work for assessments. Visa questions are outside our scope.
Your realistic 90 days
You know the old Java estate: Java 8, Spring 4, XML config, javax everywhere, tests nobody runs. Modernisation specialists move these systems to current Java and Spring Boot without breaking production, using tools like OpenRewrite and AI assistants carefully. You'll start with a codebase shaped like the ones 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.
The two worries we hear most about this move
Isn't legacy Java a dead end? Many banks, insurers and government systems in India still run on older Java, and moving them to newer versions and cloud is ongoing work. Knowing the old code is an advantage here, not a weakness. Do I need cloud certifications? They help with some employers, but they aren't the first step. A small, real migration (for example, an old app upgraded to a current Java version with tests) shows more. Consider a certification once interviews start.
Other worries, such as age, a career gap, no degree, English, family pressure and savings, are covered on the route page and the role page.
What AI changed in your old tasks
| You used to… | Now you… |
|---|---|
| Patched old services and avoided upgrades | Plan and run the upgrade with recipes, tests and a rollback |
| Fixed javax → jakarta errors one by one | Apply automated recipes and review every change |
| Wrote release notes for small fixes | Write a migration report: risks, changes, test evidence |
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | Find an open-source Spring app on Java 8 or Spring Boot 2 on GitHub | Repo forked |
| 2 | Build it and run its tests; note failures | Baseline noted |
| 3 | Read OpenRewrite's docs on Spring Boot 3 migration recipes | Notes |
| 4 | Run the recipe on a branch | Diff produced |
| 5 | Fix what breaks; record each manual change | A change log |
| 6 | Run tests again and compare | Before/after test results |
| 7 | Save 10 modernisation, migration or Java upgrade postings | 10 links |
Days 1–30: One upgrade with evidence
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Publish the upgrade branch with a migration report (what the tool did, what you did by hand, tests) | about 14 hours over 3 weeks | repo + report | Report only. | Stop at the end of the step you're on and write two lines about where you stopped. Pick it up from those notes later. |
| Send it to 5 ex-colleagues still on old Java estates | about 2 hours | 5 messages | Send it to 2 ex-colleagues still on old Java estates. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: Someone technical asks how long a similar upgrade would take at their company.
Days 31–60: Use AI assistance carefully
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Use an AI assistant to modernise one module and document every suggestion you rejected and why | about 10 hours | a log of accepted and rejected suggestions | 5 suggestions. | Stop at the end of the step you're on and write two lines about where you stopped. Pick it up from those notes later. |
| Apply to 10 java modernisation roles | about 5 hours | 10 logged | Apply to 5 roles. | Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up. |
Signal by day 60: A screening call.
Days 61–90: Show risk thinking
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Write a 1-page migration plan for a large monolith: phases, rollback, testing | about 3 hours | plan written | Bullets. | Optional. Skip it if the week is full; nothing later depends on it. |
| Post your migration report summary on LinkedIn | about 2 hours | post live | DM 3 people. | Write it as a draft and publish later. A saved draft still counts. |
Signal by day 90: A second-round interview.
One search that fits your background
The full set of search strings for this move is on the route page. They work on LinkedIn, Naukri and foundit; Instahyre and Cutshort are worth a weekly look too. Add your old job title to any of them with AND, so recruiters who want both skills find you first.
Job-hunt moves that matter for this route
- Banks, insurers and GCCs hire for Java upgrades. Search 'Java 17 migration', 'Spring Boot 3 upgrade', 'modernisation'.
- Show test evidence. Modernisation buyers fear outages.
- Ex-colleagues on old estates are your warmest leads.
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
Modernisation pay
Ask employers directly and compare offers carefully. We haven't verified pay data for modernisation roles. Offers vary widely by employer, contract type and city; compare written offers carefully rather than relying on online figures.
Scams in the upgrade market
"Certified modernisation expert" courses with placement promises, and fee-charging recruiters. Never share OTPs or UPI PINs. Official domains only. Report: cybercrime.gov.in / 1930 (India), ReportFraud.ftc.gov (US).
Modernisation questions
Will AI do all the upgrades? Tools and AI already automate a lot of mechanical change. Judgement about risk, testing and sequencing stays with people. Our view. Do I need cloud certifications? Helpful for migration-lead roles; not required to start.
Next: Java modernisation route · Java → MuleSoft · Quiz
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).
The other facts here are shared with the route page, where each is listed in full with its link.