Website Migration Checklist: Protect the Enquiry Journey

A website migration can pass its redirect checks and still lose the next customer enquiry.
Imagine a visitor opening a bookmarked service page. The old address redirects correctly, the new page loads, and the form displays a success message. Yet the notification goes to an unattended mailbox and no CRM record appears. This is a hypothetical example, but it exposes a gap in a launch checklist: reaching the right page and completing the business journey need separate evidence.
For a small service business, the useful acceptance unit is the whole journey: old link, relevant destination, working action, received enquiry and assigned owner.
1. Map old URLs to the next useful action
Start with a short list of commercially important entry points. Include pages receiving search traffic, links in directory profiles, advertised landing pages, PDFs, quotation emails and customer bookmarks. Add the main contact and booking routes even if they attract little organic traffic.
For each old URL, record the intended new page and what a visitor should be able to do there. A repair-service page should lead to the corresponding repair information and enquiry action. Redirecting every retired page to the homepage can leave visitors searching again for the service they already chose.
Google's site-move guidance recommends preparing a URL mapping, implementing redirects and monitoring the old and new URLs. It also warns that rankings can fluctuate while URLs are reprocessed. A migration handover should distinguish technical checks from outcomes that require subsequent monitoring.
2. Test the destination as a customer would
Open an old link on a phone-sized screen and follow the redirect. Check the final address, page topic, visible heading and main action. Look for a retained staging banner, incorrect canonical URL, accidental noindex instruction or a contact button hidden behind another interface element.
Test a link with an ordinary campaign query parameter as well. Decide which parameters matter to attribution and verify their intended treatment. Don't preserve every parameter blindly: some may contain obsolete state or information that shouldn't reach another system.
A redirect report answers whether navigation succeeded. A browser check answers whether the destination remains usable.
3. Prove the enquiry reached its destination
Use a clearly labelled synthetic enquiry approved by the business owner. Don't enter a real customer's details into a staging form. Where a form triggers live notifications or automations, agree on the test window and recipient first.
Trace the submission through each expected step:
- The browser shows the appropriate outcome once.
- The server records acceptance or an actionable failure.
- The designated inbox or CRM receives the test record.
- The correct team member can find and act on it.
- An acknowledgement is sent only when that behaviour is intended.
A green toast proves very little about the last four steps. Record a non-sensitive test reference and the destination's receipt time instead of circulating screenshots containing customer data.
4. Separate customer communication from analytics
A conversion event and an enquiry record answer different questions. An analytics event can fire even when downstream delivery fails. A genuine enquiry can also arrive while an analytics tag is blocked or misconfigured.
Verify both paths independently. For measurement, document the event name, trigger and deduplication behaviour. For operations, document who receives the enquiry and how failures become visible. Avoid sending form-message contents or personal details to advertising platforms as test evidence.
This separation also helps when a redesign changes the form provider but keeps the same CRM. Each handoff has an owner and a testable result.
5. Agree on recovery before changing DNS
Write down the rollback trigger, responsible person and known working release. Include the relevant DNS or hosting constraints and what happens to enquiries received during the transition. A rollback that restores the page while leaving the form pointed at a retired endpoint is incomplete.
After launch, repeat the highest-value journeys on the production address. Monitor real delivery failures, missing records and unexpected redirects. Don't manufacture customer enquiries to create reassuring activity numbers.
A compact sign-off record
For each critical journey, retain six fields: original URL, final URL, expected customer action, synthetic test reference, verified receiving destination and responsible owner. Mark unknowns as unknowns. Link the record to the release so a later investigation can identify what was actually tested.
The business question becomes concrete: can someone arriving through an existing link still reach the right service and get a response?
Muhammad Abdullah is co-founder of StackEndBox, a software engineering company building web applications, custom software and integrations. When scoping a migration, ask for the enquiry-delivery acceptance record alongside the redirect map.
Cover photo: Glenn Carstens-Peters, via Unsplash.
About the author
- Co-founder at StackEndBox, working with founders, agencies and business teams on SaaS, custom software, AI systems, automation and integrations. This publication explains implementation decisions, operating limits and practical buying questions. Synthetic examples and AI assistance are disclosed in the relevant articles. Website: https://www.stackendbox.com
Comments
Join the discussionNo comments yet. Be the first to comment.


