Cluster C · Migrate to AWS

Migrate to AWS — funded, and done for you

Build-grade guides for moving to AWS from Heroku, GCP, Azure, on-prem, Oracle, or SAP: the strategy (the 7 Rs), the tools (MGN, DMS, SCT), the realistic cost and timeline, and the database + container cutovers that actually trip teams up.

The best part: the AWS Migration Acceleration Program funds the assessment and a large chunk of the move. CloudRoute routes you to a vetted partner who runs the migration — AWS-funded, so you migrate at little to no cost. See how that works →

Start here

AWS migration — the complete 2026 guideThe complete 2026 guide to AWS migration: the 7 Rs framework, the three-phase MAP model (Assess/Mobilize/Migrate), the tooling (MGN, DMS, SCT, Migration Hub), realistic timeline + cost, and how MAP funds qualifying migrations toward $0. A partner runs it.
Migrate to AWS — the funded, done-for-you pathMigrate to AWS the done-for-you way: the full discovery→assess→landing-zone→pilot→migrate→optimize journey, rehost vs replatform, timelines, and the MAP-funded $0 path.
AWS migration services — the full tool + services mapAWS migration services explained: the native tools (MGN, DMS, SCT, Migration Hub, DataSync) — what each does and when — plus the partner services, MAP-funded toward $0.
AWS migration cost — the full 2026 breakdownWhat an AWS migration really costs in 2026: the seven cost components, pricing by estate size and by strategy (rehost vs refactor), the TCO savings — and how AWS MAP funding offsets a large share so the net approaches $0. Worked example inside.
AWS migration strategy — the 7 Rs, applied per applicationYour AWS migration strategy, the 7 Rs in depth (Retire, Retain, Rehost, Relocate, Repurchase, Replatform, Refactor): cost/effort/risk per R, how to assign one per app, and migrate-then-modernize.

Funding — AWS pays for it (MAP)

AWS Migration Acceleration Program (MAP) — the funded migration pathThe AWS Migration Acceleration Program (MAP), explained: the three phases (Assess → Mobilize → Migrate & Modernize), what AWS funds at each, how funding scales with migration size and committed spend, eligibility, the partner-filed APN mechanic, and how to actually claim it.
AWS migration funding — every program, who qualifies, how to unlock itHow AWS funds migrations: MAP credits, free Assess + funded Mobilize, OLA licensing savings, and partner incentives. Who qualifies, realistic amounts, and the partner-filed mechanic DIY migrators miss.

Migrate off your platform

Heroku → AWS — the funded migration pathHeroku to AWS, done right: dynos to ECS/Fargate or App Runner, Postgres to RDS/Aurora, the DMS cutover, real before/after cost, and a MAP-funded partner who runs it.
GCP to AWS — the service-by-service migrationMigrate Google Cloud to AWS: the full service map (GKE→EKS, Cloud SQL→RDS/Aurora, BigQuery→Redshift/Athena, Pub/Sub→SNS/SQS, Firestore→DynamoDB), IAM + networking differences, GCP egress costs, the cutover plan, and how AWS MAP funds a partner to run it.
Azure to AWS — the 2026 migration guideThe senior-engineer Azure→AWS guide: full service mapping (AKS→EKS, Azure SQL→RDS, Blob→S3, Cosmos→DynamoDB), networking gotchas, egress cost, the cutover plan, and how MAP funds it.
On-premise to AWS — the funded data-center exitThe senior-engineer guide to migrating on-prem to AWS: discovery with Application Discovery Service, VMware Cloud on AWS vs Outposts vs MGN rehost, Direct Connect + Transit Gateway, DataSync + Snowball, capex-to-opex economics, DR, and a MAP-funded partner who runs the cutover.
DigitalOcean → AWS — the funded migration pathDigitalOcean to AWS, done right: Droplets to EC2, App Platform to App Runner/ECS, Managed DB to RDS, Spaces to S3, DOKS to EKS, the DMS cutover, real cost, MAP-funded partner.
Vercel → AWS — the funded Next.js migration pathVercel to AWS, done right: Amplify vs OpenNext/SST vs Fargate, how ISR, edge middleware & image optimization map, the DNS cutover, real cost cuts, and a MAP-funded partner who runs it.
Oracle to AWS — RDS lift-and-shift vs Aurora re-platformMove Oracle to AWS two ways: lift-and-shift to RDS for Oracle, or re-platform to Aurora PostgreSQL to delete the license bill (60–90% savings). The SCT+DMS workflow, PL/SQL gotchas, CDC cutover, and MAP funding.
SAP to AWS — the funded, partner-led migrationMove SAP to AWS: SAP-certified HANA instances (High Memory / U-series up to 24 TiB), the two migration paths plus RISE with SAP, DMO tooling, HA/DR, downtime minimization, and how AWS MAP + SAP RACE funding take a large share of the cost off the table.

Database migrations

Oracle to Aurora PostgreSQL — the heterogeneous migration done rightThe deep Oracle to Aurora PostgreSQL guide: what AWS SCT auto-converts vs the hard PL/SQL (packages, autonomous transactions, CONNECT BY), DMS full-load + CDC, app data-access changes, validation, cutover & rollback, and MAP funding.
SQL Server to AWS — RDS, Babelfish, or EC2Move SQL Server to AWS three ways: RDS for SQL Server, Aurora + Babelfish to delete the license bill, or EC2 for full Always On. OLA + MAP funding, partner-led.
MySQL to Aurora — the homogeneous migration guide (2026)Migrate MySQL to Aurora MySQL — the homogeneous, low-risk move. The 3 methods, compatibility, cutover, and cost vs RDS MySQL. Partner-run, MAP-funded.
PostgreSQL → Aurora PostgreSQL — the homogeneous migrationPostgres to Aurora PostgreSQL, homogeneous (no schema conversion): the four migration methods, extension/version gotchas, the cutover, cost vs RDS, and MAP funding.
MongoDB to AWS — DocumentDB vs Atlas vs self-managedMoving MongoDB to AWS in 2026: Amazon DocumentDB vs MongoDB Atlas on AWS vs self-managed on EC2 — honest tradeoffs, the DMS data-migration path, the DocumentDB compatibility caveats, cutover, and MAP-funded done-for-you migration at low-to-$0 cost.
Heroku Postgres → RDS — the funded cutover pathMigrate Heroku Postgres to Amazon RDS or Aurora: the three cutover methods (pg_dump/restore, DMS CDC, logical replication), Heroku specifics (followers, connection limits, extensions, the DATABASE_URL swap), the runbook + rollback, and the downtime math. MAP-funded partner option.
Cloud SQL to RDS/Aurora — the engine-by-engine migrationMigrate Google Cloud SQL to Amazon RDS/Aurora by engine (MySQL, PostgreSQL, SQL Server) with DMS + native replication for near-zero-downtime cutover — run by a MAP-funded AWS partner.

Containers & Kubernetes

GKE to EKS — the cluster-boundary migrationGKE to EKS: what carries over (manifests, Helm, images) vs what you re-author — Workload Identity→IRSA, Ingress→ALB, PD→EBS, GCR→ECR, Karpenter. AWS MAP funds a partner to run it.
AKS to EKS — the 2026 Kubernetes migration playbookThe senior-engineer AKS to EKS playbook: manifests and Helm carry over; the five edges that change (identity, ingress, storage, registry, Karpenter) and how MAP funds it.
Kubernetes to EKS — the self-managed-K8s migration pathMigrate self-managed Kubernetes (kubeadm, Rancher, OpenShift) to Amazon EKS — the full remap (CSI, ALB, IRSA, ECR, Karpenter), Velero cutover, and MAP-funded delivery.

Tools & process

AWS DMS — the Database Migration Service guide (2026)AWS DMS explained: full load + CDC for near-zero-downtime moves, homogeneous vs heterogeneous (Oracle→Aurora) with SCT, the workflow, pitfalls, and cost. Partner-run, MAP-funded.
AWS Application Migration Service (MGN) — the lift-and-shift engineHow AWS MGN works: block-level replication, the install→test→cutover workflow, MGN vs DMS, VMware/on-prem fleets, and MAP-funded done-for-you migrations at ~$0.
The AWS migration checklist — every phase, start to finishThe complete AWS migration checklist: pre-migration foundation, the per-wave cutover loop, post-migration decommission. Partner-run, MAP-funded migrations.
AWS migration assessment — the MAP Assess deep diveThe AWS migration assessment (MAP Assess) explained: discovery with Application Discovery Service + Migration Evaluator, a 7-R disposition per app, dependency mapping, the MRA, a TCO business case, and a fundable wave plan. AWS often funds this phase — partner-led, often $0.
AWS migration timeline — how long a move actually takesHow long does an AWS migration take? Realistic 2026 timelines by estate size (single app 2–6 weeks to enterprise 9–24 months) and how MAP compresses the calendar.

Migrate your app

Migrate a Rails app to AWS — the funded migration pathMigrate Ruby on Rails to AWS: web + Sidekiq on ECS/Fargate, Postgres on RDS/Aurora, Redis on ElastiCache, Active Storage on S3, the DMS cutover — MAP-funded.
Django → AWS — the funded migration pathMigrate Django to AWS: gunicorn/uvicorn on ECS Fargate, RDS/Aurora Postgres, ElastiCache for Celery, S3+CloudFront for static & media, a DMS cutover — MAP-funded.
Node.js → AWS — the funded migration pathMigrate Node.js to AWS the right way: App Runner vs ECS/Fargate vs Lambda, RDS/Aurora vs DynamoDB, WebSockets, the DMS cutover — run by a MAP-funded partner.
Migrate WordPress to AWS — the full 2026 playbookMigrate WordPress to AWS: the right target (Lightsail vs EC2 vs ECS/Fargate), Aurora/RDS, S3+CloudFront for media, ElastiCache, the cutover — and a MAP-funded partner.
Migrate a .NET app to AWS — the 2026 guideSenior-engineer guide to running .NET & ASP.NET on AWS: modern .NET on App Runner/Fargate/Lambda vs .NET Framework on Windows, Porting Assistant, SQL Server options, IIS→ALB, and MAP+OLA funding.
Migrate a Laravel app to AWS — the funded migration pathMigrate Laravel to AWS, done right: PHP-FPM + nginx on ECS/Fargate or App Runner, RDS/Aurora MySQL, ElastiCache, Horizon workers, the DMS cutover, and a MAP-funded partner who runs it.

Why AWS

Heroku vs AWS — the neutral comparisonA neutral Heroku vs AWS comparison: Heroku wins on developer experience early, AWS wins on cost and scale later. The crossover point, ops burden, verdict by stage.
Why migrate to AWS — the business caseWhy migrate to AWS: the eight real benefits of AWS migration — TCO at scale, ~240 services, 36 Regions, eleven-nines reliability, 140+ compliance certs, elastic scaling, Bedrock + data — with numbers, the honest "when not to," and how MAP funds the move.
Lift-and-shift vs replatform vs refactor — the strategy-choice deep-diveRehost vs replatform vs refactor for AWS migration: cost, effort, risk, time-to-value, and long-run payoff of each, when to choose which, migrate-then-modernize sequencing, and the common mistakes.
On-premise vs cloud cost — the honest AWS TCO comparisonOn-premise vs cloud cost, honestly: the full on-prem TCO (hardware, power, staff, over-provisioning, refresh) vs AWS opex. When cloud wins, when on-prem does, plus MAP funding.