database-migration
Migrate data from MySQL to MongoDB for PayBille v2. Use when transforming schema, validating data integrity, or planning migration strategy.
Works with
--- name: database-migration description: Migrate data from MySQL to MongoDB for PayBille v2. Use when transforming schema, validating data integrity, or planning migration strategy. license: MIT --- # MySQL to MongoDB Migration ## When to Use - Planning data migration from MySQL - Transforming table data to documents - Validating migrated data - Writing migration scripts - Troubleshooting data inconsistencies ## Procedure ### 1. Analyze Current MySQL Schema - Document tables and relationships - Understand foreign keys and constraints - Identify denormalization opportunities ### 2. Design MongoDB Documents - Plan document structure - Decide embedding vs referencing - Define indexes ### 3. Write Migration Script Use [helper script](./assets/migration-helper.ts) to load and transform data. ### 4. Validate Data Use [validation script](./assets/validation-script.ts) to verify integrity. ### 5. For Each Table 1. Transform structure 2. Load into MongoDB 3. Validate count and sample records 4. Index MongoDB collection ## Best Practices - Backup MySQL before migration - Migrate in batches for large tables - Validate row counts and checksums - Test with sample data first - Enable MongoDB validation rules ## References See [MySQL to MongoDB Guide](./references/mysql-to-mongodb-guide.md) for mapping patterns.
More Database skills
azure-upgrade
microsoft/azure-skills
Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-database-setup
prisma/skills
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
