Blog
Cloud Migration
Heroku
AWS
AI
3
minutes

How AI Helped To Migrate 37 Apps From Heroku To AWS Under 2 Hours

Startups relying on Heroku often hit roadblocks as they scale. Rising costs, technical limitations, and lack of control over infrastructure force many to explore alternatives. One such startup recently migrated 37 applications from Heroku to AWS using Qovery’s DevOps AI Migration Agent. Here’s how they accomplished this migration in less than two hours, saving days of manual work.
November 3, 2025
Romaric Philogène
CEO & Co-founder
Summary
Twitter icon
linkedin icon

Why Migrate from Heroku?

While Heroku excels in simplicity, it falls short in scaling businesses:

  • Cost: Hosting multiple applications becomes expensive as usage grows.
  • Technical Limitations: Heroku lacks microservices support and advanced configuration flexibility.
  • Infrastructure Control: Limited options prevent teams from optimizing for performance, compliance, and custom workflows.

This startup needed more flexibility and scalability, making AWS the clear choice. However, manually migrating 37 applications would have been a time-consuming and error-prone process. That’s where Qovery’s DevOps AI Migration Agent played a crucial role.

The Migration Process in Four Steps

Step 1: Application Discovery

The process began with migrate.qovery.com. The DevOps AI Migration Agent connected to the startup’s Heroku account in read-only mode, automatically fetching configurations for all 37 applications, including environment variables and build settings.

Step 2: Configuration Transformation with AI

Next, the Migration Agent utilized Claude AI via AWS Bedrock API to convert Heroku configurations into Qovery Terraform Provider configurations optimized for AWS.

DevOps AI Agent Migrating Heroku Apps To AWS via Qovery

Key tasks included:

  • Translating Heroku application settings and addons (databases and external services) to AWS equivalents via Qovery.
  • Structuring secrets in a secure variables.tf file, separating them from the main Terraform configuration.

All of that can be easily reviewable and editable before getting executed.

Step 3: Validation and Auto-Remediation

After generating the Terraform files, the Migration Agent validated them using terraform validate --json. If errors were detected, the system entered an auto-remediation loop:

  1. Error messages were analyzed, and the configuration was updated automatically.
  2. Validation was retried.
Auto-remediation loop to make sure the Terraform configuration is valid

This loop could run up to 10 times, ensuring most errors were resolved without manual intervention. If a specific application couldn’t be fixed automatically, it was flagged for further review while the migration process continued.

Step 4: Delivery of Ready-to-Deploy Configurations

Once validated, the Migration Agent organized the Terraform configurations into separate folders for each application. Each folder included a README file with deployment instructions. Although optional, the startup’s team reviewed the configurations and found them deployment-ready with minimal adjustments.

$ tree
.
├── README.md
├── cost_estimation_report.md
├── app_1
│ ├── Dockerfile
│ ├── main.tf
│ └── variables.tf
├── app_2
│ ├── Dockerfile
│ ├── main.tf
│ └── variables.tf
├── app_3
│ ├── Dockerfile
│ ├── main.tf
│ └── variables.tf

So you can get into each folder and run the following commands to start the migration:

$ terraform init
$ terraform apply

Migration Time: Under 2 Hours

By automating the discovery, transformation, validation, and delivery steps, the startup completed their migration in less than two hours. What could have taken several days or weeks of manual effort was condensed into an efficient, streamlined process.

Database Migration: A Hybrid Approach

While the Migration Agent creates database instances on AWS, it doesn’t handle data transfer. In this case, Qovery’s Technical Account Managers provided expert support to help the startup migrate their database content, ensuring a smooth transition.

Results and Impact

Using Qovery’s DevOps AI Migration Agent, the startup achieved a rapid and risk-free migration. Key benefits included:

  • Lower Costs: AWS provided more predictable pricing and better resource allocation.
  • Greater Flexibility: Full control over infrastructure to support microservices and custom configurations.
  • Improved Scalability: AWS offers a robust platform for future growth and optimization.

Conclusion

Manually migrating 37 applications would have been a time-consuming process. Qovery’s DevOps AI Migration Agent proved how automation can transform a complex migration into a quick and seamless experience. For startups looking to scale beyond Heroku, Qovery offers an efficient and reliable pathway to AWS.

Share on :
Twitter icon
linkedin icon
Tired of fighting your Kubernetes platform?
Qovery provides a unified Kubernetes control plane for cluster provisioning, security, and deployments - giving you an enterprise-grade platform without the DIY overhead.
See it in action

Suggested articles

Kubernetes
 minutes
Stopping Kubernetes cloud waste: agentic automation for enterprise fleets

Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.

Mélanie Dallé
Senior Marketing Manager
Platform Engineering
Kubernetes
DevOps
10
 minutes
What is Kubernetes? The reality of Day-2 enterprise fleet orchestration

Kubernetes focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.

Morgan Perry
Co-founder
AI
Compliance
Healthtech
 minutes
Agentic AI infrastructure: moving beyond Copilots to autonomous operations

The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards

Mélanie Dallé
Senior Marketing Manager
Kubernetes
8
 minutes
The 2026 guide to Kubernetes management: master day-2 ops with agentic control

Effective Kubernetes management in 2026 demands a shift from manual cluster building to intent-based fleet orchestration. By implementing agentic automation on standard EKS, GKE, or AKS clusters, enterprises eliminate operational weight, prevent configuration drift, and proactively control cloud spend without vendor lock-in, enabling effective scaling across massive fleets.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
 minutes
Building a single pane of glass for enterprise Kubernetes fleets

A Kubernetes single pane of glass is a centralized management layer that unifies visibility, access control, cost allocation, and policy enforcement across § cluster in an enterprise fleet for all cloud providers. It replaces the fragmented practice of switching between AWS, GCP, and Azure consoles to govern infrastructure, giving platform teams a single source of truth for multi-cloud Kubernetes operations.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
 minutes
How to deploy a Docker container on Kubernetes (and why manual YAML fails at scale)

Deploying a Docker container on Kubernetes requires building an image, authenticating with a registry, writing YAML deployment manifests, configuring services, and executing kubectl commands. While necessary to understand, executing this manual workflow across thousands of clusters causes severe configuration drift. Enterprise platform teams use agentic platforms to automate the entire deployment lifecycle.

Mélanie Dallé
Senior Marketing Manager
Qovery
Cloud
AWS
Kubernetes
8
 minutes
10 best practices for optimizing Kubernetes on AWS

Optimizing Kubernetes on AWS is less about raw compute and more about surviving Day-2 operations. A standard failure mode occurs when teams scale the control plane while ignoring Amazon VPC IP exhaustion. When the cluster autoscaler triggers, nodes provision but pods fail to schedule due to IP depletion. Effective scaling requires network foresight before compute allocation.

Morgan Perry
Co-founder
Kubernetes
Terraform
 minutes
Managing Kubernetes deployment YAML across multi-cloud enterprise fleets

At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.

Mélanie Dallé
Senior Marketing Manager

It’s time to change
the way you manage K8s

Turn Kubernetes into your strategic advantage with Qovery, automating the heavy lifting while you stay in control.