Convex Migrate

If you've ever shipped a Convex schema change and watched deploys fail because existing rows didn't match the new validator, this skill is for you. It walks the safe sequence: make the new field optional, install @convex-dev/migrations, write a backfill that fixes old rows, run it, check counts, and only then make the field required. The rule it enforces that matters most is never tightening a validator before the backfill finishes, since that rejects live data. It's a plain workflow with no magic, so the value is mostly in not skipping steps under pressure. Worth installing if you're touching a schema that already has production data.

skills.sh installs: 41.3K
GitHub stars: 69
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add convex/agent-skills --skill convex-migrate --agent claude-code

Installs into .claude/skills of the current project.

Files

Migrate the schema / data on a live app

Change a deployed schema without breaking existing data: stage the schema change, install @convex-dev/migrations, write a backfill that makes old rows valid, run it, and verify before tightening the validator.

Workflow

Make the new field optional first (so deploy doesn't reject existing rows).
Install @convex-dev/migrations; write a migration that backfills/transforms existing rows.
Run the migration; verify all rows are valid.
Tighten the validator (make the field required) once the backfill is complete.

Rules

Never tighten a validator before the backfill completes — it rejects existing rows and breaks the live app.
Add new fields as optional first, migrate, then require.
Verify row counts before and after.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly