Add Website Hosts UK to your device
Install for quick access to hosting, tools, billing and support.
Learn how website migration works, what to prepare before moving hosts, how to reduce downtime and what to check after your website has been transferred.
Moving a website to a new host can sound stressful, especially if your website brings in enquiries, orders, bookings or regular visitors. The good news is that most website moves are straightforward when they are planned properly. The key is to understand what needs moving, take backups before anything changes, test the website on the new hosting, and only update DNS when you are ready.
A website migration is not just copying files from one place to another. A typical website may include website files, databases, email accounts, DNS records, SSL certificates, contact forms, redirects, cron jobs, plugins, themes and third-party integrations. Missing one of these can cause problems after the move, so it is worth following a clear checklist.
This guide explains how to move a website to a new host in a sensible order. It is written for small business owners, WordPress users, freelancers, agencies and anyone who wants to move hosting without unnecessary downtime or confusion.
To move a website to a new host, take a full backup of your files, databases and email, set up the new hosting account, upload the website, import the database, test everything before changing DNS, update the domain records, monitor DNS propagation, then check SSL, email, forms, speed and redirects once the site is live on the new server.
Websites are moved for many reasons. Sometimes the current hosting is too slow. Sometimes the website has outgrown its original package. Sometimes support is poor, email is unreliable, the control panel is difficult to use, or the website needs features the old host does not provide. A move can also happen when a business changes developer, upgrades to a better platform, or wants hosting closer to its main audience.
For a small business, the most common reason is performance. A website that was once quick can become slow as more pages, plugins, images, products and visitors are added. If the website regularly times out, reaches resource limits or feels slow inside WordPress, moving to a better hosting setup can make the site easier to manage and more reliable for visitors.
Another common reason is growth. A simple brochure website may start on basic shared hosting, then later add WooCommerce, booking forms, customer accounts, quote forms, landing pages, email marketing tools or live chat. At that point, the website may need a more suitable hosting environment, such as upgraded UK Web Hosting, WordPress Hosting, Cloud Business Hosting, VPS Hosting or VDS Hosting.
Before touching DNS or cancelling your old hosting, make a list of everything connected to the website. This is one of the most important parts of the migration. A website can look simple from the outside but still rely on several moving parts behind the scenes.
A standard WordPress website usually has two main parts: the website files and the database. The files include WordPress core files, themes, plugins, uploads, images and configuration files. The database stores pages, posts, settings, users, orders, form entries and other dynamic content. Both parts are needed for the website to work correctly.
Static HTML websites are usually simpler because they may only need files moving. However, they can still rely on redirects, forms, DNS records, SSL certificates and email routing. If your website uses custom scripts, APIs or scheduled tasks, those also need checking before the move.
The best migration starts with choosing the right destination. Moving to a new host is a good opportunity to make sure the hosting plan matches your website now, not how it looked when it first launched. A small brochure website may only need a simple shared hosting package, while a busy WordPress site, WooCommerce shop or customer portal may need more resources.
If you run WordPress, a plan built for WordPress Hosting can be a sensible choice. If you prefer a straightforward control panel with email, SSL and website management tools, DirectAdmin Hosting may be a good fit. If your business relies heavily on the website for leads or orders, Small Business Hosting or Business Hosting may be more suitable.
For heavier websites, applications or projects that need root access, a VPS may be the next step. If you need dedicated resources and stronger performance isolation, a VDS may be the better option. The aim is not to choose the most powerful plan by default. The aim is to choose hosting that gives the website enough room to run reliably.
Never begin a migration without a backup. A full backup gives you a safety net if something goes wrong, if a file is missed, or if the new hosting needs to be rebuilt. Ideally, you should keep a copy away from both the old host and the new host, such as on your local computer or secure cloud storage.
For a WordPress website, the backup should include all website files and the database. If you use WooCommerce, membership plugins or booking tools, make sure the backup is recent. Orders, customer registrations and bookings can change quickly, so timing matters. If the website receives frequent orders or form submissions, you may need to put the site into maintenance mode briefly during the final sync.
If email is hosted with your current provider, back that up too. Website migrations often focus on files and databases, but mailbox data can be just as important. If you are moving email to a new platform, check whether existing messages, folders, forwarders and aliases need to be copied.
Once you have a backup, prepare the new hosting account. Add the domain name, create the website space, set the correct PHP version if required, create the database, and prepare any email accounts that will be hosted on the new platform. This should be done before DNS is changed so the website can be tested properly.
If your website uses WordPress, check that the new hosting supports the required PHP version, database version and PHP extensions. Most modern WordPress websites need a current PHP version, enough memory, HTTPS support and suitable database performance. If your website uses older plugins or a custom theme, compatibility testing is especially important.
If your current site uses a control panel, moving to another control panel can make the process easier if both systems support standard backup formats. However, even when control panels differ, the process is usually the same: move files, move databases, update configuration, test, then point the domain to the new host.
Website files can usually be moved using a control panel file manager, FTP, SFTP or a migration tool. For WordPress, this means moving the full WordPress directory, including the wp-content folder, themes, plugins and uploads. The uploads folder is especially important because it contains images, media files and documents used across the site.
For static HTML websites, the files may simply need uploading to the correct public web directory on the new hosting account. This is often called public_html, htdocs or something similar depending on the hosting platform.
Take care not to accidentally overwrite important files on the new hosting account. If the host has placed a default index page in the web directory, it may need replacing with your actual website files. Once uploaded, check file permissions and folder structure. A common migration problem is placing files one level too deep, which can cause the homepage not to load correctly.
If the website uses a database, export it from the old host and import it into the new one. WordPress, WooCommerce, forums, customer portals and many content management systems rely on a database. Without it, the website may load only partially or not at all.
After importing the database, update the website configuration file with the new database name, username, password and host. For WordPress, this is usually done in the wp-config.php file. If these details are incorrect, the website will usually show a database connection error.
If the domain name is staying the same, the database may not need URL changes. If the website is also changing domain, extra steps are needed to update internal URLs, media paths and redirects. For a same-domain hosting move, the main task is usually ensuring the database imports cleanly and the configuration points to the new database.
This is where many rushed migrations go wrong. You should test the website on the new hosting before pointing live traffic to it. Some hosts provide a temporary URL or preview link. Another method is to edit your local hosts file so your own computer sees the website on the new server while everyone else still sees the old one.
Testing before DNS changes helps you catch problems early. You can check whether pages load, images appear, forms work, admin logins function, plugins behave correctly and the database connection is stable. If you find an issue, visitors are not affected because the live domain still points to the old hosting.
For WordPress websites, log in to the dashboard, check plugins, view important pages, test forms, review menus and make sure media files load properly. For WooCommerce websites, test product pages, basket, checkout and order emails. For service websites, test quote forms, contact forms and phone number links.
Email is one of the easiest parts of a migration to overlook. If your domain email is hosted with the old provider, changing DNS without preparing email can interrupt mail delivery. Before updating nameservers or MX records, decide whether email is staying with the old provider, moving to the new host, or moving to a separate email service.
If email is moving to Website Hosts UK, create the required mailboxes first and make a note of the new mail settings. If you need professional email using your own domain, you can review Business Email Hosting. Make sure you also copy or recreate forwarders, aliases and autoresponders where needed.
DNS records such as MX, SPF, DKIM and DMARC help control email delivery and authentication. If these are missed or changed incorrectly, emails may bounce, land in spam or fail authentication checks. Always record the old email DNS records before changing anything.
Once the website has been copied, tested and email has been prepared, it is time to point the domain to the new hosting. This usually means updating nameservers or changing DNS records such as the A record for the main domain and the CNAME record for www.
If you change nameservers, DNS management moves to the new nameserver provider. If you only change the A record, DNS may remain managed where it is. The right option depends on how your domain and hosting are set up. If you have several existing DNS records for email, verification, analytics, CRM systems or third-party tools, be careful not to lose them when changing nameservers.
After DNS changes are made, they need time to propagate. During this period, some visitors may see the old server while others see the new one. This is normal. You can use the DNS Propagation Checker to see how DNS updates are appearing from different locations. You can also use DNS Lookup to check current records for the domain.
After the domain points to the new hosting, check the SSL certificate. A website should load securely using HTTPS, especially if it has forms, login areas, checkout pages or customer data. If SSL is not installed or not active on the new hosting, visitors may see browser warnings.
Many hosting platforms can issue an SSL certificate once DNS points correctly to the new server. If the certificate does not issue immediately, DNS may not have fully propagated yet, or the domain may not be resolving correctly. You can use the SSL Checker to check certificate details and expiry.
Once SSL is active, test both the http:// and https:// versions of the site. Ideally, insecure HTTP traffic should redirect to HTTPS. Also check the www and non-www versions of the domain so visitors and search engines land on the correct version.
Once DNS has updated and SSL is working, test the live website carefully. Do not assume the move is complete just because the homepage loads. Check the pages and features that matter most to the business.
A local business should test contact forms, enquiry buttons, phone number links and location pages. An online shop should test product pages, basket, checkout, payment redirects and order emails. A membership website should test login, account pages and protected content. A brochure website should check menus, images, downloads, redirects and forms.
You can also use the Website Status Checker to confirm the site is responding and the Website Page Speed tool to get a quick view of loading performance after the move.
One of the biggest mistakes is cancelling the old hosting too soon. Keep the old hosting active until the website, email, DNS, SSL and forms have all been tested on the new host. DNS propagation can take time, and you may need access to the old account if something was missed.
Another common mistake is forgetting email. A website may move perfectly while email breaks because MX records were changed, mailboxes were not recreated, or authentication records were missed. If email is important to your business, plan that part of the migration carefully.
Rushed DNS changes can also cause problems. If you change nameservers without copying existing DNS records, third-party services may stop working. This can affect email, verification records, payment systems, CRM tools, analytics platforms and other connected services.
Imagine a local building company has a WordPress website with service pages, project galleries, testimonials and a quote request form. The site has become slow on the old host, especially when updating plugins or uploading project photos. The business decides to move to better WordPress hosting.
The sensible process would be to back up the WordPress files and database, create the new hosting account, upload the files, import the database, update the database connection details and test the site before changing DNS. The quote form should be tested carefully because that is where new business comes from. Project galleries should also be checked because missing images can make the company look less professional.
Once the site works on the new server, DNS can be updated. After propagation, SSL should be checked, the contact form tested again, and email delivery confirmed. The old hosting should remain active for a short period in case anything needs to be recovered.
An online shop needs extra care because orders, customer accounts and stock levels can change during the migration. If the store receives regular orders, timing is important. You may need to schedule the move during a quieter period or briefly pause checkout while the final database copy is taken.
After moving the files and database, test product pages, basket, checkout, payment gateways, order confirmation emails and customer account pages. A shop migration is not complete until you know customers can place orders successfully and the business receives the correct notifications.
If your shop is growing, it may also be a good time to consider hosting built for ecommerce, such as WooCommerce Hosting. A shop usually needs more predictable performance than a simple brochure website because checkout speed and reliability directly affect sales.
If you are comfortable with hosting control panels, FTP, databases, DNS and SSL, you may be able to move a simple website yourself. Static HTML websites are usually easier to move than dynamic websites. WordPress migrations are manageable for many users, but they still require care.
If the website is business-critical, receives orders, has custom code, uses multiple integrations or includes important email accounts, getting help is often the safer option. A failed migration can cost more in lost enquiries and downtime than doing it properly in the first place.
If you want hosting with more hands-on help, Managed Hosting may be worth considering. Managed support can be useful when you want the website looked after without handling every technical detail yourself.
It does not have to. If the website is copied and tested before DNS is changed, downtime can usually be reduced. Some visitors may briefly see the old server while DNS updates, but careful planning helps avoid major disruption.
DNS changes can appear quickly in some locations and take longer in others. During propagation, different networks may see different results. You can check progress using the DNS Propagation Checker.
Not always. Hosting and domain registration are separate services. You can move the website hosting while keeping the domain registered where it is, as long as DNS is updated correctly.
Usually not. Website files and email are separate. If your email is hosted with your old provider, you need to plan whether mailboxes, forwarders and DNS records are moving too.
Yes. A WordPress site can be moved manually by copying the files, exporting and importing the database, then updating the configuration file. Migration plugins can make the process easier, but they are not the only method.
Yes, for a short period. Keep the old hosting active until the new website, email, DNS, SSL, redirects and forms have all been tested. Cancelling too early can make recovery harder if something was missed.
If you are planning to move your website and are not sure which hosting option is right, start with our Start Here page or compare our UK Web Hosting plans.
For WordPress websites, take a look at WordPress Hosting. For business websites that need more performance and support, explore Business Hosting or Managed Hosting.
You can also use our free Website Tools to check DNS, SSL, website status and page speed before and after your move.
Moving a website to a new host is much easier when it is treated as a planned process rather than a rushed change. Start with backups, understand what needs moving, prepare the new hosting, test before changing DNS, then monitor the site carefully after it goes live.
The most important rule is simple: do not cancel the old hosting until you are confident everything works on the new one. Check the website, email, SSL, forms, checkout, redirects and DNS records first. A careful migration protects your visitors, your enquiries and your business reputation.
Whether you are moving a small brochure website, a WordPress site, a WooCommerce shop or a growing business platform, the right hosting move can give your website a faster, cleaner and more reliable foundation for the future.
Add Website Hosts UK to your device
Install for quick access to hosting, tools, billing and support.