convex-migrations

Evolve your Convex database schema safely with patterns for adding fields, backfilling data, removing deprecated fields, and maintaining zero-downtime deployments. Before implementing, do not assume; fetch the latest documentation: Convex handles schema evolution differently than traditional databases: Start with optional fields, then backfill: Remove field usage before removing from schema: Renaming requires copying data to new field, then removing old: Add indexes before using them in queries: Type changes require careful migration: Create a reusable migration system: - Primary: - Schema Overview: - Migration Patterns: - For broader context: - No explicit migration files or commands - Schema changes deploy instantly with npx convex dev - Existing data is not automatically transformed - Use optional fields and backfill mutations for safe migrations - Never run npx convex deploy unless explicitly instructed - Never run any git commands unless explicitly instructed - Always start with optional fields when adding new data - Backfill data in batches to avoid timeouts - Test migrations on development before production - Keep track of completed migrations to avoid re-running - Update code to handle both old and new data during transition - Remove deprecated fields only after all code stops using them - Use pagination for large datasets - Add appropriate indexes before running...