migration

Plan and execute system and data migrations with phased strategies and rollback triggers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to plan and execute system, language, framework, and data migrations while minimizing downtime, preserving data integrity, and ensuring safe rollbacks.

Core Features & Use Cases

  • Strategy Selection: Recommends Big Bang, Strangler Fig, Parallel Run, or Branch by Abstraction based on code size, team size, and data criticality.
  • Zero-Downtime Data Migration: Dual-write, backfill, verification, and phased cutover with match-rate targets.
  • Operational Safety: Feature-flagged deployments, automated rollback triggers, iterative component extraction, and two-week stability retention before removal.
  • Use Case: Move a large monolith and its database to microservices while keeping live traffic and ensuring >99.9% behavioral parity before cutover.

Quick Start

Ask the migration skill to assess your source and target stacks, propose a phased migration strategy, and generate a step-by-step rollout and rollback plan.

Frequently Asked Questions about migration

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

FAQPage Schema
How do I perform a zero-downtime database migration without losing data?

Zero-downtime database migration uses dual-write, backfill, and verification phases to sync data, followed by a phased cutover with match-rate integrity checks to ensure behavioral parity before switching traffic.

What is the best way to migrate a monolith to microservices while keeping live traffic?

Migrating a monolith to microservices safely uses the Strangler Fig pattern for iterative component extraction, feature-flagged rollouts, and automated rollback triggers to maintain live traffic stability.

How does the Strangler Fig pattern work for system migrations?

The Strangler Fig pattern works by iteratively extracting components from a legacy system, routing traffic to new implementations via feature flags, and retaining old components for two weeks of stability before removal.

Can I use feature flags to manage rollback triggers during a data migration?

Feature flags manage rollback triggers during data migration by controlling traffic routing, allowing automated rollback if match-rate integrity checks fail or behavioral parity drops below acceptable targets.

When do I need a dual-write and backfill verification process for data migration?

You need dual-write and backfill verification for data migration when moving large monoliths or critical databases, ensuring >99.9% behavioral parity and zero downtime before the final cutover.

Does this migration strategy support a REST to GraphQL transition?

This migration strategy supports REST to GraphQL transitions by assessing source and target stacks, recommending phased rollout strategies, and generating step-by-step rollout and automated rollback plans.