Managed WordPress hosting for sites on Scala Hosting and SPanel.
Scala runs its own control panel, its own security layer and its own WordPress manager. None of the three produce a file any other host knows how to read.
Three Scala products between you and your files.
Each one is doing something useful. Each one also means the usual migration path does not apply.
SPanel, not cPanel
The backup format is Scala's own, so there is no cPanel archive for another host to restore. The export is assembled from the filesystem and database rather than handed over as a file.
SShield sitting in front
Their security layer blocks and monitors traffic before WordPress. Export tooling that suddenly makes a lot of requests can trip it, so it is accounted for rather than discovered mid-copy.
SWordPress Manager hardening
It locks file permissions and can enforce a security lock that prevents writes. Copied as-is, those permissions arrive on the new host and stop plugins updating for reasons nothing explains.
Managed VPS or shared
Scala sells both, and a managed VPS may carry several sites, custom services and its own cron. Which one you are on decides how much lives outside WordPress.
Panel-level scheduled jobs
Cron created in SPanel is not visible to WordPress, so those entries are read out of the panel and recreated here before anything is switched.
Undo the hardening on the way out.
The awkward part of a Scala migration is not getting the files. It is that the files arrive with permissions and locks applied by a tool that is no longer there to lift them.
- Export assembled without relying on a panel archive
- File permissions normalised on arrival
- Security lock confirmed lifted
- SPanel cron captured
Managed, without a panel to learn.
A managed VPS gives you resources and a panel to administer them with. What changes here is that the tuning is ours to maintain rather than yours to configure.
What we change when a site arrives from Scala Hosting
Most of these are Scala's own tooling leaving traces that only make sense while their tooling is still running.
| Setting | What we do | Why |
|---|---|---|
| Export path | Files and database assembled directly rather than from a panel backup | SPanel produces backups in its own format, so there is no archive another host can restore and the usual hand-over-a-file migration route simply does not exist. |
| File permissions | Normalised after the copy | SWordPress Manager tightens permissions on the source server, and those modes travel with the files to a host where nothing is left to relax them when an update needs to write. |
| Security lock | Confirmed lifted before the site goes live | Scala's WordPress manager can enforce a lock that blocks writes to core and plugin directories, which on the new host presents as updates that fail with no useful error. |
| SShield interference | Accounted for while the export runs | Their security layer inspects traffic ahead of WordPress and can throttle the burst of requests an export generates, turning a migration into a partial copy nobody notices. |
| Panel cron | SPanel scheduled jobs read out and recreated | Jobs created in Scala's panel exist outside WordPress entirely, so a site export contains no trace of them and they stop the moment the account is closed. |
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.
Scala uses SPanel. Can you restore its backups?
Why do my plugin updates fail after a migration from Scala?
Will SShield block the migration?
I am on a managed VPS with several sites. Can they all move?
Do I lose root access on the VPS?
Leave the panel behind, keep the site intact.
Free migration, hardening unwound deliberately, and nothing closed until you confirm.