Migrate Guru plugin review and common issues

Migration stalls usually indicate a connectivity issue between Migrate Guru’s servers and your destination host. Check: (1) the destination site is publicly accessible without authentication or maintenance mode; (2) your destination host’s firewall is not blocking incoming connections from Migrate Guru’s IP ranges (check their documentation for the IP list to whitelist); (3) the destination database credentials entered are correct. If the migration has been stuck for over 30 minutes, cancel and restart — Migrate Guru will resume from where possible.

This error means the wp-config.php on the destination site has incorrect database credentials. Migrate Guru should update wp-config.php automatically, but this can fail if file permissions prevent writing. Connect via FTP or the hosting file manager, open wp-config.php, and manually update DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST to match your destination database credentials. The correct values are in your hosting control panel under MySQL Databases.

Destination connection failures mean Migrate Guru cannot reach the plugin on your destination site. Verify: the Migrate Guru plugin is installed and activated on the destination site; the destination site’s URL is correct (no typos, correct protocol http/https); no WAF (web application firewall) or security plugin is blocking Migrate Guru’s connection. Temporarily disable security plugins on the destination during migration and re-enable after completion.

Install Migrate Guru on the source site. In the migration setup, enter the destination site URL (the new domain) and the destination site’s Migrate Guru migration key. Migrate Guru will ask for the new domain during setup and automatically replace all instances of the old domain with the new one during migration — including in the database, serialized arrays, and configuration files. After migration, verify key pages and settings to confirm URL replacement was complete.

Yes, Migrate Guru supports Multisite migrations. The process is the same as a single-site migration: install on the source network, enter destination details, and initiate. Multisite migrations require the destination server to have WordPress Multisite already configured (subdomain or subdirectory mode matching the source). After migration, verify network admin settings and individual subsite URLs. Plugin and theme network-activation status is preserved.

Yes — Migrate Guru is free for sites up to 200GB without any payment required. There is no premium version. The plugin is a free offering from BlogVault as a customer acquisition tool — users who need ongoing backups can then upgrade to BlogVault’s paid backup service. The migration tool itself has no upsell or size limit for the migration function.

For sites over 512MB, Migrate Guru is the better free option. All-in-One WP Migration’s free version caps at 512MB and requires a paid Unlimited extension for larger sites. Migrate Guru handles up to 200GB for free using a server-to-server approach that does not require browser download/upload. The limitation is that Migrate Guru routes through external servers, while All-in-One WP Migration (with Unlimited) handles the transfer via browser on your own connection.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.