WP Ghost is compatible with WordPress migration plugins (Duplicator, All-in-One WP Migration, UpdraftPlus, Migrate Guru, WP Migrate DB) as long as you follow a small handoff procedure. For a simple domain change in Settings > General, WP Ghost adjusts automatically because its settings rely on paths, not domains. For a full server or site migration, export your WP Ghost settings with Backup/Restore, deactivate the plugin before migrating so the migration tool sees default WordPress paths, then reactivate and restore your settings on the new server. This keeps everything smooth on both ends.
Why the Handoff Matters
Migration plugins work by taking a snapshot of your WordPress files, database, and configuration, then packaging them for a new server. They expect standard WordPress paths, /wp-admin, /wp-login.php, /wp-content, because that is the structure every migration tool is built against. When WP Ghost is active with custom paths and rewrite rules in place, the snapshot still works, but the destination server may not have the same server configuration (Apache vs Nginx, different .htaccess rules, different hosting panel). Deactivating WP Ghost before the migration removes that dependency entirely and hands the migration tool a clean, default WordPress site to package. Reactivate on the new server and WP Ghost rebuilds its rewrite rules from scratch, this time matching the new environment.
Which Migration Scenario Applies to You?
| Scenario | Action Needed | Complexity |
|---|---|---|
| Domain change only (Settings > General) | Clear cache, verify site | Automatic |
| Same-server URL change (www to non-www, http to https) | Clear cache, run Security Check | Automatic |
| Full site to new server (same domain) | Backup, deactivate, migrate, reactivate, restore | Simple handoff |
| Full site to new server and new domain | Backup, deactivate, migrate, change domain, reactivate, restore | Simple handoff |
| Clone site (staging or duplicate) | Backup, deactivate on source, clone, reactivate both sites, restore settings | Simple handoff |
Domain Name Changes
If you are only changing the domain name in Settings > General (for example, moving from the staging domain to the live domain, or switching from non-www to www), WP Ghost adjusts automatically. WP Ghost’s settings rely on website paths, not the domain name, so the new domain inherits all your security configuration without any extra steps. After making the change, clear any active caches (WordPress cache plugin, server cache, CDN cache) and verify your site loads correctly.
Server or Full Website Migrations
Step 1. Back Up WP Ghost Settings on the Source Site
Before you touch the migration plugin, export your current WP Ghost configuration. Go to WP Ghost > Backup/Restore and click Backup. A JSON file downloads to your computer containing every setting: custom paths, firewall rules, brute force configuration, 2FA settings, security headers, disable options, and every toggle state. Store it safely, do not leave it on the WordPress server. For the full guide, see Backup and Restore.
Step 2. Deactivate WP Ghost on the Source Site
Go to the WordPress Plugins page and deactivate WP Ghost. All custom paths revert to WordPress defaults immediately. The migration plugin can now read standard WordPress structure with no rewrite rules in the way.
Step 3. Run Your Migration
Use your migration plugin of choice (Duplicator, All-in-One WP Migration, UpdraftPlus Clone, Migrate Guru, WP Migrate DB, or your host’s built-in migrator) to move the site to the new server. Follow the migration plugin’s normal procedure. WP Ghost is installed on the destination (because the migration tool moves the files), but it stays deactivated until you are ready.
Step 4. Reactivate WP Ghost on the New Server
Once the migrated site is online at the new server, log in with the default WordPress login (/wp-login.php) and reactivate WP Ghost from the Plugins page. WP Ghost starts with default settings.
Step 5. Restore Your Backup
Go to WP Ghost > Backup/Restore and upload the backup file you saved in Step 1. Click Restore Backup. All your WP Ghost settings apply instantly on the new server.
Step 6. Run a Frontend Test
Go to WP Ghost > Change Paths and run the Frontend Test. This verifies that the new server supports WP Ghost’s rewrite rules without extra configuration. If the test flags an issue, it usually means the new server is Nginx and needs a config file update, see Setup WP Ghost on Nginx Server. For Plesk or other hosting panels, check the hosting and server types guide.
Step 7. Verify with a Security Check
Finally, go to WP Ghost > Security Check and click Start Scan. The scan confirms all path changes, firewall rules, and protections are active on the new server. Any failed checks can be fixed with one click.
Frequently Asked Questions
Which migration plugins does WP Ghost work with?
All major WordPress migration plugins work with WP Ghost as long as you follow the backup-deactivate-migrate-reactivate-restore flow. This covers Duplicator, All-in-One WP Migration, UpdraftPlus (with clone/migrate add-on), Migrate Guru, WP Migrate DB, BackupBuddy, and host-provided migration tools like those offered by WP Engine, Kinsta, and Cloudways.
Do I really need to deactivate WP Ghost before migrating?
Strongly recommended. Some migrations work fine with WP Ghost active, but others run into rewrite rule conflicts, especially when the source server is Apache and the destination is Nginx (or vice versa). Deactivating removes the rewrite rules from the snapshot entirely, so the destination starts clean. It takes 10 seconds and saves hours of troubleshooting.
What if I forgot to back up my settings before migrating?
If WP Ghost was active during the migration, your settings may have migrated with the database. Try activating WP Ghost on the new server, your configuration may load automatically from the migrated options table. If paths do not work, clear cache, run a Frontend Test, and use the emergency disable guide if you get locked out. Then reconfigure from scratch using the Best Practice guide.
Does this work for staging-to-production migrations?
Yes. Configure WP Ghost on staging, test thoroughly, export the backup, and use it to apply the same configuration on production after your staging-to-production push. For agencies deploying the same configuration across multiple sites, the Backup file is your deployment tool, one config, many sites.
Will my custom login path still work on the new server?
Yes, once WP Ghost is reactivated and the backup is restored. In the window between migration and restoration, log in through the default /wp-login.php URL, that is why you deactivate WP Ghost before migrating.
Can I use the Backup file from a Nginx site on an Apache site?
Yes. The backup contains WP Ghost’s settings, not server rewrite rules. When you restore on the new server, WP Ghost generates the correct rewrite rules for that server type (Apache .htaccess or Nginx config). Always run a Frontend Test after restoring to confirm.
Does WP Ghost modify WordPress core files?
No. WP Ghost never touches, moves, or renames any file or folder on your server, including during migrations. All settings live in the WordPress options table, which migration tools handle automatically. Deactivating WP Ghost restores every default path instantly, which is why it is the clean handoff to migration plugins.