A hosting move should not be the moment a customer finds a broken contact form, an unavailable shop, or last month’s blog posts missing. A clear website hosting migration checklist gives you control of the process, whether you run a small business website, a charity site, a portfolio, or an online store.
Moving to a more dependable hosting provider can improve speed, security and the support available when you need it. However, the move itself needs planning. The aim is not simply to copy files from one server to another. It is to transfer the complete working website, confirm it behaves correctly, and switch visitors over with as little disruption as possible.
Before your website hosting migration
Start by deciding what is actually moving. In most cases, this includes your website files, database, email accounts, domain settings, SSL certificate arrangements and any scheduled tasks or redirects. Missing one of these can lead to avoidable problems after launch.
Take time to review the current account before cancelling anything. Make a note of the domain registrar, hosting login, control panel access, website platform, PHP version, database details and email configuration. If a developer built or maintains the site, ask them for these details early. Waiting until the day of migration often turns a straightforward job into an urgent one.
It is also wise to identify services connected to the website. These might include payment providers, appointment booking systems, newsletter platforms, analytics tools, maps, live chat or stock management software. Most will continue to work without changes, but some rely on specific domain records, server settings or email addresses.
Choose the right time to move
For a brochure website with modest traffic, migration can often be completed at any sensible time. For an ecommerce site, membership platform or business that receives regular enquiries, choose a quieter period. Avoid moving during a sale, product launch, major campaign or the hours when your customers are most likely to place orders.
Lower traffic does not mean no traffic. Let relevant staff know when the migration is scheduled, and make sure someone can check the site after the switch. If orders or form enquiries are business-critical, keep a record of activity shortly before and after the move so you can confirm nothing has been missed.
Back up before making changes
A full backup is your safety net. Create and download a copy of the website files and database before beginning. If your site uses a content management system such as WordPress, make sure the backup includes uploads, themes, plugins and the database content. A database alone will not restore images and design files; files alone will not restore pages, products, users or settings.
Keep the backup somewhere separate from both hosting accounts, such as secure local storage or a trusted cloud storage service. It is also sensible to check that the backup is complete and can be opened. A backup that cannot be restored is not useful when you need it.
Your website hosting migration checklist
Work through the following checks in order. They reduce the risk of an incomplete transfer and make it much easier to find the cause if something does not look right.
- Confirm access to both accounts. You need working logins for the existing host, the new hosting account, your domain registrar and any third-party DNS service. Enable access for the person carrying out the migration, but do not share passwords by email.
- Record current DNS settings. Copy all existing DNS records, including A, CNAME, MX, TXT and any verification records. MX records are particularly important if you use email on your domain. An overlooked record can stop email arriving even when the website itself is working.
- Copy website files and databases. Transfer the site to the new hosting account, then import the database and update the website configuration file with the new database name, user and password where needed.
- Match the technical environment. Check PHP version, database version, memory limits, file permissions and required extensions. An older site may depend on a particular setting, while a newer site may benefit from an up-to-date version. Do not change everything at once unless there is a clear reason to do so.
- Set up email accounts and forwarding. Recreate mailboxes, aliases, forwarding rules and autoresponders before changing DNS. Where possible, copy important existing messages or retain access to the old mailbox for a short period.
- Install and check SSL. Your site should load securely over HTTPS before the public switch. Check that the certificate covers both the main domain and the www version if both are used, and confirm insecure-content warnings do not appear on key pages.
- Test the new copy privately. Use a temporary address, preview tool or hosts-file preview supplied by your host to inspect the transferred site before pointing the domain. This allows you to test without sending normal visitors to the new server too soon.
- Update DNS and monitor propagation. When testing is complete, point the domain to the new hosting service. DNS changes can take time to update across networks, so some visitors may briefly reach the old server while others see the new one. Keep the old account active during this period.
- Test again as a customer would. Open the site on a mobile phone and desktop browser. Submit contact forms, make a test purchase where appropriate, log in to customer areas, check search, inspect images and confirm emails are being sent and received.
- Keep the old hosting live temporarily. Do not cancel it immediately after the domain change. Retaining it for several days gives DNS time to settle and provides a fallback if an overlooked issue appears.
Test more than the homepage
A homepage can look perfect while important parts of the site fail. Check a representative range of pages, especially those that generate leads or revenue. For a service business, that may mean the contact form, booking page, downloadable brochure and confirmation emails. For a shop, test product pages, basket, checkout, payment confirmation, stock updates and customer emails.
Look closely for small but damaging issues: broken images, missing fonts, old links, mixed-content warnings, error pages and forms that appear to send but never arrive. Check website forms with a real email address you can access. If messages are sent from the website using your domain, ensure the required email authentication records are in place.
If your website has a cache, clear it after migration. Cached files can make it appear that the site has not updated, or can show visitors an outdated version. Content delivery services and security tools may also need their settings refreshed to recognise the new server.
Protect search visibility and customer trust
Changing hosting should not require changing website addresses. Keep the same domain and page URLs wherever possible. If URLs must change as part of a wider rebuild, put proper redirects in place so visitors and search engines are directed to the right replacement pages.
Check that search engines are not blocked from the new site. Temporary development settings can accidentally be left enabled, preventing indexing. Review the robots settings, sitemap, analytics tracking and any conversion tracking after the move. This is especially useful for spotting a drop in enquiries or traffic that needs investigation.
Communications depend on the scale of the move. Most small brochure sites do not need a public announcement if downtime is avoided. If you run an online shop, client portal or busy membership site, a short message to customers can be considerate. Set expectations without causing unnecessary alarm, and provide another way to contact you if needed.
Common migration mistakes to avoid
The most common error is cancelling the old hosting too early. DNS can take time to update, and old email or website settings may still be serving some visitors. Keep the previous account available until you have confirmed that the new service is stable.
Another mistake is treating email as separate from the website. It is separate in technical terms, but customers will experience it as one problem if messages stop arriving. Check every mailbox and DNS record carefully, particularly if email is hosted elsewhere.
Finally, avoid using a migration as an opportunity to install a major batch of updates, redesign the site and change plugins all on the same day. Those changes may be worthwhile, but they make fault-finding harder. Move first, verify the site, then schedule improvements in manageable stages.
When to ask for hosting migration support
Many standard websites can be moved with a clear process and a little care. Yet professional help is worthwhile if your site has an online shop, several databases, bespoke coding, business-critical email, high visitor numbers or little room for disruption. A good hosting provider should explain what is included, what information is needed from you and how the site will be tested before the DNS change.
For UK businesses that value clear, human assistance, PacWebHosting.uk can help make the move feel less technical and more manageable. Reliable hosting, daily backups, SSL protection and responsive support give your site a stronger foundation after migration, not just on the day it moves.
A successful move is measured by what your customers do not notice: the site stays available, emails keep flowing and every important page continues to work. Give the process the planning it deserves, and your new hosting account can become a quieter, more dependable part of running your business.
