lifecycle/migrate-from-nextjs

Migrating Next.js App Router routes to TanStack Start requires mapping your app/pages and app/routes directories to TanStack Start route definitions and file naming conventions. The migration process provides an end-to-end plan with code examples to ensure routing parity.

Converting Next.js server actions to TanStack Start server functions involves transforming form- and action-based logic into createServerFn-powered endpoints. This adaptation maintains your data mutation workflows while enabling isomorphic execution across the unified TanStack structure.

Migrating middleware and data fetching from Next.js to TanStack Start requires rewriting your middleware, loaders, and data-fetch patterns. This ensures correct SSR behavior and isomorphic execution within the TanStack Start architecture.

Yes, achieving isomorphic execution and SSR parity when moving from Next.js to TanStack Start is the core objective. The migration guide includes a checklist to verify routing parity, safe upgrades, and correct server-side rendering behavior across typical project structures.

Migrating complex Next.js project structures with nested routes and middleware to TanStack Start requires careful adaptation of API routes and server functions. Limitations involve ensuring all data-fetch patterns are rewritten correctly to maintain isomorphic execution and routing parity without breaking SSR.