Nov 28, Paris: AI Health Hack #2 with Alan, Qovery and AWS. Applications close Nov 21

How to Migrate from Heroku to AWS: A Strategic Blueprint for Mid-Market Teams

A step-by-step Heroku-to-AWS migration checklist: inventory, VPC design, migrating Postgres, Redis and Kafka, governed CI/CD, and phased cutover with rollback.

Mélanie Dallé
Senior Marketing Manager
DEC 13, 2025 · 13 MIN
How to Migrate from Heroku to AWS: A Strategic Blueprint for Mid-Market Teams

TL;DR

  • A PaaS-to-hyperscaler migration strategy is a sequenced plan for replacing managed platform services with cloud infrastructure that you configure, govern, and operate.
  • A Heroku migration starts with an inventory of dynos, add-ons, config variables, dependencies, and data.
  • The AWS migration checklist covers compute and VPC design, stateful-service migration, governed CI/CD, and phased cutover with rollback controls.
  • Small applications may move in days, while regulated or multi-application environments can take months because networking, access controls, and audits add work (timeline guidance).
  • Self-serve tooling such as Qovery fits teams that can own architecture and ongoing governance. A consultancy fits complex estates that need hands-on redesign, compliance planning, or temporary infrastructure expertise.

What a PaaS-to-hyperscaler migration strategy is

A PaaS-to-hyperscaler migration strategy is a sequenced plan for replacing managed platform abstractions, such as Heroku dynos and add-ons, with cloud primitives you govern, including compute, networking, identity, and data services.

Qovery · Infrastructure control plane
Move from Heroku to your own AWS account
Learn more

Heroku bundles infrastructure decisions into a deployment workflow. On AWS, you must choose and configure services such as ECS, VPCs, IAM roles, and RDS while preserving application behavior.

A cloud migration strategy controls risk by ordering those decisions. You inventory dependencies before selecting replacements, migrate stateful services before cutting traffic, and validate rollback paths before production cutover. That sequence turns a Heroku migration into a repeatable AWS migration checklist rather than a collection of disconnected tool changes.

Heroku-to-AWS migration checklist

Follow the steps in order so each migration decision uses a verified inventory and a tested target. A fixed sequence also makes failures easier to isolate before production cutover.

Step 1: Inventory add-ons, config vars, and dependencies

Start by recording every Heroku resource, add-on, config variable, external integration, and deployment dependency. An incomplete inventory can leave the AWS environment without a worker, secret, scheduled job, or monitoring dependency that the application needs.

Heroku resourceCommon AWS replacement
Web and worker dynosElastic Beanstalk, EC2, ECS with Fargate, or EKS
Heroku PostgresAmazon RDS for PostgreSQL or Aurora PostgreSQL
Heroku RedisAmazon ElastiCache for Redis
Apache Kafka on HerokuAmazon Managed Streaming for Apache Kafka
Heroku Scheduler and clock dynosEventBridge Scheduler with Lambda or scheduled ECS tasks
Config VarsSystems Manager Parameter Store or Secrets Manager
Logplex and logging add-onsCloudWatch Logs, with X-Ray for tracing
Heroku CIGitHub Actions or CodeBuild
Custom domainsRoute 53

Export the application's config vars and classify each value as a secret, a runtime setting, or a build-time input. Heroku may inject credentials during builds, while a new AWS pipeline will omit them unless you configure that behavior explicitly.

Inspect each process type in the Procfile and record its command, scaling level, memory needs, ports, health checks, and shutdown behavior. Also trace connections to third-party APIs, object storage, email services, authentication providers, and webhook consumers. The completed inventory becomes the reference for compute design, data migration, CI/CD, and cutover testing.

Step 2: Choose your compute target and design the VPC

Choose a compute target based on how much infrastructure you want to operate. Elastic Beanstalk most closely resembles Heroku because it provisions EC2 instances, deploys applications, and handles basic scaling. ECS with Fargate suits containerized workloads without requiring EC2 management. EC2 gives you direct control over servers, while EKS fits applications that already depend on Kubernetes and have operators who can manage it.

AWS requires you to assemble the deployment foundation that Heroku previously managed. AWS does not provide a deploy workflow out of the box, so design the VPC before migrating workloads. Place load balancers in public subnets and application services in private subnets. Define security groups, IAM roles, and an Application Load Balancer, then connect secrets management, logging, and monitoring.

Containerization often exposes assumptions hidden by Heroku. Copying a Procfile command into a Dockerfile can produce containers that mishandle health checks, shutdown signals, or log routing. Test each image locally and in a nonproduction ECS service before treating it as the deployment artifact.

Step 3: Migrate stateful services (Postgres, Redis, Kafka)

Your database size and downtime tolerance should determine the PostgreSQL migration method. For a database under roughly 10 GB that can tolerate a maintenance window, capture a Heroku backup, restore it into Amazon RDS for PostgreSQL, and validate row counts before directing traffic to AWS. For larger databases or low-downtime requirements, use logical replication or AWS Database Migration Service to copy ongoing changes before a short final cutover.

Low-downtime migration requires early coordination with Heroku. Customers lack direct replication control by default, so you may need Heroku Support to expose write-ahead log archives in S3. Confirm access and test replication before scheduling the production cutover.

Move Heroku Redis to Amazon ElastiCache by exporting a Redis dump, restoring it, and updating the application connection string. Amazon MSK replaces Kafka on Heroku. Before moving Kafka workloads, record topic configuration and consumer offsets so applications resume without silently skipping or replaying messages. Heroku Postgres, Redis, and Kafka should remain available until you validate the AWS copies under production-like traffic. If you are still on Postgres 15, the end of Heroku support for that version is a natural deadline to plan around; we cover that case in moving Heroku Postgres 15 to your own cloud.

Step 4: Rebuild CI/CD as a governed pipeline

Your replacement pipeline should make every deployment repeatable and subject to explicit policy gates. GitHub Actions can build a container image and push it to Amazon ECR. The workflow can then deploy the same image to AWS environments. OIDC federation lets GitHub Actions assume AWS roles without storing long-lived access keys, while pull request previews provide isolated environments for review.

You should separate the migration from broader CI/CD modernization. First, reproduce the release behavior behind git push heroku main and verify that it works on AWS. After cutover, add security scans, approval rules, and policy-as-code checks. Trying to redesign the delivery pipeline during the infrastructure move often extends the migration timeline.

Qovery can provide the governed execution layer without requiring you to hand-build every deployment gate. You define permitted actions and environment rules, and Qovery applies them consistently across deployments. This approach preserves a self-service developer workflow while giving platform owners control over what reaches each AWS environment.

Step 5: Cut over with a phased rollout

A phased cutover should prove the AWS environment before it carries all production traffic. Deploy the release to staging, run functional and load tests, and then promote the same artifact to production. If your routing supports weighted traffic, start with a small production share and increase it after health checks pass.

You should lower the DNS TTL 48 to 72 hours before cutover, with a target near 60 seconds. A short TTL lets clients discover the restored Heroku endpoint quickly if you roll back.

Before changing DNS, confirm that AWS receives application logs and that dashboards and alerts detect failures. The phased rollout avoids a big-bang cutover and catches observability gaps before all users reach AWS. For the full runbook (replication options, weighted DNS, rollback triggers and who owns each step), see how to migrate off Heroku to AWS with minimal downtime.

Migrate off Heroku, into your own AWS account
Qovery gives you a governed, repeatable path to deploy into your AWS account with policy-gated CI/CD. Start in under 10 minutes.

Self-serve tooling vs. consultancy-led migration: which to choose

A self-serve platform fits migrations with a known AWS target, manageable dependencies, and an internal owner. Qovery provides a control plane for deploying into your cloud through repeatable workflows and governed CI/CD policies. Your team retains responsibility for infrastructure decisions after cutover instead of inheriting a consultant-built environment.

A systems integrator fits migrations that require architecture discovery, custom networking, or formal compliance validation. Published migration guidance estimates that solo and small teams can finish in days, while midsize SaaS companies often need several weeks. Consultancy-led projects commonly take four to eight weeks for one application and two to four months for complex or regulated estates.

Team profile / compliance needBest-fit approachTime-to-migrationWho owns ongoing governance
Solo or small team with a standard Heroku applicationSelf-serve platformDays to weeksYour team, through platform policies and CI/CD controls
Midsize team with clear service mappings and an internal AWS ownerSelf-serve platformSeveral weeksYour platform or engineering owner
Team lacking AWS networking, IAM, or database migration expertiseSystems integratorTypically 4 to 8 weeks for one applicationConsultant during delivery, then your team after handoff
Multi-application estate with audit, RBAC, or regulated workload requirementsSystems integratorTypically 2 to 4 monthsShared during migration, then an internal compliance or platform owner

A tooling-led approach works best when execution capacity creates the main constraint. Repeatable environment provisioning and policy-gated deployments reduce the manual work involved in recreating Heroku workflows on AWS. A consultancy provides more value when unanswered architecture or compliance questions must be resolved before migration can proceed.

Budget is often the deciding factor, and it is worth checking before you pick: AWS migration programs can offset part of the move, as explained in how to fund a Heroku to AWS migration with credits.

Your post-migration operating model should decide close cases. Choose self-service when your team can own policies, access controls, and deployment rules. Choose an integrator when you need external specialists to design those controls, document them, and transfer responsibility through a formal handoff.

How Qovery compares to Railway, Render, and Vercel for this migration

Qovery fits migrations where you want Heroku-like deployment ergonomics while running the application inside your AWS account. Its control plane executes declared infrastructure changes consistently and applies policy gates through the deployment pipeline. You retain control over AWS networking, Kubernetes, databases, permissions, and ongoing governance.

PlatformDeterministic execution and CI/CD governanceEffect on migration time
QoveryQovery provisions resources in your AWS account and applies repeatable deployment rules. Policy controls can govern CI/CD without requiring you to build every gate and deployment workflow yourself.Qovery can shorten the build phase when AWS ownership and governance are requirements. Your application may still need container, database, and networking changes.
RailwayRailway favors ease of use through automatic configuration and a simplified deployment experience. Its enterprise governance capabilities remain more limited than platforms built for controlled infrastructure execution.Railway can provide a quick deployment path for simpler workloads. You may spend additional time adding external controls when compliance or strict environment governance applies.
RenderRender provides Git-based deployments, preview environments, and rollback support. Render hosts applications on its managed infrastructure rather than deploying them into your AWS account.Render can reduce migration work when another hosted PaaS meets your needs. It does not complete a Heroku-to-AWS migration when your AWS account must own the infrastructure.
VercelVercel centers on serverless and edge applications. Backend-heavy Heroku workloads with long-running workers or stateful databases generally require separate services and deployment controls.Vercel may suit a frontend or serverless component, but moving a full Heroku backend can require extra service design. Available research does not support a broader time comparison.

No independent benchmark establishes a universal migration-time winner among these platforms. Workload shape determines elapsed time. Qovery removes more AWS platform engineering when you need governed CI/CD and infrastructure ownership, while Railway or Render may reach production sooner when replacing Heroku with another managed hosting experience is acceptable.

Get started migrating off Heroku

Start your Heroku migration with Qovery by connecting your application and AWS account. The Heroku to AWS migration page walks through the agent-driven path: one command, a plan you approve, and your Heroku stack left untouched until you move DNS. Qovery provides a controlled deployment path for provisioning infrastructure and running CI/CD without requiring you to build every policy gate yourself.

Governed, deterministic execution keeps a migration moving. When each deployment follows the same approved path, you reduce configuration drift and avoid delays caused by inconsistent infrastructure changes.

Frequently asked questions
How long does a Heroku-to-AWS migration take?

Migration duration ranges from days for a small application to several months for regulated or multi-application environments. Small teams may finish in days, while midsize SaaS companies often need weeks, and Qovery can reduce manual infrastructure work. A complete inventory gives you a more reliable estimate.

What are the AWS equivalents of Heroku Postgres and Redis?

Amazon RDS for PostgreSQL and Amazon ElastiCache for Redis provide the closest managed replacements. Qovery can manage these AWS resources alongside your application environments. Managed services reduce the operational work required after migration.

Do I need a systems integrator to migrate off Heroku?

A systems integrator plans and executes migrations that require specialized architecture or compliance work. Qovery offers a self-serve option when your team understands its application and wants to retain infrastructure control. Self-serve tooling can reduce handoffs and simplify ongoing governance.

Can I migrate without downtime?

Logical replication or AWS Database Migration Service can keep data synchronized before a short final cutover. Qovery can support phased environments and governed deployments around that cutover. Precutover validation and a rollback plan can reduce interruption, though application constraints may prevent guaranteed zero downtime.

Mélanie Dallé
About the author
Mélanie Dallé

Melanie leads content at Qovery. She covers platform engineering trends, Kubernetes operations, FinOps, and the tools that help engineering teams ship faster.

Next step

Migrate off Heroku, into your own AWS account

Qovery gives you a governed, repeatable path to deploy into your AWS account with policy-gated CI/CD. Start in under 10 minutes.