application-migration

Plan and manage application migrations from legacy systems to modern platforms.

14|11|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill application-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: application-migration
Source: https://github.com/DauQuangThanh/hanoi-rainbow/tree/main/skills/application-migration
Command: npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill application-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides organizations through end-to-end application migrations, helping teams move from legacy systems to modern, cloud-native architectures with structured assessment, planning, and execution.

Core Features & Use Cases

  • Migration Assessment: framework to inventory systems, dependencies, and business criticality.
  • Strategy Selection: guidance on Strangler Fig, Phased, Big Bang, etc., with decision matrices.
  • Roadmap & Execution Playbooks: phased roadmaps for migration, risk and cutover planning.
  • Reference Documentation: load migration planning, testing, and post-migration guidance from references.

Quick Start

Describe your current system and target goals to generate a detailed migration plan.

Frequently Asked Questions about application-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan an application migration from a legacy monolith to cloud-native architecture?

Application migration planning involves inventorying system dependencies, assessing business criticality, selecting a migration strategy, and generating a phased roadmap for moving legacy monoliths to cloud-native platforms. It covers assessment, data mapping, testing, and cutover execution.

What is the best migration strategy for moving large enterprise ERP or CRM systems?

The best migration strategy depends on risk tolerance and system complexity. You can choose between Strangler Fig, Phased, or Big Bang approaches using a decision matrix to evaluate trade-offs for large enterprise ERP or CRM modernization. Governance playbooks guide the final cutover.

How does the Strangler Fig pattern work for legacy system modernization?

The Strangler Fig pattern gradually replaces legacy system functionality with modern microservices by routing specific routes to new implementations, allowing phased modernization without a risky big bang cutover. It minimizes downtime during the migration process.

Can I use this for migrating custom monoliths to microservices?

Yes, this supports migrating custom monoliths to microservices by providing structured assessment templates, dependency mapping, and phased execution roadmaps tailored for complex custom architectures. It ensures data mapping and testing are integrated.

What is included in a cutover execution plan for cloud migration?

A cutover execution plan includes risk management protocols, data mapping procedures, testing validation, and governance playbooks to ensure a controlled transition from legacy systems to modern cloud platforms. It dictates post-migration operational stability.