What problem does it solve? Convex rejects deployments when the schema does not match existing data, so breaking changes like adding required fields, changing types, or splitting tables require careful multi-step migrations. This Skill guides you through safe widen-migrate-narrow workflows so you can evolve your schema without downtime or failed deploys. ## Core Features & Use Cases - Multi-Deploy Migration Planning: Structures breaking changes into widen-schema, migrate-data, narrow-schema phases with code that handles both old and new formats. - Batched Migrations Component: Uses @convex-dev/migrations for cursor-based pagination, resume from failure, dry runs, and status monitoring on large tables. - Zero-Downtime Strategies: Provides dual-write and dual-read patterns so your app keeps serving requests during the migration window. - Use Case: You need to change a boolean isPro field into a plan enum on a teams table with production data. The Skill walks you through adding the optional new field, backfilling with a migration, verifying completion, and narrowing the schema in a final deploy. ## Quick Start Ask the assistant to plan a safe migration for your breaking Convex schema change, describing the current field shape and the target shape.
