Move between clouds
without a big-bang cutover.
Practical guides for common moves: which concepts map to which, the steps in order, what the official docs warn about, and how to run old and new side by side while traffic shifts.
Facts checked against each provider's own pages
Migration guides
- Migrate from Vercel to AWSHow to move a Vercel project to AWS Amplify Hosting: what maps to what, Next.js features Amplify doesn't support, env vars, previews and a gradual cutover.
- Migrate from Vercel to CloudflareMoving Next.js from Vercel to Cloudflare Workers: vinext or OpenNext, vercel.json, ISR, images, storage, env vars, custom domains and a gradual cutover.
- Migrate from Railway to Fly.ioMoving services from Railway to Fly.io: Dockerfiles and fly launch, secrets, Postgres via pg_dump, volumes, custom domains and a gradual cutover.
- Migrate from Render to RailwayMoving from Render to Railway: importing render.yaml, environment variables, Postgres via pg_dump, disks, regions and domains, plus a gradual cutover.
- Migrate from Netlify to VercelMoving a site from Netlify to Vercel: netlify.toml and _redirects to vercel.json, functions to api/, edge functions, env vars, domains and cutover.
- Migrate from DigitalOcean to HetznerMoving Droplets to Hetzner Cloud: why snapshots can't be exported, rebuilding with cloud-init, copying data with rsync, volumes, databases, cutover.
- Migrate from AWS to Google CloudMoving from AWS to Google Cloud: Google's official service map, S3 transfer, database moves, AWS's exit egress waiver, billing and a gradual cutover.
- Migrate from RunPod to ModalMoving GPU inference from RunPod Serverless to Modal: handlers to functions, Docker images, secrets, volumes, idle billing and a gradual cutover.
The pattern every guide follows
- Inventory what you run: services, build settings, environment variables, domains, data stores and scheduled jobs.
- Map each to the target platform's equivalent, using the target's own docs.
- Deploy the same version to the target and test it on a non-production hostname.
- Move data last and deliberately: replicate or dump and restore, with a write freeze if needed.
- Shift traffic gradually, watch errors and latency, and keep the old deployment ready to take traffic back.
- Switch DNS fully, then decommission the old platform once a rollback is no longer needed.
Public betaYour next deploy
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