migrate-spring-to-quarkus

Name: migrate-spring-to-quarkus
Availability: InStock
Author: QuarkusIO

Migrate Spring Boot applications to Quarkus with build and code transformation.

30|10|Updated Mar 24, 2026

Search Tags:#migration #quarkus #spring boot #java refactor #configuration mapping #jpa panache #rest jax-rs

Ready to run

npx skills add https://github.com/quarkusio/skills --skill migrate-spring-to-quarkus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-spring-to-quarkus
Source: https://github.com/quarkusio/skills/tree/main/skills/migrate-spring-to-quarkus
Command: npx skills add https://github.com/quarkusio/skills --skill migrate-spring-to-quarkus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrating a Spring Boot application to Quarkus can be risky and time-consuming because code, configuration, and testing patterns differ significantly between the two ecosystems.

Core Features & Use Cases

Modular, gate-driven migration flow that conditionally runs build, code, frontend, testing, and cleanup phases based on what exists in your project.
Two migration strategies: Spring compatibility extensions for minimal changes, or native Quarkus migration for full adoption of Quarkus APIs.
Safety-first migration rules that avoid silent changes, preserve unmigratable code with explicit TODOs, and require compile verification after each phase.
Decision support using reference mappings for annotations, dependencies/extensions, and configuration property translation.

Quick Start

Tell the skill to migrate your project by running: migrate spring to quarkus.

Frequently Asked Questions about migrate-spring-to-quarkus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate a Spring Boot application to Quarkus without breaking the build?▼

To migrate a Spring Boot application to Quarkus safely, use a modular, gate-driven flow that conditionally transforms build setup, Java code, configuration, and tests, requiring compile verification after each phase to prevent build failures.

What is the best way to convert Spring Boot annotations and configuration to Quarkus equivalents?▼

The best way to convert Spring Boot annotations and configuration to Quarkus is by using reference-driven mapping tables that translate dependencies, annotations, and configuration properties directly into Quarkus equivalents.

Can I keep my existing Spring Boot code and still run on Quarkus?▼

Yes, you can keep existing Spring Boot code on Quarkus by selecting the Spring compatibility extension strategy, which minimizes changes, or use native Quarkus migration for full API adoption.

How do I handle unmigratable Spring code during a Quarkus migration?▼

During a Quarkus migration, unmigratable Spring code is preserved with explicit TODOs to avoid silent changes, ensuring you can identify and manually refactor remaining segments without breaking the project.

Does the Spring Boot to Quarkus migration convert Thymeleaf and JSP templates?▼

Yes, the Spring Boot to Quarkus migration process transforms optional Thymeleaf and JSP view layer templates alongside Java code, configuration, and testing patterns into Quarkus equivalents.