A website migration is rarely just a technical handover. It can change how customers find you, how quickly pages load, how leads enter your CRM and how confidently your team manages content. This website migration planning guide is built for businesses that want the commercial upside of a new platform, redesign or domain without sacrificing the search visibility and conversions they have already earned.
The risk is not migration itself. The risk is treating it as a launch-day task rather than a managed business project. A well-planned migration protects existing value while creating room for better performance, clearer messaging and scalable digital operations.
Website migration planning guide: define the business case
Start by being specific about what needs to improve. An outdated website may be slow, difficult to update, poor on mobile or unable to support new integrations. A move from Joomla to WordPress, from an older WooCommerce build to Shopify, or from legacy hosting to a modern environment can solve real problems. But the platform is not the outcome. The outcome might be more qualified enquiries, stronger organic traffic, fewer support issues or a faster path from campaign click to conversion.
Set measurable targets before design or development begins. For example, retain or improve organic sessions to priority pages, maintain form completion rates, reduce page load times, improve mobile Core Web Vitals or make product and service updates easier for internal teams. These targets give every decision a commercial filter.
It also helps to agree on the migration scope early. Are you moving content only, or redesigning templates and rewriting messaging at the same time? Are domains, email, hosting, customer accounts, product data and third-party systems included? A full redesign can be the right opportunity to improve the customer experience, but combining too many major changes without clear ownership increases risk. Where possible, separate essential migration requirements from future enhancements.
Audit what you have before you build
A new site cannot protect what nobody has identified. Begin with a complete inventory of the current website, including key landing pages, blog articles, product or service pages, downloadable files, media, forms, redirects, metadata, analytics tags and integrations.
Not every page deserves to be rebuilt. Some may be outdated, duplicated or attracting no meaningful traffic. Others may generate enquiries, hold valuable backlinks or rank for high-intent search terms despite looking unremarkable. Removing these pages without a replacement or redirect is one of the fastest ways to lose organic visibility.
Review performance data alongside technical data. Identify pages that drive leads, sales, calls and newsletter sign-ups, as well as pages with strong search impressions or external links. Then classify each URL: retain it, improve it, consolidate it, redirect it or retire it. This creates a practical content decision register rather than a vague instruction to “move everything across”.
The same audit should cover functionality. Document every form, booking tool, payment gateway, membership area, CRM connection, tracking script, cookie banner, chat tool and email automation. A website can look perfect in a staging environment while quietly failing to send a high-value enquiry to the right team.
Build the new structure around customer intent
Migration is a strong opportunity to fix weak information architecture. Customers should be able to understand what you offer, why it matters and what to do next without digging through a cluttered navigation menu. Search engines also need a clear structure that shows how service, location, industry and supporting content relate.
Map the new sitemap before finalising page templates. For most service businesses, this means prioritising core services, sector or use-case pages where justified, proof points, case studies, resources and clear contact paths. An ecommerce website may need a different model, with category logic, filters, product variants and customer account journeys requiring more attention.
Do not automatically preserve an old URL structure simply because it exists. Cleaner URLs and a more logical hierarchy can help users and editors. The trade-off is that every changed URL needs an accurate permanent redirect. If a page has meaningful authority, its closest relevant replacement matters more than redirecting everything to the homepage.
Content should be reviewed for more than keywords. Check accuracy, brand consistency, calls to action, image quality, accessibility and whether claims can be supported. A migration is an expensive time to carry forward unclear copy that does not help customers decide.
Protect SEO with a redirect and metadata plan
Search performance is often lost through small oversights rather than dramatic technical failures. The central safeguard is a URL mapping spreadsheet that matches every important old URL to its equivalent new destination. This should include high-traffic pages, indexed pages, pages with backlinks, campaign landing pages and any URL that has generated conversions.
Use permanent 301 redirects for pages that have moved. Avoid redirect chains, where one old URL passes through several other addresses before reaching the final page. They slow users down, complicate troubleshooting and can dilute signals. A redirect should send users and search engines straight to the most relevant live page.
Carry across or improve page titles, meta descriptions, headings, canonical tags, image alt text and structured data where relevant. Preserve valuable on-page themes, but do not copy old metadata blindly if the page purpose has changed. Search optimisation should reflect the new page’s actual content and intent.
Technical settings require equal care. Ensure the staging site is blocked from indexing, then remove those blocks only when the production website is ready. Check that the live site has a valid XML sitemap, sensible robots directives, working canonical URLs and the preferred domain version configured correctly. If the domain changes, plan for the added complexity around redirects, verification and brand communications.
Test the customer journey, not just the page design
A migration should be tested in a secure staging environment that closely mirrors the live hosting setup. Visual checks matter, but commercial checks matter more. Test the journeys that make the website valuable: submitting an enquiry, receiving notification emails, completing a purchase, booking an appointment, downloading a resource, creating an account and using the site on mobile.
Test across current browsers and devices, with particular attention to mobile forms, menus, buttons and page speed. Many organisations receive most of their traffic from mobile, yet approve designs on a large desktop screen. If it is difficult to enquire from a phone, the website is leaving revenue on the table.
Before launch, run a structured quality assurance pass covering at least the following:
- Every priority URL resolves correctly or redirects to its mapped destination.
- Forms, payment processes and automated emails reach the correct recipients.
- Analytics, conversion tracking and consent settings record activity as intended.
- Images, downloads, search functions and site search work without broken links.
- Administrator access, backups, security updates and recovery procedures are in place.
Give named people responsibility for sign-off. Marketing should approve messaging, tracking and search requirements. Operations should validate workflows and customer communications. Technical teams should confirm hosting, security, integrations and rollback arrangements. This avoids the common gap where each team assumes someone else checked the critical detail.
Plan launch day as a controlled release
Choose a launch window that suits the business. For a high-traffic ecommerce site, that may mean avoiding peak sales periods. For a professional services firm, it may mean launching when decision-makers are available to check leads and emails. The right time depends on the cost of disruption and the team’s ability to respond quickly.
Take a final backup of the existing site and database, freeze unnecessary content changes, then deploy against a written launch checklist. Once the new website is live, test the priority customer journeys again in the production environment. Confirm the correct domain, SSL certificate, redirects, tracking, forms and email notifications are operating as expected.
Keep the old site available as a secured rollback option for an agreed period, but do not leave duplicate public versions live. Clear escalation paths are essential. If a payment issue, lead-routing failure or indexing problem appears, the team should know who owns the fix and how quickly it must be resolved.
Monitor the first weeks closely
Launch is the beginning of the validation period, not the finish line. Monitor traffic, rankings, index coverage, crawl errors, redirect behaviour, form submissions and conversion data daily in the first week. Then continue reviewing performance over the following weeks, as search engines recrawl pages and users reveal friction points that testing did not expose.
Some movement in rankings can occur after a major migration, particularly when content, templates and URLs change at once. The goal is not to react to every fluctuation. Focus on meaningful patterns: a priority service page dropping out of search, a sharp fall in enquiries, a rise in 404 errors or a checkout issue affecting revenue. These need action quickly.
A migration is also the right time to establish better ongoing governance. Define who owns content updates, plugin and platform maintenance, backups, security checks, hosting support and monthly performance reporting. Agenda Web approaches migrations as an operational upgrade, not a one-off design exercise, because long-term performance depends on what happens after launch.
The best result is a website that feels familiar enough for existing customers to use confidently, while working far harder for the business behind it. Plan with that standard in mind, and every technical decision has a clearer purpose.