This post may contain affiliate links, meaning if you decide to make a purchase via my links, I may earn a commission at no additional cost to you. See my disclosure for more info.

Moving your blog to a new host feels like open-heart surgery on your business. Your traffic, your rankings, your email signups — all of it depends on a site that stays up while everything underneath it changes.

Here’s the reassuring truth: done in the right order, a WordPress migration involves zero downtime. Your readers never notice. In this tutorial I’ll walk you through that exact order, using SiteGround as the destination host, because it’s the host I recommend and their free migration tooling removes the scariest steps. The same sequence works for any decent host, though — the order is the trick, not the brand.

What you need

  • Access to your current hosting account and your domain registrar (where you manage DNS)
  • A new hosting account — on SiteGround, the StartUp plan ($2.99/month promotional, renewing at $17.99) handles most single blogs; GrowBig ($4.99/month promo) adds staging and room for multiple sites
  • A full backup of your site (we’ll make one in step 2 regardless)
  • A quiet two-hour window, ideally on your lowest-traffic day

One honest note on pricing: like most hosts, SiteGround’s headline prices are first-term promotions and renewals are noticeably higher. Factor the renewal price into your decision, not just the promo. Both plans come with a 30-day money-back guarantee, so a migration you regret is reversible.

The migration, step by step

Step 1: Set up the new hosting account (don’t touch the old one)

Sign up with your new host but do not cancel your current one yet — that mistake causes most horror stories. When you check out at SiteGround, use your existing domain but skip any domain transfer for now. Hosting and domain are separate things; moving your files does not require moving your domain registration.

Step 2: Take a full backup at your old host

Before anything moves, back up both halves of your site: the files (themes, plugins, uploads) and the database (posts, comments, settings). Use your old host’s backup tool, or a plugin like UpdraftPlus, and download a copy to your own computer. You’ll probably never need it. Make it anyway.

Step 3: Lower your DNS TTL a day ahead

This is the zero-downtime secret nobody mentions. Your DNS records have a TTL (time to live) — how long the internet caches the answer to “where does this site live?”. If it’s set to 24 hours, some visitors will keep hitting your old server a full day after you switch. Log in at your registrar 24-48 hours before migration day and drop the TTL on your A record to 300 seconds. Now the actual switchover propagates in minutes.

Step 4: Move the site with the migrator plugin

For WordPress, SiteGround gives you two free routes: the SiteGround Migrator plugin, or a professional transfer — your first migration is handled free by their team. The plugin route is simple: generate a migration token in your new SiteGround dashboard, install the Migrator plugin on your old site, paste the token, and let it copy everything across. Your live site keeps running untouched the whole time, because everything is being copied, not moved.

Step 5: Preview the copied site before switching anything

Never point your domain at an untested server. Use the temporary preview URL your new host provides (or edit your computer’s hosts file to force just your machine to the new server) and click through the copied site properly: homepage, a few posts, images, menus, the admin area, your contact form. If the preview misbehaves, fix it now — I’ve covered the most common culprit in my guide on what to do when a SiteGround staging site fails to load, and the same fixes apply to migration previews.

Step 6: Freeze content, then update your DNS

Pick your quiet moment. Pause scheduled posts and hold off on approving comments for a few hours, so nothing new lands on the old server after the copy. Then update the DNS at your registrar: either switch your nameservers to the new host’s, or update the A record to the new server’s IP. Thanks to step 3, the change takes effect within minutes for almost everyone.

Step 7: Reissue SSL and check the locks

On the new host, issue a fresh SSL certificate for your domain (on SiteGround this is a free Let’s Encrypt certificate, a one-click job). Then load your site and confirm the padlock shows, and that both the www and non-www versions redirect to your preferred one. A migration that breaks HTTPS technically counts as downtime — don’t skip this.

Step 8: Verify everything, then wait before canceling

Test the things that make you money and the things that break silently: forms, checkout if you sell anything, your newsletter opt-ins, permalinks on a handful of old posts. Crucially, check your email. If your email runs through your old host, you need your MX records recreated correctly, or your messages will vanish into the void. Keep the old hosting account alive for another five to seven days as a safety net, then cancel it.

Pro tips and common mistakes

  • Migrating and redesigning at the same time. Change one variable at a time. Move first, redesign later, or you’ll never know what broke what.
  • Forgetting email. The number one migration casualty is MX records. Screenshot your old DNS records before touching anything.
  • Canceling the old host same-day. DNS stragglers and forgotten files make this expensive. A week of overlap costs a few dollars and saves your sanity.
  • Ignoring hardcoded URLs. If your old site used a temporary URL anywhere, run a search-replace so images don’t quietly point at a dead server.
  • Migrating a mess. Delete inactive plugins and old themes first. Less to copy, less to break.

And if you’re reading this without an existing blog, you get to skip all of it — my walkthrough on starting a WordPress blog with zero technical knowledge starts you on the right host from day one.

FAQ

How long does it take to migrate a WordPress host?

The copying itself usually takes minutes to a couple of hours depending on site size. The full process — setup, backup, testing, DNS — fits comfortably in an afternoon. The TTL preparation in step 3 is the only part that needs a day of lead time.

Will migrating my WordPress site hurt my SEO?

Not if your URLs stay identical, which this method guarantees. Google doesn’t care which server hosts your content. Rankings suffer only when migrations change URL structures or leave the site down for long stretches — both avoidable here.

Can I really migrate with zero downtime?

Yes. The method is copy first, test the copy, then repoint DNS with a short TTL. Both servers run the same site simultaneously during the handover, so every visitor reaches a working version regardless of which server answers.

Is SiteGround’s migration actually free?

Your first migration is free — either via their WordPress Migrator plugin or handled by their team. I verified this on their site, but hosting terms change, so double-check when you sign up.

Do I need to transfer my domain to the new host too?

No, and I’d wait. Your domain can stay at your current registrar indefinitely; you only change where its DNS points. Once the migration has settled for a month, consolidate if you want to — it’s a convenience, not a requirement.

A host migration is a sequence, not a gamble: copy, test, repoint, verify, and only then cancel. If your current host is the thing holding your blog back, head over to SiteGround to set up your new home — with the first migration free and a 30-day money-back guarantee, the safety nets are already in place.