Ryz Labs/Migrations
Ryz Labs

Legacy migration runbooks

Phased strangler-fig plans, cutover and rollback steps, risk matrices and team shapes for the ten legacy migrations we get asked about most.

Each runbook covers one migration end to end: why teams are moving now (with the official end-of-life dates linked), what to inventory before you start, a phased strangler-fig plan with exit criteria, how traffic moves at cutover and how you roll back, a risk matrix, and the team shape that does the work. Ryz engineers on your team start from $7,000 per month, and once you say go, engineers can typically start in under two weeks.

The migration matrix

FromToWhy nowFirst move
COBOL / mainframeAPI-first Python servicesz/OS 2.5 end of service: September 2026Capture copybooks, CICS and batch interfaces; reconcile outputs
.NET Framework 4.x.NET 10 LTS.NET 8 and 9 support ended Nov 10, 2026; 4.6.2 ends Jan 12, 2027SDK-style projects, .NET Standard 2.0 bridge
AngularJS 1.xReact / Next.jsAngularJS support ended January 2022Next.js shell behind a proxy, route by route
Vue 2 / Nuxt 2Vue 3 / Nuxt currentVue 2 EOL Dec 31, 2023; Nuxt 2 EOL Jun 30, 2024Plugin audit, then the @vue/compat build
Xamarin / Xamarin.FormsReact NativeXamarin support ended May 1, 2024; store SDK rules moved onNative shell, then screen-by-screen
Legacy RailsRails 8.1, modular monolithOnly Rails 8.1 gets security fixes (8.0 ended Nov 7, 2026)Dual boot, one minor version at a time
PHP 5 / 7PHP 8.x + Laravel or SymfonyPHP 8.1 EOL Dec 31, 2025; 8.2 security ends Dec 31, 2026Rector + static analysis baselines, URL strangler
Python 2Supported Python 3.xPython 2 sunset Jan 1, 2020; 3.10 EOL Oct 2026Characterization tests, dual-interpreter CI
HerokuAWS (ECS, RDS)Heroku moved to a sustaining engineering model (Feb 2026)Containers per process type, database replication
Bubble / no-codeCustom code you ownWorkload-unit pricing since May 2023; no code exportInventory as spec, feature-by-feature rebuild

Dates are from the vendors' own support pages, linked on each runbook, and were checked on November 20, 2026.

All runbooks

COBOL to Python: Mainframe Exit Runbook for API-First ServicesHow to rebuild COBOL and mainframe workloads as Python services: capture the interfaces, run old and new side by side, reconcile every record, then cut over..NET Framework 4.x to .NET 10 Migration RunbookUpgrade a .NET Framework estate one project at a time: .NET Standard 2.0 bridges, YARP side-by-side hosting, CoreWCF, EF Core and Linux containers.AngularJS to React and Next.js: A Migration RunbookA route-by-route plan for retiring AngularJS 1.x: a reverse-proxy strangler, component bridges, service replacement and a cutover you can roll back.Vue 2 to Vue 3 and Nuxt 2 to Nuxt 4: A Migration RunbookHow to get a Vue 2 or Nuxt 2 codebase onto Vue 3 and current Nuxt without a rewrite: audit plugins, run the migration build, burn down warnings, then cut over.Xamarin to React Native Migration RunbookHow to get a Xamarin app shipping again: a release-unblock plan, a native shell, React Native screens one flow at a time, and store phased rollouts.Legacy Rails to Rails 8.1: Upgrade and Modernization RunbookA staff-engineer runbook for moving an old Rails monolith to Rails 8.1 one minor at a time, with dual boot, a deprecation burn-down and packwerk boundaries.Legacy PHP 5/7 to Modern PHP 8: Migration RunbookHow to get an old PHP codebase onto a supported PHP 8 release and a modern framework, route by route, without a big-bang rewrite or a dead weekend.Python 2 to Python 3 Migration Runbook: Land on a Supported 3.xA test-first plan for moving Python 2-era code to a supported Python 3 release, covering text and bytes, stored data, C extensions, dependencies and rollback.Heroku to AWS Migration RunbookA platform move, not a rewrite: containers on ECS Fargate, Heroku Postgres to RDS or Aurora, add-ons mapped one by one, and a DNS cutover you can reverse.Bubble to Custom Code Migration RunbookBubble does not export code, so this is a rebuild: pull the data out, inventory every workflow and privacy rule, and move users over one feature at a time.

How we run a migration

The same rules apply to every stack. Write characterization tests before you change anything. Move one slice at a time behind a router, a flag or a proxy, so the old system keeps serving everything you have not moved. Compare old and new outputs on real traffic before each cutover, and keep a rollback path that is one switch away until the old path is retired. Our engineers work on your team, reporting to your leads, in your repos and cloud accounts. When the work is reading and comparing large codebases, an AI pod speeds up test generation, codemods and diff triage, and every change still goes through human review.

Prototype to production

Not every system is old. If yours started as an AI-built prototype on Lovable, Bolt.new, Replit, v0, Cursor, Bubble, Make, Zapier or Airtable, the prototype-to-production runbooks and risk scorer cover the security, data and delivery work. Moving off Heroku or another platform? The AI production cost audit compares hosting, database and LLM spend at published list prices.

What it costs

Ryz engineers on your team start from $7,000 per month. Our published range is $7,000 to $15,000 per engineer per month, mostly mid-level to senior, quoted per team. Many teams begin with a pod of 3 to 5 senior engineers (a tech lead plus engineers), and a full pod is about seven. A migration budget is team size × months × monthly rate; the months depend on how many slices you move and how clean the comparison runs are, so we scope it with you instead of quoting a fixed project. See engineer rates by role or scope your team.

Related

See our legacy application modernization, mainframe modernization and cloud migration services, or browse engineers by role and guides.

Thanks — your message has been sent. We’ll get back to you soon.

Something went wrong while sending your message. Please try again or email info@ryzlabs.com.

Explore Ryz Labs

Software development servicesAI development companyIndustriesStaff augmentationAI pod teamsNearshore software developmentHire engineers by roleEngineer ratesGuidesBuyer guidesCase studiesHow we vet engineers

Ryz Labs

Senior engineers on your team. AI pod teams that ship.

Tell us what you're building. You get a scoped plan, a price and the names of the people who would do the work.

  • Only the top 1% of tens of thousands interviewed make it
  • On US business hours, including New York hours
  • Trusted by Fortune 500 engineering teams

Tell us who you need

A Ryz partner replies with a scoped team plan.

Start a conversation →

Prefer to talk? Book a 15-min call →