Migrate Remix to Next.js

Why Remix Teams Are Moving to Next.js

Remix had a clear identity: server-first React with colocated loaders, actions, and UI in a single route file. Then Shopify acquired it. Then it merged into React Router. Now it's React Router 7 with "Framework Mode" — a rebrand that left thousands of developers wondering what they're actually building on.

The React Router 7 transition introduced package restructuring (@remix-run/* → @react-router/*), configuration file changes, component renames (RemixServer → ServerRouter, RemixBrowser → HydratedRouter), and breaking type system changes. For many teams, this was the final signal to move to something with a clearer roadmap.

Next.js is that something. With the App Router, React Server Components, Server Actions, and Vercel's backing, Next.js delivers everything Remix promised — plus ISR, edge rendering, and the largest React framework ecosystem in production.

The React Router 7 Problem

Let's be direct about what happened. Remix v2 was a solid framework. The merge into React Router 7 created real problems.

Identity Crisis

Is it a router or a framework? React Router 7 ships three modes: Declarative Routing, Data Router, and Framework Mode. Framework Mode is essentially Remix rebranded, but try explaining that to a new hire reading the docs for the first time. The community's split between people using it as a SPA router and people using it as a full-stack framework.

Ecosystem Uncertainty

The @remix-run/* packages are deprecated. Migration guides exist, but they're mechanical — swap package names, rename components, update types. What they don't answer is whether this platform will go through another identity shift in 18 months. RSC support is "on the way" but still hasn't shipped. Next.js has had stable RSC since version 13.

Shrinking Mindshare

Stack Overflow answers, tutorial content, hiring pools — Next.js dominates all of them. Finding Next.js developers is straightforward. Finding someone who deeply understands React Router 7 Framework Mode? That's a much smaller pool.

What Next.js Gives You

Moving from Remix to Next.js isn't a rewrite. Both frameworks are React. Your components, hooks, and UI libraries come along mostly untouched. The real migration work is in data fetching patterns and routing conventions.

Server Components by Default

Next.js App Router components are server components by default. No special syntax, no loader functions — just async components that fetch data directly. For read-only pages, this is simpler than Remix's loader pattern.

// Remix loader pattern
export const loader = async () => {
  const posts = await db.posts.findMany();
  return { posts };
};

export default function Posts() {
  const { posts } = useLoaderData<typeof loader>();
  return <PostList posts={posts} />;
}

// Next.js Server Component
export default async function Posts() {
  const posts = await db.posts.findMany();
  return <PostList posts={posts} />;
}

Fewer abstractions. Fewer imports. The data lives right where the component is.

Server Actions Replace Form Actions

Remix's action export for form mutations maps cleanly to Next.js Server Actions. The mental model's similar — server-side mutation functions — but Server Actions are more composable. They work across components, not just at the route level.

// Next.js Server Action
'use server';

export async function updateProfile(formData: FormData) {
  const name = formData.get('name');
  await db.users.update({ where: { id: userId }, data: { name } });
  revalidatePath('/profile');
}

Rendering Flexibility

Remix gives you one rendering strategy: server-first. Next.js gives you SSG, SSR, ISR, and edge rendering — per route. A marketing page can be statically generated with ISR revalidating every 60 seconds while your dashboard streams server-rendered data. That flexibility directly affects performance and hosting costs.

Edge-Ready Infrastructure

Deploy to Vercel's edge network and your TTFB drops to sub-100ms globally. Remix can run on Cloudflare Workers, but Next.js on Vercel is turnkey — no custom server setup, no adapter configuration.

Our Migration Process

We've migrated Remix applications ranging from 20-route marketing sites to 200+ route SaaS platforms. Here's the process we've refined:

Phase 1: Audit and Architecture (Week 1)

We map every Remix route, loader, action, and error boundary. We identify which pages should be static (SSG/ISR), which need server rendering, and which require client interactivity. We also audit your current Lighthouse scores, Core Web Vitals, and indexed URLs to establish baselines.

Phase 2: Foundation Setup (Week 1-2)

We scaffold the Next.js App Router project, configure TypeScript, wire up your existing styling solution (Tailwind, CSS Modules, styled-components), and set up the deployment pipeline on Vercel or your preferred host.

Phase 3: Route Migration (Weeks 2-4)

This is the bulk of the work. Each Remix route file gets decomposed:

• Loaders → Server Components with direct data fetching, or generateStaticParams + fetch for static pages
• Actions → Server Actions in dedicated actions.ts files
• Error Boundaries → Next.js error.tsx convention
• Meta functions → Next.js generateMetadata
• Links → Next.js <Link> (nearly identical API)
• Nested layouts → Next.js layout.tsx files (this maps cleanly since both frameworks use nested routing)

React components rarely need changes beyond import paths. Your <Button>, your <Card>, your custom hooks — they all transfer directly.

Phase 4: SEO Preservation (Week 4-5)

This step isn't optional. We implement:

• 301 redirects for every URL that changes structure, configured in next.config.js
• XML sitemap generation via app/sitemap.ts
• Canonical URLs on every page
• Structured data (JSON-LD) migration
• OpenGraph and Twitter card metadata via generateMetadata
• Google Search Console monitoring for crawl errors post-launch

We've handled migrations where zero ranking pages were lost. The key is redirect mapping and metadata parity — we verify every indexed URL has a corresponding destination.

Phase 5: QA, Performance, and Launch (Week 5-6)

We run full Lighthouse audits, cross-browser testing, and load testing before cutting over DNS. Post-launch, we monitor Core Web Vitals and Search Console for two weeks to catch issues early.

Timeline and Pricing

Small Remix apps under 30 routes typically migrate in 3-4 weeks starting at $8,000. Mid-size applications (30-100 routes) run 5-8 weeks at $15,000-$30,000. Enterprise Remix platforms with complex data patterns, authentication, and extensive API integrations are scoped individually.

Every engagement starts with a free migration audit. We'll review your Remix codebase, identify the migration complexity, and deliver a fixed-price proposal within 48 hours.

The Bottom Line

Remix was a great framework. React Router 7 may find its footing eventually. But right now, Next.js has the ecosystem, the tooling, the deployment infrastructure, and the community momentum that production applications need. If the React Router rebrand has your team questioning the future of your stack, that instinct is worth acting on.