{
  "manifest_version": "1",
  "slug": "migrate-netlify",
  "title": "Sites from Netlify",
  "headline": "Migrate a Netlify site to exe.dev",
  "description": "Move a Netlify site to an exe.dev VM: the build, functions, server, database, redirects, forms, Blobs, variables, and domains, with API keys off the VM.",
  "category": "migration",
  "tags": [
    "netlify",
    "migrate from netlify",
    "netlify alternative",
    "netlify functions",
    "netlify edge functions",
    "netlify server",
    "netlify database",
    "postgres",
    "netlify forms",
    "netlify blobs",
    "scheduled functions",
    "background functions",
    "_redirects",
    "_headers",
    "netlify.toml",
    "deploy previews",
    "branch deploys",
    "image cdn",
    "api keys"
  ],
  "url": "https://exe.dev/deploy/migrate-netlify",
  "markdown_url": "https://exe-staging.dev/deploy/migrate-netlify.md",
  "upstream": {
    "website": "https://www.netlify.com",
    "source": "https://github.com/netlify/cli",
    "docs": "https://docs.netlify.com",
    "license": "Your code is yours; Netlify's redirect parser and Blobs server are MIT"
  },
  "example_vm_name": "my-site",
  "time": "1 hour",
  "stack": [
    {
      "name": "Your site",
      "detail": "The same build, served with its functions, edge functions, redirects, headers, forms, and image transforms by a small Node.js server on port 8000",
      "port": 8000,
      "data": "~/site"
    },
    {
      "name": "Branch deploys",
      "detail": "The last branch you pushed that isn't production, built with its own variables, on port 8001",
      "port": 8001
    },
    {
      "name": "PostgreSQL",
      "detail": "Your Netlify Database, copied into Postgres on the VM, the same major version; migrations run on deploy",
      "data": "/var/lib/postgresql"
    },
    {
      "name": "Blobs and form submissions",
      "detail": "Netlify's own Blobs server and a file per form, with your data from Netlify",
      "data": "~/site/data"
    },
    {
      "name": "Integrations",
      "detail": "Your API keys for Stripe, OpenAI, and others, kept by exe.dev outside the VM"
    },
    {
      "name": "The move kit",
      "detail": "The hand-over, the scripts, and the report",
      "data": "~/netlify"
    }
  ],
  "access": [
    {
      "url": "https://my-site.exe.xyz/",
      "who": "private",
      "what": "the site, until you make the move"
    },
    {
      "url": "https://www.example.com/",
      "who": "public",
      "what": "the site, after the move"
    },
    {
      "url": "https://my-site.exe.xyz:8001/",
      "who": "private",
      "what": "the branch deploy"
    },
    {
      "url": "ssh my-site.exe.xyz",
      "who": "private",
      "what": "the shell; `git push exe main` deploys"
    }
  ],
  "delivers": [
    "Your Netlify site running on the VM at https://my-site.exe.xyz/, with its functions, edge functions, server, database, redirects, headers, forms, Blobs, and variables.",
    "`git push exe main` deploying like Netlify: the build, an atomic switch, and the old deploy kept if anything fails; other branches as a branch deploy.",
    "A list of the API keys that can move into exe.dev integrations, where the VM can't read them.",
    "A report in `~/netlify/report.md`, and your steps for the move."
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20Sites%20from%20Netlify%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Fmigrate-netlify.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-site.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-site.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20Your%20Netlify%20site%20running%20on%20the%20VM%20at%20https%3A%2F%2Fmy-site.exe.xyz%2F%2C%20with%20its%20functions%2C%20edge%20functions%2C%20server%2C%20database%2C%20redirects%2C%20headers%2C%20forms%2C%20Blobs%2C%20and%20variables.%0A-%20%60git%20push%20exe%20main%60%20deploying%20like%20Netlify%3A%20the%20build%2C%20an%20atomic%20switch%2C%20and%20the%20old%20deploy%20kept%20if%20anything%20fails%3B%20other%20branches%20as%20a%20branch%20deploy.%0A-%20A%20list%20of%20the%20API%20keys%20that%20can%20move%20into%20exe.dev%20integrations%2C%20where%20the%20VM%20can%27t%20read%20them.%0A-%20A%20report%20in%20%60~%2Fnetlify%2Freport.md%60%2C%20and%20your%20steps%20for%20the%20move.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details%2C%20and%20do%20%22Rehearse%20the%0Amove%20by%20hand%22%20in%20order%2C%20skipping%20VM%20creation%3B%20the%20rest%20of%20the%20page%20is%20for%0Athe%20owner.%20Use%20the%20kit%27s%20scripts%20as%20published.%0AYou%20need%20the%20owner%20once%2C%20early%3A%20show%20them%20the%20commands%20in%20%22Hand%20over%20the%0Asite%22%20with%20this%20VM%27s%20name%2C%20and%20wait%20until%20~%2Fnetlify%2Fhanded-over%20exists%0Aand%20~%2Fgit%2Fsite.git%20has%20a%20commit.%20Install%20the%20rest%20meanwhile.%0ANever%20call%20Netlify%27s%20API%20yourself%20and%20never%20ask%20for%20a%20Netlify%20token.%0ANever%20run%20handover%20--move%20or%20netlify%2Fimport%20live%2C%20change%20DNS%2C%20or%20run%0Ashare%20set-public%3A%20the%20move%20is%20the%20owner%27s%20call.%20Scheduled%20functions%20stay%0Aoff%20until%20then.%0AKeep%20variable%20values%20out%20of%20your%20replies%20and%20the%20report.%20Never%20ask%20the%0Aowner%20to%20paste%20an%20API%20key%20into%20the%20conversation%3A%20API%20keys%20go%20into%0Aintegrations%2C%20which%20the%20owner%20adds%3B%20secret%20values%20Netlify%20won%27t%20hand%0Aover%20the%20owner%20sets%20with%20netlify%2Fimport%20set%20over%20SSH.%0AIf%20the%20site%20renders%20pages%20with%20a%20framework%27s%20Netlify%20adapter%20%28Next.js%2C%0AAstro%2C%20SvelteKit%2C%20Nuxt%2C%20Remix%29%2C%20switch%20the%20build%20to%20the%20framework%27s%20Node%0Aadapter%2C%20run%20its%20server%20with%20a%20systemd%20unit%20on%20port%208000%20in%20place%20of%0Anetlify%40production%2C%20and%20list%20in%20the%20report%20what%20moved%20out%20of%0Anetlify.toml.%20For%20anything%20else%20exe.dev%20doesn%27t%20do%20%28Identity%2C%20geolocation%2C%0Asplit%20testing%29%2C%20put%20it%20in%20the%20report%20and%20ask.%0AFinish%20with%20the%20report%27s%20summary%2C%20https%3A%2F%2F%3Cvm%3E.exe.xyz%2F%2C%20the%20keys%20that%0Acould%20move%20to%20integrations%2C%20and%20the%20owner%27s%20steps%20in%20%22Make%20the%20move%22%0Awith%20this%20VM%27s%20name%20and%20the%20site%27s%20domains.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/migrate-netlify/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Sites from Netlify on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/migrate-netlify.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-site. This VM's name is the output of `hostname`: use it wherever the recipe writes my-site. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- Your Netlify site running on the VM at https://my-site.exe.xyz/, with its functions, edge functions, server, database, redirects, headers, forms, Blobs, and variables.\n- `git push exe main` deploying like Netlify: the build, an atomic switch, and the old deploy kept if anything fails; other branches as a branch deploy.\n- A list of the API keys that can move into exe.dev integrations, where the VM can't read them.\n- A report in `~/netlify/report.md`, and your steps for the move.\n\nRead the whole recipe, including the closed details, and do \"Rehearse the\nmove by hand\" in order, skipping VM creation; the rest of the page is for\nthe owner. Use the kit's scripts as published.\nYou need the owner once, early: show them the commands in \"Hand over the\nsite\" with this VM's name, and wait until ~/netlify/handed-over exists\nand ~/git/site.git has a commit. Install the rest meanwhile.\nNever call Netlify's API yourself and never ask for a Netlify token.\nNever run handover --move or netlify/import live, change DNS, or run\nshare set-public: the move is the owner's call. Scheduled functions stay\noff until then.\nKeep variable values out of your replies and the report. Never ask the\nowner to paste an API key into the conversation: API keys go into\nintegrations, which the owner adds; secret values Netlify won't hand\nover the owner sets with netlify/import set over SSH.\nIf the site renders pages with a framework's Netlify adapter (Next.js,\nAstro, SvelteKit, Nuxt, Remix), switch the build to the framework's Node\nadapter, run its server with a systemd unit on port 8000 in place of\nnetlify@production, and list in the report what moved out of\nnetlify.toml. For anything else exe.dev doesn't do (Identity, geolocation,\nsplit testing), put it in the report and ask.\nFinish with the report's summary, https://\u003cvm\u003e.exe.xyz/, the keys that\ncould move to integrations, and the owner's steps in \"Make the move\"\nwith this VM's name and the site's domains.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe-staging.dev/deploy/migrate-netlify/prompt.txt"
  },
  "published": "2026-11-20",
  "updated": "2026-11-19",
  "verified": "2026-11-19",
  "related": [
    "migrate-railway",
    "migrate-heroku",
    "agent-secrets",
    "nodejs",
    "astro",
    "migrate-digitalocean-droplet"
  ],
  "alternatives": [
    "Netlify"
  ],
  "files": [
    "https://exe-staging.dev/deploy/migrate-netlify/backup",
    "https://exe-staging.dev/deploy/migrate-netlify/check",
    "https://exe-staging.dev/deploy/migrate-netlify/deploy",
    "https://exe-staging.dev/deploy/migrate-netlify/handover.mjs",
    "https://exe-staging.dev/deploy/migrate-netlify/import",
    "https://exe-staging.dev/deploy/migrate-netlify/site.mjs"
  ]
}
