Framework Upgrade

Migrate Next.js 14 to Next.js 15 Automatically

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

Start Migration

What changes between Next.js 14 and Next.js 15?

  • Request APIs (cookies, headers, params, searchParams) are now asynchronous and must be awaited
  • Caching defaults changed: fetch requests, GET Route Handlers, and Client Router Cache are no longer cached by default
  • React 19 is the default peer dependency with new hooks like useActionState and useFormStatus
  • Turbopack Dev is now stable and replaces Webpack for local development
  • next/image removed squoosh in favor of sharp; alt prop is no longer defaulted to empty string
  • next.config.ts (TypeScript) is now the recommended config format
  • Bundled @next/codemod CLI for automated migration assistance
  • Server Actions are no longer experimental and have a stabilized API

How Nivo migrates Next.js 14 to Next.js 15

01

Connect your project

Paste a GitHub URL or upload a ZIP file of your Next.js 14 project.

02

Nivo detects your Next.js 14 project

The engine scans your codebase to identify Next.js 14 patterns, APIs, and configuration that need updating.

03

AI applies all Next.js 15 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 breaking changes in Next.js 15?

The most impactful change is that request APIs (cookies(), headers(), params, searchParams) are now asynchronous. This requires adding await throughout your Server Components and Route Handlers. Additionally, the caching defaults have been reversed: requests are no longer cached by default, so you may need to add explicit cache directives.

Is it safe to migrate a production Next.js 14 app to 15?

Yes. Nivo scans every file for async API usage, caching patterns, and deprecated imports before making changes. It generates a detailed diff for each file so you can review every transformation before merging. The tool preserves existing behavior while updating syntax.

How long does the automated migration take?

Most projects complete in under 10 minutes. The exact time depends on the number of files that reference request APIs, caching directives, and image components. Nivo processes files in parallel and only touches files that need changes.

Do I need to upgrade to React 19 when moving to Next.js 15?

Next.js 15 uses React 19 as its peer dependency. Nivo handles the React upgrade in tandem, including updating deprecated APIs like forwardRef (now unnecessary) and adjusting to the new ref-as-prop pattern.

Will my existing API routes and middleware continue to work?

API routes (Route Handlers) still work but their caching behavior has changed—GET handlers are no longer cached by default. Middleware continues to operate the same way, though the config matcher syntax has received minor updates.

How does Nivo handle the async request API migration?

Nivo statically analyzes every usage of cookies(), headers(), params, and searchParams across your codebase. It wraps each usage in await, converts the containing function to async if needed, and handles nested destructuring patterns automatically.

Start your Next.js 14 to Next.js 15 migration

Start Migration

Free tier available — no credit card required

Related Migrations

Next.js 13Next.js 14

Automatically upgrade your Next.js 13 project to Next.js 14. Handles Server Actions stabilization, metadata API changes, and partial prerendering preparation.

Framework Upgrade
React 18React 19

Automatically migrate React 18 to React 19. Handles ref-as-prop, removal of forwardRef, new use() hook, Actions API, and deprecated legacy APIs in minutes.

Framework Upgrade
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