convex-migration-helper

To handle breaking schema changes in Convex without downtime, you use a widen-migrate-narrow deployment pattern. This workflow orchestrates multiple deployments to safely transition data structures while your application remains live and functional.

The widen-migrate-narrow pattern is a multi-deploy workflow that safely evolves Convex schemas. It first widens the schema to accept both old and new formats, migrates the existing data, and then narrows the schema to enforce the new structure exclusively.

To split nested data into a new Convex table while the app is live, you use batched and resumable data transformations. This approach processes large datasets in batches to avoid transaction limits while maintaining data integrity during the live operation.

Yes, you need the @convex-dev/migrations component to execute these schema migrations. It provides the batched, resumable, and verifiable data transformation capabilities required to handle large datasets without hitting transaction limits.

The best way to backfill data when modifying field types in Convex is using automated batching via the migrations component. This handles large datasets safely without hitting transaction limits, ensuring data transformations are resumable and verifiable throughout the process.

Convex database migrations hit transaction limits when processing large datasets in a single operation. Utilizing an automated batching component resolves this by breaking the data transformations into smaller, resumable batches that stay within operational limits.