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

Question Automate the migration process between Plesk servers using the XML/REST API

AndreyKashin

New Pleskian
Server operating system version
Almalinux 9.7
Plesk version and microupdate number
18.0.74 #2
Hello to the Plesk Support service/community,

We are trying to automate the transfer of subscriptions between Plesk servers running Obsidian 18.x

Previously, the <migration> operator in the XML API allowed you to automate this, but it seems that since Plesk 17.8 it has been deprecated and is no longer part of the current XML or REST API.

Our questions:
1. Is there a supported way to migrate subscriptions using the XML API or REST API in Obsidian/17.8+?

2. Is the Plesk Migrator CLI the only recommended automation method, or are there alternatives?

Are there plans to re-introduce API migration support in future versions?

We would like to implement an automated migration process and would appreciate recommendations on the best approach using modern Plesk tools.

Thanks!
 
Back
Top