Moving a WordPress site to a new host is one of those projects that sounds risky — visitors hitting a half-broken site, contact forms going dark, email bouncing — but it doesn’t have to be. With a little planning, you can move your site to faster LiteSpeed hosting while the old site stays live the entire time, then flip the switch only once everything checks out. This guide walks through the whole process in plain English, with the steps that actually keep you online.
Start With a Pre-Migration Checklist
Before you touch anything, take fifteen minutes to write down what your site is made of. A little inventory now saves a lot of guesswork later. Here’s what to capture:
- A full backup. Files and database both. Even if you’re using a migration plugin, keep an independent copy somewhere safe before you begin. If anything goes sideways, you can always roll back.
- Your current PHP version. You’ll find it under Tools → Site Health → Info in WordPress, or in your hosting control panel. Matching (or safely upgrading) the PHP version on the new host avoids surprise compatibility issues.
- A list of plugins and themes. Note which ones are active and which are paid — you may need license keys to reactivate them.
- Your email accounts. This is the step people forget. If your email is hosted on the same server as your website, you need a plan to recreate those mailboxes (and ideally export important mail) before DNS moves.
- Any custom DNS records. Things like SPF, DKIM, and MX records for third-party email or marketing tools. Screenshot your current DNS zone so nothing gets lost.
Choosing a Migration Method
There are two reliable ways to move a WordPress site, and the right one depends mostly on your site’s size and your comfort level.
The plugin route (easiest)
Tools like All-in-One WP Migration or Duplicate package your entire site — files, database, settings — into a single file you import on the new host. For most small-business sites this is the simplest, lowest-stress path. The main catch is file-size limits on free versions, which can matter for larger sites with lots of media.
The manual route (more control)
Here you copy the files yourself (over FTP/SFTP or a file manager) and export/import the database separately, then update wp-config.php with the new database details. It takes more steps but gives you full control and has no size limits. If you’re moving a big or unusual site, manual is often the safer bet — and it’s exactly the kind of work our team handles for you with a free managed migration.
Why LiteSpeed and LSCache Make WordPress Faster
WordPress builds most pages on the fly, querying the database every time someone visits. That’s flexible but slow under load. LiteSpeed web server speeds this up in two big ways, and they’re worth understanding before you migrate so you can take full advantage afterward.
- LiteSpeed handles traffic more efficiently than older setups, so your server stays responsive even when visitor numbers spike.
- LSCache — the free LiteSpeed Cache plugin — stores fully built pages at the server level and serves them instantly, skipping the database work entirely for repeat visitors. It also handles image optimization, minification, and other speed tweaks from one dashboard.
The practical result is faster page loads and a site that holds up better under traffic, which is a big part of why we run LiteSpeed across our cloud hosting plans.
The Zero-Downtime Migration, Step by Step
This is the heart of it. The trick to staying online is simple: your old site keeps serving visitors until you’ve fully tested the new one. Nobody hits the new server until you tell the internet to point there.
- Lower your DNS TTL first. A day or two before migrating, set the TTL (time to live) on your domain’s A record to something short, like 300 seconds. This tells the internet to check for changes more often, so when you do cut over, the switch propagates in minutes instead of hours.
- Copy the site to the new host. Use your chosen method to get all files and the database onto the LiteSpeed server. Don’t change DNS yet — the new copy just sits there quietly.
- Test using your hosts file. On your own computer, edit your local hosts file to point your domain at the new server’s IP address. Now only you see the new site at its real domain name, while the rest of the world still sees the old one. Click around, log in, test pages.
- Fix anything you find while the old site is still safely live. No pressure, no downtime — you can take your time.
- Switch DNS when you’re happy. Update the A record to the new server’s IP. Thanks to the lowered TTL, visitors start landing on the new site within minutes. Because both copies exist during the brief overlap, no one sees an error.
- Leave the old site untouched for a few days. Don’t cancel the old account immediately. Give DNS time to fully propagate and confirm everything’s running before you tear anything down.
Post-Migration Checklist
Once DNS has cut over, run through this list to make sure the new site is healthy:
- Install and activate your SSL certificate so the site loads over https without warnings.
- Re-save your permalinks. Go to Settings → Permalinks and click Save — this rebuilds your URL rules and prevents broken links and 404s.
- Install the LiteSpeed Cache plugin and enable caching. Start with the default settings, then turn on image optimization and minification once you’ve confirmed the site looks right.
- Test your contact forms. Actually submit one and confirm the message arrives.
- Send and receive a test email on each mailbox to confirm mail is flowing on the new server.
Common Gotchas (and How to Fix Them)
A few issues come up often enough that they’re worth knowing in advance:
- Mixed-content warnings. If some images or scripts still load over http after you add SSL, your browser flags the page as “not fully secure.” A plugin like Really Simple SSL, or a quick search-and-replace, cleans this up.
- Hardcoded URLs in the database. WordPress stores absolute URLs all over its database. If anything still points to a staging address or the old domain, run a proper search-and-replace tool (one that handles serialized data) rather than editing the database by hand.
- Stale cached pages. After making changes, you might still see the old version because LSCache is doing its job. Purge the cache from the LiteSpeed Cache plugin and refresh — this clears up the vast majority of “why isn’t my change showing?” moments.
Let Radiant Handle the Move
If any of this feels like more than you want to take on, you don’t have to do it alone. Radiant Solutions has been hosting Southern California businesses since 1997, and we offer free managed migrations — our team copies your site, tests it, coordinates the DNS cutover, and makes sure your forms and email work, all with zero downtime. You stay live the whole time while we do the heavy lifting. Ready to move to faster LiteSpeed hosting? Contact us and we’ll take it from here.