convex-migrations

Manage Convex database schema evolution and data migrations.

2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/metaloozee/geoveda --skill convex-migrations-metaloozee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-migrations
Source: https://github.com/metaloozee/geoveda/tree/main/.cursor/skills/convex-migrations
Command: npx skills add https://github.com/metaloozee/geoveda --skill convex-migrations-metaloozee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides robust strategies and patterns for managing schema changes in Convex databases, ensuring data integrity and minimizing downtime during application evolution.

Core Features & Use Cases

  • Schema Evolution: Safely add, remove, or rename fields in your Convex tables.
  • Data Backfilling: Implement mutations to populate new fields with existing data.
  • Zero-Downtime Migrations: Apply schema changes and data updates without interrupting service.
  • Use Case: You need to add a new avatarUrl field to your users table. This Skill guides you through making the field optional, backfilling existing users with default avatars, and then making the field required.

Quick Start

Use the convex-migrations skill to backfill the avatarUrl field for all users.

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 new required field to an existing Convex database table?

To add a required field in Convex, first define it as optional, backfill existing records with default data using mutations, and then update the schema to make the field required.

What is a zero-downtime data migration strategy for a Convex backend?

Zero-downtime migration in a Convex backend involves applying schema changes and backfilling data via mutations without interrupting service, ensuring continuous application availability.

How do I backfill existing records when updating a Convex schema?

You backfill records in Convex by running mutations that populate newly added optional fields with default values across all existing documents before enforcing schema requirements.

How do I remove deprecated fields from a Convex schema without breaking queries?

Removing deprecated fields from a Convex schema safely requires updating your application code to stop querying those fields first, then executing a mutation to strip the data.

Can I update indexes and perform type conversions during Convex schema evolution?

Yes, Convex schema evolution supports index updates and type conversions through documented patterns, allowing you to safely modify data structures while maintaining integrity.