Most migrations go smoothly when a few details are checked first. The BladeCP WordPress Migrator runs these checks for you, but it helps to know what it looks at and why.
1. One site, served from the root of its domain
The plugin moves a single WordPress site. Multisite networks are not supported yet, and the site must answer at the root of its domain, not from a subfolder such as example.com/blog.
2. Versions and PHP extensions
WordPress 6.0 or later and a 64-bit PHP 7.4 or later are required, with the sodium or OpenSSL extension. The cURL and zlib extensions are recommended: cURL streams large upload parts from disk and zlib compresses the package.
3. Free disk space
The package is built next to the site before it is sent, so the hosting account needs room for it. The check estimates the space from the size of the files and the database.
4. Custom settings in wp-config.php
The original wp-config.php does not travel. BladeCP writes a new one with new database credentials and fresh security keys, so any custom setting you added there must be added again after the migration.
5. A dashboard served over HTTPS
Connecting to BladeCP requires the WordPress dashboard to be served over HTTPS. The connection uses a one-time code and comes back to the same screen of the dashboard.
If something blocks the migration, the check says so before any package is built, and the buttons to connect and to start stay disabled until it is fixed.
