Data Migration Plan

Plan phased data migrations with validation checks and rollback paths.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MS33834/AI-SKILL --skill data-migration-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Data Migration Plan
Source: https://github.com/MS33834/AI-SKILL/tree/main/skills/data-migration-plan
Command: npx skills add https://github.com/MS33834/AI-SKILL --skill data-migration-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design a safe migration when moving data between schemas, formats, or systems, reducing the risk of downtime, corruption, and failed cutovers.

Core Features & Use Cases

  • Migration Strategy Selection: Choose between big-bang, incremental, dual-write, or backfill approaches based on volume and downtime tolerance.
  • End-to-End Phasing: Break work into schema changes, code updates, data copy, verification, and cutover steps.
  • Safety and Recovery: Define validation checks, rollback actions, batch sizing, observability, and communication plans.
  • Use Case: A team moving a production orders table to a new schema can use this Skill to plan the transition, verify data parity, and minimize service interruption.

Quick Start

Provide the source system, target system, data volume, and downtime tolerance, and ask for a migration plan.

Frequently Asked Questions about Data Migration Plan

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

FAQPage Schema
How do I plan a database migration with minimal downtime?

To plan a database migration with minimal downtime, select an incremental or dual-write strategy, define batch sizing for data copy, and establish validation checks to ensure data parity before cutover.

What is the best way to roll back a failed schema migration?

The best way to roll back a failed schema migration is to define rollback paths during planning, ensuring you can revert code updates and restore the previous database state if validation checks fail.

How do you validate data parity after moving a production table to a new schema?

Validating data parity after moving a production table involves running verification checks during the phased execution to compare row counts and data integrity between the source and target systems before cutover.

When should I choose a big-bang migration over an incremental approach?

Choose a big-bang migration over an incremental approach when your downtime tolerance allows a full service interruption, whereas incremental strategies suit continuous operations with large data volumes.

What should be included in a data migration cutover plan?

A data migration cutover plan should include phased execution steps, validation checks, rollback actions, batch sizing for locks, observability metrics, and a communication plan for service interruption.