How We Incrementally Migrated to Next.js and Vercel

A company migrated its marketing website from a no-code WYSIWYG platform to Next.js hosted on Vercel to gain greater design flexibility, safer code changes, review processes, and support for richer interactions. Its existing experience with React and Next.js, combined with Next.js features such as file-based routing, server-side rendering, API routes, and Vercel’s fast deployments, preview environments, and serverless-function support, made the combination suitable for the project. Rather than rebuilding every page before launch, the team used Next.js Rewrites to serve newly built pages while proxying unavailable routes to the old marketing site or documentation, enabling an incremental transition and earlier feedback. They also manually maintained sitemap coverage for legacy pages to avoid search-indexing gaps. To preserve marketing-team autonomy, the site uses server-side rendering to load content from the Sanity CMS, allowing nontechnical users to publish pages from predefined templates, while developers continue to build more complex and interactive components in React and CSS.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.