migration
/migration
Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the migration plan with scenarios, acceptance numbers, the parallel run and the rollback.
- Author
- DataWithBaraa ↗
- Repository
- claude-code-data-engineering-skills ↗
- Licence
- MIT
- Last repository change
- 06.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the migration plan with scenarios, acceptance numbers, the parallel run and the rollback.
Arguments
/migration [old estate]
Original author description
Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the migration plan with scenarios, acceptance numbers, the parallel run and the rollback.
How it works
- Steps
- Output
- Reads
- Writes
- Never
SKILL.md preview
--- name: migration description: Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the migration plan with scenarios, acceptance numbers, the parallel run and the rollback. argument-hint: "[old estate]" --- # Migration The job: from the old estate to a migration plan with scenarios, acceptance numbers, a parallel run and a rollback. It plans, it migrates nothing. Input: the folder, the inventory or the documentation of the old estate. ## Steps 1. Inventory the old estate: jobs, tables, schedules, owners, consumers. 2. Explain every job in three plain lines: inputs, logic, output. 3. Draw the lineage of the old estate. 4. Rate each job: risk, size, value, dead or alive. 5. Propose the cut list, with the reason for each. 6. Gather the requirements for the new platform. 7. Compare at least two target platforms on the requirements. 8. Propose the migration type per job: lift and shift, re-platform, re-engineer. 9. Design the target: where each kept job lands. 10. Map old to new, one row per old output. 11. Propose the order, in waves, the smallest proven one first. 12. Three scenarios: best, expected, worst, with effort and risk. 13. Define the acceptance numbers, per output, with the tolerance. 14. Plan the parallel run: old and new side by side, every output compared, for how long, before the cutover. 15. Plan the history load, the cutover, the rollback and the decommission of the old jobs. 16. Write the migration plan, decisions marked open for the data engineer. ## Output One migration plan: the inventory and its ratings, the cut list, the target, the waves, the scenarios, the acceptance numbers, the parallel run, the cutover and the rollback, with the open decisions marked. ## Reads - the old estate, the knowledge of the new platform ## Writes - the migration plan ## Never - Never migrates anything: it plans.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · DataWithBaraa/claude-code-data-engineering-skills | 90 | MIT |
| adobe/skills | 100 | Apache-2.0 |
| fubits1/svelte-skills | 100 | MIT |
| skillpanel/maister | 100 | MIT |
| prekuter/dryforge | 90 | Apache-2.0 |
| baek-labs/hames | 90 | MIT |
Database snapshot: 13.11.2026 · package version f13f0e808cda (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100snowflake-migration-plan
Build a high-level Snowflake to AIDP migration plan and present it for approval. States which objects can migrate and which cannot with a brief reason for each, applies user-supplied restrictions such as excluded databases or size caps, derives dependency order so views follow… - 90aidp-migration
Guide a migration of notebooks/jobs from another platform (e.g. Databricks) into AIDP. Use when the user wants to port Databricks notebooks/jobs to AIDP, move workloads onto the AIDP lakehouse, or plan a migration. Orchestration-only — it composes the other self-contained aidp-*… - 90data-migration
Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover, reconciling counts and values rather than assuming, handling the records that will not map cleanly, and planning a… - 90plan-migration
Runs the migration-planner agent on pending database migrations and returns a risk-rated execution plan with rollback paths as JSON. Use for CI or headless runs, for example `claude -p "/agents-virtuoso:plan-migration origin/main"`. - 100migration-plan
Use when the user needs a plan to migrate a database, API, data format, or infrastructure safely, with staging, validation, and rollback, rather than a single schema changeset.