• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Migration 17.5 > 17.0.x blocked... temporary workaround???

mr-wolf

Silver Pleskian
Plesk Guru
Being curious concerning the new features of 17.5 I upgraded one of my servers that are planned for termination soon. On this server I still had 3 websites that couldn't be migrated properly.

The webmaster of that site worked on that and now he has them successfully running on the new server.

I now want to repeat the Plesk migration of those sites as they are now not up-to-date anymore, but to my shock this is not allowed anymore.

Can I patch something so this check is skipped?
Otherwise I need to do it by hand...
 
To my knowledge a migration cannot be done from a newer version to an older version of the panel. It is only possible from an older version to the same or newer version.

However, it should be very easy to pack the files like

tar -czf my_archive.tar.gz /httpdocs
and dump the database content, then unpack them on the other server
tar -xf my_archive.tar.gz
and import the database dump there.

E-Mails can be migrated by drag & drop when you open both mailboxes (old and new server) at the same time in a mail client.
 
Back
Top