Most Small Business Site Migrations Fail in the Same Three Places
A slow host is costing you customers right now — Google's own data shows that a one-second delay in page load time can reduce conversions by up to 7%. You've already decided to leave. The only thing standing between you and a faster site is the fear of breaking something in the move.
That fear is valid. A botched migration can mean hours of downtime, lost form submissions, broken redirects, or — worst case — a site that simply disappears from Google search results. But every one of those risks is preventable with the right sequence. This website migration checklist walks you through the exact steps, in the exact order, so you don't lose a single file, email, or ranking when you move your website to a new host.
Bookmark this page. Work through it top to bottom. Don't skip steps.
Phase 1: Before You Touch Anything — The Pre-Migration Backup
The single biggest mistake small business owners make is starting a migration before creating a verified, restorable backup. "Verified" is the key word. A backup you can't restore is just a false sense of security.
Step 1: Back Up Your Files
Log into your current hosting control panel (cPanel, Plesk, or your host's custom dashboard) and download a full account backup. This should include:
- All website files (HTML, CSS, JavaScript, images, PDFs, videos)
- Your database (MySQL or PostgreSQL — usually a .sql file)
- Any email accounts and their stored messages
- Your current hosting configuration files (.htaccess, php.ini, etc.)
Save this to two places: your local hard drive and a cloud storage service like Google Drive or Dropbox. If your laptop dies mid-migration, you want that second copy.
Step 2: Document Everything Before You Leave
Open a simple spreadsheet and record the following while your old host is still live:
- Every URL on your site (use a free crawler like Screaming Frog's free tier for up to 500 URLs)
- Your current DNS records — especially your A record, MX records, CNAME entries, and any TXT records for email authentication (SPF, DKIM, DMARC)
- Any redirects already in place (check your .htaccess file)
- Your site's current Google Search Console performance data (screenshot it as a baseline)
This documentation is your insurance policy. If something looks wrong after the migration, you'll have a ground-truth reference to compare against.
Step 3: Test Your Backup Restore
If your new host offers a staging environment, restore your backup there before you do anything with your live DNS. Open the staged version in a browser, click through every page, submit a test form, and make sure images load. A backup you've actually tested is worth ten backups you haven't.
Phase 2: Setting Up on the New Host
With a clean backup confirmed, you can set up your site on the new host without any pressure — your old site is still live and serving visitors the entire time.
Step 4: Upload Files and Restore the Database
Use SFTP (not plain FTP — always use the secure version) to upload your site files to the new server. Then import your database backup through the new host's database management tool. Update your site's configuration file (wp-config.php for WordPress, or your framework's equivalent) with the new database credentials.
Step 5: Recreate Your DNS Records on the New Host
Don't change anything live yet. Instead, log into the new host's DNS panel and enter all the records you documented in Step 2. Pay special attention to:
- MX records: Getting these wrong means your business email stops working. Double-check them twice.
- SPF and DKIM TXT records: These prevent your outgoing emails from landing in spam folders.
- Any CNAME records for third-party tools like Google Analytics, HubSpot, or scheduling apps.
Step 6: Preview the New Site Using a Hosts File Edit
Before you flip DNS for the world, you can preview the new host's version of your site on your own computer by temporarily editing your local hosts file. This lets you confirm everything works — images, forms, checkout — without any public-facing risk. Instructions vary by operating system, but a quick search for "edit hosts file [Windows/Mac]" will walk you through it in under five minutes.
Phase 3: The DNS Switch — Minimizing Downtime
DNS propagation is where most of the fear around hosting migration for small businesses lives. Here's the truth: if you lower your TTL (Time To Live) in advance, propagation is fast and downtime is measured in minutes, not hours.
Step 7: Lower Your TTL 24–48 Hours Early
Log into wherever your domain's DNS is managed (often your domain registrar, not your host — these are frequently different companies). Find your A record and lower the TTL to 300 seconds (5 minutes). Do this 24–48 hours before your planned switch. This tells DNS servers worldwide to check for updates more frequently, so when you change the IP address, the new one spreads much faster.
Step 8: Change Your A Record to the New Host's IP
When you're ready to go live, update the A record to point to your new host's IP address. Because your TTL is now only 5 minutes, most visitors will see the new site within 5–30 minutes rather than the traditional 24–48 hours.
Keep your old host account active for at least 48–72 hours after the switch. Some ISPs cache DNS longer than they should, and a small percentage of visitors may still be hitting the old server. Having both sites live simultaneously means no one gets a broken experience during that window.
Step 9: Monitor DNS Propagation
Use a free tool like whatsmydns.net to check how your domain is resolving across different regions. You should see your new host's IP spreading globally within an hour or two of making the change.
Phase 4: The Post-Migration Audit — Don't Skip This
The migration isn't done when the site loads on the new host. It's done when you've confirmed that everything works exactly as it did before — or better.
Step 10: Run a Full Redirect Audit
If your site had any redirects set up (old blog posts forwarding to new URLs, HTTP redirecting to HTTPS, www vs. non-www), confirm they're all working on the new host. Use your URL list from Step 2 and run each one through a redirect checker. Missing redirects are how you lose search rankings — Google treats a redirect-less URL change as a deleted page.
Step 11: Check SSL and HTTPS
Your new host should provide an SSL certificate. Confirm your site loads at https:// (with the padlock), that the certificate is valid, and that HTTP requests automatically redirect to HTTPS. An invalid SSL certificate will trigger browser warnings that send visitors away instantly.
Step 12: Test Every Form and Function
Go through your site like a first-time visitor:
- Submit your contact form and confirm the submission arrives in your inbox
- Place a test order if you have a shopping cart
- Sign up for your email list and confirm the double opt-in email arrives
- Check that your calendar or event listings display correctly
- Upload a photo to your gallery if you have one
If you're switching to a platform like SiteGlowUp.ai — which handles hosting, contact forms, galleries, menus, email lists, and shopping (all for $10/month) — this step is dramatically simpler because all those tools are managed in one place rather than pieced together from separate plugins.
Step 13: Resubmit Your Sitemap to Google Search Console
Log into Google Search Console, go to Sitemaps, and resubmit your XML sitemap. This prompts Google to re-crawl your site on the new host and confirm all your pages are still indexed. Check the Coverage report over the following few days for any new errors.
Step 14: Verify Your Analytics and Tracking
Confirm your Google Analytics (or whatever analytics platform you use) is still recording sessions. If you use Google Tag Manager, verify that the GTM container is still firing. It's easy for tracking scripts to get lost during a file migration — and you want to know immediately if that happens.
One More Thing: What a Good New Host Should Look Like
Going through all this effort to switch web hosts without downtime only makes sense if the destination is worth it. Before you commit to a new host, confirm it offers: fast SSD storage, an included SSL certificate, daily backups, and a support channel that actually responds within a reasonable timeframe.
If your current site also needs a visual refresh — not just a faster server — it's worth knowing that tools exist to handle both at once. SiteGlowUp.ai lets you paste your existing URL, generates a redesigned preview in about five minutes, and hosts the result for $10/month with all addons included. You approve before paying a cent. For a small business owner who needs speed and a better-looking site, combining the migration and the redesign into one step saves a lot of back-and-forth.
For a real-world example of what a clean, fast small business site looks like post-migration, check out FlowFix Plumbing — fast load, clear service pages, working contact form, the whole package.
The Short Version
A safe website migration comes down to this sequence: back up and verify before touching anything, set up the new host while the old one stays live, lower your TTL before the DNS switch, flip the record, then audit everything systematically before declaring victory. Follow these steps and the two things you were most afraid of — data loss and downtime — simply don't happen.
The checklist is long. The alternative — a broken site, lost form leads, or a Google ranking drop — is longer. Work through it once, and you won't have to think about your host again for years.
