How to Switch Web Hosting Without Breaking Your

Your website is slow, your host’s support takes days to respond, and the renewal price just jumped 40%. You know you need to move — but you’re worried about losing data, breaking your site, or disappearing from Google. The good news: switching web hosting is far more straightforward than most people think, and this guide walks you through every step.

Why UK Site Owners Switch Web Hosts

The frustration is usually one of four things. Performance: your site has slowed down because the host has oversold their shared servers and your pages are crawling. Price: the introductory rate you signed up on has doubled or tripled at renewal, without any improvement in service. Reliability: your site keeps going down at inconvenient times, and the uptime you were promised bears no resemblance to reality. Support: when something goes wrong, you’re waiting days for a ticket response that doesn’t actually fix the problem.

All of these are legitimate reasons to move. Slow load times directly affect your Google rankings — Core Web Vitals scores are now a ranking signal, and a sluggish server is one of the most common causes of a poor LCP score. If you’re not sure which type of hosting to move to, read our guide to shared hosting, VPS, and dedicated servers before you choose your new host.

Before You Start — What the Process Actually Looks Like

The golden rule of any hosting migration: never cancel your old host until your new one is confirmed working. You’ll be paying for two hosts briefly — this overlap is deliberate and worth the small cost. The active work typically takes one to two hours. DNS propagation then runs in the background for 24–48 hours, during which your site stays live on the old host while the world catches up to the new one. Nothing to worry about during that window if you follow the steps below.

Step 1 — Back Up Everything Before You Touch Anything

A full backup is non-negotiable, regardless of what your new host promises about free migrations. You need three things: your website files, your database, and your email (if you host email on the same account).

How to back up your files via cPanel or Plesk

Most hosts use cPanel or Plesk. Both have a backup tool you can access from the main dashboard. In cPanel, look for Backup Wizard — it walks you through downloading a full account backup as a single compressed file. In Plesk, go to Websites & Domains → Backup Manager. Download the backup to your computer before doing anything else.

How to export your WordPress database

If your site runs WordPress (or any CMS), the database contains all your posts, pages, settings, and users — it’s just as important as the files. In cPanel, open phpMyAdmin, select your WordPress database from the left panel, click Export, choose Quick, and click Go. This downloads a .sql file. Keep it somewhere safe.

Don’t forget your email

If you host email on the same server as your website, export your mailboxes before migrating. Hosting migrations don’t automatically carry over historical email messages — only the account configuration. Most email clients (Outlook, Thunderbird) can export mailboxes locally.

Step 2 — Sign Up to Your New Host First

Set up the new hosting account and have it ready before you move a single file. When evaluating a new UK host, look beyond the introductory price — check what the renewal rate is, whether their data centres are UK-based (important for speed to UK visitors), what support channels they offer, and which control panel they use. If you’re moving to a higher tier, our guides to Linux VPS hosting and managed WordPress hosting cover what to look for. For a broader comparison of UK hosts, see our website hosting guide.

Step 3 — Transfer Your Files to the New Host

There are two main ways to move your files: download them from the old host and re-upload to the new one, or use the new host’s migration tool. The migration tool is convenient but often incomplete — it may not transfer databases, email, or non-standard directory structures. Always verify manually even if you use an automated tool.

Using FTP to transfer your files

FileZilla is free and the most widely used FTP client. Connect to your old host using the FTP credentials from your hosting dashboard, download your public_html folder (or equivalent) to your computer, then connect to the new host and upload the same folder. For most small sites this takes 10–30 minutes depending on file size.

Using cPanel File Manager if you prefer browser-based

If you’d rather not install FTP software, both cPanel and Plesk have a browser-based file manager. Compress your public_html folder into a .zip on the old host, download it, then upload and extract it in the file manager on the new host. Slower than FTP for large sites but fine for smaller ones.

Step 4 — Move Your Database

Files alone aren’t enough for WordPress or any database-driven site. You need to transfer the database separately and update your configuration to point at it.

Create a new database on your new host

In cPanel on the new host, open MySQL Databases. Create a new database, create a new database user, and assign the user to the database with all privileges. Note down the database name, username, and password — you’ll need these in a moment.

Import your .sql file

Open phpMyAdmin on the new host, select the empty database you just created, click Import, choose your .sql file, and click Go. For large databases that exceed phpMyAdmin’s upload limit, use the BigDump tool or ask your new host’s support — most will import it for you.

Update wp-config.php with the new database credentials

Open your wp-config.php file (in the root of your WordPress install) and update these three lines with the new database name, username, and password you created above:

define( 'DB_NAME', 'your_new_db_name' );
define( 'DB_USER', 'your_new_db_user' );
define( 'DB_PASSWORD', 'your_new_db_password' );

Save the file. This is a plain text edit — not complex development work.

Step 5 — Test Your Site on the New Host Before Changing DNS

This is the step most guides skip — and it’s one of the most important. You can preview your site on the new server before pointing your domain at it, so any problems are caught before anyone else sees them.

Using a temporary URL from your new host

Many hosts provide a temporary preview URL (sometimes called a staging URL or server IP address). Log into your new host’s control panel and look for a temporary domain or the server’s IP address — you can often browse your site at http://SERVER.IP.ADDRESS/~username/. Check with your new host’s support if you can’t find it.

The hosts file trick

A more reliable method: edit your computer’s hosts file to point your domain at the new server’s IP — but only on your machine. Everyone else still sees the live site on the old host while you browse the new one. On Windows, the hosts file is at C:\Windows\System32\drivers\etc\hosts (open Notepad as Administrator). On Mac/Linux it’s at /etc/hosts. Add a line like:

123.456.789.0   yourdomain.co.uk www.yourdomain.co.uk

Replace 123.456.789.0 with your new server’s IP address. Browse your site normally — your computer will load it from the new host. When you’re done testing, delete that line from the hosts file to return to normal.

Step 6 — Install Your SSL Certificate on the New Host

SSL certificates don’t transfer between hosts — you need a new one on the new server. The good news: Let’s Encrypt free SSL is available through cPanel and Plesk on virtually every modern host. In cPanel, look for SSL/TLS or Let’s Encrypt SSL in the security section. It takes about two minutes to activate. Do this before you point your DNS — a site without SSL shows “Not Secure” warnings in browsers and carries a minor SEO penalty.

Step 7 — Point Your DNS to the New Host

DNS is the address book that tells browsers where your site lives. To switch your site to the new host, you update the nameservers at your domain registrar (where you registered your domain — GoDaddy, Namecheap, 123-reg, etc.) — not at either hosting account.

Where to find your new host’s nameservers

Your new host’s nameservers are in their welcome email and usually in the control panel under “Account Details” or similar. They look like ns1.hostname.com and ns2.hostname.com.

How to update nameservers at your registrar

Log into your domain registrar, find the domain, and look for “Nameservers” or “DNS settings”. Replace the existing nameservers with the two your new host provided. Save the change. This triggers propagation — the process by which DNS servers around the world update their records to point your domain at the new host.

Understanding DNS propagation

Propagation takes up to 48 hours, though most visitors will see the new host within a few hours. During this window, some people will still hit the old server while others reach the new one — this is normal and expected. Use whatsmydns.net to check how propagation is progressing from different locations around the world.

Step 8 — Cancel Your Old Host Only When You’re Certain Everything Works

Wait a minimum of 48 hours after DNS has fully propagated and you’ve confirmed the site is loading correctly from the new host before cancelling the old account. Some hosts delete account data immediately on cancellation — take one final backup from the old account before you close it, just in case.

Common Mistakes That Cause Problems

• Cancelling the old host too soon. The single most common cause of unnecessary downtime. Always wait for full propagation confirmation.
• Skipping the SSL on the new host. Visitors get browser security warnings the moment DNS switches over. Set it up before you point DNS.
• Trusting the host’s free migration service completely. Automated migrations often miss databases, email, or non-standard configurations. Always verify manually.
• Pointing DNS before testing. If there’s a problem with the new setup, it immediately affects all visitors. Use the hosts file trick to test first.
• Hardcoded URLs breaking after a domain change. If you’re also changing domain names, run a search-and-replace on your database to update any hardcoded old domain references. The Search Replace DB tool handles this safely.

If you’re planning a move to a more powerful setup — such as a dedicated server — the same migration steps apply, though you’ll also need to configure the server environment itself. For most small businesses stepping up from shared hosting, a managed VPS is the sweet spot: more control and performance without the complexity of full server management.

Migration Checklist

• Full backup downloaded (files + database + email)
• New hosting account set up and active
• Files transferred to new host
• Database created on new host and .sql file imported
• wp-config.php (or equivalent config) updated with new DB credentials
• Site tested on new host before DNS change (hosts file or temp URL)
• SSL certificate installed on new host
• Nameservers updated at domain registrar
• DNS propagation confirmed (48 hours)
• Old host cancelled and final backup taken

Follow this list in order and you’ll complete the migration without downtime, without data loss, and without any impact on your search rankings.