• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

8.1 Plesk to 8.2 Plesk Migration

T

tooljob

Guest
Im trying to have as pain free migration as possible.

We have a old server running Plesk 8.1 and want to migrate ALL the data on it to a Plesk 8.2 server.

How do I migrate the data? I saw the Migration Manager in the 8.2 Control Panel . Is it as simple as supplying the hostname and login?

Also, on the old 8.1 server, if the migration fails, will if affect the domains on the old server? Hopefully, not cause that isnt kosher.

Thanks in advance for any input.

One last question would it be smarter to update the 8.1 Plesk sever to the 8.2 Plesk before I try the migration?

Thanks

TJ
 
I just migrated from 8.1.2 on FC2 to 8.2.1 on Centos5. Broke many customers applications which were installed from the vault. Could not re-install many apps from the vault as they were not php 5 compliant. Spam went crazy for some unknown reason as Spamassassin and the block lists are setup the same however everyone is getting 80% more ****. Sitebuilder broke and I have yet to get it working again.. My suggestion is upgrade first, then migrate.
 
You must log in or register to reply here.

Similar threads

C
Issue Plesk Migrator Error(Failed to connect to target Plesk server by Plesk API: Plesk error [1005]: Protocol version '1.6.8.0' is not supported. Current
Replies
2
Views
9K
coffee34
C
S
Question Possible to do a reverse email migration using Plesk migration tool?
Replies
2
Views
3K
sagelike
S
hschramm
Question Debian 12 to 13 Dist-Upgrade
Replies
10
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
M
Resolved Migrator tool imports domain and now domain requires httpAuth to access
Replies
4
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
M
Issue Plesk Migration Gets Stuck On Specific Subscription
Replies
0
Views
3K
Matt M
M
Back
Top