aurora-to-tidb-migration

Migrate Aurora MySQL schemas and data to TiDB with validation.

2|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/pingcap-inc/TiShift --skill aurora-to-tidb-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aurora-to-tidb-migration
Source: https://github.com/pingcap-inc/TiShift/tree/main/aurora-to-tidb
Command: npx skills add https://github.com/pingcap-inc/TiShift --skill aurora-to-tidb-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating from Aurora MySQL to TiDB can be complex due to compatibility gaps, DDL transformation, and data-transfer challenges. This skill provides a structured, end-to-end workflow to assess TiDB compatibility, convert MySQL schemas for TiDB, load data, and validate results.

Core Features & Use Cases

  • Assess compatibility: analyze a source Aurora MySQL schema to identify blockers, required changes, and readiness for TiDB.
  • Convert schemas: generate TiDB-compatible DDL with proper data types, collations, and index handling.
  • Load and validate: plan data-transfer strategies and verify row counts and schema parity against the source.
  • Use Case: A team migrating an Aurora data warehouse to TiDB Cloud can run this skill to ensure a smooth transition with cost awareness.

Quick Start

Run the aurora-to-tidb migration skill against your Aurora MySQL source and TiDB target to begin the end-to-end migration workflow.

Frequently Asked Questions about aurora-to-tidb-migration

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

FAQPage Schema
How do I migrate Aurora MySQL to TiDB end-to-end?

To migrate Aurora MySQL to TiDB, you analyze source compatibility, convert schemas to TiDB-compatible DDL, load data, and validate row counts. This structured workflow ensures a smooth transition to TiDB Cloud or self-hosted deployments.

What compatibility issues block Aurora MySQL migration to TiDB?

Common Aurora MySQL to TiDB migration blockers involve DDL transformation gaps, data type mismatches, and collation differences. Analyzing the source schema identifies required changes and assesses TiDB readiness before data transfer.

Can I migrate Aurora MySQL to self-hosted TiDB or does it require TiDB Cloud?

You can migrate Aurora MySQL to both self-hosted TiDB and TiDB Cloud deployments. The migration workflow applies to either target environment, requiring network access to the source and MySQL clients to execute.

How do I validate data loading results after moving Aurora MySQL to TiDB?

To validate data loading from Aurora MySQL to TiDB, verify row counts and check schema parity against the source database. This validation phase confirms data transfer accuracy and structural consistency post-migration.

What is the best way to convert Aurora MySQL schemas for TiDB compatibility?

The best way to convert Aurora MySQL schemas for TiDB is to generate TiDB-compatible DDL with proper data types, collations, and index handling. This schema conversion step prevents structural errors during data loading.

Do I need network access to Aurora MySQL to run a TiDB migration assessment?

Yes, you need network access to the Aurora MySQL source and the TiDB target environment, plus the ability to run MySQL clients. AI-assisted analysis and cost evaluation are optional features during the assessment.