Lorixen.
EN

Moving a WordPress Site With a Migration Plugin: What Usually Breaks

Short answer: Plugins such as All-in-One WP Migration, Duplicator or UpdraftPlus copy files and the database well, but the move tends to fail on five things: archive size limits on import, URLs stored inside serialised data, scheduled tasks and caching, outgoing email and forms, and the SSL certificate on the new server. Prepare by cleaning the site and noting its settings, import onto the new host, preview it through your computer's hosts file before touching DNS, and only switch traffic once forms, email and checkout pass. Keep the old hosting live for at least a week so you can roll back by changing one DNS record.

Before you export: a short preparation list

Most failed migrations were doomed before the export button was pressed. Spend twenty minutes on this first:

  • Record versions. Note the PHP version, WordPress version and database type on the old host (Tools > Site Health > Info shows all three). Set the new host to the same or a newer, supported PHP version.
  • Shrink the archive. Delete unused themes and plugins, empty the trash, and exclude old backup folders that sit inside wp-content. Backup plugins love storing their own archives there, which doubles the export size.
  • List integrations. Payment gateways, SMTP services, Google Analytics, reCAPTCHA keys tied to a domain, and any IP allow-list at a supplier (for example a stock feed that only accepts calls from the old server's IP).
  • Lower the DNS TTL. At your DNS provider, reduce the TTL on the main A record to something short such as 300 seconds a day before the move, so the final switch spreads quickly.
  • Freeze changes. Tell staff not to publish posts or edit products during the move window. On a shop, choose a quiet hour, because orders placed on the old server after the export will not exist on the new one.

Archive size limits on import

The most searched failure is the import stopping at a size cap. There are two separate limits:

  1. The plugin's own cap. Some free versions of migration plugins limit the size of archive they will import and sell an extension to lift it. Read the plugin's documentation before you rely on it for a large site.
  2. The server's upload limit. PHP settings such as upload_max_filesize, post_max_size and max_execution_time decide how large a file the browser upload can handle and how long the import may run.

Ways around both:

  • Ask the new host to raise the PHP limits temporarily; many do it in minutes.
  • Upload the archive by SFTP into the plugin's import folder and restore it from there instead of through the browser.
  • Move the uploads folder separately by SFTP and export only the database and code through the plugin.

Serialised URLs and the old domain

If the domain stays the same, URLs are less of a concern. If you are also moving from a temporary address, a staging subdomain or from http to https, the old address is stored all over the database, including inside serialised PHP arrays used by widgets, page builders and theme options.

A plain find-and-replace in phpMyAdmin breaks serialised data, because each string carries its own length. The symptom is widgets vanishing or a page builder layout going blank. Use a tool that understands serialisation instead: the migration plugin's own replace step, a dedicated search-replace plugin, or WP-CLI's search-replace command with a dry run first. Also check siteurl and home in the wp_options table, and hard-coded links in theme files or custom CSS.

Preview the new server with your hosts file

Never switch DNS to test. Instead, point only your own computer at the new server:

  1. Get the new server's IP address from the hosting panel.
  2. Edit the hosts file (on Windows C:\Windows\System32\drivers\etc\hosts, on macOS and Linux /etc/hosts) and add a line such as 203.0.113.25 example.com www.example.com with your real IP and domain.
  3. Flush the DNS cache or restart the browser, then load the site. A temporary banner in the admin bar or a test page helps confirm you are really looking at the new server.
  4. Remove the line when testing is finished.

Note that the browser may warn about the certificate during this preview, because the new host cannot issue a certificate for your domain until DNS points there. That warning is expected at this stage.

Cron, caching and other quiet failures

Things that look fine on the homepage but fail later:

  • WP-Cron and real cron. If the old host disabled WP-Cron and ran a server cron job instead, the new server needs the same job. Otherwise scheduled posts, subscription renewals and backup jobs silently stop.
  • Caching layers. Copied cache folders and object cache drop-ins (object-cache.php, advanced-cache.php) can point to Redis or Memcached services that do not exist on the new host, causing errors or a stale site. Purge and reconfigure the cache plugin after import.
  • File permissions. If uploads fail on the new server, check that the web server user can write to wp-content/uploads.
  • Server rules. Redirects or security rules in .htaccess do nothing on an Nginx server. List any you depend on and ask the host to translate them.

Email, forms and SSL after the switch

Once DNS points to the new server:

  • Outgoing mail. WordPress sends through PHP mail by default, which many hosts restrict. Configure an SMTP plugin with your mail provider or a transactional service, then submit every form on the site and confirm the messages arrive.
  • MX records. If you move nameservers as well, copy the MX, SPF, DKIM and DMARC records exactly, or your company email stops.
  • SSL issuance. Request the certificate in the new panel as soon as DNS resolves there. Free certificates are usually issued within minutes, but only once the domain points to the server.
  • Mixed content. Check the browser console for images or scripts still loading over http.

The rollback plan

Keep the old account paid and untouched for at least a week. If something serious breaks after go-live, change the A record back to the old IP, and with the short TTL you set earlier most visitors return to the old server quickly. Write down the old IP and the exact DNS values before you start, so a rollback is a two-minute task rather than a search through old emails.

For the general WordPress steps behind all of this, the official migrating guide is worth a read.

FAQ

Should I migrate with a plugin or ask the new host to do it?

Many hosts offer free migration and handle the size limits on their side. A plugin suits you when you want control over the timing. Either way, run the same testing list before switching DNS.

Why is my new site showing the old content?

Usually the browser or your DNS resolver still points to the old server, or a cache on the new server is serving stale pages. Check with the hosts file method and purge every cache layer.

Do I lose orders placed during the move?

Orders placed on the old server after you exported are not in the new database. Choose a quiet time, put the shop in maintenance mode for the final export, or note those orders and enter them manually.

If a migration has left you with a broken page builder or missing emails, send us the details and we can take the move off your plate.

Sources

WhatsAppBook a call