What problem does it solve? Evolving a Convex database schema without breaking existing documents is tricky because Convex has no explicit migration files and does not automatically transform existing data. This Skill provides proven patterns for adding fields, backfilling data, renaming fields, changing types, and managing indexes without downtime. ## Core Features & Use Cases - Safe Field Evolution: Add new fields as optional, backfill in batches with paginated internal mutations, then make them required once data is consistent. - Field Renames and Type Changes: Copy data to new fields with fallback reads, convert types via mapping logic, and remove deprecated fields only after code stops using them. - Migration Runner Pattern: Track migration status in a dedicated table with start, progress, completion, and failure states to prevent duplicate runs. - Use Case: You need to add a required avatarUrl field to an existing users table with thousands of documents. Use this Skill to add it as optional, run a batched backfill mutation scheduled via the Convex scheduler, then tighten the schema. ## Quick Start Use the convex-migrations skill to add a new required field to my users table and backfill existing documents in batches.
