Architecture Migration

Migrate Nuxt 2 to Nuxt 3 Automatically

Upload your project and get production-ready migrated code in minutes.

Start Migration

What changes between Nuxt 2 and Nuxt 3?

  • Vue 3 and Composition API required; Options API still works but asyncData/fetch replaced by useAsyncData/useFetch
  • Nitro server engine replaces serverMiddleware; API routes move to server/api/ directory
  • Auto-imports for composables, components, and utilities; explicit imports often unnecessary
  • nuxt.config.js becomes nuxt.config.ts with restructured configuration options
  • Directory structure changes: store/ to composables/ or Pinia, middleware behavior updated
  • Runtime config replaces process.env pattern; useRuntimeConfig() composable required
  • Vuex replaced by useState composable or Pinia for state management
  • Plugin system overhauled: defineNuxtPlugin with nuxtApp parameter

How Nivo migrates Nuxt 2 to Nuxt 3

01

Connect your project

Paste a GitHub URL or upload a ZIP file of your Nuxt 2 project.

02

Nivo detects your Nuxt 2 project

The engine scans your codebase to identify Nuxt 2 patterns, APIs, and configuration that need updating.

03

AI applies all Nuxt 3 migration transforms

Hybrid AST + AI engine applies deterministic transforms for configuration and dependencies, and AI-powered transforms for complex code changes. Every change gets a confidence score.

04

Download migrated codebase + review report

Get a ZIP with your fully migrated code, a complete migration report, and a checklist of items flagged for manual review.

Frequently Asked Questions

What are the biggest changes from Nuxt 2 to Nuxt 3?

The migration to Vue 3 underpins everything: Composition API, new reactivity system, and template changes. The Nitro server engine replaces the old serverMiddleware with a new file-based API routing system. Configuration and directory conventions have also changed significantly.

Is the Nuxt 2 to 3 migration safe for production?

Yes. Nivo transforms your pages, components, plugins, middleware, and server routes to Nuxt 3 conventions. Each file gets a reviewable diff. The Nuxt Bridge module is also supported for incremental migration.

How long does a Nuxt 2 to 3 migration take?

Most projects complete in 15 to 25 minutes. Nuxt 2 to 3 is one of the larger framework migrations due to the combined Vue 2-to-3 and Nuxt-specific changes. Nivo handles both layers simultaneously.

What happens to my Vuex store?

Nivo migrates Vuex modules to either Pinia stores or Nuxt's built-in useState composable, depending on complexity. Simple state can use useState; complex stores with actions and getters map well to Pinia.

Do I need to rewrite my API routes?

Server middleware and API routes move from serverMiddleware in nuxt.config to the server/api/ directory with file-based routing. Nivo restructures your server code into the new Nitro convention automatically.

Start your Nuxt 2 to Nuxt 3 migration

Start Migration

Free tier available — no credit card required

Related Migrations

Vue 2Vue 3

Automatically migrate Vue 2 to Vue 3. Handles Composition API adoption, v-model changes, removed filters, Vuex to Pinia, and template compiler updates.

Architecture Migration
Next.js Pages RouterNext.js App Router

Automatically migrate Next.js Pages Router to App Router. Handles getServerSideProps to Server Components, layouts, metadata API, and data fetching patterns.

Architecture Migration
WebpackVite

Automatically migrate from Webpack to Vite. Converts webpack.config.js to vite.config.ts, handles loaders-to-plugins mapping, HMR, and bundle optimization.

Architecture Migration