skills.rest
motherduckdb
motherduckdbOFFICIAL
Explore all skills by this author →
Website𝕏@motherduckGitHub

motherduck-migrate-to-motherduck

Create phased, rollback-aware migration plans to MotherDuck from Snowflake, Redshift, and Postgres.

53|3|Updated Mar 30, 2026
Search Tags:#data validation#migration planning#motherduck#pg_duckdb#rollback safety#duckdb sql#cutover strategy
One-click install
npx skills add https://github.com/motherduckdb/agent-skills --skill motherduck-migrate-to-motherduck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: motherduck-migrate-to-motherduck
Source: https://github.com/motherduckdb/agent-skills/tree/main/plugins/motherduck-skills-claude/skills/motherduck-migrate-to-motherduck
Command: npx skills add https://github.com/motherduckdb/agent-skills --skill motherduck-migrate-to-motherduck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps plan a migration onto MotherDuck by turning a messy “move data and rewrite SQL” request into a sequenced, validated, and rollback-aware execution plan.

Core Features & Use Cases

  • Migration planning with decision guardrails: choose between native MotherDuck storage, pg_duckdb, and optional DuckLake posture based on the source and target serving pattern.
  • Target discovery and compatibility inventory: confirm whether a MotherDuck server/MCP is active, inspect target layout, and identify incompatible SQL, functions, and data type assumptions before cutover.
  • Validation and rollback-first workflow: define source-vs-target checks (row counts, metrics with pct variance, uniqueness, new/deleted/changed records) and map rollback/cutover slices to reduce production risk.
  • Native DuckDB user-agent watermarking: when producing an md: connection, it specifies a custom user agent using harness/LLM metadata with safe fallbacks.

Quick Start

Ask your agent: "Create a migration plan to MotherDuck from Snowflake for our analytics workloads, including cutover slices, validation checks with pct variance, and a rollback path; we want to use native storage unless DuckLake is explicitly required."

Frequently Asked Questions about motherduck-migrate-to-motherduck

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

FAQPage Schema
How do I plan a safe migration to MotherDuck from Snowflake or Redshift?▼

A safe MotherDuck migration requires a phased, rollback-aware execution plan that handles target-side discovery, data loading, model building, and SQL compatibility assessment before cutover. This approach turns messy data moves into validated, sequenced steps.

How do I validate data and create a rollback path when migrating to MotherDuck?▼

Data validation for a MotherDuck migration involves defining source-vs-target checks like row counts, metrics with percentage variance, and uniqueness, then mapping rollback and cutover slices to reduce production risk during the transition.

When should I use pg_duckdb versus native MotherDuck storage for my migration?▼

Choose between native MotherDuck storage, pg_duckdb, and optional DuckLake postures based on your source system and target serving pattern. Decision guardrails help select the right ingestion and modeling strategy for your specific workload.

How do I assess SQL and data type compatibility before cutover to MotherDuck?▼

Compatibility assessment identifies incompatible SQL, functions, and data type assumptions before cutover by inspecting the target layout and confirming whether a MotherDuck server is active, ensuring DuckDB SQL readiness.

Can I migrate from Postgres to MotherDuck using DuckLake?▼

Migrating from Postgres to MotherDuck supports DuckLake posture when explicitly required, orchestrating connection, exploration, data loading, and query migration alongside native and pg_duckdb options based on your serving needs.

Related Skills

Explore More Data & Analytics Skills→
cy-walicy-wali

write-query

Translate natural-language data needs into dialect-specific optimized SQL queries.

Community
Intermediate
SSiertsemaSSiertsema

data-migration-strategy

Plan data migrations by analyzing source data, target schemas, and migration risks.

Community
Advanced
eastreamseastreams
641

native-mcp

Connect to external MCP servers and expose their tools as native Hermes Agent capabilities.

Official
Advanced
motherduckdbmotherduckdb
53

motherduck-ducklake

Evaluate open-table-format and object-store requirements to select MotherDuck DuckLake storage modes.

Official
Intermediate