Changing your website? Plan the migration before launch.
A migration changes more than design. It can affect URLs found in Google, campaign forms, commercial integrations and team access. Preparation starts by listing what exists and deciding where each part belongs, before selecting a launch date.
Build a useful inventory
Collect current pages, downloadable files and contact points. Compare the list with visits, searches and enquiries when those records are available. An older page that barely appears in navigation may still bring customers. Mark what will be retained, rewritten, merged or removed and assign someone to approve each decision.
Map old addresses to destinations
For changing URLs, Google recommends mapping destinations and using relevant redirects. Do not indiscriminately redirect old pages to the homepage. Your migration table should contain the previous URL, destination and reason. Review internal links, language references and canonical addresses as well. Test examples before applying rules to the complete list.
- Service pages and articles that receive visits.
- Campaign pages and links in external profiles.
- Images or documents with shared links.
- Addresses that should continue to return a genuine not-found response.
Rehearse the operational journey
A launch can look correct while enquiries still go to an old mailbox. Test the form, delivery, CRM and reply. If DNS changes, identify email records and other services on the domain. Decide who can change each system and when they should intervene. Keep the previous configuration and define a clear condition for rolling back.
Monitor after publication
Check priority pages, indexability and the sitemap. Compare errors, enquiries and traffic with the previous period while considering seasonality and campaigns. Search fluctuations can occur; redirects do not justify promising zero loss. Keep a record of checks, discovered problems and decisions so the team can follow the outcome.
Frequently asked questions
Should I change domain and platform together?
It may be necessary, but increases the number of variables. Separate changes where practical and document the intended effect of each.
When can I shut down the old site?
Distinguish the old application from addresses and redirects that must still work. The plan depends on infrastructure and the transition period.
Reference documentation
A note from ArqWeb
This guide organises checks and decisions for a common situation. Implementation depends on the website, access and systems involved. We can assess your situation if you need help applying these steps.
Let's look at your situation.
Tell us what you need and what you have already. We will reply with next steps and a proposal suited to the work.
Discuss my requirements