A hosting move should not mean your website disappears for a day, your business email stops working or customers are met with an error page. Knowing how to migrate website hosting properly comes down to planning the order of events: copy the site, test it privately, then direct your domain to the new server only when everything is ready.
For a small business, charity or sole trader, the aim is simple. Keep the website, email and enquiries running while moving to hosting that offers better support, performance or security. The technical work matters, but it does not need to be complicated when it is approached methodically.
Start with a clear picture of what you are moving
Before opening a new hosting account or changing any settings, identify every service connected to your current provider. A website may include more than its visible pages. It could rely on a database, contact forms, image files, a content management system such as WordPress, scheduled tasks, email inboxes and SSL security.
Make a short record of your domain name, current hosting login, domain registrar, website platform and email addresses. If your domain and hosting are held with different companies, note this clearly. You can move the hosting without transferring the domain itself, but you will still need access to the domain’s DNS settings to point it at the new server.
It is also worth checking how much storage your site uses and whether it has any special requirements. An online shop, membership site or booking system may need a little more care than a brochure website because new orders, bookings or user data could be added while the move is taking place. In these cases, arrange the final copy and switch-over at a quieter time.
Take a complete, usable backup first
A backup is your safety net, not a formality. Download a full copy of the website files and export the database before making changes. For WordPress, the files include themes, plugins, uploads and core software, while the database contains pages, posts, settings and form entries.
Do not assume that an old automatic backup is enough. Check its date and make sure you can access it. Keep a copy somewhere separate from the existing hosting account, such as secure local storage or approved cloud storage. If anything unexpected happens during the migration, you need a version of the site that you can restore.
If your email is hosted with the same provider, consider that separately. Website files do not normally include mailbox contents. You may need to recreate mailboxes at the new host, copy existing messages or use an email migration service. For many businesses, protecting email continuity is just as important as keeping the website available.
Set up the new hosting account before changing DNS
Create the new hosting account and add the domain name to it. At this stage, do not alter the domain’s nameservers or DNS records. Your live website should remain where it is until the replacement has been copied, checked and prepared.
Upload or transfer the website files to the correct web root folder on the new account. Import the database, then update the website configuration file with the new database name, username, password and server details. The exact process varies by platform, but the principle is the same: the new copy of the website must be able to find its own data.
For WordPress, migration tools can reduce manual work, particularly for a straightforward site. However, a plugin is not always the best option for a large website, a site with custom code or an online shop with regular transactions. A manual migration or assistance from your hosting provider can provide more control in those situations.
Install an SSL certificate on the new hosting account before the site goes live. Modern browsers expect websites to use HTTPS, and visitors may be wary if they see a security warning. Check that your certificate covers the correct version of the domain, including www if you use it.
Test the new copy before making it public
Testing is the step that prevents a small issue becoming a public one. Most hosting providers offer a temporary address, preview URL or a way to view the website before DNS changes take effect. Use this to inspect the new copy without sending ordinary visitors there.
Check more than the home page. Visit key service pages, submit a contact form, test site search if you use it, and open pages containing images or downloads. Sign in to the administration area and confirm that you can update content. If you sell online, place a test order where possible and check payment, order emails and stock updates.
Pay close attention to links, images and redirects. A website copied from an old server can still contain references to its previous location. These may cause mixed-content browser warnings, broken images or redirects that send visitors back to the old account.
This is also a sensible moment to review basic security. Update the website platform, themes and plugins where appropriate, remove unused accounts and make sure the new hosting account has strong, unique passwords. Migration is a useful opportunity to tidy up, but avoid major redesigns or software changes immediately before the switch. Move first; improve later.
How to migrate website hosting with minimal disruption
Once the site works correctly on the new account, you can direct the domain to it. This is done by changing either the nameservers or individual DNS records at the company managing your domain name.
Changing nameservers hands DNS management to the new hosting provider. This can be convenient when the hosting account is set up to manage the website and email records for you. Updating individual records gives you more control and can be preferable where email, marketing tools or other services are managed elsewhere.
The right route depends on your existing setup. If business email is provided by Microsoft 365 or another specialist service, changing nameservers without recreating the required email records can interrupt mail delivery. Record your current MX, SPF, DKIM and any other important DNS entries before changing anything. These records are often overlooked, yet they are essential for reliable business email.
DNS changes can take time to spread across the internet. Many changes are visible within a few hours, but allow up to 24 to 48 hours for full propagation. During that window, some visitors may reach the old server while others see the new one. Keep the old hosting active until you are confident the new site and email are working correctly for everyone.
For a frequently updated website, make a final backup or database export immediately before changing DNS. Restore that final copy to the new server if needed. This reduces the risk of losing recent enquiries, orders or content changes made after the first migration copy.
Check email carefully after the move
Email problems are one of the most common migration frustrations because the website can appear fine while messages stop arriving. Once DNS has been updated, send test messages to and from each important mailbox. Check webmail or your email application, then confirm messages are not being marked as spam.
If mailboxes are moving to the new host, create them before the DNS switch and configure them on staff devices after the new mail service is active. Use the correct incoming and outgoing server settings supplied by the new provider. Avoid deleting the old mailboxes until you have confirmed that historic messages are safely copied and new mail is being received.
If you use Microsoft 365, keep its DNS records in place. Your web hosting move should not affect it, provided the relevant email records are preserved accurately.
Keep the old account briefly, then monitor the new one
Do not cancel the previous hosting service the moment the new site loads. Keep it available for at least several days, and longer if your DNS settings have a high time-to-live value or your site receives regular submissions. This gives you a fallback while you monitor the new account.
During the first few days, check website uptime, contact-form notifications, error logs and email delivery. Ask a colleague or trusted customer to view the site from a different connection, as your own browser or network may still be showing a cached version. Confirm that backups are now running on the new hosting service and that you know how to restore one if required.
A good migration is rarely about rushing a technical change. It is about protecting the services your organisation relies on and making each change at the right time. If you would rather not handle the transfer yourself, Pac Web Hosting can provide migration assistance so you have practical support while your website settles into its new home.
