migration-strategy

Plan and execute large-scale system migrations using the Strangler Fig pattern.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill migration-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-strategy
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/migration-strategy
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill migration-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large-scale migrations are high-risk, complex efforts that require careful planning, coordination across teams, and robust rollback strategies to minimize downtime and preserve feature parity.

Core Features & Use Cases

  • Strangler Fig pattern for incremental migration from monoliths to microservices.
  • Zero-downtime database migration planning and execution.
  • Cloud migration and re-platforming guidance, including dependency mapping and cutover strategies.
  • Framework and language upgrade planning with risk assessment and staged rollout.
  • Example: migrate a legacy monolith to a collection of services while maintaining user-visible functionality.

Quick Start

Draft a complete Migration Plan using the provided template and guidelines.

Frequently Asked Questions about migration-strategy

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

FAQPage Schema
How do I migrate a monolith to microservices without downtime?

Apply the Strangler Fig pattern to incrementally extract services from the legacy monolith, maintaining feature parity and user-visible functionality while progressively routing traffic to the new microservices architecture.

What is the Strangler Fig pattern and when should I use it for cloud migration?

The Strangler Fig pattern incrementally replaces legacy monolith functionality with new microservices until the old system is fully decommissioned, making it ideal for complex cloud migration or re-platforming projects where high risk and downtime must be minimized.

How do I plan a zero-downtime database migration?

Plan a zero-downtime database migration by mapping dependencies, executing staged rollouts, and implementing continuous data integrity checks alongside robust rollback procedures to ensure data consistency during the cutover.

What are the best strategies for framework upgrades with rollback procedures?

The best strategies for framework upgrades use staged rollouts with comprehensive risk assessment, ensuring robust rollback procedures are in place to revert changes if data integrity or feature parity is compromised during execution.

Can I use this approach for re-platforming legacy systems at a large scale?

Yes, this approach supports large-scale re-platforming of legacy systems by providing comprehensive migration planning templates, dependency mapping, and cutover strategies tailored for complex architectural transformations.