Your current host has been slow for months. Load times are creeping up, you’ve had two unexplained outages in the last six weeks, and your Google Search Console is starting to show declining impressions that could be performance-related. You’ve decided to move to Bluehost — but the prospect of migrating a live blog without breaking something is keeping you from pulling the trigger.
Moving your blog to Bluehost doesn’t have to cost you rankings or readers. This guide covers every step in the right order: backing up your site, setting up Bluehost, migrating with the right tool, updating your DNS without triggering a traffic drop, and running the post-migration checklist that confirms everything transferred correctly.
Before you touch anything: back up your current site
The first rule of any blog migration is that nothing moves until you have a complete, verified backup of your current site. A backup made the morning of your migration is the insurance policy that turns a catastrophic error into a ten-minute restore. Skipping this step because you’re confident nothing will go wrong is how bloggers lose years of content.
UpdraftPlus is the most reliable free backup plugin for WordPress — it’s one of the essential WordPress plugins every new blog needs from day one. If you have it installed, go to Settings → UpdraftPlus Backups and click Backup Now. Select both database and files. Choose to store the backup to Google Drive or Dropbox rather than your server — you want the backup somewhere independent of the host you’re about to leave.
If you don’t have UpdraftPlus, install it now, configure the remote storage, and run the backup before doing anything else in this guide. The entire migration rests on this foundation.
After the backup completes, download a local copy to your computer as a second redundancy. Verify the backup files are present and the folder sizes look correct. A backup you haven’t verified is not a backup you can trust.
Your action: Install UpdraftPlus, run a full backup to Google Drive, download a local copy, and confirm the file sizes match your expectations before continuing.
Setting up your Bluehost account
Sign up for Bluehost at bluehost.com before starting the migration. Choose the Basic plan if you’re running a single blog. During checkout, you have two options for your domain: register a new domain, or use your existing domain. Choose I’ll use an existing domain and enter your current domain name. Bluehost will hold the domain in your account without transferring the registration — the transfer is a separate step you’ll handle after migration is confirmed working.
Complete the signup and log into your Bluehost dashboard. From the dashboard, go to My Sites → Create Site. Select the option to create a blank WordPress site — don’t use any pre-installed themes or starter content since your migrated site will bring its own.
Write down your new Bluehost nameservers — they’ll look something like ns1.bluehost.com and ns2.bluehost.com. You’ll need these in the DNS cutover step.
Your action: Complete the Bluehost signup, create a blank WordPress site on your domain, and copy your assigned nameservers to a notes document before continuing.
Migrating your content with Duplicator or All-in-One WP Migration
Two plugins reliably handle WordPress-to-WordPress migrations without technical expertise: Duplicator and All-in-One WP Migration. Both are free for most blog sizes.
Using All-in-One WP Migration (recommended for most bloggers)
All-in-One WP Migration is the simpler of the two options and works well for blogs under 512MB in total size. On your current (old) host:
Install All-in-One WP Migration from Plugins → Add New and activate it. Go to All-in-One WP Migration → Export and select Export to File. The plugin creates a single archive file containing your entire site — database, themes, plugins, and media files. Download that file to your computer.
On your new Bluehost WordPress installation, install All-in-One WP Migration and go to All-in-One WP Migration → Import. Upload the archive file you just downloaded. The plugin imports everything and overwrites the blank installation with your complete site. Log out and log back in with your original WordPress credentials once the import completes.
Using Duplicator for larger sites
If your blog exceeds 512MB, use Duplicator Pro or migrate manually via cPanel file manager and phpMyAdmin. Duplicator creates an installer package that you upload directly to your new hosting account and run through a browser-based installer — slightly more technical than All-in-One, but handles larger sites reliably.
Bluehost also offers a free migration service for accounts on their standard plans. If you’d rather hand the technical process to their team, submit a migration request through the Bluehost dashboard. Response times vary but the service is included at no extra cost.
Your action: Install All-in-One WP Migration on your current site, export your site as a single archive file, then install the same plugin on your new Bluehost WordPress site and import that archive.
Updating your DNS without triggering a traffic drop
DNS propagation is the step most bloggers handle wrong — and it’s the step that determines whether your migration causes traffic disruption or not.
Your domain currently points to your old host through DNS records at your domain registrar (wherever you registered your domain — Namecheap, GoDaddy, or through your current host). Changing those DNS records to point to Bluehost is the final cutover step. Once DNS propagates, all new visitors reach your site on Bluehost instead of your old host.
The key to avoiding traffic disruption is timing and testing. Before changing your DNS, verify that the migrated site on Bluehost is working correctly by temporarily editing your computer’s local hosts file to preview the Bluehost version. This lets you test the site fully before anyone else sees it. Most bloggers skip this step and discover problems after DNS has already propagated — at which point visitors are seeing a broken site while you scramble to fix it.
Once you’ve confirmed the migrated site looks and functions correctly on Bluehost, update your nameservers at your domain registrar from your old host’s nameservers to Bluehost’s nameservers (ns1.bluehost.com and ns2.bluehost.com). DNS propagation typically completes within one to four hours but can take up to 48 hours in some regions.
Keep your old hosting account active for 48 to 72 hours after the DNS update. During propagation, some visitors will still land on your old host while others reach Bluehost. Canceling the old account before propagation completes causes those visitors to see a broken site.
Your action: Log into your domain registrar, update your nameservers to Bluehost’s values, and set a reminder to check your site’s status four hours after making the change.
The post-migration SEO checklist
Traffic loss after a migration almost always comes from three sources: broken internal links, missing redirects, or crawl errors that weren’t there before. Running through a short checklist after DNS propagates catches these issues before Google’s next crawl registers them.
First, log into Google Search Console and submit your sitemap — go to Sitemaps in Search Console, enter your sitemap URL (typically yoursite.com/sitemap.xml — RankMath generates this automatically), and click Submit. A fresh sitemap submission tells Google to recrawl your site with priority.
Second, run a broken link check using Screaming Frog (free for up to 500 URLs) or a plugin like Broken Link Checker. Any internal links that returned a 404 error on your old host will still return 404s on the new one — and Google penalizes sites with significant broken link counts.
Third, check your site speed using Google PageSpeed Insights. Your score on the new host should be equal to or better than your old host’s score. If it’s significantly lower, install WP Rocket or W3 Total Cache and enable caching before you’ve accumulated any traffic on the new host.
Fourth, verify your RankMath or Yoast SEO settings carried over correctly. Open three or four posts and confirm the meta titles, descriptions, and focus keyphrases are still populated. Migration plugins sometimes lose custom fields, and finding out three weeks later is worse than catching it now.
Your action: Submit your sitemap to Search Console, run a broken link check, test your PageSpeed score, and spot-check five posts for correct SEO metadata — all within the first 24 hours after DNS propagation completes.
The bottom line
Moving your blog to Bluehost without losing traffic is entirely achievable — but it requires doing the steps in the right order. Back up first, migrate second, test before DNS cutover third, and run the SEO checklist within 24 hours of going live on the new host.
The migration itself takes two to four hours for most blogs. The traffic protection comes from the preparation, the pre-cutover testing, and the post-migration verification — not from luck.
Your next step: Install UpdraftPlus on your current site and run a full backup to Google Drive right now, even if you’re not ready to migrate yet. Having a recent backup in place is the starting point that everything else depends on.