content-migration
Move content between platforms, domains, or URL structures while preserving SEO equity, user bookmarks, and integrations. Use this skill when planning a CMS migration, replatforming, consolidating sites, changing URL structures, or merging content from multiple sources. Triggers on content migration, replatform, CMS migration, domain migration, URL restructure, redirect map, site merge, content consolidation, migration plan, post-migration drop. Also triggers when planning a launch that involves moving existing content.
Profile →npx skills add rampstackco/claude-skills --skill content-migration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Content Migration Move content from one platform, domain, or URL structure to another without breaking SEO, user bookmarks, or downstream integrations. Stack-agnostic. --- ## When to use - Migrating from one CMS to another (e.g., WordPress to a headless setup) - Consolidating multiple sites into one - Splitting one site into multiple - Changing URL structures - Domain migration (one brand to another, mergers, rebrands) - Migrating from a custom build to a platform (or vice versa) - Content audit-driven cleanup as part of a larger move ## When NOT to use - A net-new site with no existing content (no migration needed) - Single-page edits or content updates within an existing site (use `content-and-copy`) - Performance or technical SEO improvements without URL changes (use `seo-technical`) - Routine content audits (use `seo-content-audit`) --- ## Required inputs - The source: current platform, current URL structure, current content inventory - The destination: target platform, target URL structure, target capabilities - The reason for migration (drives priority of what to preserve) - Constraints (timeline, budget, downtime tolerance) - Stakeholders (SEO, content, dev, comms, support
- When to use
- When NOT to use
- Required inputs
- The framework: 6 phases
- Phase 1: Inventory
- Phase 2: Audit and decide
- Phase 3: Map URLs
- Phase 4: Build and stage
- Phase 5: Cut over
- Phase 6: Monitor and recover
- Workflow
- Step 1: Set the scope
- Step 2: Build the inventory
- Step 3: Decide per piece
What does the content-migration skill do?
Move content between platforms, domains, or URL structures while preserving SEO equity, user bookmarks, and integrations. Use this skill when planning a CMS migration, replatforming, consolidating sites, changing URL structures, or merging content from multiple sources. Triggers on content migration, replatform, CMS migration, domain migration, URL restructure, redirect map, site merge, content consolidation, migration plan, post-migration drop. Also triggers when planning a launch that involves moving existing content.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill content-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.