Practical resources for migrations, DNS, and hosting changes

Start Here

If you are using HostCheck for the first time, start with the guides that explain how to test a website safely before changing DNS. Those articles cover the basic workflow: prepare the new server, preview the site on the target IP, inspect important pages and forms, and only then update DNS records. This sequence matters because most migration problems are caused by switching traffic before the replacement server has been checked thoroughly.

This section is designed for visitors who want the shortest path to a reliable launch. Rather than reading every article in the blog, begin with the core migration and DNS pages below. They provide the minimum background needed to avoid the most common mistakes, including broken virtual hosts, missing SSL configuration, stale DNS records, and incomplete content transfers.

Migration Planning

Migration planning resources focus on what needs to happen before a cutover window begins. That includes taking verified backups, lowering DNS TTL values ahead of time, matching server software versions where possible, checking mail routing, and making sure there is a rollback option if the new environment does not behave as expected. Good planning reduces downtime far more effectively than rushing to fix issues after a DNS switch has already gone live.

If you are moving a CMS site such as WordPress, these articles are especially important because application-level settings can break even when files and databases appear to have transferred correctly. Redirect behaviour, upload paths, PHP extensions, and plugin compatibility often need explicit review. The migration planning articles below help you work through those risks methodically instead of discovering them in production.

DNS and Infrastructure Fundamentals

Understanding the infrastructure behind a migration makes troubleshooting much easier. DNS issues are often blamed for problems that actually come from application configuration, and application bugs are often blamed on DNS when propagation is still incomplete. The guides in this section explain the parts that are most often confused: nameservers versus records, how TTL affects propagation windows, and which record types control web traffic, email routing, and third-party verification services.

These background articles are useful whether you manage a single brochure website or a large estate of domains. They provide the context needed to interpret what you see during a cutover, especially when different users appear to reach different servers or when email and website behaviour diverge after a hosting change.

Troubleshooting and Technical Reference

When a preview does not behave as expected, the fastest fix usually comes from identifying which layer is failing. Some issues are caused by routing and host headers, others by reverse proxy behaviour, and others by the target server returning a specific HTTP error code. This section groups the technical reference articles that help you diagnose those cases with less guesswork.

These guides are particularly useful if the website looks correct when accessed one way but not another, or if only some pages fail during testing. For example, previewing by IP alone may show the wrong site on a shared server, while a 403 or 500 response in a preview may point to permissions, rewrites, or server configuration instead of DNS. The articles below explain those patterns in practical terms.

Security, Performance, and Operations

Once a migration is technically complete, operational checks still matter. A server can load pages successfully and still have problems with SSL, caching, missing security headers, weak file permissions, or poor performance under load. The articles in this section are intended for the verification stage after the core preview looks correct and before the old environment is fully retired.

These resources are also useful for routine website maintenance outside of migration work. If your site has already moved successfully, you can use them to tighten security, improve performance, and review ongoing operational practices such as certificate handling, patching, and post-launch monitoring.

Suggested Workflow for a Safe Launch

If you are preparing for a live switch, this is the workflow we recommend visitors follow when using the articles in this resource centre:

1. Review the migration planning guides and prepare backups, rollback options, and DNS timing.
2. Read the DNS fundamentals if you need to confirm how records, nameservers, and propagation will affect the launch.
3. Use HostCheck to preview the target server with the correct domain and inspect key templates, forms, media, and redirects.
4. If anything fails, use the troubleshooting and technical reference material to identify whether the issue is related to virtual hosting, reverse proxying, or server response codes.
5. Before retiring the old environment, run through the security and operations checks so the new server is not only live, but properly maintained.

Who This Page Is For

This page is intended for web developers, freelance site managers, agencies, hosting support teams, and business owners who need a practical starting point for website infrastructure changes. Some visitors will only need a simple DNS explanation, while others will be coordinating multi-step migrations with CMS platforms, CDN layers, SSL certificates, and email dependencies. The goal of the resource centre is to serve both groups by making the most relevant material easier to find.

We keep this page deliberately focused on evergreen guidance that supports the main HostCheck tool. Instead of acting as a general marketing page, it works as a structured library of articles that help visitors understand what to test, what can go wrong, and how to reduce risk before they move live traffic.

How These Resources Are Maintained

HostCheck articles are written to support real migration work, not generic traffic acquisition. We group the most useful pages here, review them when technical practices change, and update or correct them when needed. For details on how content is reviewed, see our Editorial Policy.