Migrations

System and stack migration playbooks

Step-by-step plans for moving critical systems: why teams migrate, the phases, the pitfalls, and what to measure before and after cutover.

Talk to an engineer

Architecture advisory

Migration index

25 modernization playbooks

Legacy monolithtoModular microservices

Monolith to microservices migration: a strangler fig playbook

Break a monolith into independently deployable services one bounded context at a time, without a big-bang rewrite.

4 phasesRead the playbook

Next.js Pages RoutertoNext.js App Router

Next.js Pages Router to App Router migration

Move a Pages Router application to the App Router and React Server Components route by route, shipping less client-side JavaScript without a rewrite.

4 phasesRead the playbook

HerokutoAWS or Google Cloud

Heroku to AWS or Google Cloud migration

Move off Heroku's dyno limits, add-on pricing and networking constraints to containers on AWS or Google Cloud, with a planned and rehearsed database cutover.

4 phasesRead the playbook

On-premises data centertoAWS landing zone

On-premises to AWS cloud migration

Move data center workloads to a multi-account AWS landing zone in planned waves, with each workload's dependencies mapped before it moves.

4 phasesRead the playbook

MySQL / MariaDBtoPostgreSQL

MySQL to PostgreSQL migration and schema translation

Move MySQL databases to PostgreSQL for transactional DDL, richer indexing, JSONB and extensions such as PostGIS and pgvector, with live replication until cutover.

4 phasesRead the playbook

REST APIstoGraphQL / gRPC

REST to GraphQL and gRPC API migration

Reduce over-fetching and serialization overhead by putting GraphQL in front of UI clients and using gRPC between internal services.

4 phasesRead the playbook

AngularJS / AngulartoReact and Next.js

Angular to React and Next.js incremental migration

Move an Angular application to React and Next.js route by route, so feature work continues while the old framework is retired.

4 phasesRead the playbook

Vue.jstoReact and Next.js

Vue to React and Next.js migration strategy

Consolidate your frontend on React and Next.js to share one component model with React Native and render on the server with React Server Components.

4 phasesRead the playbook

Django (sync)toFastAPI (async)

Django to FastAPI async API modernization

Move blocking Django endpoints to asynchronous FastAPI services where concurrency matters — AI streaming, slow upstream calls — while Django keeps the admin.

4 phasesRead the playbook

Create React App (CRA)toVite / Next.js

Create React App (CRA) to Vite or Next.js migration

Move off deprecated Create React App to Vite or Next.js for faster local development and builds.

4 phasesRead the playbook

EC2 / virtual machinestoAmazon EKS

EC2 to Amazon EKS Kubernetes migration

Containerize EC2 server fleets and move them to an autoscaling Amazon EKS cluster, so you stop paying for idle capacity sized for peaks.

4 phasesRead the playbook

DatadogtoPrometheus and Grafana

Datadog to Prometheus and Grafana migration

Replace a growing Datadog bill with OpenTelemetry, Prometheus and Grafana, keeping the dashboards and alerts your on-call team relies on.

4 phasesRead the playbook

WordPresstoHeadless WordPress and Next.js

WordPress to headless Next.js migration

Keep the WordPress editor your content team knows while visitors get a fast Next.js frontend — and take WordPress itself off the public internet.

4 phasesRead the playbook

ElasticsearchtoOpenSearch / ClickHouse

Elasticsearch to OpenSearch and ClickHouse migration

Separate search from log analytics: OpenSearch for full-text relevance and ClickHouse for high-volume logs, each sized for its own workload.

4 phasesRead the playbook

JavaScripttoStrict TypeScript

JavaScript to strict TypeScript migration

Convert a JavaScript codebase to strict TypeScript file by file, so type errors are caught at compile time instead of in production.

4 phasesRead the playbook

Client-side SPA (Vite, CRA)toReact Server Components

Client SPA to React Server Components migration

Move rendering from the browser to the server with React Server Components, so low-powered devices download and run less JavaScript.

4 phasesRead the playbook

Self-managed PostgreSQL (EC2)toAurora PostgreSQL Serverless v2

Self-managed PostgreSQL to Aurora Serverless v2

Hand database operations — backups, failover and storage growth — to Aurora Serverless v2, with replication running until a short, rehearsed cutover.

4 phasesRead the playbook

Redux / Redux ThunktoZustand and TanStack Query

Redux to Zustand and TanStack Query migration

Separate server state (TanStack Query) from client UI state (Zustand), and delete the actions, reducers and thunks that only existed to move data around.

4 phasesRead the playbook

Custom WebpacktoTurbopack / Vite

Webpack to Turbopack and Vite migration

Replace a fragile custom Webpack configuration with Turbopack or Vite, which start faster and need far less configuration.

4 phasesRead the playbook

Firebase FirestoretoSupabase and PostgreSQL

Firebase Firestore to Supabase PostgreSQL migration

Move from Firestore documents to relational PostgreSQL on Supabase for SQL joins, transactions and pricing that doesn't depend on document reads.

4 phasesRead the playbook

Segment (Twilio)toRudderStack (self-hosted)

Segment to RudderStack customer data platform migration

Take ownership of your customer event pipeline: move from Segment to RudderStack, keep personal data in your own infrastructure, and load events straight into your warehouse.

4 phasesRead the playbook

Auth0 (Okta)toClerk or self-hosted auth

Auth0 to Clerk and modern identity migration

Move from per-MAU Auth0 pricing and redirect-based login to developer-first authentication with embedded components and built-in B2B organizations.

4 phasesRead the playbook

Travis CI / CircleCItoGitHub Actions

CircleCI and Travis CI to GitHub Actions migration

Consolidate CI in GitHub Actions to remove a separate CI vendor and keep build results next to the pull request.

4 phasesRead the playbook

Stripe Charges (legacy)toStripe Billing and usage metering

Stripe Charges to Stripe Billing and usage metering

Rebuild billing on Stripe Billing: subscriptions and usage-based pricing, tax calculation and a self-serve customer portal, with idempotent webhooks underneath.

4 phasesRead the playbook

AWS LambdatoCloud Run / ECS Fargate

AWS Lambda to containers on Cloud Run or Fargate

Move functions that have outgrown Lambda — long jobs, latency-sensitive APIs, complex local setups — into standard containers on Cloud Run or ECS Fargate.

4 phasesRead the playbook

Plan the cutover before you start the migration

Tell us what you're moving and how much data is involved. An engineer will reply within one business day to set up a call on sync strategy, verification and rollback.

Request a strategy call