lifecycle/migrate-from-nextjs

To migrate Next.js App Router projects to TanStack Start, translate page routes, layouts, and data-fetching patterns from the app/ directory into src/routes/ using Start conventions, replacing Next.js primitives with Start equivalents.

The best way to convert Next.js server actions to TanStack Start is enforcing server function usage. This translates server actions and data loading to Start equivalents, maintaining isomorphic execution and server-side logic.

Yes, you can incrementally migrate a large Next.js codebase to TanStack Start. The approach uses concrete mapping patterns and incremental adoption steps to reduce risk and validate correctness across the project.

Middleware translation works by mapping Next.js middleware to TanStack Start primitives. The migration scope covers middleware, server functions, and SEO metadata to ensure isomorphic behavior is preserved.

Yes, this migration handles SEO metadata translation from Next.js. The scope covers SEO metadata across a typical project, ensuring data loading and metadata generation correctly map to their TanStack Start equivalents.

You validate correctness after migrating Next.js data loading by applying the provided migration checklist. This validates correctness and performance, ensuring isomorphic behavior with TanStack Start primitives.