Framework Upgrade

Migrate Next.js 13 to Next.js 14 Automatically

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

Start Migration

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

  • Minimum Node.js version raised from 16.14 to 18.17
  • Server Actions moved from experimental to stable; 'use server' directive is now the standard pattern
  • next export command removed in favor of output: 'export' in next.config.js
  • Metadata API changes: viewport, colorScheme, and themeColor moved from metadata to dedicated viewport export
  • next/image default import changed from ImageResponse; use og import path instead
  • Partial Prerendering introduced as experimental feature requiring config opt-in
  • next/font import stabilized; @next/font package deprecated
  • WASM target support and improved tree shaking for smaller bundles

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

01

Connect your project

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

02

Nivo detects your Next.js 13 project

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

03

AI applies all Next.js 14 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 breaks when upgrading from Next.js 13 to 14?

The main breaking changes are the minimum Node.js 18.17 requirement, the removal of next export in favor of config-based output, and the viewport/themeColor metadata split. Server Actions also moved from experimental flags to stable, so you need to remove experimental.serverActions from your config.

Is the Next.js 13 to 14 migration safe for production apps?

Yes. Next.js 14 is largely backward-compatible with 13. Nivo identifies and updates the specific breaking points—metadata exports, image imports, and config changes—while leaving stable code untouched.

How long does a Next.js 13 to 14 migration take?

Typically 5 to 10 minutes. The migration is lighter than the 14 to 15 jump because most APIs remained stable. The bulk of changes involve metadata exports and configuration adjustments.

Do I need to rewrite my App Router code?

No. The App Router is stable in both versions. The main updates involve removing experimental flags for Server Actions and adjusting metadata exports. Your routing structure, layouts, and loading states remain unchanged.

Can I skip from Next.js 13 directly to 15?

While possible, it is recommended to migrate incrementally. Nivo supports a two-step approach: 13 to 14 first, then 14 to 15. This avoids compounding breaking changes and makes debugging easier.

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

Start Migration

Free tier available — no credit card required

Related Migrations

Next.js 14Next.js 15

Automatically migrate your Next.js 14 project to Next.js 15. Handles async request APIs, new caching defaults, React 19 integration, and Turbopack changes 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
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