Alexa Web Servers Blog

What to Do Before Changing Your Hosting Provider: A Complete Checklist

Practical notes on WordPress, servers, performance, security, and maintenance for businesses that want a serious online presence.

Posted on 15 November 2026
Illustration for the article What to Do Before Changing Your Hosting Provider: A Complete Checklist

Changing hosting provider looks like an administrative task: sign up for the new plan, upload the files and point the domain at the new server. In practice it is one of the few technical decisions that can take your site offline, cut off email for the whole team and cost you ranking positions on Google in the same afternoon. The good news is that almost every problem we see in real migrations can be avoided with advance work: knowing exactly what you have, holding backups you have actually tested, controlling DNS and following a checklist nobody skips.

This guide is the checklist we would use before moving any business website: what to document, what to measure, what to ask the new provider and in which order to do things so the only visible change is on the invoice, not in your traffic.

Why a hosting migration is more delicate than it looks

A mid-sized business site is not just a WordPress install: it is a domain, a DNS zone with ten or twenty records, email with several mailboxes and aliases, a database with years of orders, a few certificates, scheduled tasks and a handful of external integrations nobody remembers configuring. When one of those gets left behind, the failure shows up days later, at the worst possible moment.

Five fronts move at the same time:

  • DNS: the single point of failure for everything. One forgotten MX record and email stops arriving; one forgotten CNAME on a subdomain and an internal tool breaks.
  • Email: the service that breaks most often in migrations, because it depends on MX, SPF, DKIM and DMARC at once, and because mailboxes do not always live on the same server as the website.
  • SEO: if URLs change, redirects are lost or the site serves errors for a few days, Google notices quickly and recovery is slower than the drop itself.
  • Integrations: payment gateways, webhooks, form delivery, ERP, newsletters. They all point at something, and none of them warns you when it fails.
  • Continuity: the old hosting is usually your safety net. Cancelling it too early is the most expensive mistake on the list.

Step 1: a complete inventory of what you run today

Before comparing new plans, spend an hour writing down what is already in production. That document serves the migration, and it serves you the day you need to restore something or switch provider again.

Domain and DNS

Export the full DNS zone from your current panel and save it. Do not rely on memory: the records nobody remembers are usually the ones holding up email or a marketing tool’s verification.

  • A and AAAA records for the domain and every active subdomain.
  • CNAME records (subdomains, CDN, third-party verifications).
  • MX records and their priority.
  • TXT records: SPF, DKIM, DMARC and service verifications.
  • Registrar, ownership and domain renewal date.
  • Current TTL values for the records you are going to change.

Email

Establish clearly where each mailbox lives and how much space it uses. If email sits on the hosting you are leaving, you have an email migration inside the website migration, and it deserves a plan of its own.

  • Accounts, aliases, distribution lists and forwarders.
  • Number and size of mailboxes.
  • Mail clients configured on the team’s phones and computers (they will need updated incoming and outgoing servers).
  • If you use an external email service, the records that authorise it.

WordPress, database and server

  • PHP version and the extensions used by the theme and plugins.
  • Database size and the size of wp-content.
  • List of active plugins, and which ones are abandoned.
  • System cron tasks and WordPress scheduled events.
  • SSH, WP-CLI or control panel access: whatever you need to work comfortably.
  • Administrator users and who maintains the site.

Integrations pointing at your site

Review payment gateways, webhooks, forms connected to a CRM, Google Search Console, Google Analytics, advertising pixels, newsletters, booking tools and any API with an authorised URL. When the IP or test domain changes, those connections break silently.

Minimum inventory table

Item Where to check it Why it matters
DNS zone Registrar or hosting panel It points both traffic and email
Mailboxes and aliases Email panel Email is usually business-critical
PHP version Panel or WordPress site health It determines compatibility on the new server
Database and file size phpMyAdmin, panel or WP-CLI It defines copy and transfer time
SSL certificates Panel or browser Prevents security warnings after the switch
Scheduled tasks System cron and WordPress Backups, reports and syncs depend on them
External integrations Each service’s dashboard They break with no warning and no trace

Step 2: backups you have verified, not just created

A backup you have never restored is a backup you do not know exists. Before touching anything, produce and check:

  • A full copy of files and database, downloaded outside the old server.
  • A copy of the mailboxes if the provider offers no direct export.
  • A DNS zone export as text, stored somewhere you can reach without the old hosting.
  • Certificates and keys if you managed them yourself.
  • The contents of .htaccess, redirect rules and server configuration.
  • A record of cron tasks and the absolute paths they use.

The real test is restoring that copy in a test environment and confirming the site loads, the forms send and you can log in to the dashboard. If that works you have a safety net; if it does not, you have a compressed file.

If you want to go deeper on how to approach this, we have a guide on the importance of daily backups.

Step 3: measure your starting point before moving anything

Without prior data you cannot prove the migration went well, or spot what got worse. Write down concrete values, with a date:

  • Server response time (TTFB) and load time for the homepage and for one product or service page.
  • The result of a performance test on mobile and on desktop.
  • Uptime history for the last few weeks, if you have it.
  • Indexed pages and crawl errors in Google Search Console.
  • Rankings for the ten searches that matter most to you.
  • Enquiries, calls or orders in a normal week.

That set of numbers is also your internal business case if you have to justify the change: before and after, same metric, same tool.

Step 4: plan DNS in advance

DNS is where a migration is won or lost. Two basic rules:

  • Lower the TTL of the records you are going to change at least 24 to 48 hours before the switch, so propagation is fast and a rollback is possible within minutes.
  • Do not change website DNS and email at the same time. If something fails, you will not know which of the two caused it.

Keep the old hosting active and accessible until the new site has been running normally for several days. If your domain and DNS sit with the provider you are leaving, consider moving the registrar first or delegating DNS to a stable third party: that way the hosting change does not depend on an account you are abandoning.

Step 5: choose the migration window carefully

The best time to migrate is the most boring slot in the calendar: midweek, in the morning, with no active campaigns and the team available to test. Avoid:

  • Campaign weeks, launches or peak sales season.
  • Friday afternoons and the eve of public holidays.
  • Moments when the only person who understands the DNS is travelling.

Coordinate the window with the new provider’s support team: it helps to know whether someone will be available during the switch or whether they only answer email the next day.

Step 6: what to demand from the new provider before signing

The comparison should not revolve only around disk space or how many sites you can host. These are the questions that separate serious managed hosting from cheap hosting:

Criterion What to ask Warning sign
PHP versions Which versions do you offer, and can I change version per site? Only one old version, no control
Storage NVMe or SATA disks? Is there an inode limit? Hidden limits that appear mid-migration
Backups Frequency, retention and is restoration included? Backups as a paid extra, no restoration
Data location Which country holds servers and backups? Vague answers about location
Support Who replies, in which language, with what time commitment? No defined hours, no named person
Technical access SSH, WP-CLI, own panel, logs? No access beyond a basic panel
Test environment Is staging included to test updates? Everything is tested in production
Email Are business mailboxes included or separate? Email on overloaded shared servers
Migration Do they do it, or do you? What is in scope? «We send you the credentials and that is it»
Exit Can I take my site and email with me whenever I want? Domain retention or exit penalties

If the new plan improves nothing on this list, you probably do not need to change hosting — you need to tune the one you already have. Before deciding, it may help to review how to choose the right hosting plan.

The mistakes that cost the most

  • Cancelling the old hosting before verifying the new one. It is mistake number one and the only one with no quick fix.
  • Not documenting the DNS records that are not about the website. Email, subdomains and verifications get lost in the switch.
  • Migrating without checking the PHP version or the extensions. A plugin that needs a specific extension stops working, and the symptom shows up as a critical error.
  • Moving email at the same time as the website. If something fails, there is no way to isolate the cause.
  • Forgetting forms, checkout and webhooks. The site loads but orders never arrive: the quietest failure of all.
  • Letting the domain expire during the move. Check the renewal date before you start.
  • Uploading an old backup over the new site. Get the order right: migrate first, update afterwards, never the other way round.
  • Having no rollback plan. If you do not know how to revert within an hour, you are not ready to begin.

What to check right after the migration

With DNS pointing at the new server, switch into checking mode for the first 48 hours:

  • Homepage, main pages, blog, shop and a couple of product or service pages.
  • A valid SSL certificate with no warnings, and HTTP-to-HTTPS redirection working.
  • Contact form: a real submission and real delivery, including the automatic reply.
  • Email: send and receive from inside and from outside, and check SPF, DKIM and DMARC.
  • Test orders if there is a shop, including the payment gateway and the confirmation email.
  • Internal links, menus, images and downloadable files.
  • Scheduled tasks: backups, reports and syncs.
  • Server error log and any new 404 errors.
  • Search Console and Analytics receiving data.
  • Speed measured with the same tool you used before migrating.

If anything on that list fails, that is the moment to act — not three weeks later when a customer reports they cannot buy.

How to avoid losing Google rankings

SEO is not lost by changing servers; it is lost by changing URLs or serving errors for days. To keep it under control:

  • Keep the URL structure wherever possible; if it changes, prepare a 301 redirect map before the switch.
  • Confirm no noindex left over from the test environment remains.
  • Review robots.txt and the sitemap on the new server.
  • Keep canonicals pointing at the final URLs.
  • Verify the domain responds both with and without www, and that only one version is the primary.
  • In Search Console, watch coverage and crawl errors for two or three weeks.

How long it really takes

Phase Typical time Who does it
Inventory and documentation 2 to 4 hours Whoever knows the site
Backups and restoration test 1 to 2 hours Hosting or technical support
Transfer of files, database and email 1 to 4 hours New provider or yourself
Adjustments, testing and fixes 2 to 4 hours Development and content
DNS propagation Minutes to 24-48 hours Depends on the previous TTL

A small site can be migrated in a morning; a shop with email, subscriptions and active campaigns needs planning and someone watching during the switch. What never works is improvising.

Frequently asked questions

How long should I keep the old hosting active?

At least two weeks after the migration. It costs little and it is your safety net if an email problem or a forgotten subdomain appears.

Will I lose Google rankings when I change hosting?

Not if you keep the URLs, avoid serving errors and keep the content. What gets penalised is instability and changing addresses, not the server itself.

Can I migrate email myself?

You can, but do it once the website is stable on the new server, not at the same moment. Before moving the MX records, confirm the mailboxes exist and that SPF and DKIM are ready.

What if my site is an online shop?

Then add a complete test order with a real or test-mode payment, review the webhooks and confirm that order emails arrive. It is the part most often forgotten and the one that costs the most sales.

Would you rather we handled it?

At Alexa Web Servers we take care of migrations and ongoing website maintenance so that changing hosting is a boring operation: inventory, verified backups, controlled DNS, tested email and a review afterwards of what actually matters. If you are thinking about changing provider, write to us through the contact form and we will tell you what to review in your specific case, with no obligation.

And if you prefer to work through the checklist yourself, our resources store has the tools and templates to do it methodically: https://alexawebservers.com/blog/shop/.

Check our tools

If what you need is to automate provisioning, backups and monitoring on the new server, the Server Automation Toolkit brings together the scripts and the working structure we use to put a server into production properly, without repeating tasks by hand. You can see it here:

Server Automation Toolkit

And if your priority is for the new site to load faster than the old one, start with the Website Speed Optimization Checklist, which is free and lets you measure before and after with the same criteria.

💬 Chat with us