work-item-migration

Migrate Azure DevOps work items across projects with parent, area path, and iteration mapping.

Updated Mar 31, 2026

Search Tags:#automation #migration #hierarchy #rest-api #project-structure #azure-devops #work-items

Ready to run

npx skills add https://github.com/shellicar/skills --skill work-item-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work-item-migration
Source: https://github.com/shellicar/skills/tree/main/skills/work-item-migration
Command: npx skills add https://github.com/shellicar/skills --skill work-item-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Migrating Azure DevOps work items across projects is complex due to parentage, area paths, and iterations. This skill provides a structured workflow to ensure correct placement and preserve hierarchy during migration.

Core Features & Use Cases

Cross-project migration with parent/child relationships preserved.
Decide between Move, Recreate, or Consolidate with cross-project linking and migration notes.
Handles hierarchy reorganization and area/iteration mappings for target projects.

Quick Start

Run a migration by selecting source work items and initiating the workflow to move or recreate items in the target project.

Frequently Asked Questions about work-item-migration

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

FAQPage Schema

How do I migrate Azure DevOps work items between projects while preserving parent-child hierarchy?▼

To migrate Azure DevOps work items across projects, use a structured workflow that carefully orders parent and child items, correctly mapping parentage, area paths, and iterations in the target project.

What is the best way to consolidate Azure DevOps work items from multiple projects?▼

Consolidating Azure DevOps work items involves a structured workflow that handles cross-project linking, migration notes, and hierarchy reorganization across Initiative, Epic, PBI, and Task levels to ensure correct placement in the target project.

Can I recreate Azure DevOps work items during a cross-project migration to preserve history?▼

Yes, you can optionally recreate Azure DevOps work items during a cross-project migration. This approach preserves history while applying correct area path and iteration mappings to the target project structure.

Does Azure DevOps work-item migration require REST API calls for hierarchy mapping?▼

Yes, Azure DevOps work-item migration requires REST API calls to execute the structured workflow, ensuring careful ordering of parent and child items alongside accurate area path and iteration mapping.

How do I handle area path and iteration mapping when moving work items across Azure DevOps projects?▼

Handle area path and iteration mapping by applying a structured migration workflow that reorganizes the hierarchy and translates source project structures to the target project during the cross-project move or recreate process.

When should I choose to move instead of recreate Azure DevOps work items during a project migration?▼

Choose to move Azure DevOps work items for direct relocation, or recreate them when you need to preserve history within a consolidation scenario using cross-project linking and migration notes.