Step 1: Prepare Your Current Site

Before touching anything, get your site in order. This prevents surprises during the move.

  • Take a full backup: Use a reliable plugin to export your entire database and the wp-content folder. Don't rely on your host's automatic backups for this.
  • Clean house: Deactivate unused plugins and themes. Delete spam comments and post revisions. A smaller, cleaner site migrates faster.
  • Document credentials: Note down your current database name, username, password, and host (usually localhost). You'll need these.
  • Reduce visitor impact: Consider putting up a brief "maintenance mode" notice when you start the final sync.

Step 2: Choose Your Migration Method

Pick the tool that matches your comfort level. Don't overcomplicate it.

Plugin Method (Easiest)

Plugins like Duplicator or All-in-One WP Migration handle the technical details. You install the plugin on your old site, create a "package" (a zip file and installer), and then upload that to your new host. It's ideal for most single-site migrations.

Manual Method (Most Control)

You manually export your database via phpMyAdmin and download your site files via FTP/SFTP. You then import the database and upload the files to the new server. This method is essential for very large sites or when you need to troubleshoot specific issues.

Note

If you're moving to a new host that offers free migration (many managed WordPress hosts do), use their service. It's the least stressful option. For example, when you move to Hostinger WordPress hosting, their team can often handle the transfer for you.

Step 3: Upload Everything to the New Host

This is the core move. The order matters.

  1. On your new hosting account, create a new database and user. Note the new credentials.
  2. Upload all your WordPress files (via FTP or the host's file manager) into the public directory (often public_html).
  3. Import your saved database backup into the new database you just created.
  4. Crucially, you must update the site's configuration to point to this new database. Edit the wp-config.php file in your uploaded files, changing the DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST values to the new ones.

Step 4: Test Thoroughly & Switch DNS

Do not change your domain's nameservers yet. First, test the migrated copy.

  • Access the test site: Your new host will provide a temporary URL (like a subdomain or an IP address). Use that to visit your migrated site.
  • Check everything: Click through pages, test forms, log into the admin dashboard, and ensure images/media loaded. Clear your browser cache if things look odd.
  • The DNS Switch: Only when the test site is perfect, update your domain's nameservers or A record at your domain registrar to point to your new host's server. This propagation can take 24-48 hours globally.
  • Finalize: Once DNS has fully propagated, set up SSL/HTTPS on the new host, and you're done.

The most common pitfall is rushing the DNS change before verifying the new site works. Patience here saves you from downtime.

Frequently asked questions

How long does a WordPress migration take?

The technical file transfer can take 30 minutes to a few hours, depending on your site's size. The longest part is often DNS propagation, which can take up to 48 hours to complete worldwide, though it's often faster.

Will my site be down during migration?

Properly planned, downtime is minimal. You perform the migration on the new server while your old site remains live. Downtime only occurs during the brief period after you switch DNS and before the new site is fully accessible to all visitors.

Do I need to update WordPress URLs after moving?

If you use a migration plugin or correctly update your database during import, URLs should be handled automatically. If you see broken links on your test site, you may need to run a search-and-replace in the database for your old domain name.

What's the biggest risk when migrating?

The biggest risk is not having a verified, restorable backup of your original site. Always confirm you can restore from your backup before making the final DNS cutover. Skipping the testing phase on the new host is a close second.

Affiliate disclosure: If you buy through our links, we may earn a commission at no extra cost to you.

Ready to get started? Check out Hostinger's plans.

Related reads