Treat migration as more than a launch task
A rebuild changes more than the appearance of pages. It can change URLs, headings, files, internal links, metadata, forms, and the way search engines discover content. Migration planning protects the parts of the current website that visitors, partners, and search systems already rely on. Start early, before new page designs make old content difficult to map.
Assign one person to own the inventory and decisions, even when several people contribute. Keep a shared record with the current URL, page purpose, content decision, proposed destination, redirect requirement, and review status. A spreadsheet is enough if it is complete, consistently maintained, and accessible to the people making changes.
Build an honest inventory
Collect more than the visible navigation. Include indexed pages, unlinked landing pages, downloads, images that receive traffic, feeds, resource files, form endpoints, and important print or campaign links. Use the content management system, analytics, search tools, server logs, and a crawl where available. Compare sources because each can reveal different parts of the site.
For every item, record its role and condition. A page with little recent traffic may still answer a valuable question or be linked from elsewhere. Conversely, a page with visits may be creating confusion or attracting the wrong audience. Decide based on purpose, quality, and evidence rather than traffic alone.
Map old destinations to useful new ones
For each URL that will change, identify the closest equivalent new page. A redirect should take a visitor to the answer they expected, not simply to the home page. If several weak pages become one stronger page, map each old URL to that destination and update internal links to use the new address directly. If content is genuinely retired and has no relevant replacement, document the decision instead of creating a misleading redirect.
Keep URL changes limited when there is no clear benefit. Stable, readable addresses are easier for people to share and easier for owners to maintain. Avoid changing a URL merely because a new template makes it possible, especially when the current address is well established.
Prepare and test redirects
Create a redirect list with one old URL, one intended destination, and the reason for the mapping. Use permanent redirects for lasting moves when your platform supports them. Check for chains, loops, accidental case differences, missing trailing-slash rules, and redirects that point to irrelevant pages. Do not rely on a single global rule unless you have verified its effect on every important path.
Test from a clean browser session and with automated checks. Confirm that old links resolve, new pages load, canonical references are sensible, and important files still work. Keep the old-to-new map after launch so support requests and future audits have a reliable reference.
Review after release
Before release, crawl the new site and check status codes, internal links, page titles, headings, structured data where used, robots instructions, XML sitemaps, forms, downloads, and analytics tagging. Compare the new content with the approved inventory so a missing page is not mistaken for a deliberate retirement. Ask people who know the site to test real journeys, including links from emails or documents.
Limitations: A careful migration cannot control every external link, search engine decision, browser cache, or user habit. Reporting tools may also show incomplete data. Keep monitoring available signals, respond to broken destinations quickly, and avoid making several unrelated structural changes at once when you need to understand what happened.
A practical perspective from Web Design Elevate. Recommendations depend on the website, its audience, available evidence and technical context.
Talk through your current website