content-migration

1# Content Migration
2 
3Move content from one platform, domain, or URL structure to another without breaking SEO, user bookmarks, or downstream integrations. Stack-agnostic.
4 
5---
6 
7## When to use
8 
9- Migrating from one CMS to another (e.g., WordPress to a headless setup)
10- Consolidating multiple sites into one
11- Splitting one site into multiple
12- Changing URL structures
13- Domain migration (one brand to another, mergers, rebrands)
14- Migrating from a custom build to a platform (or vice versa)
15- Content audit-driven cleanup as part of a larger move
16 
17## When NOT to use
18 
19- A net-new site with no existing content (no migration needed)
20- Single-page edits or content updates within an existing site (use `content-and-copy`)
21- Performance or technical SEO improvements without URL changes (use `seo-technical`)
22- Routine content audits (use `seo-content-audit`)
23 
24---
25 
26## Required inputs
27 
28- The source: current platform, current URL structure, current content inventory
29- The destination: target platform, target URL structure, target capabilities
30- The reason for migration (drives priority of what to preserve)
31- Constraints (timeline, budget, downtime tolerance)
32- Stakeholders (SEO, content, dev, comms, support)
33 
34---
35 
36## The framework: 6 phases
37 
38Every content migration follows the same arc. Skipping a phase is how migrations go badly.
39 
40### Phase 1: Inventory
41 
42You can't migrate what you don't know. Build a complete map of what exists.
43 
44For each piece of content:
45- URL
46- Title
47…