Do we need to rewrite any of our application code?

It depends on where you're starting from. Your business logic almost never changes. If you already run on Docker with mix releases, we change what surrounds the app, not the app itself. On an older buildpack setup there's a bit more: mix releases don't have Mix at runtime, so things like Mix.env() checks move into config/runtime.exs and env lookups. Targeted, well-understood work, and we handle it as part of the migration.

How long does a Heroku migration typically take?

Most migrations complete in 8-10 weeks. Simple apps with one database can be done in under two weeks. Complexity is driven by the number of add-ons, background job queues, and whether you have strict downtime requirements.

Can you migrate our Postgres database with no downtime?

Yes. We use logical replication to keep the old and new databases in sync during the cutover window, so the switch takes seconds, not hours.

Which platforms do you migrate to?

We're cloud provider agnostic and can migrate to almost any platform. For teams that need AWS for compliance or existing infrastructure reasons, we use ECS Fargate or EKS depending on the workload, and on the shape of your team and how much ops they want to own.

01 · Platform Migration

Heroku Migration for Elixir Apps

Move beyond dyno bills and platform limits without disrupting the team or application that got you here.

Heroku AWS Fly.io

Talk to a BEAMOps specialist

Result

A calm, zero-surprise route off Heroku

/ / How we work

Clear from first conversation to handover.

You always know what's happening, why it matters, and what comes next.

M / 01

Discovery

We audit your Heroku setup, understand your traffic patterns, and agree a target architecture.
M / 02

Build

We provision the new environment, wire up deployments, and run your app in parallel so there's no big-bang cutover.
M / 03

Cutover & handover

We flip DNS, monitor for 48 hours, and hand over full documentation so your team owns what comes next.

/ / A good fit?

Built for teams at an inflection point.

01
Teams paying $500+/month in Heroku dynos and add-ons
02
Engineering leads whose app is hitting Heroku's connection or slug size limits
03
Startups preparing a Series A infrastructure tidy-up
04
Small teams who need the migration done right, without owning the whole project themselves

/ / What's included

No mystery.
Just the work.

We shape every engagement around your context, but these are the foundations you can expect.

|> Current-state audit: dynos, add-ons, config vars, build pipeline, scheduled tasks
01
|> Target platform selection and architecture design (AWS ECS, EC2, or self-hosted)
02
|> Terraform config written and reviewed
03
|> Zero-downtime cutover plan with rollback procedure
04
|> Database migration and connection pool tuning
05
|> Post-migration monitoring setup and handover documentation
06

/ / Common questions

Things you might be wondering.

: It depends on where you're starting from. Your business logic almost never changes. If you already run on Docker with mix releases, we change what surrounds the app, not the app itself. On an older buildpack setup there's a bit more: mix releases don't have Mix at runtime, so things like Mix.env() checks move into config/runtime.exs and env lookups. Targeted, well-understood work, and we handle it as part of the migration.
: Most migrations complete in 8-10 weeks. Simple apps with one database can be done in under two weeks. Complexity is driven by the number of add-ons, background job queues, and whether you have strict downtime requirements.
: Yes. We use logical replication to keep the old and new databases in sync during the cutover window, so the switch takes seconds, not hours.
: We're cloud provider agnostic and can migrate to almost any platform. For teams that need AWS for compliance or existing infrastructure reasons, we use ECS Fargate or EKS depending on the workload, and on the shape of your team and how much ops they want to own.

/ / Keep exploring

Elixir Consulting