sweetclaude:migrate

Migrate legacy work items into unified ISSUE-NNN format with preflight checks.

6|3|Updated Apr 12, 2026

Search Tags:#automation #refactoring #migration #backlog #project-management

Ready to run

npx skills add https://github.com/carson-sweet/sweetclaude --skill sweetclaude-migrate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sweetclaude:migrate
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/migrate
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill sweetclaude-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) components.

What problem does it solve?

This skill automates the complex, error-prone process of migrating legacy project work items into the unified ISSUE-NNN format required by modern SweetClaude versions.

Core Features & Use Cases

Automated Migration: Safely transforms flat BL-NNN backlogs or typed legacy taxonomies (stories, bugs, debt) into the current standard.
Safety & Recovery: Includes preflight checks, automated backups, and atomic finalization to ensure data integrity.
Use Case: Use this when upgrading a project from an older version of SweetClaude to ensure all historical work items are correctly indexed and accessible in the new system.

Quick Start

Run the sweetclaude:migrate skill to initiate the automated migration process for your current project directory.

Frequently Asked Questions about sweetclaude:migrate

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

FAQPage Schema

How do I migrate a legacy project backlog into the new ISSUE-NNN format?▼

The migration process handles flat BL-NNN backlogs and typed legacy taxonomies such as stories, bugs, and debt by orchestrating preflight checks, automated backups, and atomic finalization to ensure all historical work items are correctly indexed.

What is the safest way to refactor legacy project work items during an upgrade?▼

The safest way to refactor legacy work items is using automated preflight checks and atomic file transformations that create backups before finalizing the unified ISSUE-NNN indexing, ensuring full data integrity and recovery options.

Do I need Python 3 to automate project backlog migration?▼

Yes, Python 3 is required to run the migration scripts that access internal project state directories and execute the atomic file transformations needed to rebuild the unified backlog cache.

Can I convert flat backlog structures and typed taxonomies into a unified format?▼

Yes, you can convert both flat backlog structures and typed legacy taxonomies into a unified format by running automated migration steps that validate legacy work items and transform them into the standardized ISSUE-NNN indexing system.

What happens if the project backlog migration fails halfway through?▼

If the backlog migration fails, the automated preflight checks and atomic finalization design ensure data integrity by preserving automated backups, preventing partial file transformations from corrupting the project state.