← ClaudeAtlas

couchbase-migration-executionlisted

Execute data migrations into Couchbase from MongoDB, PostgreSQL, MySQL, Oracle, SQL Server, DynamoDB, Cassandra, files, or custom sources. Use whenever the user asks about migrating, migration strategy, dual-write, change data capture / CDC, Debezium, AWS DMS, big-bang vs phased migration, strangler-fig, cutover, rollback, cbimport, cbexport, cbtransfer, validation after migration, count parity, traffic switching, feature flags during migration, reconciliation between source and target, or 'how do I move my data from X to Couchbase.' Triggers on operational mechanics distinct from couchbase-data-modeling (modeling AFTER migration) — this skill is about actually MOVING the data, keeping source and target in sync during transition, validating equivalence, switching traffic, and rolling back if needed. Use proactively for migration planning, ETL pipeline design, dual-write patterns, CDC tool selection, cutover runbooks, and migration rollback decisions.
celticht32/Couchbase-Skills-for-Claude.ai · ★ 1 · API & Backend · score 75
Install: claude install-skill celticht32/Couchbase-Skills-for-Claude.ai
# Couchbase migration execution A skill for *executing* data migrations into Couchbase — the mechanics of moving data, keeping source and target in sync during transition, validating equivalence, and switching production traffic. Distinct from the sibling skills: - `couchbase-data-modeling` — how to MODEL the data after migrating (document shape, boundaries, access patterns) - `couchbase-sizing` — how to size the target cluster - `couchbase-app-integration` — how to write app code that uses Couchbase (relevant during dual-write) - `couchbase-mcp` — operating the cluster (creating the target, running queries during validation) - **`couchbase-migration-execution` (this skill)** — the operational mechanics of moving data and switching over If the conversation is "how do I get my data from X into Couchbase," this is the right skill. ## When this skill applies - "How do I migrate from MongoDB / Postgres / DynamoDB / MySQL to Couchbase?" - "Should I do a big-bang migration or phased?" - "What's dual-write?" - "How do I keep the source and target in sync during migration?" - "Can I use CDC for this?" - "How do I validate the migration worked?" - "How do I cut over production traffic?" - "What if the migration goes wrong — can I roll back?" - "Tooling for bulk loading into Couchbase?" ## Pick the right reference | Question | Read | |---|---| | "Big-bang vs phased vs strangler-fig vs dual-write — which approach?" | `references/strategies.md` | | "What tools exist — cbimport, ET