WP Panel v1.5.0 is officially released.
This version adds the „Website Migration“ feature, which supports migrating WordPress and general PHP websites between two WP Panel servers of the same version. Website files, databases, domains, SSL certificates, and main runtime configurations can all be transferred and restored through the panel.
What content can be migrated with Website Migration?
Currently supported for migration:
- WordPress websites and general PHP websites
- Website files and databases
- Primary domain and domain aliases
- SSL certificates and private keys
- PHP, Nginx, and FastCGI Cache related configurations
- Website monitoring settings
- WordPress Cron settings
- Panel scheduled tasks that can be safely migrated
- Runtime settings such as CDN Real IP groups
Backup history, access logs, security event history, custom command scheduled tasks, and server-level remote backup credentials will not be migrated. These need to be reconfigured by the administrator according to the new server environment.
Secure connection between two panels
The receiving server can generate one-time pairing information, through which the migrating-out server establishes a panel connection.
The connection process uses HTTPS, one-time high-strength credentials, and certificate fingerprint pinning. Before officially starting the migration, the receiving server also checks:
- Whether the versions and migration protocols of the two panels are consistent
- Whether the receiving server already has the same domain name
- Whether the receiving server has sufficient disk space
- Whether the network connection between the two servers is normal
The panel will not overwrite websites with the same domain name on the receiving server.
Support for migrating multiple websites separately
Administrators can select one, multiple, or all eligible websites at once.
Each website has an independent migration task and running status. If one website fails to migrate, it will not prevent other websites in the same batch from continuing; failed websites can be handled or retried individually.
The migration page displays the current stage, transferred capacity, and real-time transfer speed, allowing administrators to track migration progress.
Streaming chunked transfer and resumable breakpoints
Website files are transferred in streaming tar.zst chunks, without the need to generate a complete website archive on the migrating-out server first.
The system performs size and SHA-256 checks on files, chunks, and database artifacts. If the transfer is interrupted or the panel restarts, it can continue based on the confirmed progress, avoiding re-transferring data that has already been verified.
Large files and databases use independent transfer and verification mechanisms to reduce disk and memory pressure when migrating large websites.
Automatic maintenance mode during migration
After the migration starts, the migrating-out website enters a dedicated maintenance mode and returns HTTP 503, preventing new orders, posts, comments, or other data changes during the migration.
At the same time, WP Panel pauses panel-managed write-type background tasks for that website. Original settings are preserved and will not be permanently altered by the migration process.
After the receiving server completes the restoration of files, database, and runtime configuration, it performs a local health check. If the check passes, the target website is automatically enabled and the runtime settings recorded before migration are restored.
Three handling methods after migration completion
After the receiving server completes the technical migration, the migrating-out server provides three clear options for finalization:
Migration completed
End the current migration task but retain the website files and database on the migrating-out server.
The source website will be displayed as „Migrated“ and will remain in maintenance mode. If you need to re-enable the source site later, you can select „Restore Source Site“ from the website management page.
Migration completed and source site deleted
After ending the migration, proceed to WP Panel's original website deletion process.
This operation will delete the website files, database, system user, and runtime configuration on the migrating-out server. It is suitable when you have confirmed that the new server is running normally and no longer need to keep the old site.
Migration failed
Cancel the current migration and restore the original website on the migrating-out server.
This operation only processes the current server and does not require the receiving server to be online. If the receiving server has already left behind websites or migration resources, they can be handled separately on the receiving server.
DNS remains managed by the administrator
WP Panel does not automatically modify or determine DNS, CDN, or proxy platform resolution results.
After the receiving server completes the migration, administrators still need to do the following themselves:
- Check whether the website on the receiving server is functioning properly;
- Modify the domain resolution to point to the new server;
- Wait for DNS or CDN configuration to take effect;
- Confirm that actual access has switched;
- Then decide whether to keep, restore, or delete the source site.
这样可以避免面板替管理员猜测复杂的公网解析状态。
Preparation before use
使用网站搬家前,请确认:
- 两台服务器都已升级到 WP Panel v1.5.0;
- 两台面板可以通过各自的 HTTPS 地址互相访问;
- 待迁移网站当前处于启用状态;
- 接收服务器不存在相同主域名或域名别名;
- 接收服务器拥有足够的磁盘空间;
- 已了解迁移期间源网站会进入 503 维护状态;
- 已提前规划 DNS 或 CDN 切换时间。
大网站的维护时间主要取决于网站数据量、数据库大小以及两台服务器之间的网络速度,建议在业务低峰期操作。
Upgrade and compatibility
WP Panel v1.5.0 会自动创建网站搬家所需的数据表,无需手动执行 SQL。
升级本身不会修改现有网站文件、数据库、SSL 证书或 Nginx/PHP 配置。只有管理员主动开始搬家后,面板才会对选中的网站启用迁移维护状态并执行相
关操作。
本次版本不涉及安装脚本、面板更新签名或回滚流程变更,已安装服务器可以直接升级。
Upgrade now
WP Panel v1.5.0 已正式发布:
View the v1.5.0 release page (https://github.com/naibabiji/wp-panel/releases/tag/v1.5.0)
After upgrading the two servers involved in the migration, you can enter „Site Migration“ from the „Site Management“ page to establish a panel connection and start the migration.