Agent skill · software engineering · onewave-ai
database-migrator
Migrates databases between providers (Postgres, MySQL, Supabase, PlanetScale, MongoDB). Reads source schema, generates migration scripts, handles data type mapping, foreign keys, indexes, triggers, stored procedures. Validates migration with row counts and checksums. Generates migration-plan.md with step-by-step execution guide, rollback procedures, estimated downtime.
Why this skill is useful
Adds executable migration scripts and a comprehensive migration plan that the AI cannot generate from general knowledge alone.
What it needs
Requires bash, grep installed locally. About 3k tokens when loaded. Last updated 2026-07-15. 242 stars on the source repository.
What this skill does
Database Migrator Move schemas, data, and logic between database providers. This is a cross-provider migration engine, not a schema designer: it handles data type incompatibilities, provider-specific SQL dialects, foreign key ordering, sequence and auto-increment translation, trigger rewrites, and stored procedure conversion. It validates with row counts and checksums and produces an auditable migration-plan.md. Contents references/schema-discovery.md -- Extraction queries for relational, MongoDB, Supabase, and PlanetScale sources. references/type-mapping.md -- Data type maps (PG/MySQL/Mongo) and SQL function translation. references/script-generation.md -- DDL, sequence, trigger, procedure, and view translation. references/data-migration.md -- Export, transform, and import commands per provider. references/validation.md -- Row count, checksum, FK integrity, index, and spot-check queries. references/rollback-and-downtime.md -- Rollback scripts, backup/restore, downtime estimation. references/migration-plan-template.md -- Full migration-plan.md output template. references/edge-cases.md -- Large tables, lossy mappings, document flattening, multi-schema, quality checklist. Supported Paths and Complexity Supported source/target pairs: PostgreSQL, MySQL, Supabase (Postgres), PlanetScale (MySQL), and MongoDB, in any direction. Low: Same underlying engine (e.g., Postgres to Supabase). Mostly connection and permission changes. Medium: Same paradigm, different dialect (e.g., Postgres to MySQL). Requires type mapping and dialect translation. Medium-High: Different dialect plus provider constraints (e.g., PlanetScale has no database-level foreign keys). High: Paradigm shift (e.g., relational to document). Requires schema redesign, not just translation. When to Use Moving a production database from one provider to another. Migrating between self-hosted and managed services. Replicating a schema across providers for multi-cloud or disaster recovery. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills onewave-ai/database-migrator