convex-migration-helper

To safely execute Convex migrations, widen the schema first, backfill data in batches, and narrow the schema after verification. This structured workflow reduces downtime and prevents data inconsistency during breaking changes.

The best way to backfill Convex documents is using online migrations with batch data processing and progress tracking. This allows you to migrate data safely and add required fields without disrupting your active services.

Yes, you can perform a dry run of your Convex data migration. The workflow supports dry runs and status monitoring, allowing you to validate batch processing and backfill operations before committing to the actual schema changes.

Yes, you need the @convex-dev/migrations component to run these batch processing migrations. This component is required to facilitate the safe backfilling, batch processing, and status monitoring features during your deployment workflow.

The multi-deploy workflow handles schema narrowing by providing a safe deployment strategy where you backfill and verify data first. After verification, you can safely narrow the schema across multiple deployments without losing data.