convex-migration-helper

To add a new required field in Convex without downtime, widen the schema, migrate existing data asynchronously, and then narrow the schema. This approach ensures smooth schema evolution by validating data before enforcing strict types.

The best way to handle breaking Convex schema changes is preferentially adding new fields over direct type changes. You manage table reshaping, backfills, and zero-downtime rollouts using the @convex-dev/migrations framework.

Yes, you can perform data migrations online in Convex. The skill executes asynchronous batch updates during the migration process, allowing you to reshape tables and backfill data without interrupting active service.

Yes, you need the @convex-dev/migrations package and the Convex framework to execute schema evolution. The skill relies on these dependencies to manage schema validation, data backfills, and online rollouts.

Preferring new fields over type changes during Convex schema migration prevents breaking existing application logic. This strategy allows you to widen the schema and migrate data safely before narrowing it to enforce new validation rules.