How to Migrate to a New Host Without Losing Traffic

Changing web hosts is one of those tasks that sits on a business owner’s to-do list for months, sometimes years. The current host is slow, the support is frustrating, the renewal price jumped, or you’ve simply outgrown the plan you signed up for back when the site was new. You know you should move. But there’s a nagging fear that holds everyone back: what if I break the site and lose all my traffic? That fear is reasonable. A botched migration can knock a site offline for hours, scramble URLs, drop your search rankings, and send customers to a broken page right when they’re ready to buy.

Here’s the good news. A host migration that’s planned carefully is almost boring. Done right, your visitors never notice anything changed, your Google rankings stay exactly where they were, and your email keeps flowing. The difference between a smooth move and a disaster isn’t luck or technical genius. It’s preparation, sequencing, and a few habits that catch problems before they go live. This guide walks you through the entire process in plain English, in the order you should actually do it, so you can migrate to a new host without losing traffic, customers, or your hard-won search visibility.

Why Site Migrations Go Wrong (and Why Yours Won’t)

Before we get into the steps, it helps to understand what actually causes traffic loss during a move. Almost every horror story traces back to one of a handful of avoidable mistakes. When you know what they are, you can build your plan to dodge each one.

• Going live before the new site is fully tested. People point their domain at the new host first, then discover broken pages, missing images, or a contact form that doesn’t send. Now the problems are public.
• Changing URLs without redirects. If /services/plumbing becomes /plumbing-services and nothing tells search engines about it, the old ranking page returns a “not found” error and the traffic evaporates.
• Forgetting email. For many small businesses the domain handles both the website and the company email. Move the domain carelessly and the phones may keep ringing, but the inbox goes silent.
• DNS confusion. The system that connects your domain name to your server is the single most misunderstood part of hosting, and the place where most downtime happens.
• No backup. If something goes wrong and there’s no clean copy of the old site, a bad day turns into a catastrophic one.

Every step below exists to neutralize one of these risks. Follow the sequence and you remove the failure points one at a time.

Step 1: Take a Full Inventory Before You Touch Anything

The most overlooked phase of a migration is the part that happens before any files move. You can’t reproduce a site faithfully on a new host if you don’t know everything that lives on the current one. Spend an afternoon documenting what you have.

What to write down

• Where your domain is registered. This is often separate from your hosting. Your domain might live at GoDaddy while your site sits on another provider entirely. You’ll need login access to the registrar to update DNS.
• What platform the site runs on. WordPress, Shopify, Wix, Squarespace, a custom build? Each migrates differently. WordPress and other self-hosted platforms give you the most control. Hosted builders like Wix and Squarespace can’t simply be copied to a new host because the platform and the hosting are the same thing.
• Your email setup. Is email handled by your host, by Google Workspace, by Microsoft 365, or somewhere else? Note the MX records, because these must survive the move untouched.
• Plugins, integrations, and third-party scripts. Booking tools, payment processors, chat widgets, analytics tags. List them so nothing gets left behind.
• SSL certificate. Note whether you have a paid certificate or a free one. The new host should provide a fresh certificate, but you want to confirm HTTPS works before launch.

This inventory is your map. If you’re not confident reading DNS records or identifying your email provider, this is exactly the kind of groundwork an experienced partner handles routinely as part of managed website hosting, so the move is planned rather than improvised.

Step 2: Lower Your DNS TTL a Few Days Early

This single step prevents most of the downtime people fear, and almost nobody knows to do it. DNS records carry a setting called TTL, or “time to live,” measured in seconds. It tells the internet how long to cache the answer to “where does this domain point?” If your TTL is set to 86400 (a full day), then when you finally switch hosts, some visitors could keep landing on the old server for up to 24 hours.

The fix is to log into your DNS settings a few days before the planned migration and lower the TTL to something short, like 300 seconds (five minutes). Wait for the old, long TTL to expire so the new short value takes effect. Now, when you flip the switch on launch day, the internet picks up the change in minutes instead of a day. After everything is confirmed working, you can raise the TTL back up. It’s a small, technical, wildly effective trick that turns a nail-biting cutover into a quick, controlled transition.

Step 3: Build and Test the Site on the New Host First

Here is the golden rule of safe migrations: never point your live domain at the new host until the new site is fully built and tested there. Your existing site keeps serving real visitors the entire time you’re working on the copy. The public sees no disruption because nothing public has changed yet.

To do this, you copy all the site files and the database to the new host and access them through a temporary address the host provides, or by editing a local file on your computer (the “hosts” file) that lets only you preview the new server while everyone else still sees the live site. Then you test relentlessly:

• Click through every important page. Does it load? Are the images there?
• Submit the contact form and confirm the message actually arrives.
• Run a test transaction if you sell online.
• Check the site on a phone, not just a desktop.
• Confirm any booking, scheduling, or chat tools still connect.
• Verify the SSL certificate is active so the address shows HTTPS with no security warning.

Only when you’ve signed off on every one of these does the migration become safe to launch. This staging-and-testing discipline is the same standard that good agencies apply to every website design and development project, and it’s what separates a quiet, successful launch from a public scramble.

Step 4: Protect Your URLs and Redirects

This is the step that directly protects your search traffic, so pay close attention if your business depends on Google. Search engines have spent months or years learning that a specific page on your site answers a specific question. As long as that page keeps the exact same URL after the move, the ranking transfers seamlessly. A true “lift and shift” migration, where you move to a new host but keep identical URLs, is the safest kind because search engines barely notice.

The danger appears when URLs change. Maybe you’re also redesigning, or switching platforms, and the address structure shifts. When that happens, you need 301 redirects. A 301 is a permanent instruction that says “this page has moved here forever,” and it passes the old page’s ranking authority to the new address. Without it, the old URL returns a “404 not found,” your ranking dies, and any links pointing to that page now lead nowhere.

Your redirect checklist

• Make a complete list of your current URLs before the move. A crawl of the site or your XML sitemap gives you this.
• For any URL that changes, create a 301 redirect from the old address to the new one.
• Map them one to one wherever possible. Don’t lazily redirect everything to the homepage; that throws away the specific relevance Google associated with each page.
• Test a sample of redirects after launch to confirm they fire correctly.

This protection of rankings sits right at the heart of solid search engine optimization work, because a migration is one of the few moments where years of SEO progress can be lost in an afternoon if redirects are mishandled.

Step 5: Handle Email and DNS Records With Care

For a service business, losing email is arguably worse than losing the website for an hour. Customers email quotes, suppliers send invoices, and leads come through contact forms. The mistake that causes silent inboxes is treating the DNS migration as a single “point everything at the new host” action.

Your DNS holds several different record types, and they don’t all serve the website:

• A and CNAME records point your domain and “www” to the web server. These are the ones that should move to the new host.
• MX records route your email. If your email is handled by Google Workspace or Microsoft 365, these MX records must stay exactly as they are. Wiping them out by accident is the classic cause of a dead inbox.
• TXT records often carry email authentication like SPF, DKIM, and DMARC. Preserve these or your outgoing email may start landing in spam folders.

The safe approach is to copy your existing DNS records exactly, change only the records that point to the web server, and leave everything email-related untouched unless you’re deliberately moving email too. If you are moving email along with hosting, do that as a separate, carefully tested step, never as a casual side effect of the website move.

Step 6: Go Live, Then Watch Closely

Once the new site is tested and your redirects are ready, launch is anticlimactic, which is exactly how it should be. You update the A and CNAME records to point at the new host. Because you lowered your TTL in Step 2, the change propagates within minutes for most visitors.

Pick a low-traffic window for the cutover. For a typical Long Island service business, that’s often late evening or early morning, not the middle of a busy Tuesday. After you flip the records, don’t walk away. The next hour is when you confirm everything actually works in the real world:

• Load your homepage and several interior pages from a device that isn’t on your office network, like your phone on cellular data.
• Confirm HTTPS is working with no certificate warnings.
• Send a test through your contact form and watch for the email to arrive.
• Send yourself an email to your business address to confirm mail is flowing.
• Spot-check a handful of your most important ranking pages and any redirects.

Keep the old hosting account active for at least a couple of weeks after the move. It costs little, and it’s your safety net. If something surfaces that you missed, the old site is still there to reference or roll back to.

Step 7: Post-Migration SEO Housekeeping

The site is live and stable. Now you do the quiet follow-up work that locks in your rankings and tells search engines the move went smoothly.

• Submit your sitemap in Google Search Console. This nudges Google to recrawl and confirm the new setup. Watch the coverage and any crawl-error reports over the following weeks.
• Check for crawl errors and broken links. A quick crawl of the new site catches any redirect you missed or any internal link still pointing at an old address.
• Confirm your analytics is still tracking. It’s surprisingly common for a tracking tag to get dropped during a file move. Verify you’re still collecting data the day after launch, not three weeks later.
• Monitor your rankings and traffic for a few weeks. A small, brief dip during a transition isn’t unusual, but it should recover quickly. A sustained drop is a signal to investigate redirects and indexing.
• Re-raise your DNS TTL back to a normal value once you’re confident everything is stable.

While you’re in there, a migration is also a natural moment to think about how your new, faster host can support broader goals, from page speed (which both visitors and search engines reward) to how well your content is structured for the AI assistants that increasingly answer customer questions. A site on solid, well-configured hosting is the foundation everything else, including your visibility in tools like ChatGPT and Google’s AI answers, is built on.

Special Cases Worth Flagging

A few situations deserve extra caution. If you’re moving an e-commerce store, treat payment processing and order data as the highest priority and test a real transaction before and after. If you’re changing platforms at the same time as hosts (say, leaving Wix for WordPress), you’re really doing two projects at once, and the URL and redirect mapping becomes far more involved. And if your site has a lot of organic traffic, the stakes of getting redirects right are high enough that it’s worth bringing in help rather than learning on your live, revenue-generating website.

The Takeaway

Migrating to a new host doesn’t have to cost you a single visitor. The whole game is preparation: inventory what you have, lower your TTL, build and test the new site privately before anyone sees it, protect every URL with proper redirects, leave your email records alone, launch in a quiet window, and watch closely afterward. Do those things in order and the move becomes a non-event for your customers, exactly as it should be. If reading through this list made you realize how many moving parts are involved, you don’t have to take the risk on your own. Our team handles migrations, hosting, and the SEO protection around them every day. Talk to MJW Media about managed hosting and a stress-free migration, and let us move your site without losing a beat.

Related Resources

• SEO Services
• GEO, AEO & AI SEO Services
• How to Improve SEO Without Writing More Blogs
• Celebrating 15 Years in Business: MJW Media Thanks You with 15% Off for New Clients!
• How SEO Helps NYC Businesses Gain Visibility and Drive Traffic