Website redesign content migration is not a file-transfer exercise. It is a decision-making process that determines which content should move unchanged, which needs improvement, which pages should be combined, and which should be retired. The goal is to improve the new site without sacrificing search visibility, analytics continuity, user journeys or valuable institutional knowledge.
The safest approach combines a content audit, UX and business priorities, technical migration planning, redirect mapping, metadata preservation and post-launch monitoring. Treat the work as a controlled change to the site’s information architecture—not as a last-minute CMS task.
What content migration includes in a website redesign
In a redesign, migration can involve more than copying page text into a new template. Depending on the project, the migration scope may include:
- Page copy, headlines, calls to action and supporting resources
- Images, illustrations, documents, video embeds and downloadable assets
- URL structures, navigation labels, breadcrumbs and internal links
- Title tags, meta descriptions, canonical tags, structured data and open graph fields
- Authors, publication dates, categories, tags and content relationships
- Forms, tracking events, conversion definitions and analytics annotations
- CMS fields, reusable modules, permissions and publishing workflows
Some migrations are largely technical. Others require a substantial content strategy because the existing site has duplicated pages, outdated claims, weak navigation or content that no longer reflects the organization. Before selecting a migration method, define what must remain stable and what is intentionally changing.
Start with a complete content inventory
A URL crawl is a useful starting point, but it is not a complete inventory. Combine the crawl with CMS exports, analytics data, search performance data, sitemap files, backlink information and stakeholder knowledge. The resulting worksheet should show each page’s current role, condition and proposed destination.
Useful inventory fields include:
- Current URL and proposed URL
- Page type, template and content owner
- Primary topic, audience and business purpose
- Organic clicks, impressions and ranking queries
- Engagement and conversion activity
- Internal links, external references and backlinks
- Last reviewed date and content freshness
- Legal, compliance or accessibility considerations
- Migration recommendation and rationale
Do not judge a page by traffic alone. A low-traffic page may support an important sales journey, answer a high-value question, rank for a specialized query or provide evidence required by buyers. Conversely, a page with visits may have poor intent alignment, duplicate another page or attract users who never find a useful next step.
Use five migration decisions: keep, improve, merge, redirect or retire
Every indexed page should receive an explicit disposition. Avoid vague labels such as “review later,” because unresolved pages tend to become accidental duplicates or broken links after launch.
Keep
Keep a page when its purpose, audience and performance remain valid and the new design can support it without substantial editorial changes. Keeping does not necessarily mean copying the page exactly. Review headings, internal links, accessibility, media formats and conversion paths before approving the transfer.
Rewrite or improve
Rewrite pages with valuable intent but weak execution. Common signals include outdated product information, unclear positioning, thin explanations, poor scanability, conflicting calls to action or content that does not match the page’s target audience.
Preserve the page’s useful subject coverage and search equity while improving its structure. Record major changes so stakeholders understand whether a performance shift is expected after launch.
Merge
Merge pages when several URLs address substantially the same need or when separate pages create a confusing journey. A strong merge produces one authoritative destination rather than combining text indiscriminately.
Before merging, compare each page’s search queries, links, conversions, backlinks and audience. Select the strongest destination based on intent and future architecture. Then create a content brief for the consolidated page, map the old URLs to it, and review internal links after publication.
Redirect
Redirect a page when its URL should no longer resolve independently but users or search engines still need a clear replacement. A one-to-one, relevant redirect is usually preferable to sending many unrelated URLs to a generic page.
Document the source URL, destination URL, redirect type, reason and validation status. Redirect chains, loops and irrelevant destinations can create usability and crawling problems.
Retire
Retire content only when it has no suitable replacement and no continuing audience, legal, operational or historical value. Confirm that the page is not linked from important journeys, included in feeds or required for customer support. A retirement decision should be deliberate, not simply the result of an incomplete export.
Make decisions with a repeatable scoring framework
A simple scoring model can make editorial decisions more consistent across a large site. Score each page against criteria such as business value, user value, search value, content quality, freshness and duplication risk. The exact weighting should reflect the organization’s goals.
| Question | What to examine | Likely action |
|---|---|---|
| Does the page serve a distinct need? | Audience, intent, navigation role and support questions | Keep or improve if the need is valid |
| Does it produce meaningful value? | Conversions, assisted journeys, qualified visits and links | Protect, improve or consolidate carefully |
| Is the information accurate? | Dates, offers, policies, product details and ownership | Rewrite or retire |
| Does another page cover the same intent? | Overlapping topics, titles, rankings and internal links | Merge and redirect |
| Is there a relevant replacement? | Topic, audience and user expectation | Redirect only when the match is appropriate |
The framework should support judgment, not replace it. Ask subject-matter experts to review high-risk pages, especially regulated, technical, legal, financial or product content.
Protect UX and search signals during the move
Content decisions and technical implementation must stay connected. A page can be editorially approved yet still lose value if its URL, canonical, structured data or internal-link context changes without a plan.
Build a redirect map before development ends
Create the redirect map while the new information architecture is still editable. Map every old URL that will change to its most relevant new destination. Include trailing-slash variations, legacy folders, campaign URLs and important downloadable assets where applicable.
Test for missing sources, duplicate destinations, redirect chains, loops and redirects to irrelevant pages. Keep the map available for developers, SEO reviewers and post-launch analysts.
Preserve or intentionally update canonical and schema signals
Review canonical tags on every migrated template. A copied canonical pointing to an old domain, staging URL or unrelated page can undermine the migration. Structured data should also be checked against the new page type, visible content and organizational requirements. Do not preserve markup merely because it existed; validate whether it remains accurate.
Rebuild internal links in context
Internal links carry navigation meaning and help users discover related information. Do not rely only on automated replacement of old URLs. Review links in body copy, related-content modules, breadcrumbs, navigation, footers and downloadable resources. Remove links to retired pages and update anchor text when the destination’s purpose has changed.
For the broader relationship between structure and visual communication, see design services and design guidance. For implementation considerations across templates and systems, the web development resource is also relevant.
Plan the CMS migration around content models
A redesign is an opportunity to fix an unsuitable content model. Before importing content, define which fields are required, optional, reusable or controlled by editors. Decide how the CMS will handle headings, summaries, authors, media, related content, calls to action, localization and redirects.
Be cautious when mapping rich text into a new editor. Formatting can introduce empty paragraphs, inconsistent heading levels, inaccessible links, broken embeds or unnecessary inline markup. Test representative page types—not just one ideal article—before approving a bulk import.
For a deeper look at systems, field mapping and migration execution, review CMS migration during a website redesign. That work should be coordinated with the editorial inventory rather than treated as a separate technical stream.
Keep analytics and measurement continuity
Analytics data is part of the migration risk profile. Confirm that the new templates preserve the analytics property, consent behavior, page-view measurement, events, form tracking and conversion definitions required by the business.
Document any intentional changes to events or conversion logic before launch. If URLs, page types or funnel steps change, create an annotation or release record so post-launch comparisons are meaningful. Validate tracking in a staging or controlled environment where possible, while remembering that some production behavior—such as redirects and consent flows—requires live testing.
The related guide on analytics tracking in a website redesign can help teams organize this work alongside content and development milestones.
Run migration QA in several passes
Quality assurance should combine automated checks with human review. A practical sequence includes:
- Pre-launch crawl: confirm that approved URLs, metadata, canonicals, headings, links and structured data behave as expected in the new environment.
- Content sampling: review representative pages from every template, topic group and migration method.
- Redirect testing: test old URLs individually and in batches, including important legacy paths.
- Functional testing: verify forms, search, filters, downloads, media, navigation and user permissions.
- Accessibility review: check headings, keyboard access, link purpose, alternative text, contrast and focus behavior.
- Analytics validation: confirm page views, events, conversions and consent behavior.
- Launch comparison: compare the live site against the approved inventory and redirect map.
Prioritize defects by impact. A broken conversion form, incorrect canonical or failed redirect deserves faster attention than a minor copy inconsistency, though both should enter a tracked backlog.
Monitor the site after launch
Migration work continues after deployment. Establish a monitoring period with clear owners and escalation rules. Review crawl errors, indexed pages, redirects, organic impressions, branded and non-branded queries, conversions, top landing pages, internal search behavior and support feedback.
Expect some volatility when URLs, content, templates or intent alignment change. The purpose of monitoring is not to react to every fluctuation, but to identify technical failures, unexpected page omissions and meaningful changes in user behavior. Compare performance by page group and migration decision—kept, rewritten, merged, redirected and retired—rather than judging the redesign as one undifferentiated set.
If the redesign itself needs broader planning across audit, information architecture, content, development and launch governance, see the website redesign resource. For organic visibility considerations, the SEO services resource provides a related strategic context without replacing the migration plan.
Website redesign content migration checklist
- Inventory URLs, CMS records, media, metadata and important assets.
- Identify page purpose, audience, performance and ownership.
- Assign every page a keep, improve, merge, redirect or retire decision.
- Review high-value pages with content and subject-matter owners.
- Define the new URL, template and content model before bulk import.
- Prepare and test a complete redirect map.
- Validate canonicals, structured data, metadata and internal links.
- Preserve or intentionally rebuild analytics and conversion tracking.
- Test representative page types for accessibility and functionality.
- Monitor search, analytics, redirects and user feedback after launch.
Final takeaway
The best content migration is selective. It protects content that serves a real purpose, improves pages with unrealized value, consolidates duplication and removes material that no longer belongs—while preserving the technical signals and measurement needed to evaluate the change. Treating migration as an early, cross-functional redesign workstream gives teams more control than attempting to copy the old site after the new experience is already built.
