Migrate
Migrate from Render to Unbroker: services, Postgres, variables and DNS
To move off Render, keep the same commit, test the database first, switch DNS last, and leave a way back. Recreate each service from Git, rehearse the Postgres restore, and point DNS only after that copy works. Keep Render available until new writes land on Unbroker.
Checked Nov 12, 2026. Render service, cron, variable, domain, and Postgres pages were read on render.com/docs that day. Unbroker Free and Pro come from the plans page and unbroker.cloud/pricing.
Before you start: inventory
Write down every web service, static site, background worker, cron job, private service, variable, environment group, disk, database, and domain. Include anything that can still write after the web process is quiet. You need the Git repository, the running Render settings, DNS, and a backup you trust.
Render's Blueprint spec can help with that inventory. It lists web, worker, cron, and private services, and a static site as a web service with a static runtime, plus commands, variable groups, and disks. It is not an Unbroker import. The field-by-field map is render.yaml, field by field. Pro is required for a Dockerfile, workers, persistent volumes, scheduled jobs, 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 Render concepts to Unbroker
A Render service becomes one or more Unbroker services. The table is the mapping the migration tutorial and the product docs support. Anything missing from a row stays on Render or gets rebuilt by you.
Do not paste a Render hostname into the destination database URL. Recreate variables in the right environment. Values that point at a Render resource, including a database connection string or an environment group, have to be replaced. Service variables override shared project variables. If a static frontend bakes public variables such as VITE_* or NEXT_PUBLIC_* into its bundle, set the API origin and rebuild after it changes.
| Render | On Unbroker | What does not carry over |
|---|---|---|
| Web service | A repository service from the same Git revision. Use a framework preset, or a Dockerfile on Pro. | render.yaml is not imported. The onrender.com subdomain is not your Unbroker hostname. |
| Static site | A static build preset and the output directory you set. Static sites are included on Free and on Pro. | If the frontend bakes public variables into the bundle, rebuild it after the API origin changes. |
| Background worker | A worker on Pro, with the consumer's start command. Workers have no public URL and run one replica. | It is a long-running process, not a copy of the queue, and it does not receive inbound HTTP. |
| Cron job | A scheduled job or a one-off command on Pro. A command that starts, finishes, and exits is that flow, not a worker. | The schedule is not imported. Render cron jobs use a UTC cron expression, must exit, cannot use a persistent disk, and stop after 12 hours. At most one run of that job is active. |
| Private service | A service that listens can be private: no public URL, reachable from other services in the same environment. | Do not publish it only to move it. The internal hostname is not copied. |
| Environment variables | Service variables. Shared project variables require Pro. Each one is Production, Preview, or All. | Values are not copied, including secrets. Replace anything that points at a Render host, database, or environment group. |
| Postgres | A managed cluster on Pro, or an Apps Postgres node you operate. The smallest managed plan is 1 vCPU, 1 GB RAM, and 10 GB at $21.21 a month. | There is no automatic transfer. An Apps node does not reproduce Render's managed recovery. |
| Persistent disk | A service volume, with a file transfer you plan. Volumes require Pro. | The bytes are not moved for you. A database dump does not include them. |
| Custom domain | The default hostname first, then a custom domain and managed TLS on Pro. | DNS and callback URLs stay yours to change. Render documents custom domains on web services and static sites. |
Recreate services from Git
Connect the same repository and branch and deploy that revision. Choose a framework preset. A Dockerfile or a container image requires Pro. A GitHub-connected service with automatic deploys can deploy on push to the configured branch. That push is not a data migration.
Set the build output directory for a static site and the start command for a server. A worker uses the Worker category and the consumer's start command. It stays running, has no public URL, and runs one replica. A command that exits belongs in a scheduled job or a one-off command, both on Pro, not in a worker. Confirm that schedule before you substitute a long-running worker, and do not create a public endpoint just to host a private service. Unbroker as a Render alternative is the product comparison. This page is the move.
Move the database
Render's backup page, read on November 12, 2026, documents point-in-time recovery for paid Postgres and a logical export you can download. Recovery creates another instance on Render. It is not an export to a different host. The same page documents pg_dump against the external database URL when the dashboard does not create a logical backup. The service types page says a free Postgres instance expires 30 days after creation, and the free compute plan has no recovery and no Render-created logical backup. This page does not repeat those commands.
Restore into an isolated database and check versions, extensions, permissions, and connection limits before you trust the copy. 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, and it does not automatically reproduce the managed recovery of the database you left. Rehearse on a throwaway target: row counts, logins, and a safe read path. Files on a persistent disk need their own transfer. A database dump does not include them. For the final copy, stop HTTP writes, background workers, and scheduled writers first. Do not leave two consumers performing the same production side effects. 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: login, a read, a controlled write, and a background task. Then lower DNS TTL, create the record Unbroker shows, and update callback URLs, allowed origins, and trusted hosts. Custom domains and managed TLS require Pro. Keep the Unbroker hostname for checks. Render documents custom domains on web services and static sites, and those services keep an onrender.com subdomain unless you disable it. That name is not the destination hostname.
Before Unbroker accepts new writes, you can often put DNS back on Render 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. Keep the source and a recoverable backup until you accept the new deployment. 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.
What Free and Pro cover
On November 12, 2026, pricing listed Free at $0 and Pro at $25 a month with $25 of usage credit. The plans page states the same fees. The credit resets each cycle and does not roll over. If eligible usage stays under the credit, the monthly charge is still $25. That pricing page lists app CPU at $0.03 per configured vCPU-hour and memory at $0.015 per configured GiB-hour while replicas run.
Free can build managed Node.js and static sites: one project, up to two services, 250m CPU and 256 MiB per service, and three deploys per UTC day. Those caps are on the plans page and on pricing. Free services sleep when idle and wake on the next request. Workers, Dockerfiles, container images, persistent volumes, scheduled jobs, custom domains, shared project variables, private repository credentials, and managed databases require Pro. The managed Postgres price, if you use a cluster, is separate from the Pro fee. This page does not turn a Render compute plan into that invoice.
Questions
How do I migrate from Render?
Inventory the services, recreate each one from the same Git commit, restore a logical backup into a test database, and switch DNS only after that copy works. Keep Render available until new writes land on Unbroker.
How do I move a Render cron job?
Render cron jobs run a command on a UTC schedule and then exit. They cannot use a persistent disk, a run stops after 12 hours, and at most one run of that job is active. On Unbroker, scheduled jobs and one-off commands require Pro. A command that exits is that flow, not a worker. The Render schedule is not imported. Confirm the destination schedule before you substitute a long-running worker, and stop scheduled writers before the final copy.
How do I export Render Postgres?
Use the backup options Render documents for that database. Point-in-time recovery stays on Render, as a new instance. A logical export or pg_dump is what you can restore elsewhere. The free compute plan has no dashboard recovery and no Render-created logical backup, and a free instance expires after 30 days. Restore into an isolated Unbroker database and check row counts and a real read path. This page does not add export flags.
Do I need Pro to migrate from Render?
A Dockerfile, workers, persistent volumes, scheduled jobs, 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.
Can I keep zero downtime when moving off Render?
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 Render. After those writes, DNS alone is not a data rollback.
Does render.yaml import into Unbroker?
No. Render's Blueprint file can help you inventory services, commands, variable groups, and disks. It is not an Unbroker import format. Recreate each service from Git.
Can a coding agent run the migration with ubctl?
An agent can deploy the service from Git with ubctl. It does not export the Render database, rehearse the restore, or change DNS. Those steps stay with you.
Sources
- Migration tutorial
- Render service types
- Render cron jobs
- Render Blueprint spec
- Render environment variables
- Render custom domains
- Render Postgres backups
- Unbroker plans
- Billing and usage
- Unbroker service types
- Unbroker environment variables
- Unbroker custom domains
- Deploy from Git
- Background workers
- Database choices
- Unbroker pricing
- Render alternative