Scala Hosting Migration

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.

SPanel export handledHardening unwoundFree migration
Free migrationSPanel exportPermissions resetDaily backupsFree SSL24/7 support
A stack of their own

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.

No cPanel archiveAssembled directly

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.

Migration

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
SPanel export
Assembled directly
complete
Permissions
Normalised
reset
Security lock
Lifted
confirmed
DNS cutover
Awaiting your go-ahead
scheduled
Performance

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.

Free
migration, done by us
No
panel to administer
14
edge regions
MagicWP131 ms
Managed VPS, untuned590 ms
Scala shared plan870 ms

Illustrative comparison of a page load before and after the move. Your numbers depend on plan type and how the VPS was configured.

Configuration

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.

SettingWhat we doWhy
Export pathFiles and database assembled directly rather than from a panel backupSPanel 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 permissionsNormalised after the copySWordPress 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 lockConfirmed lifted before the site goes liveScala'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 interferenceAccounted for while the export runsTheir 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 cronSPanel scheduled jobs read out and recreatedJobs 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.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly
Starter
For personal sites, blogs, and portfolios.
$20/mo
Billed $240 yearly · save $60
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
Billed $960 yearly · save $240
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
Billed $3000 yearly · save $600
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Scala uses SPanel. Can you restore its backups?
Not as an archive — the format is Scala's own. The export is assembled from the filesystem and the database directly instead, which reaches the same place without needing another host to understand their backup file.
Why do my plugin updates fail after a migration from Scala?
Usually the hardening came with the files. SWordPress Manager tightens file permissions and can apply a security lock, and once those arrive on a host where that tool is not running there is nothing left to relax them when an update needs to write.
Will SShield block the migration?
It is taken into account beforehand. Their security layer inspects requests ahead of WordPress and can throttle a burst, which is how an export ends up quietly incomplete rather than obviously failed.
I am on a managed VPS with several sites. Can they all move?
Yes, and the first step is listing them. A managed VPS often carries staging copies, side projects and services that nothing in any one site's export would reveal.
Do I lose root access on the VPS?
Yes, and that is the real trade. You get SFTP, WP-CLI and staging instead of a machine and a panel to run it with, which is worth being clear about before the move rather than after.

Leave the panel behind, keep the site intact.

Free migration, hardening unwound deliberately, and nothing closed until you confirm.