Migrating a WordPress site to new hosting means moving every file, database table, plugin, theme, and configuration from your current server to a new one — without breaking anything, losing data, or experiencing extended downtime. The process is straightforward when done correctly but can be catastrophic when done carelessly: broken links, missing images, database connection errors, and days of downtime are common consequences of rushed or poorly planned migrations. A 2023 WP Engine survey found that 42% of WordPress site owners who migrated hosting without professional help experienced at least one significant issue.

Your current hosting is slow, unreliable, or too expensive. You have found a better provider with faster servers, better support, or lower prices. But your website has years of content, dozens of plugins, customer data, and complex configurations — the thought of moving everything without breaking it feels overwhelming. The good news: WordPress migration is a solved problem with reliable tools and proven processes. Whether you do it yourself with a migration plugin or hire a professional, understanding the process ensures nothing falls through the cracks.

This guide covers the complete WordPress migration process — from pre-migration planning and backup creation through DNS propagation and post-migration testing — so you can move your site confidently with minimal downtime.

What Should You Do Before Migrating Your WordPress Site?

Pre-migration preparation prevents 90% of migration problems. Before touching anything, you need a complete backup of your current site, a list of everything that needs to transfer, access credentials for both hosting accounts, and a migration timeline that minimizes business disruption. Rushing into migration without preparation is how businesses end up with broken websites and lost data.

Pre-Migration Checklist

  • Create a complete backup: Use a backup plugin (UpdraftPlus, BlogVault, or All-in-One WP Migration) to create a full backup of your files and database. Store this backup in at least two locations — cloud storage and local download. This is your safety net if anything goes wrong during migration
  • Document your current setup: Note your PHP version, WordPress version, active plugins and their versions, active theme, any custom code modifications, server configurations (like .htaccess rules), and cron jobs. Your new hosting environment needs to match or exceed these requirements. Check your hosting control panel for PHP version and server settings
  • Verify new hosting compatibility: Confirm your new host supports your required PHP version, MySQL/MariaDB version, and any server modules your plugins need (like Imagick or ionCube). Check that your hosting plan has sufficient storage, bandwidth, and database capacity. Incompatible hosting causes cryptic errors that are difficult to diagnose after migration
  • Note your DNS settings: Screenshot or export your current DNS records (A records, CNAME records, MX records for email, TXT records for verification). DNS changes are the final step of migration, and incorrect DNS records can break your email, website, or both. If your email runs through your domain (yourname@yourbusiness.com), DNS changes affect email delivery
  • Plan your timing: Schedule migration during your lowest-traffic period — typically late evening or early morning on a weekday. Inform your team that the website may be briefly unavailable. If you process orders or leads through your site, consider a maintenance page during the transition to prevent lost transactions

What Is the Easiest Way to Migrate a WordPress Site?

The easiest migration method is using a dedicated migration plugin that handles the entire process — packaging your site’s files and database, transferring them to the new server, and unpacking everything in the correct locations. For sites under 2GB (which covers most small business websites), a migration plugin completes the entire process in 30-60 minutes with minimal technical knowledge required.

Migration Methods Compared

  • Migration plugin (recommended for most): All-in-One WP Migration, Duplicator, or BlogVault. Install the plugin on your current site, export everything, install WordPress on new hosting, install the same plugin, and import. Handles database URL replacement automatically. Best for sites under 2GB without complex server configurations. Cost: free to $69 depending on plugin and site size
  • Host-provided migration: Many hosting companies (SiteGround, WP Engine, Cloudways) offer free migration as part of their onboarding. Their migration team handles everything — you provide current hosting credentials and they move your site. Best option if available, as hosting migration teams handle hundreds of migrations weekly and know every edge case
  • Manual migration (advanced): Export database via phpMyAdmin, download all files via FTP/SFTP, upload files to new server, import database, update wp-config.php with new database credentials, and run search-replace on URLs in the database. Required for sites with complex configurations, very large databases, or specific server requirements. Takes 1-3 hours and requires technical comfort with databases and FTP
  • cPanel transfer (if available): If both your old and new hosting use cPanel, you can use cPanel’s built-in backup and restore or the Transfer Tool. Create a full cPanel backup on the old host, download it, and restore it on the new host. This moves everything including email accounts and DNS zones — the most complete migration method when available

How Do You Handle DNS and Minimize Downtime?

DNS propagation — the process of your domain pointing to the new server instead of the old one — is the step that causes the most anxiety during migration. After changing your DNS records, it takes 15 minutes to 48 hours for the change to propagate worldwide. During this window, some visitors see the new site while others still see the old site. Planning for this overlap period is essential to prevent lost data and confused customers.

Minimizing Migration Downtime

  • Test on new hosting before changing DNS: Upload your site to the new hosting and test it using the temporary URL or IP address your host provides. Verify every page, form, and function works correctly before pointing your domain to the new server. This way, when DNS switches over, visitors immediately see a fully working site
  • Lower TTL before migration: DNS records have a Time-To-Live (TTL) value that controls how long browsers cache the old DNS information. Lower your TTL to 300 seconds (5 minutes) 24-48 hours before migration. This ensures that when you change DNS records, the new records propagate faster — reducing the window where some visitors see the old site
  • Keep old hosting active for 72 hours: Do not cancel your old hosting immediately after migration. Keep it active for at least 72 hours to ensure all DNS caches worldwide have updated. Some ISPs and corporate networks cache DNS aggressively — premature cancellation means those visitors see an error page
  • Freeze content changes during transition: Do not publish new blog posts, process orders, or make any website changes during the DNS propagation window. Changes made on either server during this period may not transfer to the other. Resume normal operations only after DNS propagation is complete and all traffic routes to the new server
  • Update SSL certificate: Your new hosting needs its own SSL certificate. Most modern hosts (SiteGround, Cloudways) automatically provision free Let’s Encrypt SSL certificates. Verify HTTPS works on the new server before DNS switchover — a site that loads without SSL after migration creates browser security warnings that scare visitors away

WordPress migration is a standard process that thousands of businesses complete every week without incident — when it is planned properly and executed methodically. The difference between a smooth migration and a disaster is preparation, testing, and patience. If you want your migration handled professionally with zero downtime and zero risk to your business, schedule a free consultation with Spilt Media’s WordPress team.

Frequently Asked Questions

Will I lose SEO rankings when migrating hosting?

Not if done correctly. A hosting migration (same domain, same content, same URLs) should have zero impact on SEO rankings. Search engines care about your domain and content, not which server they are on. The risks to SEO come from mistakes: broken URLs, missing redirects, extended downtime, or accidentally changing your URL structure. Use Google Search Console to verify indexing status after migration and check for crawl errors within the first week.

How long does a WordPress migration take?

Using a migration plugin, the actual file and database transfer takes 30-60 minutes for most small business sites. Testing and verification add another 1-2 hours. DNS propagation takes 15 minutes to 48 hours depending on your registrar and global DNS caches. Plan for the full process to take one business day including testing and DNS propagation, even though the active work is only 2-3 hours.

Will my email be affected by the migration?

If your email uses the same domain as your website and runs through your hosting provider (not a separate service like Google Workspace or Microsoft 365), then yes — email will be affected during DNS propagation. If you use Google Workspace, Microsoft 365, or another external email service, your email will continue working as long as you preserve the MX records when updating DNS. Always document your current MX records before making any DNS changes.

Can I migrate a WordPress site with WooCommerce?

Yes, but WooCommerce sites require extra care. Customer accounts, order history, product data, and payment gateway configurations all need to transfer correctly. Use a migration plugin that handles the full database (All-in-One WP Migration or BlogVault). After migration, test the checkout process end-to-end including payment processing in test mode. Verify that all product images display correctly and that customer account logins still work on the new server.

What if something goes wrong during migration?

This is why you created a complete backup before starting. If the new site is broken or data is missing, do not change DNS — your old site continues running normally on the old server. Troubleshoot the new site using the temporary URL, or restore from your backup and start the migration process over. As long as you do not cancel your old hosting prematurely and have a verified backup, migration failures are inconvenient but never catastrophic.