vercel-migration-deep-dive

name	vercel-migration-deep-dive
description	Migrate to Vercel from other platforms or re-architecture existing Vercel deployments. Use when migrating from Netlify, AWS, or Cloudflare to Vercel, or when re-platforming an existing Vercel application. Trigger with phrases like "migrate to vercel", "vercel migration", "switch to vercel", "netlify to vercel", "aws to vercel", "vercel replatform".
allowed-tools	Read, Write, Edit, Bash(vercel:*), Bash(npm:*), Bash(npx:*)
version	1.18.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","vercel","migration","replatform"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Vercel Migration Deep Dive

Overview

Migrate applications to Vercel from Netlify, AWS (Lambda/CloudFront/S3), Cloudflare Workers, or traditional hosting. Covers configuration mapping, DNS cutover, feature parity validation, and incremental migration with the strangler fig pattern.

Current State

!vercel --version 2>/dev/null || echo 'Vercel CLI not installed' !cat package.json 2>/dev/null | jq -r '.name // "no package.json"' 2>/dev/null || echo 'N/A'

Prerequisites

• Access to current hosting platform
• Git repository with application source
• DNS management access for domain cutover
• Vercel account (Pro recommended for production)

Instructions

Step 1: Configuration Mapping

From Netlify:

Netlify	Vercel Equivalent
netlify.toml	vercel.json
_redirects / _headers	vercel.json redirects/headers
Netlify Functions (netlify/functions/)	API routes (api/)
Netlify Edge Functions	Edge Middleware or Edge Functions
NETLIFY_ENV	VERCEL_ENV
Deploy previews	Preview deployments (automatic)
Branch deploys	Branch preview URLs

// Netlify _redirects → vercel.json
// FROM: /old-page /new-page 301
// TO:
{
  "redirects": [
    { "source": "/old-page", "destination": "/new-page",