Migrate as easily as you deploy
Straightforward migration. Switch in hours or days, not a multi-month project.
How migration works
Connect your Heroku account
We'll import your existing apps, environment variables, and add-on configuration automatically.
Review your build config
Build auto-detects your buildpack and environment. Review and confirm — or customise if needed.
Run in parallel, cut over when ready
Deploy to Build alongside Heroku. Validate, test, then switch DNS when you're confident. Zero downtime.
Connect your Git repository
Point Build at your existing repo. No changes to your codebase required.
Map your services to Build primitives
Define your runtime using your existing Buildpack or Dockerfile. Provision managed add-ons to replace databases, caches, and background services.
Switch when you're ready
Run Build alongside your current platform. Migrate data and shift traffic at your own pace. Switch in hours or days, not a quarter-long project.
Frequently asked questions
How long does migrating to Build take?
Migrating from Heroku takes minutes using our direct integration, which automatically imports your existing apps, environment variables, and add-on configuration to Build. Validating and cutting over usually takes hours or days, depending on how long you run both platforms in parallel. Migrations from other platforms may require more work, but our engineer-led migration support is available to help with the move.
Do I need to change my code to move to Build?
Build supports Buildpacks and Dockerfiles, so many teams can move without changes.
What does Build import automatically from Heroku?
Connecting a Heroku account to Build imports your apps, environment variables, add-on configuration and pipeline setup automatically. Your Heroku apps keep running while you validate, so nothing switches over until you choose to.
Can I run Build and my current platform side by side?
You can run Build alongside your current platform while it keeps serving traffic, then switch DNS when you are confident. Running in parallel is the recommended path and how most migrations avoid downtime entirely.
Who does the work, me or Build?
Engineer-led migration support is included as standard on Build Enterprise plans, so a Build engineer works alongside your team rather than just handing you docs. You keep control of timing and cutover.