A new website can look perfect and still create operational problems if migration is treated as an afterthought. Before launch, the team needs an inventory of what exists, what is moving, what is changing and which dependencies must continue working.
Inventory important URLs
Record pages that receive traffic, rank in search, are linked from campaigns or appear in external documents. Changed URLs should have intentional redirect mappings rather than relying on visitors to find the new location.
Account for forms and enquiries
List every form, recipient, notification and integration. A migrated contact form that silently stops sending email is a business failure even if the page itself loads correctly.
Protect analytics and measurement
Confirm analytics, Search Console, pixels, consent tools and conversion events before launch. Otherwise the organisation loses the ability to compare performance before and after the redesign.
Separate website DNS from email DNS
A website move may require changing A or CNAME records, but MX and other email-related records often need to remain. Document the DNS zone before making changes.
Prepare rollback and backups
Take a usable pre-launch backup and define what happens if the launch must be rolled back. Migration should have a recovery path, not only a launch plan.
What to do next
Use this as a working checklist for your organisation, then adapt it to the actual platform, risk and procurement context. If you are preparing a website project, takeover or ongoing support requirement, WebNT can review the scope with you before implementation begins.