convex-migration-helper

Execute Convex schema migrations with zero downtime by applying a widen–migrate–narrow deployment workflow. This multi-deploy sequence ensures service availability while handling both old and new document formats throughout the migration window.

The widen–migrate–narrow workflow is a multi-deploy migration sequencing strategy that matches Convex schema validation constraints. It guides you through expanding schema rules, backfilling data, and then restricting rules to safely ship breaking changes.

Handle data backfills during Convex table splits, merges, or type changes by using online migration safety patterns. This ensures reads and writes remain functional while both old and new data shapes coexist during the production rollout.

You can rename or delete required fields in Convex without breaking deployments by using deprecation patterns. The migration Skill plans the required field additions and shape restructuring across multiple deploys to maintain service availability.

You need online migrations for Convex schema evolution when shipping breaking changes like required field additions, type restructuring, or table merges. This process handles concurrent reads and writes when both old and new document formats exist.

Migrating Convex data without a multi-deploy workflow risks breaking deployments and losing data because Convex schema validation constraints reject mismatched document shapes. Single-deploy updates fail when old and new data formats collide.