data-migration

Migrate data between systems using Expand-Contract phases with zero downtime.

Updated May 11, 2026

Search Tags:#backfill #data-migration #dual-write #expand-contract #shadow-read

Ready to run

npx skills add https://github.com/resultakak/argos --skill data-migration-resultakak

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-migration
Source: https://github.com/resultakak/argos/tree/main/skills/data-migration
Command: npx skills add https://github.com/resultakak/argos --skill data-migration-resultakak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Data migration projects often suffer from downtime, data inconsistency, and complex orchestration. This skill provides a disciplined Expand-Contract approach with idempotent backfill, shadow reads, and controlled cutover to minimize risk and downtime.

Core Features & Use Cases

Expand-Contract phases (Expand, Migrate, Switch, Contract) to enable zero-downtime transitions.
Dual-write with idempotency keys, chunked backfill, and shadow validation for data integrity.
Audit, compliance, and rollback drills to maintain governance and recoverability.

Quick Start

Plan your first migration by outlining source/target schemas and initiating the Expand phase.

Frequently Asked Questions about data-migration

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

FAQPage Schema

How do I perform a zero-downtime database migration across different cloud engines?▼

A zero-downtime database migration uses an Expand-Contract approach with phased cutover, dual-write idempotency, and chunked backfill to transition data safely without service interruptions.

What is the Expand-Contract pattern for data migration and when do I need it?▼

The Expand-Contract pattern enables zero-downtime data migration by expanding schema, migrating data via backfill, switching traffic, and contracting the old schema. It is needed when downtime risk is unacceptable.

How to validate data integrity during a dual-write migration process?▼

Validate data integrity during a dual-write migration by using idempotency keys for safe retries, chunked backfill for consistency, and shadow reads to compare source and target data before final cutover.

Can I roll back a database migration after the controlled cutover phase?▼

Yes, rollback readiness after controlled cutover is maintained through built-in audit trails and rollback drills, ensuring you can safely revert the database migration if data inconsistency or errors occur.

What are the limitations of using chunked backfill for large data migrations?▼

Chunked backfill requires careful orchestration to avoid locking issues during large data migrations, but it ensures idempotent processing and maintains consistency without overwhelming source or target databases.