← Back to Skills Marketplace
1kalin

Data Migration Planner

by 1kalin · GitHub ↗ · v1.0.0
cross-platform ✓ Security Clean
669
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install afrexai-data-migration
Description
Plans and documents detailed data migrations, including schema mapping, ETL pipeline design, validation tests, rollback strategies, and runbook creation.
README (SKILL.md)

Data Migration Planner

Plan, execute, and validate data migrations between systems. Covers schema mapping, ETL pipeline design, rollback strategies, and post-migration validation.

What It Does

Given source and target system details, this skill:

  1. Maps source → target schemas with field-level transformation rules
  2. Generates an ETL pipeline plan with staging, transform, and load phases
  3. Creates validation queries (row counts, checksum, referential integrity)
  4. Builds a rollback plan with point-of-no-return criteria
  5. Produces a migration runbook with go/no-go gates

Usage

Tell your agent:

  • "Plan a migration from Salesforce to HubSpot CRM"
  • "Create a data migration runbook for moving from MySQL to PostgreSQL"
  • "Map our legacy ERP data to the new system schema"

Migration Framework

Phase 1: Discovery

  • Inventory all source tables/objects and record counts
  • Document data types, constraints, and relationships
  • Identify data quality issues (nulls, duplicates, orphans)
  • Map business rules that affect data interpretation

Phase 2: Schema Mapping

For each source entity, document:

Source Field Type Target Field Type Transform Notes
(field) (type) (field) (type) (rule) (edge cases)

Phase 3: ETL Pipeline

Extract → Stage (raw) → Clean → Transform → Validate → Load → Verify
  • Extract: Full vs incremental, API vs direct DB, rate limits
  • Stage: Raw landing zone, no transforms, audit trail
  • Clean: Dedup, null handling, encoding fixes
  • Transform: Type conversions, lookups, calculated fields
  • Validate: Pre-load checks (counts, checksums, business rules)
  • Load: Batch size, parallelism, error handling
  • Verify: Post-load reconciliation

Phase 4: Validation

  • Row count match (source vs target, per table)
  • Checksum validation on key columns
  • Referential integrity checks
  • Business rule validation (e.g., all active accounts migrated)
  • User acceptance sampling (random 5% manual review)

Phase 5: Cutover

  • Go/no-go criteria checklist
  • Point-of-no-return definition
  • Rollback procedure and time estimate
  • Communication plan (users, stakeholders)
  • Parallel run period (if applicable)

Risk Factors

  • Data volume: >10M rows = batch strategy required
  • Downtime window: Zero-downtime needs CDC/dual-write
  • Data quality: Garbage in = garbage out. Clean BEFORE migrating
  • Dependencies: Other systems reading from source during migration
  • Compliance: GDPR/HIPAA data handling during transit

Output Format

Deliver a migration runbook as structured markdown with:

  1. Executive summary (what, why, when, risk level)
  2. Schema mapping tables
  3. ETL pipeline specification
  4. Validation test suite
  5. Cutover runbook with rollback
  6. Timeline with milestones

Cost Estimation

Typical migration costs by complexity:

  • Simple (1-5 tables, \x3C1M rows): $5K-$15K or 1-2 weeks internal
  • Medium (10-50 tables, 1-10M rows): $25K-$75K or 1-2 months
  • Complex (50+ tables, 10M+ rows, multiple systems): $100K-$500K or 3-6 months

Built by AfrexAI — AI Context Packs for business automation.

Calculate your AI automation ROI: Revenue Calculator

Usage Guidance
This skill appears coherent and low-risk because it is instruction-only and does not request credentials or install code. Before using it in production: 1) Avoid pasting live production credentials into any agent UI unless you trust the agent runtime and have least-privilege credentials (use read-only, scoped accounts). 2) Prefer running discovery on anonymized or copy datasets when possible; redact PII/HIPAA-sensitive fields. 3) Confirm any data access the agent requests goes only to the stated source/target systems and not to external endpoints. 4) Use this skill for planning and runbooks, but implement actual migration steps in controlled tooling and monitored environments. If you need higher assurance, ask the publisher for details on how the agent uses collected data and how to safely provide credentials.
Capability Analysis
Type: OpenClaw Skill Name: afrexai-data-migration Version: 1.0.0 The skill bundle is designed to help an AI agent plan data migrations. All files (SKILL.md, README.md, _meta.json) contain only descriptive text, planning frameworks, and marketing links. There is no executable code, no instructions for the AI agent to perform malicious actions (e.g., data exfiltration, unauthorized system access, persistence), and no evidence of prompt injection attempts aimed at subverting the agent's intended behavior. The external links are for marketing purposes and do not instruct the agent to interact with them maliciously.
Capability Assessment
Purpose & Capability
The SKILL.md describes planning, schema mapping, ETL design, validation, and cutover runbooks which matches the 'Data Migration Planner' name. The skill requires no environment variables, binaries, or installs, which is proportionate for a planning/consulting tool.
Instruction Scope
Instructions are limited to producing migration plans, templates, and checklists. They do instruct the agent to 'inventory' source objects and record counts given source/target details — which implies the agent (or user) will provide or use data/system access. The SKILL.md does not instruct any explicit data collection, file reads, or transmission to external endpoints, but it also lacks explicit guidance about handling credentials, redacting sensitive data, or avoiding exfiltration. This is reasonable for a planning skill but worth noting for operational safety.
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be written to disk or downloaded during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no unexplained or disproportionate credential requests.
Persistence & Privilege
Default privileges are used (always: false, model invocation enabled). The skill does not request permanent presence or system-level changes.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install afrexai-data-migration
  3. After installation, invoke the skill by name or use /afrexai-data-migration
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of Data Migration Planner skill. - Supports schema mapping, ETL pipeline planning, and validation test creation for migrations between systems. - Generates migration runbooks covering executive summary, schema mapping, ETL steps, validation, and rollback. - Outlines best practices and risk considerations for data migration projects. - Provides usage instructions and example prompts for planning various data migrations.
Metadata
Slug afrexai-data-migration
Version 1.0.0
License
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Data Migration Planner?

Plans and documents detailed data migrations, including schema mapping, ETL pipeline design, validation tests, rollback strategies, and runbook creation. It is an AI Agent Skill for Claude Code / OpenClaw, with 669 downloads so far.

How do I install Data Migration Planner?

Run "/install afrexai-data-migration" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Data Migration Planner free?

Yes, Data Migration Planner is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Data Migration Planner support?

Data Migration Planner is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Data Migration Planner?

It is built and maintained by 1kalin (@1kalin); the current version is v1.0.0.

💬 Comments