How to Plan a CMS Migration Content Inventory Before Replatforming
A CMS migration can fail long before the new templates are deployed. If nobody has decided which pages matter, which content is still accurate, or what should happen to old URLs, the build team may be asked to migrate everything and resolve the uncertainty later.
A CMS migration content inventory gives the project a shared view of the existing website before content is moved. It should do more than count URLs. It should help marketing, SEO, development and operations decide what to keep, improve, merge, redirect, archive or replace.
This guide explains how to create a practical inventory for a UK website replatform. It focuses on content migration planning before the new CMS structure is finalised.
What a CMS migration content inventory should achieve
The inventory is a working decision register for the current website. Its purpose is to connect each content item with a clear migration action and an owner.
By the end of the exercise, your team should be able to answer:
- Which pages are commercially or operationally important?
- Which content is still accurate and useful?
- Which pages overlap and could be consolidated?
- Which URLs need a direct equivalent after the migration?
- Which items should be rewritten, archived or removed?
- Who owns the decision and the new content?
This prevents a common replatforming mistake: treating every existing page as equally valuable simply because it has a URL.
Start with a complete source list
Begin with more than a CMS export. A website migration content audit is more reliable when it combines several sources, because no single system usually contains the complete picture.
Useful sources to combine
- CMS page and post exports
- XML sitemaps
- Analytics landing-page reports
- Search Console pages and queries
- Existing redirect files or server logs
- Navigation and internal-link crawls
- Campaign, sales and customer-service landing pages
- Important PDFs, downloads and resource files
Include content that may not appear in the main navigation. Paid campaign pages, help articles, downloadable documents and old service URLs can still receive traffic or support customer journeys.
VERIFY: the exact export options and available URL history will depend on the current CMS, analytics setup, consent configuration and hosting environment.
Choose the right inventory fields
An inventory becomes difficult to use when it contains either too little information or every possible metric. Start with fields that support a decision.
Core identification fields
- Current URL
- Page title
- Content type
- Primary topic, service or product area
- Parent section or proposed new location
- Current owner
Performance and risk fields
- Organic visits or entrances
- Conversions, enquiries or assisted actions where available
- Backlinks or important referring sources
- Paid campaign use
- Customer-service or operational importance
- Known technical or content issues
Migration decision fields
- Keep unchanged
- Improve or rewrite
- Merge with another page
- Move to a new URL
- Redirect and retire
- Archive or delete
- Decision owner
- Required-by date
Keep the distinction between evidence and judgement. For example, traffic is evidence. “Keep” is a decision that should be supported by evidence and reviewed by an owner.
Classify content by job, not only by format
Content types such as page, blog post, PDF or landing page are useful, but they do not explain why the content exists. Add a practical job classification to the inventory.
Common categories include:
- Demand generation: service pages, campaign landing pages and buying guides.
- Product discovery: category pages, comparison content and product information.
- Trust and proof: case studies, testimonials, accreditations and process pages.
- Support: delivery, returns, FAQs, help content and documentation.
- Operational: trade information, customer portals, forms and account resources.
- Legacy or low-purpose: outdated announcements, duplicate pages and expired campaigns.
This classification helps stakeholders judge content according to its business role. A low-traffic returns page may still be essential. An old article with reasonable visits may still be unsuitable if it is inaccurate or no longer supports the business.
Use a decision framework for keep, improve, merge or retire
Do not make migration decisions from traffic alone. A page with low visits may protect search visibility, support a sales process or answer a question customers regularly ask.
Keep
Keep content when it is accurate, useful, aligned with the future website structure and worth maintaining. Confirm whether the URL should remain the same or whether it needs a controlled move.
Improve
Mark content for improvement when the underlying purpose is sound but the page has weak information, outdated examples, poor structure, unclear calls to action or weak internal links. Separate copy work from template work so the project can estimate both.
Merge
Merge pages when several URLs cover substantially the same intent or when a single stronger page would be easier to maintain. Record the surviving page and the URLs that will point to it.
Redirect and retire
Retire content when it is obsolete, duplicated, inaccurate or no longer serves a genuine user or business need. If the old URL has useful signals or external references, map it to the closest relevant destination rather than automatically sending it to the homepage.
This decision structure should be agreed before the migration team starts building templates. It is one of the most useful parts of a CMS replatforming checklist because it turns an inventory into an actionable scope.
Record relationships between pages
Content does not migrate in isolation. A page may be linked from navigation, related articles, forms, campaign adverts or structured data. Record relationships that could be affected by the new CMS.
Useful relationship fields include:
- Pages linking to this item
- Important internal links from this item
- Parent and child pages
- Related services or products
- Forms, downloads or integrations used on the page
- Redirect destination if the page is removed
This is particularly important for pages that sit inside a conversion journey. Removing a supporting guide or changing a service URL may affect more than organic search; it may also disrupt paid traffic, sales conversations or customer support routes.
Separate content ownership from migration ownership
One person may know the subject matter while another manages the migration task. Record both where necessary.
For each important item, identify:
- Subject-matter owner
- Marketing or commercial approver
- SEO reviewer, where relevant
- Technical migration owner
- Final decision-maker for uncertain items
Without named ownership, pages tend to remain in an “under review” state until the project deadline. A simple status such as proposed, approved, blocked or complete makes the inventory easier to manage.
Build the inventory in review waves
Do not wait until every URL has been perfectly enriched before making decisions. Review the inventory in waves so the highest-risk content is resolved first.
- Priority commercial pages: core services, products, lead-generation pages and campaign destinations.
- High-visibility SEO pages: pages with strong organic entrances, backlinks or important search visibility.
- Operational and trust content: delivery, returns, contact, process, account and support pages.
- Long-tail and legacy content: older posts, low-traffic pages, documents and uncertain items.
This approach gives the project a usable early scope while lower-priority decisions continue. It also reduces the chance that a large content volume hides a small number of commercially critical pages.
Connect the inventory to migration QA
The content inventory should feed the later testing plan. Add a priority or risk field so the team knows which pages need stronger pre-launch and post-launch checks.
High-risk items may need:
- Pre- and post-migration URL checks
- Metadata comparison
- Form or conversion testing
- Mobile review
- Canonical and indexability checks
- Internal-link verification
- Analytics and campaign validation
HOFK’s guide to auditing redirect chains for paid landing pages covers a related but narrower post-planning task. The inventory should identify which campaign pages need that level of attention.
Use a practical CMS migration content inventory template
A useful first version might include these columns:
- Current URL
- Page purpose
- Content owner
- Performance evidence
- Migration action
- New URL or destination
- Rewrite required
- Template required
- Redirect required
- Priority
- Decision status
- Review notes
Do not treat this as a database that must contain every possible detail. Treat it as a shared project tool. If a column does not change a decision, remove it or move it into a later technical specification.
Final CMS replatforming checklist
- Have all CMS content types been exported?
- Have sitemaps, analytics and campaign URLs been compared with the CMS list?
- Does every important item have a clear business purpose?
- Has each page been marked keep, improve, merge, redirect or retire?
- Are destination URLs recorded for moved or merged content?
- Have page relationships, forms and downloads been captured?
- Does every priority item have a named owner?
- Are high-risk pages connected to migration QA checks?
- Have uncertain decisions been assigned a deadline?
How HOFK can help
A content migration often crosses CMS configuration, responsive templates, SEO, analytics, redirects and connected workflows. HOFK can support with full stack development, ecommerce, mobile-ready design and SEO & Adwords where the migration needs both implementation and commercial context.
The practical work may involve structuring the inventory, reviewing the future content model, mapping page relationships, supporting URL decisions or connecting migration checks to the new website. The aim is not to move every old page automatically. It is to help create a clearer, more maintainable website after replatforming.
Conclusion
A CMS migration content inventory is most valuable when it records decisions, not just URLs. Combine CMS exports with analytics, search, campaign and operational evidence. Then classify each item by purpose, assign an owner and decide whether it should be kept, improved, merged, redirected or retired.
That makes content migration planning more practical and gives the wider CMS replatforming checklist a stronger foundation. Before the new templates are built, make sure the team knows what content deserves to move, what needs work and what should not be carried forward.
Frequently asked questions
What is a CMS migration content inventory?
It is a structured list of existing website content that records each item’s purpose, performance evidence, owner, migration action and future destination.
What should be included in a website migration content audit?
Include CMS URLs, sitemap entries, analytics and search evidence, campaign pages, content purpose, ownership, redirects, new destinations and decisions to keep, improve, merge or retire.
Should every page be migrated to the new CMS?
No. Some pages should be improved, consolidated, redirected, archived or removed. The decision should consider usefulness, accuracy, business value and technical risk rather than URL count alone.
When should content decisions be made during a replatform?
Make the main keep, merge and retire decisions before finalising the new content model and templates. Earlier decisions reduce uncertainty for design, development, SEO and migration QA.
How do you prioritise a large content inventory?
Review commercial pages, high-visibility SEO pages and operational content first. Then work through long-tail and legacy items, assigning owners and deadlines to uncertain decisions.