data-migration

Migrate tables between heterogeneous database engines with schema inspection and reconciliation.

1.5k|222|Updated Jul 4, 2025
One-click install
npx skills add https://github.com/Datus-ai/Datus-agent --skill data-migration-datus-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-migration
Source: https://github.com/Datus-ai/Datus-agent/tree/main/datus/resources/skills/data-migration
Command: npx skills add https://github.com/Datus-ai/Datus-agent --skill data-migration-datus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the complex, error-prone manual work of migrating data between different database engines, removing the need for manual type mapping, dialect-specific DDL adjustments, and time-consuming post-migration reconciliation.

Core Features & Use Cases

  • End-to-end migration lifecycle: Handles full cross-database table migration from source inspection to final reconciliation for any source/target database pair.
  • Automated type mapping: Uses adapter Mixin hints to correctly map source column types to target dialect requirements, preventing data type mismatches and data loss.
  • Built-in validation and checks: Includes DDL validation, transfer integrity verification, and optional deep audit checks to ensure migrated data is accurate and complete.
  • Use case: For example, if you need to move a 10M row customer transactions table from MySQL to StarRocks, this Skill automatically generates the correct StarRocks DDL, transfers all rows, and verifies the row count matches to confirm a successful migration.

Quick Start

Use the data-migration skill to move the 'customer_orders' table from your configured PostgreSQL source database to the ClickHouse target database and confirm the migration completed successfully.

Frequently Asked Questions about data-migration

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

FAQPage Schema
How do I migrate data between heterogeneous database engines with incompatible schemas?

Cross-database data migration is handled by inspecting the source schema, generating target DDL, transferring bulk data, and running post-migration reconciliation. This process applies automated type mapping to correctly convert source column types to target dialect requirements, preventing data loss.

What is the best way to handle cross-database type mapping to prevent data type mismatches?

Cross-database type mapping is automated using adapter Mixin hints to correctly map source column types to target dialect requirements. This mechanism prevents data type mismatches and data loss during heterogeneous database transfers without requiring manual DDL adjustments.

How do I transfer a large table from MySQL to StarRocks and verify the row count matches?

Table transfer from MySQL to StarRocks is executed by automatically generating the correct StarRocks DDL, transferring all rows, and verifying the row count matches. This end-to-end workflow includes built-in transfer integrity verification to confirm a successful migration.

Does this data transfer workflow include post-migration reconciliation checks?

Post-migration reconciliation is included as a core part of the end-to-end cross-database table migration lifecycle. It provides configurable reconciliation checks and optional deep audit checks to verify transfer integrity and ensure migrated data is accurate and complete.

Why does DDL validation matter when transferring data across different SQL dialects?

DDL validation is necessary because incompatible SQL dialects require specific schema adjustments before data transfer. Built-in validation checks ensure the generated target DDL is structurally correct, preventing transfer errors and ensuring reliable data loading across heterogeneous database engines.