convex-migrations

Manage Convex database schema migrations with batch processing and tracking.

Updated Apr 12, 2026

Search Tags:#typescript #database #migrations #schema #data-modeling #convex

Ready to run

npx skills add https://github.com/elcokiin/peluqueria --skill convex-migrations-elcokiin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convex-migrations
Source: https://github.com/elcokiin/peluqueria/tree/main/.agents/skills/convex-migrations
Command: npx skills add https://github.com/elcokiin/peluqueria --skill convex-migrations-elcokiin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of evolving database schemas in a reactive environment, preventing downtime and data corruption during field additions, removals, or type changes.

Core Features & Use Cases

Zero-Downtime Migrations: Implements patterns for backfilling data and handling optional fields to ensure application stability during schema updates.
Migration Runner Pattern: Provides a robust, trackable system for executing long-running data transformations in batches.
Use Case: When adding a new required field to a user profile, use this Skill to safely backfill existing records with default values before enforcing the new schema constraint.

Quick Start

Use the convex-migrations skill to generate a backfill mutation for adding a new required field to the users table.

Frequently Asked Questions about convex-migrations

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

FAQPage Schema

How do I safely add a required field to an existing Convex database schema without downtime?▼

A migration runner pattern handles long-running data transformations in batches, providing a trackable system for schema evolution. It ensures zero-downtime deployments by safely processing field additions, removals, and type conversions.

Can I perform type conversions and index creation on a Convex database while the application is live?▼

Yes, you can perform type conversions and index creation on a live Convex database by using batch processing and migration tracking strategies. This facilitates zero-downtime deployments and ensures consistent data integrity in reactive backend environments.

What is the best way to handle data backfilling when removing fields from a Convex schema?▼

The best way to handle data backfilling during field removals or additions in Convex is to implement patterns for backfilling data and handling optional fields. This ensures application stability and prevents data corruption during schema updates.

Why does changing a schema constraint in Convex require a migration strategy for existing records?▼

Changing a schema constraint requires a migration strategy because existing records must be backfilled with default values to satisfy new constraints. Without this, reactive backend environments face data corruption and application downtime during schema updates.

What are the limitations of evolving a reactive database schema without batch processing?▼

Without batch processing, evolving a reactive database schema risks application instability and downtime during long-running data transformations. A trackable migration runner pattern is required to safely handle large-scale field additions and type conversions.