WordPress hosting for sites leaving Plesk.
Plesk manages WordPress with its own toolkit, which means the site arrives carrying changes it did not make itself and cannot explain.
What Plesk changed on your behalf.
WP Toolkit edits the site directly. Those edits look like corruption on a host that did not make them.
Hardening, identified and re-applied
Toolkit security measures rewrite wp-config values and file permissions. We work out which are in place and reproduce the intent here rather than leaving settings nobody recognises.
Everything in the subscription
A Plesk subscription commonly holds several domains and subdomains plus their databases. Each one is listed and decided on rather than assumed dead.
Scheduled tasks in the panel
Plesk tasks live in the subscription rather than WordPress, so they stop the day it does. Those are read out and recreated as platform jobs.
Two web servers, one site
Plesk usually proxies nginx in front of Apache, which means live rules can be in either .htaccess or the nginx directives. Both get read before either is discarded.
Mail on the subscription
As with any panel host, the domain move takes mail with it unless the MX position is settled beforehand.
Undo what the panel did, then move.
Copying a Plesk site faithfully carries across a set of changes made by software that is no longer present - which is how a migrated site ends up behaving oddly for no visible reason.
- Toolkit changes identified before the copy
- Subscription contents listed and decided
- Cutover at a time you choose
- Old host left running until you confirm
One origin instead of two.
Collapsing a proxied nginx-and-Apache pair into a single tuned origin removes a hop and a whole class of configuration that could disagree with itself.
What we change when a site arrives from Plesk
These are the specific things a Plesk migration needs, and most of them exist because the panel managed the site for you.
| Setting | What we do | Why |
|---|---|---|
| WP Toolkit hardening | Audited and its intent reproduced as platform settings | Toolkit edits wp-config and file permissions directly, and those changes look like damage on a host that did not apply them. |
| Subscription contents | Every domain, subdomain and database enumerated | One subscription frequently serves several sites, and the forgotten one is always the one somebody still uses. |
| Scheduled tasks | Read from the panel and recreated as platform jobs | Plesk tasks belong to the subscription rather than WordPress, so they stop when it is cancelled and nothing reports it. |
| nginx and Apache rules | Both read, then collapsed into a single origin configuration | Plesk proxies one in front of the other, so discarding either without reading it drops rules that were live. |
| MX position agreed before the DNS change | Plesk hosts mail on the subscription, so moving the domain takes the mailboxes unless that is planned. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
What does WP Toolkit actually change about my site?
My subscription has several domains on it. What happens to them?
Where do Plesk scheduled tasks go?
Plesk uses both nginx and Apache. Which rules matter?
Can I export from Plesk myself?
Leave Plesk without inheriting decisions it made for you.
Free migration, toolkit changes understood rather than copied, and one origin instead of two.