convex-migrations

To backfill data and add fields to a Convex database without downtime, use a migration runner with cursor-based pagination and batched execution. This safely updates existing records incrementally while your application remains online.

The best way to rename fields or change types in Convex schemas is to copy data to new fields, then remove the old ones. This multi-step migration is coordinated safely with progress tracking and failure handling.

Cursor-based pagination for Convex schema migrations processes records in safe, manageable batches. The migration runner tracks progress and uses cursors to iterate through multi-table schemas without overwhelming the database.

Yes, you can create indexes and coordinate multi-step migrations across multiple Convex tables. The migration runner interface manages start, progress updates, completion, and failure handling for reliable deployments.

You need a migration runner to safely evolve Convex schemas and add indexes because it provides batched execution and failure handling. This ensures reliable zero-downtime deployments when modifying multi-table structures.