convex-migrations

Automate batched Convex database schema migrations with progress tracking.

Updated Feb 26, 2026

Search Tags:#indexing #migrations #data-integrity #convex #schema-evolution #batched-processing #migration-tracking

Ready to run

npx skills add https://github.com/NitzanSelwyn/MomentumTrackerAdmin --skill convex-migrations-nitzanselwyn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convex-migrations
Source: https://github.com/NitzanSelwyn/MomentumTrackerAdmin/tree/main/.claude/skills/Convex%20Migrations
Command: npx skills add https://github.com/NitzanSelwyn/MomentumTrackerAdmin --skill convex-migrations-nitzanselwyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convex migrations provide a structured, auditable approach to evolving database schemas without downtime. Teams can safely apply schema changes, backfill data in batches, and monitor progress across environments.

Core Features & Use Cases

Structured migration tracking with a centralized migrations table.
Batch processing and progress updates to avoid long-running tasks.
Support for adding/removing/renaming fields, index changes, and type migrations.

Quick Start

Start by naming a migration, then run it to process data in batches until completion.

Frequently Asked Questions about convex-migrations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run zero-downtime schema migrations on a Convex database?▼

Zero-downtime Convex schema migrations are automated by processing data in batches using cursors, tracking progress in a dedicated migrations table, and using start, update, complete, and fail mutations to ensure deterministic, auditable schema evolution.

What is the best way to backfill data in batches during Convex schema evolution?▼

Batched data backfilling during Convex schema evolution uses chunked processing with cursors to avoid long-running tasks, while a centralized migrations table tracks progress and ensures data integrity across large production datasets.

Can I track migration progress and handle failures for large Convex datasets?▼

Migration progress and failures for large Convex datasets are tracked using a dedicated migrations table with start, update, complete, and fail mutations, providing an auditable record and optional rollback hooks for handling errors.

Does Convex support adding and removing fields without causing production downtime?▼

Adding, removing, or renaming fields and indexes in Convex avoids production downtime by applying changes through batched, chunked processing with cursors, ensuring data integrity without blocking ongoing operations.

What are the limitations of batched Convex migrations?▼

Batched Convex migrations require a dedicated migrations table and chunked processing with cursors to avoid long-running tasks, meaning migration execution depends on sequential batch completion and careful failure handling rather than instant schema switching.