migration-helper

Safely migrate Convex schemas and data when making breaking changes. Problem : Existing documents won't have the new field. Solution : Add as optional first, backfill data, then make required. Example : Change tags: v.array(v.string()) to separate table For large tables, process in batches: Use cron jobs for gradual migration: For zero-downtime migrations: - Adding new required fields to existing tables - Changing field types or structure - Splitting or merging tables - Renaming fields - Migrating from nested to relational data - No Automatic Migrations : Convex doesn't automatically migrate data - Additive Changes are Safe : Adding optional fields or new tables is safe - Breaking Changes Need Code : Required fields, type changes need migration code - Zero-Downtime : Write migrations to keep app running during migration - Don't make field required immediately : Always add as optional first - Don't migrate in a single transaction : Batch large migrations - Don't forget to update queries : Update all code using old field - Don't delete old field too soon : Wait until all data migrated - Test thoroughly : Verify migration on dev environment first