Migrate
Migrate from Railway to Unbroker: services, variables, Postgres and DNS
Same commit, a test database first, DNS last, and a way back. Recreate each Railway service from Git, rehearse the Postgres restore, and switch DNS only after that copy works. Keep Railway available until new writes land on Unbroker.
Checked Nov 3, 2026. Railway plan fees were read on railway.com/pricing that day. Unbroker limits come from the current catalogue.
Before you start: inventory
Write down every service, variable, volume, database, domain, and anything that can still write after the web process is quiet. Include workers and scheduled tasks. You need the Git repository, Railway configuration, DNS, and a backup you trust.
Pro is required for a Dockerfile, workers, private repository credentials, custom domains, and a managed database. Free can build managed Node.js and static sites inside its caps. Use a maintenance window if you cannot keep both databases consistent while traffic moves.
Map Railway concepts to Unbroker
A Railway project becomes one or more Unbroker services. The table is the mapping the product actually supports. Anything missing from a row stays on Railway or gets rebuilt by you.
Do not paste an internal Railway hostname into the destination database URL. Railway's Postgres template documents PGHOST, PGPORT, PGUSER, PGPASSWORD, PGDATABASE, and DATABASE_URL inside the project. Public access, when you turn it on, adds DATABASE_PUBLIC_URL. Recreate the connection on Unbroker after the restore, not by copying the old host.
| Railway | On Unbroker | What does not carry over |
|---|---|---|
| Project | A project that holds the services. | Railway service-reference expressions are not imported. |
| Service | A service from the same Git repository and branch, or a Dockerfile on Pro. | The Railway template catalog is not copied. |
| Variables | Service variables, or shared project variables on Pro. | Values are not copied for you. Recreate them, including secrets. |
| Volume | A persistent volume on the service, or storage you operate yourself. | The bytes are not moved automatically. Plan the copy. |
| Database | An Apps database node you operate, or a managed cluster on Pro. The smallest managed Postgres plan is 1 vCPU, 1 GB RAM, and 10 GB at $21.21 a month. | There is no automatic transfer. Use a logical backup you restore yourself. |
| Domain | The default hostname first, then a custom domain on Pro. | DNS and callback URLs stay yours to change. |
Recreate services from Git
Connect the same repository and branch. Choose a framework preset. A Dockerfile or a container image requires Pro. A GitHub-connected service can deploy on push to the configured branch. That push is not a data migration.
Translate build and start commands when the preset is not enough. Recreate variables as service variables. Do not paste secrets into Git. Unbroker as a Railway alternative is the product comparison. This page is the move.
Move the database
Take a logical backup with the PostgreSQL tools you already use, and restore it into an isolated database. Railway's Postgres page, read on November 3, 2026, describes a single-node template and a separate conversion if you want high availability. It does not publish a one-click export into another host. This page does not invent flags for that export.
On Unbroker, a managed Postgres cluster requires Pro. The smallest catalogue plan is 1 vCPU, 1 GB RAM, and 10 GB at $21.21 a month, separate from the Pro fee. An Apps Postgres node is a database image you operate. It is not that cluster. Rehearse on a throwaway target: row counts, logins, and a safe read path. For the final copy, stop writers first. A dump taken while writes continue does not include later changes.
Switch DNS and keep a rollback path
Prove the app on the Unbroker hostname. Then lower DNS TTL, point the domain at Unbroker, and update callback URLs. Custom domains and managed TLS require Pro. Keep the Unbroker hostname in place for checks.
Before Unbroker accepts new writes, you can often put DNS back on Railway and keep using the unchanged source database. After new writes land on Unbroker, changing DNS is not a data rollback. Reconcile those writes or restore an agreed backup. There is no automatic zero-downtime transfer. The tutorial does not provide one. How long the window lasts depends on the database size and on the rehearsal you already timed. This page does not publish a duration.
How the bill changes
On November 3, 2026, Railway listed Hobby at $5 a month with $5 of usage, and Pro at $20 a month with $20 of usage. CPU and memory are billed per second for what a running service uses. Unbroker Free is $0 inside published caps. Pro is $25 a month with $25 of credit, and app CPU and memory follow the capacity you configure while replicas run.
Those meters are not the same shape, so this page does not convert one into the other. Read Railway pricing for the published rates and usage and capacity for the difference. Migrating from Heroku instead?
Questions
How do I migrate from Railway?
Inventory the project, recreate each service from the same Git commit, restore a logical backup into a test database, and switch DNS only after that copy works. Keep Railway available until new writes land on Unbroker.
How do I export my Railway Postgres database?
Use a logical backup with the PostgreSQL tools you already trust, against a connection Railway documents for that database. Restore it into an isolated Unbroker database and check row counts and a real read path. This page does not add export flags Railway's docs do not list.
Can I keep zero downtime when moving off Railway?
Do not plan on zero. Stop writers for the final backup, restore that backup, then send traffic. Before Unbroker takes new writes, DNS can return traffic to Railway. After those writes, DNS alone is not a data rollback.
Do I need Pro to migrate?
A Dockerfile, workers, private repository credentials, custom domains, and a managed database require Pro. Pro is $25 a month with $25 of credit. Free can build managed Node.js and static sites inside its caps. The database price, if you use a managed cluster, is separate.
How long does a Railway migration take?
It depends on the database size and on how long export, transfer, restore, and checks took in your rehearsal. This page does not publish a duration.
Can a coding agent run the migration with ubctl?
An agent can deploy the service from Git with ubctl or the MCP endpoint. It does not export the Railway database, rehearse the restore, or change DNS. Those steps stay with you.