{ "schemaVersion": "1.0", "item": { "slug": "migration-architect", "name": "Migration Architect", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/alirezarezvani/migration-architect", "canonicalUrl": "https://clawhub.ai/alirezarezvani/migration-architect", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/migration-architect", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=migration-architect", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md", "assets/database_schema_after.json", "assets/database_schema_before.json", "assets/sample_database_migration.json", "assets/sample_service_migration.json" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/migration-architect" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/migration-architect", "agentPageUrl": "https://openagent3.xyz/skills/migration-architect/agent", "manifestUrl": "https://openagent3.xyz/skills/migration-architect/agent.json", "briefUrl": "https://openagent3.xyz/skills/migration-architect/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Migration Architect", "body": "Tier: POWERFUL\nCategory: Engineering - Migration Strategy\nPurpose: Zero-downtime migration planning, compatibility validation, and rollback strategy generation" }, { "title": "Overview", "body": "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." }, { "title": "1. Migration Strategy Planning", "body": "Phased Migration Planning: Break complex migrations into manageable phases with clear validation gates\nRisk Assessment: Identify potential failure points and mitigation strategies before execution\nTimeline Estimation: Generate realistic timelines based on migration complexity and resource constraints\nStakeholder Communication: Create communication templates and progress dashboards" }, { "title": "2. Compatibility Analysis", "body": "Schema Evolution: Analyze database schema changes for backward compatibility issues\nAPI Versioning: Detect breaking changes in REST/GraphQL APIs and microservice interfaces\nData Type Validation: Identify data format mismatches and conversion requirements\nConstraint Analysis: Validate referential integrity and business rule changes" }, { "title": "3. Rollback Strategy Generation", "body": "Automated Rollback Plans: Generate comprehensive rollback procedures for each migration phase\nData Recovery Scripts: Create point-in-time data restoration procedures\nService Rollback: Plan service version rollbacks with traffic management\nValidation Checkpoints: Define success criteria and rollback triggers" }, { "title": "Database Migrations", "body": "Schema Evolution Patterns\n\nExpand-Contract Pattern\n\nExpand: Add new columns/tables alongside existing schema\nDual Write: Application writes to both old and new schema\nMigration: Backfill historical data to new schema\nContract: Remove old columns/tables after validation\n\n\n\nParallel Schema Pattern\n\nRun new schema in parallel with existing schema\nUse feature flags to route traffic between schemas\nValidate data consistency between parallel systems\nCutover when confidence is high\n\n\n\nEvent Sourcing Migration\n\nCapture all changes as events during migration window\nApply events to new schema for consistency\nEnable replay capability for rollback scenarios\n\nData Migration Strategies\n\nBulk Data Migration\n\nSnapshot Approach: Full data copy during maintenance window\nIncremental Sync: Continuous data synchronization with change tracking\nStream Processing: Real-time data transformation pipelines\n\n\n\nDual-Write Pattern\n\nWrite to both source and target systems during migration\nImplement compensation patterns for write failures\nUse distributed transactions where consistency is critical\n\n\n\nChange Data Capture (CDC)\n\nStream database changes to target system\nMaintain eventual consistency during migration\nEnable zero-downtime migrations for large datasets" }, { "title": "Service Migrations", "body": "Strangler Fig Pattern\n\nIntercept Requests: Route traffic through proxy/gateway\nGradually Replace: Implement new service functionality incrementally\nLegacy Retirement: Remove old service components as new ones prove stable\nMonitoring: Track performance and error rates throughout transition\n\ngraph TD\n A[Client Requests] --> B[API Gateway]\n B --> C{Route Decision}\n C -->|Legacy Path| D[Legacy Service]\n C -->|New Path| E[New Service]\n D --> F[Legacy Database]\n E --> G[New Database]\n\nParallel Run Pattern\n\nDual Execution: Run both old and new services simultaneously\nShadow Traffic: Route production traffic to both systems\nResult Comparison: Compare outputs to validate correctness\nGradual Cutover: Shift traffic percentage based on confidence\n\nCanary Deployment Pattern\n\nLimited Rollout: Deploy new service to small percentage of users\nMonitoring: Track key metrics (latency, errors, business KPIs)\nGradual Increase: Increase traffic percentage as confidence grows\nFull Rollout: Complete migration once validation passes" }, { "title": "Infrastructure Migrations", "body": "Cloud-to-Cloud Migration\n\nAssessment Phase\n\nInventory existing resources and dependencies\nMap services to target cloud equivalents\nIdentify vendor-specific features requiring refactoring\n\n\n\nPilot Migration\n\nMigrate non-critical workloads first\nValidate performance and cost models\nRefine migration procedures\n\n\n\nProduction Migration\n\nUse infrastructure as code for consistency\nImplement cross-cloud networking during transition\nMaintain disaster recovery capabilities\n\nOn-Premises to Cloud Migration\n\nLift and Shift\n\nMinimal changes to existing applications\nQuick migration with optimization later\nUse cloud migration tools and services\n\n\n\nRe-architecture\n\nRedesign applications for cloud-native patterns\nAdopt microservices, containers, and serverless\nImplement cloud security and scaling practices\n\n\n\nHybrid Approach\n\nKeep sensitive data on-premises\nMigrate compute workloads to cloud\nImplement secure connectivity between environments" }, { "title": "Progressive Feature Rollout", "body": "# Example feature flag implementation\nclass MigrationFeatureFlag:\n def __init__(self, flag_name, rollout_percentage=0):\n self.flag_name = flag_name\n self.rollout_percentage = rollout_percentage\n \n def is_enabled_for_user(self, user_id):\n hash_value = hash(f\"{self.flag_name}:{user_id}\")\n return (hash_value % 100) < self.rollout_percentage\n \n def gradual_rollout(self, target_percentage, step_size=10):\n while self.rollout_percentage < target_percentage:\n self.rollout_percentage = min(\n self.rollout_percentage + step_size,\n target_percentage\n )\n yield self.rollout_percentage" }, { "title": "Circuit Breaker Pattern", "body": "Implement automatic fallback to legacy systems when new systems show degraded performance:\n\nclass MigrationCircuitBreaker:\n def __init__(self, failure_threshold=5, timeout=60):\n self.failure_count = 0\n self.failure_threshold = failure_threshold\n self.timeout = timeout\n self.last_failure_time = None\n self.state = 'CLOSED' # CLOSED, OPEN, HALF_OPEN\n \n def call_new_service(self, request):\n if self.state == 'OPEN':\n if self.should_attempt_reset():\n self.state = 'HALF_OPEN'\n else:\n return self.fallback_to_legacy(request)\n \n try:\n response = self.new_service.process(request)\n self.on_success()\n return response\n except Exception as e:\n self.on_failure()\n return self.fallback_to_legacy(request)" }, { "title": "Validation Strategies", "body": "Row Count Validation\n\nCompare record counts between source and target\nAccount for soft deletes and filtered records\nImplement threshold-based alerting\n\n\n\nChecksums and Hashing\n\nGenerate checksums for critical data subsets\nCompare hash values to detect data drift\nUse sampling for large datasets\n\n\n\nBusiness Logic Validation\n\nRun critical business queries on both systems\nCompare aggregate results (sums, counts, averages)\nValidate derived data and calculations" }, { "title": "Reconciliation Patterns", "body": "Delta Detection\n-- Example delta query for reconciliation\nSELECT 'missing_in_target' as issue_type, source_id\nFROM source_table s\nWHERE NOT EXISTS (\n SELECT 1 FROM target_table t \n WHERE t.id = s.id\n)\nUNION ALL\nSELECT 'extra_in_target' as issue_type, target_id\nFROM target_table t\nWHERE NOT EXISTS (\n SELECT 1 FROM source_table s \n WHERE s.id = t.id\n);\n\n\n\nAutomated Correction\n\nImplement data repair scripts for common issues\nUse idempotent operations for safe re-execution\nLog all correction actions for audit trails" }, { "title": "Database Rollback", "body": "Schema Rollback\n\nMaintain schema version control\nUse backward-compatible migrations when possible\nKeep rollback scripts for each migration step\n\n\n\nData Rollback\n\nPoint-in-time recovery using database backups\nTransaction log replay for precise rollback points\nMaintain data snapshots at migration checkpoints" }, { "title": "Service Rollback", "body": "Blue-Green Deployment\n\nKeep previous service version running during migration\nSwitch traffic back to blue environment if issues arise\nMaintain parallel infrastructure during migration window\n\n\n\nRolling Rollback\n\nGradually shift traffic back to previous version\nMonitor system health during rollback process\nImplement automated rollback triggers" }, { "title": "Infrastructure Rollback", "body": "Infrastructure as Code\n\nVersion control all infrastructure definitions\nMaintain rollback terraform/CloudFormation templates\nTest rollback procedures in staging environments\n\n\n\nData Persistence\n\nPreserve data in original location during migration\nImplement data sync back to original systems\nMaintain backup strategies across both environments" }, { "title": "Risk Categories", "body": "Technical Risks\n\nData loss or corruption\nService downtime or degraded performance\nIntegration failures with dependent systems\nScalability issues under production load\n\n\n\nBusiness Risks\n\nRevenue impact from service disruption\nCustomer experience degradation\nCompliance and regulatory concerns\nBrand reputation impact\n\n\n\nOperational Risks\n\nTeam knowledge gaps\nInsufficient testing coverage\nInadequate monitoring and alerting\nCommunication breakdowns" }, { "title": "Risk Mitigation Strategies", "body": "Technical Mitigations\n\nComprehensive testing (unit, integration, load, chaos)\nGradual rollout with automated rollback triggers\nData validation and reconciliation processes\nPerformance monitoring and alerting\n\n\n\nBusiness Mitigations\n\nStakeholder communication plans\nBusiness continuity procedures\nCustomer notification strategies\nRevenue protection measures\n\n\n\nOperational Mitigations\n\nTeam training and documentation\nRunbook creation and testing\nOn-call rotation planning\nPost-migration review processes" }, { "title": "Pre-Migration Checklist", "body": "Migration plan reviewed and approved\n Rollback procedures tested and validated\n Monitoring and alerting configured\n Team roles and responsibilities defined\n Stakeholder communication plan activated\n Backup and recovery procedures verified\n Test environment validation complete\n Performance benchmarks established\n Security review completed\n Compliance requirements verified" }, { "title": "During Migration", "body": "Execute migration phases in planned order\n Monitor key performance indicators continuously\n Validate data consistency at each checkpoint\n Communicate progress to stakeholders\n Document any deviations from plan\n Execute rollback if success criteria not met\n Coordinate with dependent teams\n Maintain detailed execution logs" }, { "title": "Post-Migration", "body": "Validate all success criteria met\n Perform comprehensive system health checks\n Execute data reconciliation procedures\n Monitor system performance over 72 hours\n Update documentation and runbooks\n Decommission legacy systems (if applicable)\n Conduct post-migration retrospective\n Archive migration artifacts\n Update disaster recovery procedures" }, { "title": "Executive Summary Template", "body": "Migration Status: [IN_PROGRESS | COMPLETED | ROLLED_BACK]\nStart Time: [YYYY-MM-DD HH:MM UTC]\nCurrent Phase: [X of Y]\nOverall Progress: [X%]\n\nKey Metrics:\n- System Availability: [X.XX%]\n- Data Migration Progress: [X.XX%]\n- Performance Impact: [+/-X%]\n- Issues Encountered: [X]\n\nNext Steps:\n1. [Action item 1]\n2. [Action item 2]\n\nRisk Assessment: [LOW | MEDIUM | HIGH]\nRollback Status: [AVAILABLE | NOT_AVAILABLE]" }, { "title": "Technical Team Update Template", "body": "Phase: [Phase Name] - [Status]\nDuration: [Started] - [Expected End]\n\nCompleted Tasks:\n✓ [Task 1]\n✓ [Task 2]\n\nIn Progress:\n🔄 [Task 3] - [X% complete]\n\nUpcoming:\n⏳ [Task 4] - [Expected start time]\n\nIssues:\n⚠️ [Issue description] - [Severity] - [ETA resolution]\n\nMetrics:\n- Migration Rate: [X records/minute]\n- Error Rate: [X.XX%]\n- System Load: [CPU/Memory/Disk]" }, { "title": "Technical Metrics", "body": "Migration Completion Rate: Percentage of data/services successfully migrated\nDowntime Duration: Total system unavailability during migration\nData Consistency Score: Percentage of data validation checks passing\nPerformance Delta: Performance change compared to baseline\nError Rate: Percentage of failed operations during migration" }, { "title": "Business Metrics", "body": "Customer Impact Score: Measure of customer experience degradation\nRevenue Protection: Percentage of revenue maintained during migration\nTime to Value: Duration from migration start to business value realization\nStakeholder Satisfaction: Post-migration stakeholder feedback scores" }, { "title": "Operational Metrics", "body": "Plan Adherence: Percentage of migration executed according to plan\nIssue Resolution Time: Average time to resolve migration issues\nTeam Efficiency: Resource utilization and productivity metrics\nKnowledge Transfer Score: Team readiness for post-migration operations" }, { "title": "Migration Planning Tools", "body": "migration_planner.py: Automated migration plan generation\ncompatibility_checker.py: Schema and API compatibility analysis\nrollback_generator.py: Comprehensive rollback procedure generation" }, { "title": "Validation Tools", "body": "Database comparison utilities (schema and data)\nAPI contract testing frameworks\nPerformance benchmarking tools\nData quality validation pipelines" }, { "title": "Monitoring and Alerting", "body": "Real-time migration progress dashboards\nAutomated rollback trigger systems\nBusiness metric monitoring\nStakeholder notification systems" }, { "title": "Planning Phase", "body": "Start with Risk Assessment: Identify all potential failure modes before planning\nDesign for Rollback: Every migration step should have a tested rollback procedure\nValidate in Staging: Execute full migration process in production-like environment\nPlan for Gradual Rollout: Use feature flags and traffic routing for controlled migration" }, { "title": "Execution Phase", "body": "Monitor Continuously: Track both technical and business metrics throughout\nCommunicate Proactively: Keep all stakeholders informed of progress and issues\nDocument Everything: Maintain detailed logs for post-migration analysis\nStay Flexible: Be prepared to adjust timeline based on real-world performance" }, { "title": "Validation Phase", "body": "Automate Validation: Use automated tools for data consistency and performance checks\nBusiness Logic Testing: Validate critical business processes end-to-end\nLoad Testing: Verify system performance under expected production load\nSecurity Validation: Ensure security controls function properly in new environment" }, { "title": "CI/CD Integration", "body": "# Example migration pipeline stage\nmigration_validation:\n stage: test\n script:\n - python scripts/compatibility_checker.py --before=old_schema.json --after=new_schema.json\n - python scripts/migration_planner.py --config=migration_config.json --validate\n artifacts:\n reports:\n - compatibility_report.json\n - migration_plan.json" }, { "title": "Infrastructure as Code", "body": "# Example Terraform for blue-green infrastructure\nresource \"aws_instance\" \"blue_environment\" {\n count = var.migration_phase == \"preparation\" ? var.instance_count : 0\n # Blue environment configuration\n}\n\nresource \"aws_instance\" \"green_environment\" {\n count = var.migration_phase == \"execution\" ? var.instance_count : 0\n # Green environment configuration\n}\n\nThis 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." } ], "body": "Migration Architect\n\nTier: POWERFUL\nCategory: Engineering - Migration Strategy\nPurpose: Zero-downtime migration planning, compatibility validation, and rollback strategy generation\n\nOverview\n\nThe 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.\n\nCore Capabilities\n1. Migration Strategy Planning\nPhased Migration Planning: Break complex migrations into manageable phases with clear validation gates\nRisk Assessment: Identify potential failure points and mitigation strategies before execution\nTimeline Estimation: Generate realistic timelines based on migration complexity and resource constraints\nStakeholder Communication: Create communication templates and progress dashboards\n2. Compatibility Analysis\nSchema Evolution: Analyze database schema changes for backward compatibility issues\nAPI Versioning: Detect breaking changes in REST/GraphQL APIs and microservice interfaces\nData Type Validation: Identify data format mismatches and conversion requirements\nConstraint Analysis: Validate referential integrity and business rule changes\n3. Rollback Strategy Generation\nAutomated Rollback Plans: Generate comprehensive rollback procedures for each migration phase\nData Recovery Scripts: Create point-in-time data restoration procedures\nService Rollback: Plan service version rollbacks with traffic management\nValidation Checkpoints: Define success criteria and rollback triggers\nMigration Patterns\nDatabase Migrations\nSchema Evolution Patterns\n\nExpand-Contract Pattern\n\nExpand: Add new columns/tables alongside existing schema\nDual Write: Application writes to both old and new schema\nMigration: Backfill historical data to new schema\nContract: Remove old columns/tables after validation\n\nParallel Schema Pattern\n\nRun new schema in parallel with existing schema\nUse feature flags to route traffic between schemas\nValidate data consistency between parallel systems\nCutover when confidence is high\n\nEvent Sourcing Migration\n\nCapture all changes as events during migration window\nApply events to new schema for consistency\nEnable replay capability for rollback scenarios\nData Migration Strategies\n\nBulk Data Migration\n\nSnapshot Approach: Full data copy during maintenance window\nIncremental Sync: Continuous data synchronization with change tracking\nStream Processing: Real-time data transformation pipelines\n\nDual-Write Pattern\n\nWrite to both source and target systems during migration\nImplement compensation patterns for write failures\nUse distributed transactions where consistency is critical\n\nChange Data Capture (CDC)\n\nStream database changes to target system\nMaintain eventual consistency during migration\nEnable zero-downtime migrations for large datasets\nService Migrations\nStrangler Fig Pattern\nIntercept Requests: Route traffic through proxy/gateway\nGradually Replace: Implement new service functionality incrementally\nLegacy Retirement: Remove old service components as new ones prove stable\nMonitoring: Track performance and error rates throughout transition\ngraph TD\n A[Client Requests] --> B[API Gateway]\n B --> C{Route Decision}\n C -->|Legacy Path| D[Legacy Service]\n C -->|New Path| E[New Service]\n D --> F[Legacy Database]\n E --> G[New Database]\n\nParallel Run Pattern\nDual Execution: Run both old and new services simultaneously\nShadow Traffic: Route production traffic to both systems\nResult Comparison: Compare outputs to validate correctness\nGradual Cutover: Shift traffic percentage based on confidence\nCanary Deployment Pattern\nLimited Rollout: Deploy new service to small percentage of users\nMonitoring: Track key metrics (latency, errors, business KPIs)\nGradual Increase: Increase traffic percentage as confidence grows\nFull Rollout: Complete migration once validation passes\nInfrastructure Migrations\nCloud-to-Cloud Migration\n\nAssessment Phase\n\nInventory existing resources and dependencies\nMap services to target cloud equivalents\nIdentify vendor-specific features requiring refactoring\n\nPilot Migration\n\nMigrate non-critical workloads first\nValidate performance and cost models\nRefine migration procedures\n\nProduction Migration\n\nUse infrastructure as code for consistency\nImplement cross-cloud networking during transition\nMaintain disaster recovery capabilities\nOn-Premises to Cloud Migration\n\nLift and Shift\n\nMinimal changes to existing applications\nQuick migration with optimization later\nUse cloud migration tools and services\n\nRe-architecture\n\nRedesign applications for cloud-native patterns\nAdopt microservices, containers, and serverless\nImplement cloud security and scaling practices\n\nHybrid Approach\n\nKeep sensitive data on-premises\nMigrate compute workloads to cloud\nImplement secure connectivity between environments\nFeature Flags for Migrations\nProgressive Feature Rollout\n# Example feature flag implementation\nclass MigrationFeatureFlag:\n def __init__(self, flag_name, rollout_percentage=0):\n self.flag_name = flag_name\n self.rollout_percentage = rollout_percentage\n \n def is_enabled_for_user(self, user_id):\n hash_value = hash(f\"{self.flag_name}:{user_id}\")\n return (hash_value % 100) < self.rollout_percentage\n \n def gradual_rollout(self, target_percentage, step_size=10):\n while self.rollout_percentage < target_percentage:\n self.rollout_percentage = min(\n self.rollout_percentage + step_size,\n target_percentage\n )\n yield self.rollout_percentage\n\nCircuit Breaker Pattern\n\nImplement automatic fallback to legacy systems when new systems show degraded performance:\n\nclass MigrationCircuitBreaker:\n def __init__(self, failure_threshold=5, timeout=60):\n self.failure_count = 0\n self.failure_threshold = failure_threshold\n self.timeout = timeout\n self.last_failure_time = None\n self.state = 'CLOSED' # CLOSED, OPEN, HALF_OPEN\n \n def call_new_service(self, request):\n if self.state == 'OPEN':\n if self.should_attempt_reset():\n self.state = 'HALF_OPEN'\n else:\n return self.fallback_to_legacy(request)\n \n try:\n response = self.new_service.process(request)\n self.on_success()\n return response\n except Exception as e:\n self.on_failure()\n return self.fallback_to_legacy(request)\n\nData Validation and Reconciliation\nValidation Strategies\n\nRow Count Validation\n\nCompare record counts between source and target\nAccount for soft deletes and filtered records\nImplement threshold-based alerting\n\nChecksums and Hashing\n\nGenerate checksums for critical data subsets\nCompare hash values to detect data drift\nUse sampling for large datasets\n\nBusiness Logic Validation\n\nRun critical business queries on both systems\nCompare aggregate results (sums, counts, averages)\nValidate derived data and calculations\nReconciliation Patterns\n\nDelta Detection\n\n-- Example delta query for reconciliation\nSELECT 'missing_in_target' as issue_type, source_id\nFROM source_table s\nWHERE NOT EXISTS (\n SELECT 1 FROM target_table t \n WHERE t.id = s.id\n)\nUNION ALL\nSELECT 'extra_in_target' as issue_type, target_id\nFROM target_table t\nWHERE NOT EXISTS (\n SELECT 1 FROM source_table s \n WHERE s.id = t.id\n);\n\n\nAutomated Correction\n\nImplement data repair scripts for common issues\nUse idempotent operations for safe re-execution\nLog all correction actions for audit trails\nRollback Strategies\nDatabase Rollback\n\nSchema Rollback\n\nMaintain schema version control\nUse backward-compatible migrations when possible\nKeep rollback scripts for each migration step\n\nData Rollback\n\nPoint-in-time recovery using database backups\nTransaction log replay for precise rollback points\nMaintain data snapshots at migration checkpoints\nService Rollback\n\nBlue-Green Deployment\n\nKeep previous service version running during migration\nSwitch traffic back to blue environment if issues arise\nMaintain parallel infrastructure during migration window\n\nRolling Rollback\n\nGradually shift traffic back to previous version\nMonitor system health during rollback process\nImplement automated rollback triggers\nInfrastructure Rollback\n\nInfrastructure as Code\n\nVersion control all infrastructure definitions\nMaintain rollback terraform/CloudFormation templates\nTest rollback procedures in staging environments\n\nData Persistence\n\nPreserve data in original location during migration\nImplement data sync back to original systems\nMaintain backup strategies across both environments\nRisk Assessment Framework\nRisk Categories\n\nTechnical Risks\n\nData loss or corruption\nService downtime or degraded performance\nIntegration failures with dependent systems\nScalability issues under production load\n\nBusiness Risks\n\nRevenue impact from service disruption\nCustomer experience degradation\nCompliance and regulatory concerns\nBrand reputation impact\n\nOperational Risks\n\nTeam knowledge gaps\nInsufficient testing coverage\nInadequate monitoring and alerting\nCommunication breakdowns\nRisk Mitigation Strategies\n\nTechnical Mitigations\n\nComprehensive testing (unit, integration, load, chaos)\nGradual rollout with automated rollback triggers\nData validation and reconciliation processes\nPerformance monitoring and alerting\n\nBusiness Mitigations\n\nStakeholder communication plans\nBusiness continuity procedures\nCustomer notification strategies\nRevenue protection measures\n\nOperational Mitigations\n\nTeam training and documentation\nRunbook creation and testing\nOn-call rotation planning\nPost-migration review processes\nMigration Runbooks\nPre-Migration Checklist\n Migration plan reviewed and approved\n Rollback procedures tested and validated\n Monitoring and alerting configured\n Team roles and responsibilities defined\n Stakeholder communication plan activated\n Backup and recovery procedures verified\n Test environment validation complete\n Performance benchmarks established\n Security review completed\n Compliance requirements verified\nDuring Migration\n Execute migration phases in planned order\n Monitor key performance indicators continuously\n Validate data consistency at each checkpoint\n Communicate progress to stakeholders\n Document any deviations from plan\n Execute rollback if success criteria not met\n Coordinate with dependent teams\n Maintain detailed execution logs\nPost-Migration\n Validate all success criteria met\n Perform comprehensive system health checks\n Execute data reconciliation procedures\n Monitor system performance over 72 hours\n Update documentation and runbooks\n Decommission legacy systems (if applicable)\n Conduct post-migration retrospective\n Archive migration artifacts\n Update disaster recovery procedures\nCommunication Templates\nExecutive Summary Template\nMigration Status: [IN_PROGRESS | COMPLETED | ROLLED_BACK]\nStart Time: [YYYY-MM-DD HH:MM UTC]\nCurrent Phase: [X of Y]\nOverall Progress: [X%]\n\nKey Metrics:\n- System Availability: [X.XX%]\n- Data Migration Progress: [X.XX%]\n- Performance Impact: [+/-X%]\n- Issues Encountered: [X]\n\nNext Steps:\n1. [Action item 1]\n2. [Action item 2]\n\nRisk Assessment: [LOW | MEDIUM | HIGH]\nRollback Status: [AVAILABLE | NOT_AVAILABLE]\n\nTechnical Team Update Template\nPhase: [Phase Name] - [Status]\nDuration: [Started] - [Expected End]\n\nCompleted Tasks:\n✓ [Task 1]\n✓ [Task 2]\n\nIn Progress:\n🔄 [Task 3] - [X% complete]\n\nUpcoming:\n⏳ [Task 4] - [Expected start time]\n\nIssues:\n⚠️ [Issue description] - [Severity] - [ETA resolution]\n\nMetrics:\n- Migration Rate: [X records/minute]\n- Error Rate: [X.XX%]\n- System Load: [CPU/Memory/Disk]\n\nSuccess Metrics\nTechnical Metrics\nMigration Completion Rate: Percentage of data/services successfully migrated\nDowntime Duration: Total system unavailability during migration\nData Consistency Score: Percentage of data validation checks passing\nPerformance Delta: Performance change compared to baseline\nError Rate: Percentage of failed operations during migration\nBusiness Metrics\nCustomer Impact Score: Measure of customer experience degradation\nRevenue Protection: Percentage of revenue maintained during migration\nTime to Value: Duration from migration start to business value realization\nStakeholder Satisfaction: Post-migration stakeholder feedback scores\nOperational Metrics\nPlan Adherence: Percentage of migration executed according to plan\nIssue Resolution Time: Average time to resolve migration issues\nTeam Efficiency: Resource utilization and productivity metrics\nKnowledge Transfer Score: Team readiness for post-migration operations\nTools and Technologies\nMigration Planning Tools\nmigration_planner.py: Automated migration plan generation\ncompatibility_checker.py: Schema and API compatibility analysis\nrollback_generator.py: Comprehensive rollback procedure generation\nValidation Tools\nDatabase comparison utilities (schema and data)\nAPI contract testing frameworks\nPerformance benchmarking tools\nData quality validation pipelines\nMonitoring and Alerting\nReal-time migration progress dashboards\nAutomated rollback trigger systems\nBusiness metric monitoring\nStakeholder notification systems\nBest Practices\nPlanning Phase\nStart with Risk Assessment: Identify all potential failure modes before planning\nDesign for Rollback: Every migration step should have a tested rollback procedure\nValidate in Staging: Execute full migration process in production-like environment\nPlan for Gradual Rollout: Use feature flags and traffic routing for controlled migration\nExecution Phase\nMonitor Continuously: Track both technical and business metrics throughout\nCommunicate Proactively: Keep all stakeholders informed of progress and issues\nDocument Everything: Maintain detailed logs for post-migration analysis\nStay Flexible: Be prepared to adjust timeline based on real-world performance\nValidation Phase\nAutomate Validation: Use automated tools for data consistency and performance checks\nBusiness Logic Testing: Validate critical business processes end-to-end\nLoad Testing: Verify system performance under expected production load\nSecurity Validation: Ensure security controls function properly in new environment\nIntegration with Development Lifecycle\nCI/CD Integration\n# Example migration pipeline stage\nmigration_validation:\n stage: test\n script:\n - python scripts/compatibility_checker.py --before=old_schema.json --after=new_schema.json\n - python scripts/migration_planner.py --config=migration_config.json --validate\n artifacts:\n reports:\n - compatibility_report.json\n - migration_plan.json\n\nInfrastructure as Code\n# Example Terraform for blue-green infrastructure\nresource \"aws_instance\" \"blue_environment\" {\n count = var.migration_phase == \"preparation\" ? var.instance_count : 0\n # Blue environment configuration\n}\n\nresource \"aws_instance\" \"green_environment\" {\n count = var.migration_phase == \"execution\" ? var.instance_count : 0\n # Green environment configuration\n}\n\n\nThis 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." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/alirezarezvani/migration-architect", "publisherUrl": "https://clawhub.ai/alirezarezvani/migration-architect", "owner": "alirezarezvani", "version": "2.1.1", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/migration-architect", "downloadUrl": "https://openagent3.xyz/downloads/migration-architect", "agentUrl": "https://openagent3.xyz/skills/migration-architect/agent", "manifestUrl": "https://openagent3.xyz/skills/migration-architect/agent.json", "briefUrl": "https://openagent3.xyz/skills/migration-architect/agent.md" } }