Master database schema and data migrations across ORMs (Sequelize, TypeORM, Prisma), including rollback strategies and zero-downtime deployments.

Database Migration Master database schema and data migrations across ORMs (Sequelize, TypeORM, Prisma), including rollback strategies and zero downtime deployments. Do not use this skill when The task is unrelated to database migration You need a different domain or tool outside this scope Instructions Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification. If detailed examples are required, open resources/implementation playbook.md . Use this skill when Migrating between different ORMs Performing schema transformations Moving data between databases Implementing rollback procedures Zero downtime deployments Database version upgrades Data model refactoring ORM Migrations Sequelize Migrations TypeORM Migrations Prisma Migrations Schema Transformations Adding Columns with Defaults Renaming Columns (Zero Downtime) Changing Column Types Data Transformations Complex Data Migration Rollback Strategies Transaction Based Migrations Checkpoint Based Rollback Zero Downtime Migrations Blue Green Deployment Strategy Cross Database Migrations PostgreSQL to MySQL Resources references/orm switching.md : ORM migration guides references/schema migration.md : Schema transformation patterns references/data transformation.md : Data migration scripts references/rollback strategies.md : Rollback procedures assets/schema migration template.sql : SQL migration templates assets/data migration script.py : Data migration utilities scripts/test migration.sh : Migration testing script Best Practices 1. Always Provide Rollback : Every up() needs a down() 2. Test Migrations : Test on staging first 3. Use Transactions : Atomic migrations when possible 4. Backup First : Always backup before migration 5. Small Changes : Break into small, incremental steps 6. Monitor : Watch for errors during deployment 7. Document : Explain why and how 8. Idempotent : Migrations should be rerunnable Common Pitfalls Not testing rollback procedures Making breaking changes without downtime strategy Forgetting to handle NULL values Not considering index performance Ignoring foreign key constraints Migrating too much data at once Limitations Use this skill only when the task clearly matches the scope described above. Do not treat the output as a substitute for environment specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

database-migration