{"id":3630,"date":"2026-10-29T12:47:57","date_gmt":"2026-10-29T11:47:57","guid":{"rendered":"https:\/\/www.panelalpha.com\/blog\/?p=3630"},"modified":"2026-10-29T13:11:12","modified_gmt":"2026-10-29T12:11:12","slug":"panelalpha-engine-2-2-0-wordpress-migration","status":"publish","type":"post","link":"https:\/\/www.panelalpha.com\/blog\/panelalpha-engine-2-2-0-wordpress-migration\/","title":{"rendered":"PanelAlpha Engine 2.2.0: Take your WordPress to your own VPS"},"content":{"rendered":"

The PHP world has been keeping a close eye on security lately, and so have we. We’ve been doing our part to keep PanelAlpha users protected, making sure the necessary fixes and updated images are available. Now that those security updates are in place (and hopefully already installed on your servers), we’re back with something we’ve been looking forward to sharing: PanelAlpha Engine 2.2.0<\/strong>.<\/p>\n

This release brings a much bigger role for WordPress in the new Engine. You can now move an existing WordPress site onto your own server and manage it through an AI assistant, API or CLI.<\/strong> Alongside that, we’ve added more ways to monitor your projects, work with staging copies, and manage the services around your applications.<\/p>\n\n\n

\"PanelAlpha<\/figure>\n\n\n\n

Bring your WordPress to Engine<\/h2>\n\n\n

Moving an existing website to a new server can be tricky, especially when you need to keep its domain, content and settings intact. With Engine 2.2.0, you can import an existing WordPress site<\/strong><\/a> into a new project or an empty one you\u2019ve already created, without having to handle the whole move yourself.<\/p>\n

There are two ways to connect the source site:<\/p>\n\n\n

\n
\n 1<\/span>\n

Let Engine handle it.<\/strong> Simply provide your WordPress admin credentials and Engine will take care of the connection.<\/p>\n <\/div>\n

\n 2<\/span>\n

Do it through a plugin.<\/strong> Install the migration plugin yourself using a temporary link valid for 24 hours.<\/p>\n <\/div>\n<\/div><\/div>\n\n\n

Before starting, Engine can check the source and tell you whether it’s ready to be imported. If something is preventing the move, you get a reason before any new project or files are created.<\/p>\n

Your site keeps its domain, and Engine shows the DNS record you’ll need when you’re ready to point it to the new server. You can follow the import’s progress, resume it if needed, or cancel it and remove what the migration created.<\/p>\n

For us, this is an important part of making self-hosting more practical. You should be able to bring a project you’ve already built, rather than feel that moving to your own server means starting over.<\/p>\n\n\n

Manage WordPress with your assistant<\/h2>\n\n\n

Once your site is running, there’s a lot more you can do without opening wp-admin for every task. Engine now provides dedicated WordPress operations through MCP<\/strong><\/a>, the API and CLI<\/strong><\/a>. Your assistant can help you check and update plugins or themes, manage users, work with WordPress core, clear caches, change settings, or export and import the database.<\/p>\n

These are specific operations rather than instructions to run arbitrary commands, which makes common tasks easier to describe and use. For example, you can ask your assistant to check for plugin updates or clear a site’s cache. And when a plugin or theme is causing trouble, you can run supported operations without loading plugins, giving you another way to work on a site that isn’t behaving as expected.<\/p>\n

Importantly, WordPress running in a project’s own containers is included too<\/strong>. Both the new WordPress operations and WP-CLI<\/strong><\/a> are available there, including database commands. Whether you’re using classic PHP hosting or a container-based WordPress setup, you have more ways to handle maintenance from the tools you already use.<\/p>\n\n\n

See what each project is using<\/h2>\n\n\n

Keeping projects running also means understanding what they need from your server. Engine now records CPU and memory use for each project and each container<\/strong>, with recent measurements and a history you can look back through. Server metrics are available over the last hour, day, week or 30 days, including disk usage.<\/p>\n

You can also see this month’s bandwidth use in the project list, along with clearer information about each application’s type and current status. That makes it easier to see which projects are running normally, which are still building and where you might need to take a closer look. Instead of checking everything separately, you get a more useful picture of your server and the projects on it.<\/p>\n\n\n

\"PanelAlpha

Help us keep Engine moving<\/h3>

We’re building Engine in the open, and every bit of interest helps. If you like what we’re doing, a \u2605<\/strong> on GitHub would mean a lot. And if you’ve got feedback, spotted an issue or want to contribute, we’re always happy to hear from you.<\/p>Explore Engine on GitHub<\/a><\/div><\/div><\/div><\/div>\n\n\n\n

Less manual work around your projects<\/h2>\n\n\n

There are also useful changes to the tools and services around deployment. Engine can now register and maintain deployment webhooks<\/strong> directly with GitHub, GitLab and Bitbucket, so you have fewer steps to handle when connecting a repository. With a project’s Cloudflare token, your assistant can check its settings, clear the cache and adjust its security level. And a new SSL check helps you compare the certificate visible through public DNS with the one served by Engine.<\/p>\n

We’ve also made <\/strong>staging<\/strong><\/a> and <\/strong>cloning<\/strong><\/a> safer for container projects<\/strong>. Copies now get their own database, public address, account, environment variables and tokens rather than sharing those of the original project. WordPress copies use their own database and domain too, and a failed push can roll back its changes. That gives you more room to test without putting the live project at risk.<\/p>\n

Token rotation is available too<\/strong>, allowing you to replace a token while keeping the old one valid for a short handover period. We’ve also tightened how Git commands access remote addresses, kept file operations within their projects, and updated the Engine and account images with the latest OS security fixes.<\/p>\n\n\n

Not done making things easier<\/h2>\n\n\n

We want people to have more control over where their projects run, without all the extra stress that comes with it. With every release, we’re working to make that choice easier, whether you’re moving an existing website, launching something new, or managing projects already running on your server.<\/p>\n\n

There’s always room to improve, and we’re putting as much effort into getting the basics right as we are into building new features. Version 2.2.0 brings plenty of both, so have a look at the full changelog to see what else we’ve been working on.<\/p>\n

View full changelog<\/span><\/a><\/p>\n

\n

Before you update:<\/strong> We’re getting close to having the Control Panel and Engine 2.x working together. But until that happens, if you’re using the PanelAlpha Control Panel, please stick with Engine 1.x. <\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"

The PHP world has been keeping a close eye on security lately, and so have we. We’ve been doing our part to keep PanelAlpha users protected, making sure the necessary fixes and updated images are available. Now that those security updates are in place (and hopefully already installed on your servers), we’re back with something […]<\/p>\n","protected":false},"author":3,"featured_media":3631,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3630","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-release-notes"],"_links":{"self":[{"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/posts\/3630","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/comments?post=3630"}],"version-history":[{"count":27,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/posts\/3630\/revisions"}],"predecessor-version":[{"id":3659,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/posts\/3630\/revisions\/3659"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/media\/3631"}],"wp:attachment":[{"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/media?parent=3630"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/categories?post=3630"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/tags?post=3630"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}