Generate your way out.

Check your package.json and config to generate a portable Dockerfile, database-aware docker-compose file and migration runbook. Review provider-specific changes before moving to your own server.

The map, on purpose

Most “migrate off X” tools promise to do the move for you. That's the wrong shape: every stack is different, the platform-specific pieces don't have drop-in replacements, and a half-automated migration that silently drops data is the single scariest thing you can do to a production app. So this gives you the inspectable starting point instead — a container that runs anywhere, the stateful services wired up, and a runbook you read end to end and adapt. You migrate; the tool just removes the blank-page problem.

It also tells you the truth about the parts that aren't portable. If your app leans on a proprietary primitive, the runbook names it and what to replace it with — no pretending a rewrite is a redeploy.