• 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.

Question Possible to do a reverse email migration using Plesk migration tool?

sagelike

New Pleskian
Server operating system version
Almalinux
Plesk version and microupdate number
18.0.77
Hi there,

I am in the process of migrating from a older Plesk server to newer Plesk server. Both have same version of Plesk but Source server has older version of AlmaLinux.

Migration is proceeding well but the most worrisome part of the migration will be email which will come at the end.

My question is:

If I migrate email to the Destination server but it doesn't work as planned for some reason and I have to move back the Source server, can I setup a migration on the Source and pull back any new email that may have arrived at the Destination but which now needs to be moved back to the original Source so that no email is lost.

I hope that makes sense.

Thanks in advance,
G
 
Back
Top