← ClaudeAtlas

duckdb-migratelisted

Migrate DuckDB 1.4 or 1.5 deployments to 2.0. Covers storage version 69, lambda and regex breaks, removed settings, export/import, and phased cutover. Use when the user asks to migrate or upgrade to DuckDB 2.0, when 1.x binaries cannot open a file, or to pin backward-compatible storage versions.
srimon12/duckdb-2-skills · ★ 1 · AI & Automation · score 65
Install: claude install-skill srimon12/duckdb-2-skills
# DuckDB 2.0 migration Execute migration steps sequentially. For Python API breaking changes, see `duckdb-python`. For lambda syntax rules, see `duckdb-sql`. Before upgrading a binary shared across processes, upgrade all readers to 2.0 or pin new files to a legacy storage version. Support windows: | Line | End of community support | | --- | --- | | 2.0.0 LTS | 2027-10-22 | | 1.4 LTS | 2026-11-17 | | 1.5 | 2027-03-01 | The release calendar tentatively schedules 2.0.1 for 2026-11-18. For mission-critical workloads, wait for patch releases and validate on a shadow copy; 1.5 community support continues through 2027-03-01. ## Order of work 1. **Inventory**: Catalog every process, database file, client library, and extension accessing DuckDB. 2. **Pin format**: Enforce backward-compatible storage versions on any file that older readers must open. 3. **Back up**: Create file backups or export catalogs and data; verify the restore procedure. 4. **Shadow run**: Spin up a shadow database and replay production workloads against DuckDB 2.0. 5. **Upgrade**: Install the 2.0 binary and update all extensions concurrently. 6. **SQL checks**: Scan queries for syntax and semantic breaks, then run the full test suite. 7. **Cut over**: Shift live workloads to 2.0, retaining previous binaries and backups until verification completes. For step-by-step gate criteria and automated search patterns, see [references/checklist.md](references/checklist.md). ## Storage DuckDB 2.0 creates files usi