convex-migration-helper

Plan and execute Convex schema and data migrations with the widen-migrate-narrow workflow.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/liminal-ai/liminal-build --skill convex-migration-helper-liminal-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-migration-helper
Source: https://github.com/liminal-ai/liminal-build/tree/main/.agents/skills/convex-migration-helper
Command: npx skills add https://github.com/liminal-ai/liminal-build --skill convex-migration-helper-liminal-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plans and executes safe Convex schema and data migrations during breaking changes.

Core Features & Use Cases

  • Guidance on the widen-migrate-narrow workflow to evolve schemas without downtime.
  • Online migrations that allow the app to continue serving requests while data is transformed in batches.
  • Best-practice references for common patterns, backfilling, splitting/merging tables, and validating outcomes.

Quick Start

Explain the breaking-change scenario and the desired migration outcomes to generate a safe, multi-step Convex migration plan.

Frequently Asked Questions about convex-migration-helper

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

FAQPage Schema
How do I run zero-downtime Convex migrations for schema changes?

Zero-downtime Convex migrations use the widen-migrate-narrow workflow to evolve schemas without downtime, allowing the app to continue serving requests while data is transformed in batches.

What is the widen-migrate-narrow workflow for evolving Convex schemas?

The widen-migrate-narrow workflow is a safe migration pattern that widens the schema first, migrates existing data, then narrows the schema, ensuring zero-downtime during breaking changes.

How do I backfill existing documents during a Convex deployment?

Backfilling existing documents during a Convex deployment is handled through online migrations that transform data in batches while the application continues serving requests.

Can I use the @convex-dev/migrations component for multi-deploy strategies?

Yes, the @convex-dev/migrations component supports multi-deploy strategies and provides best-practice references for common patterns, backfilling, and validating outcomes across deployments.

When do I need a multi-step Convex migration plan?

A multi-step Convex migration plan is needed when deployment validation fails, existing documents require backfilling, fields change, or zero-downtime migration across deployments is required.