Migrate from Netlify to Vercel
redirects, functions and all.
Vercel publishes a guide for this move. Most of the work is translating netlify.toml and _redirects into vercel.json and moving functions to Vercel's conventions.
Facts checked against each provider's own pages
The short answer
Import the repo into Vercel, translate netlify.toml build settings and _redirects rules into vercel.json (a 200 status in Netlify means a rewrite), move functions from Netlify's directory to Vercel's api/ directory with the Request/Response signature, turn edge functions into Routing Middleware, and re-enter environment variables per environment[1].
What maps to what
| On Netlify | On Vercel | Notes |
|---|---|---|
| netlify.toml [build] | Vercel project settings / vercel.json | Netlify's file overrides UI settings[2]; Vercel's is vercel.json[3]. |
| _redirects / [[redirects]] | vercel.json redirects and rewrites | Netlify status 200 = rewrite[1]. Each vercel.json rule counts toward 2,048 routes per deployment[4]. |
| netlify/functions/ | api/ directory | Netlify's default is netlify/functions/[5]; Vercel uses api/ with a Request/Response signature[1]. |
| netlify/edge-functions/ | Routing Middleware | Per Vercel's migration guide[1]. |
| [context.*.environment] and UI variables | Environment variables per environment | Paste a .env to bulk import; up to 1,000 per environment, 64 KB total[6]. |
| Deploy Previews | Preview deployments | Every non-production branch and PR[7]. |
| Netlify DNS / external DNS | Vercel domain settings | Apex via A record, subdomain via a project CNAME, or Vercel nameservers[8]. |
The migration, step by step
- 01
- 02
- 03
Move functions
Move each function from netlify/functions/ to api/ and adapt it to the Request/Response signature; move edge functions to Routing Middleware[1].
- 04
Re-create environment variables
Add variables for Production, Preview and Development; you can paste a .env file. Changes apply only to new deployments, so redeploy after editing[6].
- 05
Add the domain
Add it under Settings → Domains, then point an apex A record or a subdomain CNAME at Vercel, or delegate to Vercel's nameservers[8].
Things the docs warn about
- Vercel's migration guide says Netlify functions live in functions/, but Netlify's own docs give the default as netlify/functions/[5]; check netlify.toml's [functions] setting for your actual path.
- Vercel's Hobby plan is for personal, non-commercial projects[9]; a commercial site moving off Netlify Free needs Vercel Pro.
- Each redirect in vercel.json counts toward the 2,048-route limit per deployment[4]; large lists belong in Bulk Redirects.
- Netlify-specific features without a counterpart in Vercel's guide, such as Netlify Database[10], need their own plan; Vercel offers Postgres through Marketplace partners[11].
Run both during cutover, then switch
AW3 Host connects both your Netlify and Vercel accounts, so the old and new deployments run side by side from one dashboard and API instead of a big-bang switch.
Weighted routing sends a small share of traffic to Vercel first (for example 5%, then 25%, 50% and 100%) while Netlify serves the rest. Health checks every 60 seconds watch both; if the Vercel side fails, failover moves traffic back automatically, and rollback to the previous release is one step. Daily cost sync shows what each provider costs during the overlap, and budget policies alert you if the double-running period gets expensive. Secrets for both are stored encrypted per environment.
When Vercel has carried all traffic cleanly for long enough that you no longer need the fallback, point DNS at it for good and decommission Netlify.
Netlify vs Vercel at a glance
| Netlify | Vercel | |
|---|---|---|
| Category | Frontend platform | Frontend platform |
| Pricing model | Credit-based: each plan includes monthly credits that deploys, compute, bandwidth and requests draw down[12] | Per-seat plan plus metered usage; Pro's $20/mo fee includes one deploying seat and $20 of usage credit[15] |
| Compute billing granularity | Functions compute metered in GB-hours (10 credits per GB-hour); 2 credits per 10k web requests; 15 credits per production deploy[12] | Active CPU metered on actual CPU time and billed per CPU-hour; provisioned memory per GB-hour while an instance is alive[16] |
| Internet egress (first paid tier) | 20 credits per GB; derived ≈ $0.133/GB on Pro (extra credits $10 per 1,500) or $0.20/GB on Personal ($5 per 500)[12] | $0.15/GB on-demand Fast Data Transfer in US regions (iad1); $0.15–$0.35/GB by region[17] |
| Regions / locations | Functions: 12 self-serve regions, 2 more via support (counted from docs list)[13] | 19 compute regions; 126 points of presence[18] |
| Deploy model | Git continuous deployment, CLI or API[14] | Git push (GitHub, GitLab, Bitbucket) auto-deploys, or the Vercel CLI; OCI containers in beta[7] |
| Persistent volumes | — | — |
| Config file | netlify.toml (overrides UI settings); _redirects file for redirects[2] | vercel.json (or vercel.toml / vercel.ts)[3] |
Frequently asked questions
- How do I convert Netlify _redirects to Vercel?
- Turn each rule into an entry in vercel.json's redirects array, or rewrites for rules with a 200 status. Very large lists can use Vercel's Bulk Redirects with CSV, JSON or JSONL.
- Where do Netlify functions go on Vercel?
- Into the api/ directory, using the Request/Response signature. Netlify edge functions become Vercel Routing Middleware.
- Does Vercel have Netlify's Deploy Previews?
- Yes. Vercel creates a preview deployment for every push to a non-production branch and for every pull request.
Sources
- Vercel KB: Migrate to Vercel from Netlify. https://vercel.com/kb/guide/migrate-to-vercel-from-netlify (checked 2026-11-16)
- Netlify Docs: File-based configuration. https://docs.netlify.com/build/configure-builds/file-based-configuration/ (checked 2026-11-16)
- Vercel: Project configuration. https://vercel.com/docs/project-configuration (checked 2026-11-16)
- Vercel Docs: Redirects. https://vercel.com/docs/redirects (checked 2026-11-16)
- Netlify Docs: Get started with functions. https://docs.netlify.com/build/functions/get-started/ (checked 2026-11-16)
- Vercel Docs: Environment variables. https://vercel.com/docs/environment-variables (checked 2026-11-16)
- Vercel: Environments. https://vercel.com/docs/deployments/environments (checked 2026-11-16)
- Vercel Docs: Add a domain. https://vercel.com/docs/domains/working-with-domains/add-a-domain (checked 2026-11-16)
- Vercel: Hobby plan. https://vercel.com/docs/plans/hobby (checked 2026-11-16)
- Netlify Docs: Netlify Database. https://docs.netlify.com/build/data-and-storage/netlify-db/ (checked 2026-11-16)
- Vercel: Storage. https://vercel.com/docs/storage (checked 2026-11-16)
- Netlify Docs: Credit-based pricing plans. https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/ (checked 2026-11-16)
- Netlify Docs: Functions configuration. https://docs.netlify.com/build/functions/configuration/ (checked 2026-11-16)
- Netlify: Pricing. https://www.netlify.com/pricing/ (checked 2026-11-16)
- Vercel: Pro plan. https://vercel.com/docs/plans/pro-plan (checked 2026-11-16)
- Vercel: Functions usage and pricing. https://vercel.com/docs/functions/usage-and-pricing (checked 2026-11-16)
- Vercel: Regional pricing, iad1. https://vercel.com/docs/pricing/regional-pricing/iad1 (checked 2026-11-16)
- Vercel: Regions. https://vercel.com/docs/regions (checked 2026-11-16)
Your next deploy
goes everywhere.
Connect a provider, point a service at it, and ship. Add the second provider when you're ready.
No card needed · Free tier · Pay as you go after that