Content Migration Template for Product Teams

What This Template Is For

Content migrations happen more often than teams expect. You switch CMS platforms. You consolidate two help centers after an acquisition. You move documentation from a wiki to a purpose-built docs site. You restructure URLs after a site redesign. You migrate from Zendesk to Intercom, from WordPress to Next.js, from Confluence to Notion.

Every migration shares the same risks: broken links, lost content, SEO damage, formatting errors, and missing redirects. A blog post that ranked on page one disappears because nobody set up the redirect. A help article loses its images because the migration script did not handle image paths. An onboarding flow breaks because hardcoded links point to old URLs.

This template provides a structured approach to planning, executing, and verifying content migrations. It covers content inventory, URL mapping, redirect planning, quality assurance, and post-migration monitoring. For the content audit that should precede any migration (so you only migrate content worth keeping), use the content audit template. For measuring the SEO impact of your migration, track organic traffic weekly for 90 days post-launch.

How to Use This Template

1. Audit before migrating. Do not migrate content you plan to delete. Run a content audit first and migrate only the keep and revise items. This reduces migration scope by 20-40% in most cases.
2. Map every URL. Create a complete source-to-destination URL map before writing any migration code. Missing redirects are the most common migration failure and the hardest to recover from.
3. Migrate in stages. Migrate one content section at a time (help center first, then blog, then marketing pages). This limits blast radius and makes rollback feasible.
4. Verify with automated checks. Manual spot-checks miss errors at scale. Use automated crawlers, link checkers, and diff tools to verify every migrated page.
5. Monitor for 90 days. SEO impact from migrations takes weeks to materialize. Monitor organic traffic, crawl errors, and 404 rates for a full quarter after launch.

Content Migration Template

Migration Overview

Pre-Migration Checklist

Complete these before any content is moved.

• ☐ Content audit completed (keep/revise/delete decisions made)
• ☐ Source content fully inventoried (pages, images, files, metadata)
• ☐ Destination platform configured and tested
• ☐ URL mapping document completed (see below)
• ☐ Redirect rules written and tested in staging
• ☐ Content formatting rules defined (how markdown/HTML/rich text converts)
• ☐ Image and media asset migration path tested
• ☐ Metadata mapping defined (titles, descriptions, tags, categories, dates)
• ☐ Internal link rewriting plan documented
• ☐ External link audit completed (third-party sites linking to your content)
• ☐ Stakeholders informed of timeline and potential disruptions
• ☐ Rollback procedure tested

Content Inventory

Create a complete inventory of content to migrate.

Inventory summary:

URL Mapping

Map every source URL to its destination. This is the most critical document in the migration.

• ☐ Every source URL mapped to a destination
• ☐ Deleted pages mapped to the nearest relevant page (not homepage)
• ☐ Merged pages mapped to the consolidation target
• ☐ URL patterns validated (no trailing slashes, consistent casing)
• ☐ Redirect rules tested in staging environment

Metadata Mapping

Define how content metadata translates between platforms.

Migration Execution Plan

Break the migration into phases with clear milestones.

Quality Assurance Checklist

Run these checks after each migration phase.

Automated checks (run on every migrated page):

• ☐ Page returns 200 status code
• ☐ Title and meta description present and correct
• ☐ All internal links resolve (no 404s)
• ☐ All images load correctly
• ☐ No broken formatting (unclosed tags, missing line breaks)
• ☐ Canonical URL points to destination URL
• ☐ Source URL redirects to destination URL with 301

Manual checks (run on 10% sample, prioritizing high-traffic pages):

• ☐ Content matches source (no missing paragraphs or sections)
• ☐ Formatting preserved (headings, lists, tables, code blocks)
• ☐ Images display at correct size and quality
• ☐ Embedded media (videos, iframes) still works
• ☐ Navigation and breadcrumbs correct on new platform
• ☐ Page loads in under 3 seconds
• ☐ Mobile layout renders correctly

Post-Migration Monitoring

Track these metrics weekly for 90 days after go-live.

Filled Example: Help Center Migration (Zendesk to Intercom)

Overview

Inventory Summary

This template pairs well with the content governance template for establishing ownership of migrated content on the new platform. For the taxonomy decisions that often accompany migrations, use the taxonomy template. For broader product launch coordination, the Product Launch Playbook covers multi-team execution planning.