Migration guides
Every guide below has the same four parts: what the app costs on both sides, the config file before and after, the gotchas that cost people an afternoon, and the cutover steps in the order you should do them. A small app takes about an hour. The DNS flip is the only step your users can see.
Wherever you are coming from, everything lands in one place — Helsinki, Finland — under one Danish company, MICCI, on one EUR invoice, with the GDPR data processing agreement signed at signup.
The four guides
- Migrate from Render — The closest mapping of the four — render.yaml concepts carry over, and the Postgres dump streams straight across.
- Migrate from Heroku — Dynos become services, add-ons become managed databases, and the Procfile mostly survives the trip.
- Migrate from Railway — Same zero-config deploys; what changes is a flat monthly price and a region with a name on it.
- Migrate from Vercel — The one with real work in it — serverless functions become an always-on Node server you can hold open.
Coming from somewhere else? There is nothing special about the four above — any repo that builds from a Dockerfile or a standard buildpack deploys without a guide, and getting started is the whole procedure. Still deciding which platform to leave? The comparisons come first. Stuck mid-move, write to us — we answer.