Back to Blog

Spring Boot 3 Is Out of Free Support. Here Is the No-Drama Path to Boot 4 and Java 25

• 3 min read • Ahmed Daoudi

Plenty of production Java services are still on Spring Boot 3, and many teams have not noticed the clock ran out. Spring Boot gives each minor release roughly 13 months of open-source updates, then moves it to paid commercial support through Broadcom's Tanzu Spring. With 3.5 past that window in mid-2026, the whole 3.x line is now in that commercial-only phase.

Where things stand

On the JDK side, check your vendor. Oracle's free license terms for Java 21 ended a year after Java 25 arrived, while distributions such as Eclipse Temurin keep shipping 21 updates on their own schedule. Either way, Java 25 is where new work should land.

The migration in five steps

1. Get to the latest 3.5.x first

Do not jump from 3.1 straight to 4.1. Move to the newest 3.5 patch, fix every deprecation warning, and make sure the test suite is green. Most of the breaking changes in 4.0 remove things that were deprecated in 3.x, so a clean 3.5 build is half the migration.

2. Let OpenRewrite do the boring part

OpenRewrite has recipes for Spring Boot 4 that rewrite imports, properties and dependency coordinates. Run them on a branch, read the diff, and commit in small pieces so reviewers can follow.

3. Plan for Jackson 3

Boot 4 defaults to Jackson 3, which moves to new package names. Custom serializers, ObjectMapper customizations and anything that reflects on Jackson types needs attention. This is where JSON contracts can break silently, so add tests that compare serialized responses against known fixtures before you upgrade.

4. Check the modular starters and null-safety

Spring Boot 4 split auto-configuration into more focused modules, so a build that compiled on 3.x can fail at startup if a starter is missing. Spring Framework 7 also adopts JSpecify annotations for null-safety, and Kotlin code in particular will surface new warnings.

5. Then move the JDK

Once the app runs on Boot 4 with Java 17 or 21, switch the toolchain to 25. You get the newer garbage collector improvements and mature virtual threads, which in Boot can be enabled with a single property.

Where migrations actually go wrong

In my experience the compile errors are the easy part. The painful bugs are runtime ones: a property that was renamed and now silently falls back to a default, a security filter chain that behaves differently, a lazy-loading assumption in JPA that only fails under real traffic. If your entities lean on Lombok's @Data, read my post on Spring Boot, Lombok and JPA antipatterns before you start, because an upgrade is the moment those problems surface.

Treat it as a platform migration, not a version bump: staging environment, real traffic replay if you can, and a rollback plan. It is a week of careful work for most services, and far cheaper than running unsupported software in production.

Sources