PagePotPagePotPagePot
  • Features
    • All features
    • Sitemap builder
    • Content planner
    • Diagram maker
    • AI assistant
    • Review and approval
    • Multilingual planning
    • Tree testing
    • SEO planning
  • Solutions
    • All solutions
    • Agencies
    • Marketing and digital teams
    • Education
    • Government
    • Website redesigns
  • Integrations
    • All integrations
    • AI agents (MCP)
    • Drupal
    • WordPress
    • API and webhooks
  • Pricing
  • Help Center
PagePot
  • Features+
    • All features
    • Sitemap builder
    • Content planner
    • Diagram maker
    • AI assistant
    • Review and approval
    • Multilingual planning
    • Tree testing
    • SEO planning
  • Solutions+
    • All solutions
    • Agencies
    • Marketing and digital teams
    • Education
    • Government
    • Website redesigns
  • Integrations+
    • All integrations
    • AI agents (MCP)
    • Drupal
    • WordPress
    • API and webhooks
  • Pricing
  • Help Center
Start free trialSign In

Plan your next website with PagePot

Sitemap, content, diagrams and client approval in one workspace.

Start free trial
14-day Pro trialNo credit card neededFree client reviewersSitemaps, content, assets and approvals in one placeFor new websites and established onesExport to PDF, Word, CSV and XMLImport pages into DrupalPlan every language on one structure
14-day Pro trialNo credit card neededFree client reviewersSitemaps, content, assets and approvals in one placeFor new websites and established onesExport to PDF, Word, CSV and XMLImport pages into DrupalPlan every language on one structure
PagePotPagePot

PagePot is a collaborative workspace for website content: sitemaps, page content, assets, feedback and approvals in one place.

Contact us

Features

  • All features
  • Sitemap builder
  • Content planner
  • Diagram maker
  • AI assistant
  • Review and approval
  • Multilingual planning
  • Tree testing
  • SEO planning

Solutions

  • All solutions
  • Agencies
  • Marketing and digital teams
  • Education
  • Government
  • Website redesigns

Integrations

  • All integrations
  • AI agents (MCP)
  • Drupal
  • WordPress
  • API and webhooks

Resources

  • Templates
  • Blog
  • Help
  • Changelog
  • FAQ
  • Compare

Company

  • About
  • Pricing
  • Security
  • Contact

© Copyright 2026 PagePot. All Rights Reserved.

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
Features
Solutions
Integrations
  1. Home
  2. Guides
  3. Website Content Migration Plan: A Step-by-Step Guide

Website Content Migration Plan: A Step-by-Step Guide

Build a website content migration plan: inventory and audit your pages, map them to a new structure and content models, plan redirects, then run QA and launch.

A website content migration plan describes how content moves from an old site to a new one: what you have, what you keep, where each piece goes, what shape it takes in the new CMS, and how old URLs lead to new ones. Without a plan, migrations tend to go one of two ways. Either everything is copied across, clutter included, or content is rewritten ad hoc and pages quietly disappear, taking their search traffic with them.

This guide walks through a migration in seven steps: inventory, audit, mapping, content models, URLs and redirects, QA, and launch. The advice is vendor-neutral and works whichever CMS you are moving from or to.

Step 1: Take a content inventory

You can't plan what you haven't counted. The inventory is a list of every page on the current site, with enough detail to make decisions about it.

Ways to build the inventory

  • Import the XML sitemap. Most sites publish one at /sitemap.xml. It is the quickest starting point, but it only lists what the CMS chose to include. Orphaned pages, old campaign pages and PDFs are often missing.
  • Crawl the site. A crawler follows links from the home page and finds what visitors can actually reach. It can also record page titles, headings and meta descriptions. Watch for robots.txt rules, login areas and pages that need JavaScript to render.
  • Export from the CMS. The old CMS may list content that isn't linked anywhere. Compare this with the crawl to find orphans.
  • Ask the people who run the site. They know about the microsite on a subdomain, the forms nobody links to and the landing pages used in email campaigns.

What to record for each page

FieldWhy it matters
URLNeeded for redirects and for checking nothing is lost
Title and main headingIdentifies the page
Page typeGroups pages that will share a template
OwnerWho decides what happens to it
Last updatedOld content is a candidate for review
Traffic and inbound linksHigh-value pages need extra care
Meta title and descriptionKeeps search metadata that works
Files and mediaPDFs and images must move too

Traffic and backlink figures come from your analytics and search tools. Even rough numbers help you spot the pages you can't afford to lose.

Step 2: Audit the content

With the inventory in hand, decide what happens to each page. Four decisions cover almost everything:

DecisionWhen to use itWhat happens
KeepAccurate, useful, performing wellMoves across as is, or with light edits
UpdateUseful but outdated, thin or off-brandRewritten before or during migration
MergeSeveral pages cover the same topicCombined into one stronger page
RemoveOutdated, duplicated, no traffic, no purposeNot migrated; its URL redirects or is retired

Some tips for the audit:

  • Give every page an owner and a decision. "We'll see" is how clutter survives.
  • Be careful removing pages with traffic or inbound links, even if they look dated. Update or merge them instead, or make sure they redirect to a relevant page.
  • Note legal, compliance or accessibility content that must be kept regardless of traffic.
  • Record the decision against the page in the inventory, so the migration team works from one list.

A redesign is the best chance you will get to cut content. Teams commonly find that a large share of an old site can be merged or removed.

Step 3: Map content to the new structure

Next, design the new sitemap and map every kept, updated or merged page to its place in it.

  • Start the new structure from audience needs, not the old navigation. The old sitemap is evidence, not a template.
  • Put the old and new structures side by side. For each old page, note its new home.
  • Look for gaps: pages the new site needs that the old site never had. These need new content, with owners and due dates.
  • Check that merged pages have one clear destination.
  • Get stakeholders to approve the new sitemap before content work starts.

The visual sitemap vs XML sitemap guide explains how an old site's XML sitemap can seed a visual sitemap for this step.

Step 4: Define content models

Old content rarely fits a new CMS as is. A product page that used to be one block of rich text may need to become separate fields for a summary, a price, a gallery and specifications.

For each page type in the new site:

  • List its fields, their types and which are required.
  • Set limits, such as character counts and image sizes, that match the new design.
  • Add instructions for whoever is restructuring the content.
  • Define metadata such as categories and tags, which often have to be cleaned up during migration.
  • Ask a developer to confirm the model matches what will be built.

Then move content into those models during planning, not in the new CMS. Restructuring content in a planning tool means writers and reviewers can work on it before the CMS is ready, and approvals happen against content in its final shape. See pre-CMS planning for why this order saves rework.

Step 5: Plan URLs and redirects

URLs are where migrations most often lose search traffic. Plan them as carefully as the content.

Plan new URLs

  • Set a slug for every page in the new sitemap and agree the URL pattern.
  • Keep URLs that already work, where the new structure allows. An unchanged URL needs no redirect.
  • Avoid duplicate paths.
  • For multilingual sites, agree how language appears in the URL (for example /es/...).

Build the redirect map

  • List every old URL from the inventory in one column and its new URL in the next.
  • Use permanent (301) redirects for pages that have moved.
  • Redirect removed pages to the most relevant remaining page, not all to the home page. Where there is no sensible destination, letting the URL return "gone" or "not found" is acceptable.
  • Avoid redirect chains: point old URLs straight to their final destination.
  • Include files such as PDFs, and old campaign URLs.
  • Agree who implements the redirects. This is usually done in the new CMS, the web server or the hosting platform, so it belongs in the build handoff.

Step 6: Quality assurance

Test before launch, using the inventory and redirect map as your checklist.

  • Every page in the new sitemap exists on the new site, with its approved content.
  • No placeholder text, broken images or missing files.
  • Internal links point to new URLs, not old ones that redirect.
  • SEO titles, meta descriptions, canonicals and robots settings carried across.
  • Structured data validates.
  • Every old URL in the redirect map lands on the right page, in one hop.
  • Forms, search and other integrations work.
  • Each language version is complete and linked to its translations.
  • Accessibility basics: heading order, alt text, contrast, keyboard use.

Step 7: Launch and follow up

  • Launch at a quiet time, with the team available to fix problems.
  • Switch on redirects as part of the launch, not after.
  • Publish the new XML sitemap and submit it to search engines.
  • Watch crawl errors and "not found" reports for the first few weeks, and add redirects for any old URLs you missed.
  • Compare traffic for key pages before and after.
  • Keep the inventory and redirect map: you will need them for questions later.

How PagePot helps

PagePot handles the planning side of a migration. You can start a project by importing the old site's XML sitemap, bringing a plan across from a Slickplan XML export (pages, templates, copy, SEO and files), or crawl the site (Pro plan and up) with options for page limits, folders, robots.txt, basic authentication and JavaScript rendering, and optionally bring its SEO metadata into the plan. Restructure the result in the sitemap builder, move content into templates with required fields and limits in the content planner, and get approval through review and approval. Slugs and search fields are planned per page in SEO planning, and the CSV page inventory, content handoff ZIP or the Drupal integration take the plan into the build. Redirects themselves are set up in your CMS or hosting. For more on redesigns, see website redesign.

FAQ

What is a website content migration plan?

It is a document or workspace that lists every page on the old site, what will happen to it (keep, update, merge or remove), where it goes in the new structure, what shape it takes in the new CMS, and how its old URL redirects to its new one.

How do I get a list of all pages on my website?

Start with the XML sitemap, usually at /sitemap.xml. Then crawl the site to find pages the sitemap misses, and compare both with an export from your CMS. Each method catches pages the others don't.

Should I migrate all my old content?

Usually not. A migration is a good time to remove outdated and duplicate content and merge thin pages. Be careful with pages that have traffic or inbound links: update or merge them rather than deleting them, and redirect their URLs.

How do I avoid losing SEO traffic during a migration?

Keep working URLs where you can, map every old URL to a relevant new one with permanent redirects, carry over titles and meta descriptions that perform well, and monitor crawl errors after launch.

When should redirects be planned?

During planning, as soon as the new sitemap and slugs are agreed. The redirect map is part of the build handoff, so developers can set redirects up before launch day.