Website migration checklist: keep the pages people still need
Written by Derrick KityoA migration needs to preserve useful pages, files and working journeys. Plan the URL map, connected systems, editor handover and recovery before launch.

A website move can look successful because the new homepage loads. Meanwhile, a useful document has disappeared, an enquiry goes to the wrong place and a staff member can’t update the page they own.
My starting point for a migration is a record of what needs to survive. That includes content, addresses, connected services and the people responsible for them.
This website migration checklist covers that whole handover. It applies to a change of platform, domain or URL structure; the specific technical steps depend on the move.
1. Decide what is changing
List the domains, sites and systems included. A visual redesign with stable URLs is different from a platform move that changes addresses, templates and integrations.
Separate necessary changes from improvements that can wait. Moving the content, rewriting every service page and replacing the booking system together may create more uncertainty than the team can sensibly review.
Name the person who can approve the scope and the people who own content, infrastructure and connected services. Those responsibilities need to be clear before launch week.
2. Inventory pages, files and useful journeys
Collect existing URLs and identify the pages people still use. Include downloads, resources, forms and destinations linked from emails or printed material. Search data and analytics can help prioritise, but they aren’t the whole inventory.

An infrequently visited policy or admissions document may still be important. Ask the organisation which pages have responsibilities that a traffic report won’t explain.
Record the current address, intended destination, action and person checking it. Keep content that will be retired distinct from content that has moved.
3. Agree the destination of each important URL
Use a direct replacement where one exists. Avoid sending every old address to the homepage and hoping people will work out the rest.
Google’s site-move guidance recommends permanent server-side redirects for moved URLs and warns against irrelevant redirects. It also advises keeping redirects for at least a year, and longer where useful. Search visibility can fluctuate during a move; a checklist can’t guarantee unchanged rankings.
Here’s a fictional school example of a URL map:
Current URL: /admissions.html
Decision: Move
Destination or action: /admissions with the relevant content retained
Person checking: Admissions owner
Current URL: /files/term-dates.pdf
Decision: Replace with a useful public page
Destination or action: /term-dates, with document links handled deliberately
Person checking: Office editor
Current URL: /events/old-open-day
Decision: Review as a finished event
Destination or action: Keep an accurate archive or retire intentionally
Person checking: Events owner
The map describes decisions, rather than automatic redirect rules for every school. Confirm what the old page contained before choosing its replacement.
Want to apply this to your own website or app?
Tell me what you are working on and where it is getting stuck. I will help you turn the useful ideas into shipped work.
4. Back up and rehearse the move
Keep appropriate backups of content, files, configuration and other data the project is responsible for. Check what can actually be restored. A folder labelled “backup” is little help if nobody can explain how to use it.
Rehearse with representative material on a protected preview. Use fictional or appropriately prepared data for forms and other workflows. Record the steps needed to repeat the move.
Keep the preview out of public discovery using suitable access controls and indexing settings. Before launch, check that restrictions intended for the preview won’t block the public site.
5. Check content and search settings together
Review the material in its new template. Check headings, links, images, alt text, documents and any dates or ownership information the content needs.
Verify titles, descriptions, canonical URLs, indexing directives and sitemap entries against the intended public addresses. Check that links use final destinations rather than relying on old redirects throughout the site.
Preserve structured data only where it still describes the visible page accurately. Moving old markup unchanged can retain statements the new page no longer supports.
6. Test complete tasks and connected services
Submit a test enquiry with fictional information and confirm the right team receives it. Follow an external booking link, download a document and check any account or payment journey included in the scope.
Test an unavailable destination too. Agree what the visitor sees, how the problem is detected and who can recover the request. A working page doesn’t prove the handoff behind its main button works.
Include representative mobile and keyboard journeys. If the website uses an external embed, it is part of the journey people experience.
7. Rehearse the editor’s first update
Ask a real editor to find and update representative content in the new arrangement. They should know where the approved source lives and what they can publish.
For an education site, that might mean changing an event or replacing a document. My education website work includes planning around those recurring staff tasks, rather than treating migration as a file-copying exercise.
Resolve missing access and confusing fields before asking the team to maintain the public site. Include domain and account recovery responsibilities in the handover.
8. Agree cutover and a usable recovery plan
Choose a launch window with the organisation and the people supporting its infrastructure. Record who changes domains or routing, who checks the result and who can decide to stop.
Define which faults would justify reversing the change. Account for new submissions and content updates if a rollback becomes necessary. Sending traffic back shouldn’t quietly discard information received after launch.
Agree any content freeze and how urgent updates will be handled. Tell the staff affected when normal editing can resume.
9. Check the public result immediately
Test the actual public domain after cutover. Confirm representative old URLs reach their intended replacements and important documents remain reachable. Check the complete enquiry route again.
Verify secure connections, the intended indexing settings and the public sitemap. Check measurement arrangements against the current setup, including whether consent and event handling still behave as agreed.
Record what was checked and what remains open. A successful deployment message is evidence that a release happened, rather than evidence that every journey works.
10. Keep monitoring after the launch call
Review errors, broken links, enquiries and the work staff need to do. Use comparable search and analytics periods where possible, allowing for the organisation’s calendar and other changes.
Investigate a meaningful fall in activity instead of assigning every change to search reprocessing. A missing form destination or an accidentally blocked section needs a direct fix.
For help scoping the move, website migration support starts with the current site and the responsibilities involved. The website brief template gives you a place to collect the scope, URL map and acceptance checks.
Frequently asked questions
Will redirects guarantee that we keep the same search rankings?
No. Appropriate redirects help people and search engines find moved content, but search visibility can fluctuate. Preserve useful content and accurate settings, check the public result and monitor for specific problems without promising unchanged rankings.
Should every old URL redirect to the homepage?
No. Map moved content to a relevant replacement. If material is being retired, make that an intentional decision. Redirecting unrelated pages to the homepage can leave people without the information they expected.
When is a website migration finished?
Launch is one stage. The team also needs a working editor handover, checked public journeys and a plan for unresolved issues and monitoring. Agree completion around those responsibilities, rather than an arbitrary number of hours after deployment.

.jpg)






