Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Migration Architect

alirezarezvani/claude-skills

  • 586 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

migration-architect is a Claude skill that generates zero-downtime migration plans, compatibility checks, and rollback runbooks for developers who move databases or services without taking production offline.

About

migration-architect is a Claude skill categorized as Engineering Migration Strategy that combines proven patterns with automated planning tooling for complex system transitions. Its core scripts include migration_planner.py for automated migration plan generation and compatibility_checker.py for schema and API compatibility validation, plus rollback strategy generation for safer cutovers. Developers reach for migration-architect when replacing a database engine, splitting a monolith service, or upgrading schemas where downtime is unacceptable and rollback must be rehearsed. The skill produces structured plans, compatibility reports, and runbooks agents can execute or hand to SRE teams. It targets ship-phase readiness work rather than greenfield schema design.

  • Three core scripts: `migration_planner.py`, `compatibility_checker.py`, `rollback_generator.py`
  • Reference catalogs for migration patterns, zero-downtime techniques, and data reconciliation strategies
  • Sample JSON specs for database and service migrations plus before/after schema fixtures
  • Tiered as POWERFUL engineering migration strategy with automated plan and rollback procedure generation
  • Emphasizes compatibility validation before cutover and explicit rollback paths

Migration Architect by the numbers

  • 586 all-time installs (skills.sh)
  • Ranked #249 of 1,440 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill migration-architect

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs586
repo stars★ 23.5k
Security audit3 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills ↗

How do you plan a zero-downtime database migration?

Generate zero-downtime migration plans, compatibility checks, and rollback runbooks when moving databases or services without taking the product offline.

Who is it for?

Backend and platform engineers executing database or service migrations who need scripted planning and compatibility validation before production cutover.

Skip if: Greenfield schema design on empty databases or trivial single-table ALTERs with approved maintenance windows.

When should I use this skill?

The user plans a database engine swap, blue-green service migration, or schema change that must avoid downtime and include rollback steps.

What you get

Migration plans, schema and API compatibility reports, rollback runbooks, and validation checklists for cutover.

  • migration plan
  • compatibility report
  • rollback runbook

By the numbers

  • Includes 2 core scripts: migration_planner.py and compatibility_checker.py

Files

SKILL.mdMarkdownGitHub ↗

Migration Architect

Tier: POWERFUL Category: Engineering - Migration Strategy Purpose: Zero-downtime migration planning, compatibility validation, and rollback strategy generation

Overview

The Migration Architect skill provides comprehensive tools and methodologies for planning, executing, and validating complex system migrations with minimal business impact. This skill combines proven migration patterns with automated planning tools to ensure successful transitions between systems, databases, and infrastructure.

Core Capabilities

1. Migration Strategy Planning

  • Phased Migration Planning: Break complex migrations into manageable phases with clear validation gates
  • Risk Assessment: Identify potential failure points and mitigation strategies before execution
  • Timeline Estimation: Generate realistic timelines based on migration complexity and resource constraints
  • Stakeholder Communication: Create communication templates and progress dashboards

2. Compatibility Analysis

  • Schema Evolution: Analyze database schema changes for backward compatibility issues
  • API Versioning: Detect breaking changes in REST/GraphQL APIs and microservice interfaces
  • Data Type Validation: Identify data format mismatches and conversion requirements
  • Constraint Analysis: Validate referential integrity and business rule changes

3. Rollback Strategy Generation

  • Automated Rollback Plans: Generate comprehensive rollback procedures for each migration phase
  • Data Recovery Scripts: Create point-in-time data restoration procedures
  • Service Rollback: Plan service version rollbacks with traffic management
  • Validation Checkpoints: Define success criteria and rollback triggers

Quick Start — plan → check compatibility → generate rollback

All paths relative to this skill folder; sample inputs in assets/, expected shapes in expected_outputs/.

# 1. Generate the migration plan from a spec (copy assets/sample_database_migration.json)
python3 scripts/migration_planner.py --input migration_spec.json --format json -o migration_plan.json

# 2. Check schema/API compatibility — exits non-zero unless fully compatible (CI gate)
python3 scripts/compatibility_checker.py --before assets/database_schema_before.json --after assets/database_schema_after.json --type database --format json -o compatibility.json

# 3. Generate the rollback runbook from the plan
python3 scripts/rollback_generator.py --input migration_plan.json --format both -o rollback_runbook

Outputs chain: migration_plan.json (phases, risks, estimated_duration_hours) feeds step 3; compatibility.json reports overall_compatibility plus breaking_changes_count / potentially_breaking_count.

Gate: the migration is not approved until (a) compatibility_checker exits 0 (overall_compatibility: compatible) or every breaking/potentially-breaking item is explicitly accepted by the owner in writing, and (b) a rollback runbook exists for every phase in the plan. Re-run both checks after any schema revision.

Migration Patterns

Database Migrations

Schema Evolution Patterns

1. Expand-Contract Pattern

  • Expand: Add new columns/tables alongside existing schema
  • Dual Write: Application writes to both old and new schema
  • Migration: Backfill historical data to new schema
  • Contract: Remove old columns/tables after validation

2. Parallel Schema Pattern

  • Run new schema in parallel with existing schema
  • Use feature flags to route traffic between schemas
  • Validate data consistency between parallel systems
  • Cutover when confidence is high

3. Event Sourcing Migration

  • Capture all changes as events during migration window
  • Apply events to new schema for consistency
  • Enable replay capability for rollback scenarios
Data Migration Strategies

1. Bulk Data Migration

  • Snapshot Approach: Full data copy during maintenance window
  • Incremental Sync: Continuous data synchronization with change tracking
  • Stream Processing: Real-time data transformation pipelines

2. Dual-Write Pattern

  • Write to both source and target systems during migration
  • Implement compensation patterns for write failures
  • Use distributed transactions where consistency is critical

3. Change Data Capture (CDC)

  • Stream database changes to target system
  • Maintain eventual consistency during migration
  • Enable zero-downtime migrations for large datasets

Service Migrations

Strangler Fig Pattern

1. Intercept Requests: Route traffic through proxy/gateway 2. Gradually Replace: Implement new service functionality incrementally 3. Legacy Retirement: Remove old service components as new ones prove stable 4. Monitoring: Track performance and error rates throughout transition

graph TD
    A[Client Requests] --> B[API Gateway]
    B --> C{Route Decision}
    C -->|Legacy Path| D[Legacy Service]
    C -->|New Path| E[New Service]
    D --> F[Legacy Database]
    E --> G[New Database]
Parallel Run Pattern

1. Dual Execution: Run both old and new services simultaneously 2. Shadow Traffic: Route production traffic to both systems 3. Result Comparison: Compare outputs to validate correctness 4. Gradual Cutover: Shift traffic percentage based on confidence

Canary Deployment Pattern

1. Limited Rollout: Deploy new service to small percentage of users 2. Monitoring: Track key metrics (latency, errors, business KPIs) 3. Gradual Increase: Increase traffic percentage as confidence grows 4. Full Rollout: Complete migration once validation passes

Infrastructure Migrations

Cloud-to-Cloud Migration

1. Assessment Phase

  • Inventory existing resources and dependencies
  • Map services to target cloud equivalents
  • Identify vendor-specific features requiring refactoring

2. Pilot Migration

  • Migrate non-critical workloads first
  • Validate performance and cost models
  • Refine migration procedures

3. Production Migration

  • Use infrastructure as code for consistency
  • Implement cross-cloud networking during transition
  • Maintain disaster recovery capabilities
On-Premises to Cloud Migration

1. Lift and Shift

  • Minimal changes to existing applications
  • Quick migration with optimization later
  • Use cloud migration tools and services

2. Re-architecture

  • Redesign applications for cloud-native patterns
  • Adopt microservices, containers, and serverless
  • Implement cloud security and scaling practices

3. Hybrid Approach

  • Keep sensitive data on-premises
  • Migrate compute workloads to cloud
  • Implement secure connectivity between environments

Feature Flags for Migrations

Progressive Feature Rollout

# Example feature flag implementation
class MigrationFeatureFlag:
    def __init__(self, flag_name, rollout_percentage=0):
        self.flag_name = flag_name
        self.rollout_percentage = rollout_percentage
    
    def is_enabled_for_user(self, user_id):
        hash_value = hash(f"{self.flag_name}:{user_id}")
        return (hash_value % 100) < self.rollout_percentage
    
    def gradual_rollout(self, target_percentage, step_size=10):
        while self.rollout_percentage < target_percentage:
            self.rollout_percentage = min(
                self.rollout_percentage + step_size,
                target_percentage
            )
            yield self.rollout_percentage

Circuit Breaker Pattern

Implement automatic fallback to legacy systems when new systems show degraded performance:

class MigrationCircuitBreaker:
    def __init__(self, failure_threshold=5, timeout=60):
        self.failure_count = 0
        self.failure_threshold = failure_threshold
        self.timeout = timeout
        self.last_failure_time = None
        self.state = 'CLOSED'  # CLOSED, OPEN, HALF_OPEN
    
    def call_new_service(self, request):
        if self.state == 'OPEN':
            if self.should_attempt_reset():
                self.state = 'HALF_OPEN'
            else:
                return self.fallback_to_legacy(request)
        
        try:
            response = self.new_service.process(request)
            self.on_success()
            return response
        except Exception as e:
            self.on_failure()
            return self.fallback_to_legacy(request)

Data Validation and Reconciliation

Validation Strategies

1. Row Count Validation

  • Compare record counts between source and target
  • Account for soft deletes and filtered records
  • Implement threshold-based alerting

2. Checksums and Hashing

  • Generate checksums for critical data subsets
  • Compare hash values to detect data drift
  • Use sampling for large datasets

3. Business Logic Validation

  • Run critical business queries on both systems
  • Compare aggregate results (sums, counts, averages)
  • Validate derived data and calculations

Reconciliation Patterns

1. Delta Detection

   -- Example delta query for reconciliation
   SELECT 'missing_in_target' as issue_type, source_id
   FROM source_table s
   WHERE NOT EXISTS (
       SELECT 1 FROM target_table t 
       WHERE t.id = s.id
   )
   UNION ALL
   SELECT 'extra_in_target' as issue_type, target_id
   FROM target_table t
   WHERE NOT EXISTS (
       SELECT 1 FROM source_table s 
       WHERE s.id = t.id
   );

2. Automated Correction

  • Implement data repair scripts for common issues
  • Use idempotent operations for safe re-execution
  • Log all correction actions for audit trails

Rollback Strategies

Database Rollback

1. Schema Rollback

  • Maintain schema version control
  • Use backward-compatible migrations when possible
  • Keep rollback scripts for each migration step

2. Data Rollback

  • Point-in-time recovery using database backups
  • Transaction log replay for precise rollback points
  • Maintain data snapshots at migration checkpoints

Service Rollback

1. Blue-Green Deployment

  • Keep previous service version running during migration
  • Switch traffic back to blue environment if issues arise
  • Maintain parallel infrastructure during migration window

2. Rolling Rollback

  • Gradually shift traffic back to previous version
  • Monitor system health during rollback process
  • Implement automated rollback triggers

Infrastructure Rollback

1. Infrastructure as Code

  • Version control all infrastructure definitions
  • Maintain rollback terraform/CloudFormation templates
  • Test rollback procedures in staging environments

2. Data Persistence

  • Preserve data in original location during migration
  • Implement data sync back to original systems
  • Maintain backup strategies across both environments

Risk Assessment Framework

Risk Categories

1. Technical Risks

  • Data loss or corruption
  • Service downtime or degraded performance
  • Integration failures with dependent systems
  • Scalability issues under production load

2. Business Risks

  • Revenue impact from service disruption
  • Customer experience degradation
  • Compliance and regulatory concerns
  • Brand reputation impact

3. Operational Risks

  • Team knowledge gaps
  • Insufficient testing coverage
  • Inadequate monitoring and alerting
  • Communication breakdowns

Risk Mitigation Strategies

1. Technical Mitigations

  • Comprehensive testing (unit, integration, load, chaos)
  • Gradual rollout with automated rollback triggers
  • Data validation and reconciliation processes
  • Performance monitoring and alerting

2. Business Mitigations

  • Stakeholder communication plans
  • Business continuity procedures
  • Customer notification strategies
  • Revenue protection measures

3. Operational Mitigations

  • Team training and documentation
  • Runbook creation and testing
  • On-call rotation planning
  • Post-migration review processes

Migration Runbooks

Pre-Migration Checklist

  • [ ] Migration plan reviewed and approved
  • [ ] Rollback procedures tested and validated
  • [ ] Monitoring and alerting configured
  • [ ] Team roles and responsibilities defined
  • [ ] Stakeholder communication plan activated
  • [ ] Backup and recovery procedures verified
  • [ ] Test environment validation complete
  • [ ] Performance benchmarks established
  • [ ] Security review completed
  • [ ] Compliance requirements verified

During Migration

  • [ ] Execute migration phases in planned order
  • [ ] Monitor key performance indicators continuously
  • [ ] Validate data consistency at each checkpoint
  • [ ] Communicate progress to stakeholders
  • [ ] Document any deviations from plan
  • [ ] Execute rollback if success criteria not met
  • [ ] Coordinate with dependent teams
  • [ ] Maintain detailed execution logs

Post-Migration

  • [ ] Validate all success criteria met
  • [ ] Perform comprehensive system health checks
  • [ ] Execute data reconciliation procedures
  • [ ] Monitor system performance over 72 hours
  • [ ] Update documentation and runbooks
  • [ ] Decommission legacy systems (if applicable)
  • [ ] Conduct post-migration retrospective
  • [ ] Archive migration artifacts
  • [ ] Update disaster recovery procedures

Tools and Technologies

Migration Planning Tools

  • migration_planner.py: Automated migration plan generation
  • compatibility_checker.py: Schema and API compatibility analysis
  • rollback_generator.py: Comprehensive rollback procedure generation

Validation Tools

  • Database comparison utilities (schema and data)
  • API contract testing frameworks
  • Performance benchmarking tools
  • Data quality validation pipelines

Monitoring and Alerting

  • Real-time migration progress dashboards
  • Automated rollback trigger systems
  • Business metric monitoring
  • Stakeholder notification systems

Best Practices

Planning Phase

1. Start with Risk Assessment: Identify all potential failure modes before planning 2. Design for Rollback: Every migration step should have a tested rollback procedure 3. Validate in Staging: Execute full migration process in production-like environment 4. Plan for Gradual Rollout: Use feature flags and traffic routing for controlled migration

Execution Phase

1. Monitor Continuously: Track both technical and business metrics throughout 2. Communicate Proactively: Keep all stakeholders informed of progress and issues 3. Document Everything: Maintain detailed logs for post-migration analysis 4. Stay Flexible: Be prepared to adjust timeline based on real-world performance

Validation Phase

1. Automate Validation: Use automated tools for data consistency and performance checks 2. Business Logic Testing: Validate critical business processes end-to-end 3. Load Testing: Verify system performance under expected production load 4. Security Validation: Ensure security controls function properly in new environment

Integration with Development Lifecycle

CI/CD Integration

# Example migration pipeline stage
migration_validation:
  stage: test
  script:
    - python scripts/compatibility_checker.py --before=old_schema.json --after=new_schema.json
    - python scripts/migration_planner.py --config=migration_config.json --validate
  artifacts:
    reports:
      - compatibility_report.json
      - migration_plan.json

Infrastructure as Code

# Example Terraform for blue-green infrastructure
resource "aws_instance" "blue_environment" {
  count = var.migration_phase == "preparation" ? var.instance_count : 0
  # Blue environment configuration
}

resource "aws_instance" "green_environment" {
  count = var.migration_phase == "execution" ? var.instance_count : 0
  # Green environment configuration
}

This Migration Architect skill provides a comprehensive framework for planning, executing, and validating complex system migrations while minimizing business impact and technical risk. The combination of automated tools, proven patterns, and detailed procedures enables organizations to confidently undertake even the most complex migration projects.

Related skills

microsoftAzure DeploySafely execute production deployments of already-prepared applications to Microsoft Azure.478k1.3kmicrosoftAzure ValidateRun deep pre-deployment checks on Azure configuration, infrastructure definitions, RBAC roles, and managed identities before pushing to production.477k1.3kxixu-meGithub Actions DocsGet precise, docs-grounded answers about GitHub Actions workflows, syntax, security, and migration instead of relying on stale knowledge.275k72mattpocockSetup Pre CommitAutomatically run Prettier, type checking, and tests on every commit via Husky and lint-staged.161k188kvercel-labsDeploy To VercelSafely turn any local project into a live Vercel preview with one instruction.97.8k29.5kvercel-labsVercel Cli With TokensDeploy projects to Vercel from agents and scripts using token authentication instead of interactive browser login.73.4k29.5k

How it compares

Use migration-architect for cutover planning and rollback runbooks; use ORM migration framework docs when you only need incremental schema diffs in development.

FAQ

What scripts does migration-architect provide?

migration-architect provides migration_planner.py for automated migration plan generation and compatibility_checker.py for schema and API compatibility validation. Together they produce cutover plans, compatibility reports, and rollback strategies for production migrations.

When should developers use migration-architect?

Developers use migration-architect when moving databases or services without taking the product offline. The skill focuses on zero-downtime patterns, compatibility gates, and rollback runbooks during ship-phase migration work.

Is Migration Architect safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

DevOps & CI/CDinfradeploy
Browse by category
AI & AgentsFrontend & DesignBackend & DataDev ToolsAutomationTesting & ReviewSecurityMonitoring & CloudDocs & Planning
Design & frontend
Design systemsAnimation & motionAccessibility (a11y)CSS & TailwindUI designUXDesign to codeshadcn/uiLanding pagesBest design skills
Most searched skills
find-skillscavemanfrontend-designbrainstormingsystematic-debuggingstop-slopemil-design-engui-ux-pro-maxkarpathy-guidelinesweb-design-guidelinesreact-best-practicesgrill-meimprovemicrosoft-foundryagent-browser
Browse all listings
All agent skillsAll MCP serversAll marketplacesAll plugins

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.