Interactive Migration Checklist
WordPress-to-News-CMS Migration Checklist
Plan the migration as a newsroom, data, search, and commercial continuity project—not simply a database export.
Interactive checklist
Your progress is stored only in this browser.
Inventory and baseline
Content and URL mapping
Build and newsroom rehearsal
Launch and monitoring
Migration risk register
Record the owner, evidence, risk, and acceptance criteria for each area before the migration window is approved.
| Planning area | Decision to document |
|---|---|
| URLs | Current URL inventory, redirect map, canonicals, and high-traffic or high-link-value pages. |
| Content | Articles, categories, tags, authors, media, PDFs, and archive behaviour. |
| SEO | Titles, descriptions, structured data, sitemap, internal links, and indexing controls. |
| Editorial | Roles, approvals, publishing workflow, corrections, and archive access. |
| Revenue | Ad units, sponsored content, subscriptions, ePaper, and conversion paths. |
| Launch | Redirect checks, analytics, Search Console, monitoring, and rollback ownership. |
The migration is complete only when publishing is stable
A successful import is not a successful launch. Editors must be able to publish and correct stories confidently, readers must reach the intended content, and search engines must see consistent canonical URLs, metadata, structured data, and redirects.
Compare post-launch results with the recorded baseline. Investigate important losses by URL group, template, section, device, acquisition channel, and integration instead of making broad changes without evidence.
Publisher migration planning
Request a publisher migration review
Share your current platform, approximate article count, languages, ePaper or app requirements, and intended launch date. We will use that context to discuss a migration plan suited to your publication.
Request a migration reviewMore publisher resources
Continue with another practical planning tool.