Spring Boot and Java upgrade assessment
Open-source support for each Spring Boot line is limited in time, and many companies run services on versions that no longer get fixes. This assessment tells you what it would take to move, in what order, and where the risks are, before you commit a team to the work.
Who it is for
Teams with several Spring Boot services on Boot 2.x or early 3.x, or Java 8/11, who need a realistic plan and effort range for management or an audit.
What you get
- An inventory of your services: Spring Boot and Java versions, main dependencies, build tools and runtime.
- A risk list per service, based on the real changes between versions: the move from javax to jakarta namespaces, the Java 17 minimum for Spring Boot 3, the removal of WebSecurityConfigurerAdapter in Spring Security 6, Hibernate 6 behaviour changes, and deprecated configuration properties.
- A recommended migration order (low-risk services first, shared libraries early) with the intermediate versions to step through.
- Effort ranges per service and a test strategy, so you can plan the work or compare quotes.
- A short list of quick wins: dependency updates and configuration clean-ups you can do now.
How it works
- A short scoping call to agree which repositories are in scope.
- You send build files (pom.xml or Gradle files) and, if you wish, anonymised configuration. No production access is needed.
- You receive the written report and a walkthrough call.
What is not included
- The migration itself (it can be quoted separately after the assessment).
- Legal or contractual advice about Java distributions or licences.
- A guarantee of the exact effort: ranges depend on test coverage and code quality.
Why now
According to spring.io (checked 30 October 2026): open-source support for Spring Boot 3.5 ended on 30 June 2026, and for Spring Boot 4.0 it ends on 31 December 2026. Commercial support for 3.4 also ends on 31 December 2026. All earlier lines (2.x, 3.0–3.4) no longer receive open-source fixes.
Price and timing
Launch price: 490 € fixed for up to 5 services or repositories, plus 60 € for each additional service. Written report within 5 working days of receiving the build files. Prices exclude VAT where applicable.
Send us a short message with what you run and what you need. We reply with questions or a proposal. We do not send unsolicited messages.
Message us on LinkedInFrequently asked questions
Where do I find current support dates?
Check the Spring Boot support policy on spring.io and the support page of your Java vendor. The report states the dates it used and when they were checked.
Do you need access to our code?
Build files are enough for the plan. For a deeper review of specific modules we agree access and confidentiality first.
Can you do the migration too?
Yes, as a separate, scoped engagement after you have seen the plan.
Free tools that help you start
JVM and pool sizing · OAuth2 and CORS error guides · PostgreSQL error codes
Adamant Solutions is an independent consultancy. Product names belong to their owners. This page describes a service; it is not a guarantee of results. Privacy and cookies · Terms