Run Build in parallel. Switch when you're ready.
Our engineers help you move your applications and data to Build, while your current platform keeps running.
Choose your migration path
Whether you're coming from Heroku or another cloud platform, you can get Build running alongside your existing infrastructure before moving production.
Moving from Heroku
Connect your Heroku account and automatically import your apps, environment variables, add-on configuration and pipelines. Get your application running on Build in minutes.
See the Heroku migrationMoving from another platform
Build supports Buildpacks and Dockerfiles, so many applications can move without code changes. Our engineers help you plan the migration and get everything running.
See how migrations workMigrate your Heroku app in minutes
Build connects directly to Heroku and imports your existing configuration, removing much of the manual setup.
Connect your Heroku account
Build imports your apps, environment variables, add-on configuration and pipeline setup.
Review your configuration
We detect your Buildpack and environment. Review what was imported and make any changes you need.
Migrate your database
Transfer your data to Build, using an approach that fits your database size and requirements.
Deploy alongside Heroku
Run your application on Build while Heroku continues serving production. Test and validate it, then switch traffic when you are ready.
Baremetrics moved beyond Heroku
Baremetrics migrated using Build's direct Heroku integration, moving workloads one component at a time without downtime.
Today, Baremetrics runs deployments of more than 200 dynos and processes 32,000 database writes per second on Build.
Read the Baremetrics case studyThe Build team are super responsive and eager to work with us to ensure our infrastructure needs are met as we scale. Quick to get on a call and offer proactive solutions to any issues we may see on the horizon.
Migrating from Render, Vercel, AWS or elsewhere?
Others Subtitle
Many applications can move to Build without a rewrite. We support Buildpacks and Dockerfiles, so you can often keep your existing build configuration.
The main work is usually migrating your services, databases, networking and other dependencies. Our engineers help you map these out and plan the move.
Review your current setup
We review your application, services, data and dependencies, then put together a migration plan and timeline.
Deploy on Build
Get your application and supporting services running on Build while your existing platform continues serving production.
Test and switch over
Validate your application on Build, then move production traffic when you're ready. Migrate everything together or service by service, depending on your setup.
Saambaa runs 50 million requests a day on Build
Saambaa moved from its previous infrastructure to Build, where it now serves 50 million requests a day.
With less infrastructure to manage, its engineers can spend more time building geographic products, publisher tools and AI capabilities.
Read the Saambaa case studyBuild provides peace of mind through reliable, scalable infrastructure. Their support network is straightforward and responsive. We've eliminated the runaround and communication gaps we dealt with in the past. Build feels like a true partner and gives us a level of confidence we've never had before.
Your migration. Backed by Build engineers.
Run the migration yourself with help when you need it, or have our engineers take a more active role. We support your team from initial planning through to production.
Engineer-led migration support is included with every Enterprise plan.
Risk Title
Risk Subtitle
Risk Stage Build. Risk Body Build
Risk Stage Data. Risk Body Data
Risk Stage Cutover. Risk Body Cutover
Risk Stage Rollback. Risk Body Rollback
Frequently asked questions
Will my existing Heroku workflow still work?
Yes, Build supports Git-based deployments, Procfiles, process types, config vars, pipelines and review apps. Most teams can keep their existing workflows, with little or no change.
How long does migrating to Build take?
For Heroku, our direct integration imports your application configuration in minutes. Testing and moving production traffic usually takes hours or days, depending on your application. For other platforms, the timeline depends on your services, databases and dependencies. A Build engineer can review your setup and help you estimate the work before you start.
Do I need to change my code?
Often, no. Build supports Buildpacks and Dockerfiles, so many applications can use their existing build configuration. Applications that depend on platform-specific services may need some changes.
What does Build import automatically from Heroku?
Build imports your apps, environment variables, add-on configuration and pipelines. Your Heroku applications continue running while you configure and test them on Build.
Can I run Build alongside my existing platform?
Yes, you can deploy and test on Build while your current platform continues serving production. You decide when to switch traffic.
Can I roll back after migrating?
Rollback depends on your application and data setup. We help plan the rollback process before cutover, including traffic routing and data synchronization.
Who handles the migration?
You decide how much to take on. Your team can manage the migration with engineering support from Build, or work with us more closely throughout the process. Engineer-led migration support is included with Enterprise plans.