Legacy hosting migration

Moving a legacy Plesk account to current UKC hosting

Plesk 9 and Plesk 11 are retired platforms. A legacy account should be migrated to a supported UKC server rather than upgraded in place.

Old platformsNo longer supported
Correct routeMigrate the account
Before switchingTest website and mail

Do not follow old Plesk 9 or Plesk 11 upgrade instructions

Those versions, their PHP releases and their operating systems are obsolete. The safe route is a controlled migration to current hosting with application testing before DNS is changed.

Confirm whether the account is actually legacy

  1. Open My Services and select the hosting service.
  2. Use Log in to Plesk and note the Plesk version and server hostname.
  3. If the panel is Plesk Obsidian on a current UKC server, no Plesk 9 or 11 migration is required.
  4. If the service is inaccessible or clearly identifies an old panel, request a migration review.

What needs checking before migration

  • Website software, PHP version, extensions and scheduled tasks.
  • Database names, users, versions and application connections.
  • Mailboxes, aliases, forwarders, autoresponders and recent messages.
  • DNS provider, nameservers, custom records and external services.
  • SSL certificates and any IP allowlists or licensed applications.

How a controlled move normally works

  1. UKC confirms the source account, destination plan and compatibility risks.
  2. Website, database and mail data are copied to current hosting.
  3. The copied website and essential functions are tested on the destination.
  4. A final data synchronisation is scheduled for content that continued changing.
  5. DNS is updated and both platforms are monitored during propagation.

The expected interruption depends on the application, data volume, DNS and mail activity. It should be assessed for the individual service rather than promised as universally zero downtime.

Information that helps us plan the move

Service
Domain name, UKC service and current server or panel.
Application
CMS or custom software and any known version requirements.
Change window
Preferred quiet period and any business-critical dates.
External links
APIs, allowlists, payment services or licences tied to the old server.

Do not send passwords in the ticket. UKC will use the access already held for the managed service or provide a secure method if additional access is required.

Ready for a legacy hosting review?

Send the service details above and describe the website's most important user journey, such as checkout, login or form delivery. We will identify the appropriate current platform and the checks required before switching.

Request a migration review

Was this answer helpful?

« Back