Leave Vercel for Your Own Server: A Next.js Migration Runbook

Description and use

Step‑by‑step plan to migrate a Next.js app from Vercel to Levelrail, covering inventory, mapping, test deployment, DNS cutover, and shadow run.

Problem

Migrating a Next.js app from Vercel to a self‑hosted platform requires moving configuration that lives only in Vercel’s dashboard, such as environment variables, domains, cron jobs, and integrations.

Outcome

The migration runbook enables a controlled, reversible transition from Vercel to Levelrail, preserving environment variables, domains, cron jobs, and other settings while allowing a shadow run to validate correctness.

Workflow

• Inventory Vercel configuration items
• Map each Vercel concept to a Levelrail counterpart
• Build the app on a test URL without real domains
• Lower DNS TTLs and switch DNS records
• Run a shadow period with both platforms active

Evidence

Moving off Vercel is hard because of configuration, not code.

Source

Vercel holds configuration in its dashboard that never lived in your repo: env vars per environment, domain redirects, cron schedules, integrations.

Source

Run the new setup beside Vercel, and keep Vercel as your rollback until the checks at the end pass.

Source

Vercel has no automatic importer. Everything here is manual.

Source

The platform injects env only when a container starts, so it never reaches the build.

Source