Netlify to Vercel Migration

Point this agent at a repository that deploys to Netlify and ask it to plan the move to Vercel. It reads netlify.toml, _redirects, _headers, and your functions directories, then produces Vercel-side configuration it can deploy and verify against a preview.

What it does

1. Map the Netlify surface: netlify.toml, _redirects, _headers, serverless and edge functions, build plugins, deploy contexts, env vars, and Forms/Identity usage — each finding tiered mechanical / rework / redesign.
2. Plan a site-by-site migration: env var transfer, DNS and preview strategy, feature-gap decisions before cutover, and a rollback path.
3. Generate the Vercel config: vercel.json redirects/headers/rewrites, functions converted to Vercel Functions or framework API routes, edge functions converted to Edge Middleware, and build settings mapping.
4. Sandbox — deploy a preview to a test team with VERCEL_TOKEN, then curl-assert redirect, header, and rewrite parity rule by rule and report PASS/PARTIAL/FAIL evidence.

Prerequisites

• VERCEL_TOKEN — Vercel access token scoped to a test team
• VERCEL_TEAM_ID — optional; team slug/ID for deploys when the token can reach more than one team
• NETLIFY_AUTH_TOKEN — optional; read-only enumeration of live Netlify sites, env vars, and forms for mapping

Current scope

This solution migrates static/framework sites, redirect/header/rewrite rules, serverless functions, edge functions, and build settings. It does not migrate Netlify Forms submissions or provide a form backend, does not port Netlify Identity users (an external auth provider is required), does not translate build plugins, and does not change your DNS — cutover is planned but executed by you.