Phased strangler-fig plans, cutover and rollback steps, risk matrices and team shapes for the ten legacy migrations we get asked about most.
By the Ryz Labs team · Updated November 2026
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.
| From | To | Why now | First move |
|---|---|---|---|
| COBOL / mainframe | API-first Python services | z/OS 2.5 end of service: September 2026 | Capture 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, 2027 | SDK-style projects, .NET Standard 2.0 bridge |
| AngularJS 1.x | React / Next.js | AngularJS support ended January 2022 | Next.js shell behind a proxy, route by route |
| Vue 2 / Nuxt 2 | Vue 3 / Nuxt current | Vue 2 EOL Dec 31, 2023; Nuxt 2 EOL Jun 30, 2024 | Plugin audit, then the @vue/compat build |
| Xamarin / Xamarin.Forms | React Native | Xamarin support ended May 1, 2024; store SDK rules moved on | Native shell, then screen-by-screen |
| Legacy Rails | Rails 8.1, modular monolith | Only Rails 8.1 gets security fixes (8.0 ended Nov 7, 2026) | Dual boot, one minor version at a time |
| PHP 5 / 7 | PHP 8.x + Laravel or Symfony | PHP 8.1 EOL Dec 31, 2025; 8.2 security ends Dec 31, 2026 | Rector + static analysis baselines, URL strangler |
| Python 2 | Supported Python 3.x | Python 2 sunset Jan 1, 2020; 3.10 EOL Oct 2026 | Characterization tests, dual-interpreter CI |
| Heroku | AWS (ECS, RDS) | Heroku moved to a sustaining engineering model (Feb 2026) | Containers per process type, database replication |
| Bubble / no-code | Custom code you own | Workload-unit pricing since May 2023; no code export | Inventory 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.
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.
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.
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.
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.
Ryz Labs
Tell us what you're building. You get a scoped plan, a price and the names of the people who would do the work.
Privacy choices
Essential cookies
Required for core site functionality, security, and your saved privacy choices.
Analytics cookies
Help us understand how visitors use the site so we can improve performance and content.
Marketing cookies
May be used to measure campaigns and make marketing more relevant.