Migrate from Render to Build
Build and Render run the same shapes of application: web services, background workers, scheduled jobs and managed data. Your application usually moves without a rewrite, because Build deploys from the Buildpack or Dockerfile you already use.
What does not move is Render’s render.yaml. There is no importer and no direct equivalent, so your services and their settings are recreated once on Build.
There are two parts to a migration: your services, and your data. You do not have to do both at once.
For a comparison of the two platforms, see Compare Build & Render.
1. Inventory what you are running
Section titled “1. Inventory what you are running”Before touching Build, list what Render is running for you. Your render.yaml is the quickest source if you have one:
- Web services, and which is public
- Background workers and cron jobs
- Private services
- Managed Postgres and key-value stores
- Environment groups and the variables in them
Each service becomes an app or a process type on Build, so this list is your build order.
2. Create the app on Build
Section titled “2. Create the app on Build”Open the team you are deploying into and click New app. Set the team, the pipeline, and which stage of that pipeline the app occupies.
Connect your GitHub repository, then set the stack and buildpacks, or point Build at your Dockerfile if that is how Render built it. See Deploying applications.
3. Recreate your services
Section titled “3. Recreate your services”Render runs each service separately. On Build, processes belonging to one application live together in a Procfile:
- A Render web service becomes your
webprocess - Background workers become worker processes
- Cron jobs become scheduled jobs
Services that genuinely need to be separate applications, rather than processes of one, get their own Build app. Private services are one case where you usually want this, with private networking between them.
4. Bring your environment variables across
Section titled “4. Bring your environment variables across”Copy your Render environment variables into the Build app’s config vars. Where Render used an environment group shared between services, decide whether those variables belong to one application on Build or need repeating.
Leave database connection strings until you have provisioned the database.
5. Deploy and check
Section titled “5. Deploy and check”Scale your web process to one dyno, then open the app and confirm it serves as it does on Render.
Scale workers only when you mean to run them. Until you have moved your data, a worker here may still be pointed at your Render database and will act on real jobs.
Your database
Section titled “Your database”Render’s managed Postgres is replaced by Schema To Go. The instance is recreated rather than imported.
- Provision the database on Build. Set
import_urlto your Render database when you create it, and Build pulls the data across for you. How long that takes depends on the size of the data. - Attach it to your app. In the add-on’s Attachments section, choose Attach to App and set the attached-as name to
DATABASE, so your app seesDATABASE_URL. - Redeploy.
A large production database usually wants a replication-based approach rather than an import, so that cutover is a short switch rather than a long copy.
Engineer-led migration support is included on Enterprise plans. Talk to us before you move production data.
6. Cut over
Section titled “6. Cut over”When you are satisfied, move traffic by pointing DNS at Build. Your Render services keep running, so you can point DNS back if you need to.
Need help
Section titled “Need help”See Get support, or talk to an engineer about your migration.
