Starting Subscription Migration

To transfer a subscription to Plesk, nest the migrate-webspaces node into the selected-objects node. The node is defined by complex type SelectedDomains (plesk_migration.xsd) and structured as follows:

SelectedDomains

  • The target-owner node is required. It defines the login name of subscription owner (admin, reseller or customer) after migration. Data type: string.
  • The webspace node is required. It holds the collection of data defining settings for the migration of a subscription. Data type: MappedDomain (plesk_migration.xsd).
    • The name node is required. It defines the name of the subscription (in unicode) that should be migrated. Data type: string.
    • The ip node is optional. It defines mapping rules for the IP address on which the subscription is hosted. For information on this node structure, refer to the IP Addresses Mapping section. Data type: MappedIp (plesk_migration.xsd).
    • The db-server node is optional. It defines mapping rules for databases used on the subscription. For information on this node structure, refer to the Databases Mapping section. Data type: MappedDbServer (plesk_migration.xsd).

Important: When creating request packets, put nodes and elements in the order they follow in the packet structure.

Remarks

To make the customer accounts owned by Plesk administrator after migration, include the target-owner node with value "admin" in the request packet.

 

Next in this section:

Request Samples

 
Request Samples
1. Starting migrations in Plesk for Windows

1.1 Migrating a single subscription

This packet starts migration of subscription called example.com from remote Plesk for Windows server with only the required options specified. When the migration is completed, the subscription will belong to a customer with login name "mary_jane".

<packet>
<migration>
<start>
   <host>192.0.2.220</host>
   <login>admin</login>
   <password>jkSGtvbg55</password>
   <destination-host-directory/>
   <system-type>windows</system-type>
   <selected-objects>

      <migrate-webspaces>
         <target-owner>mary_jane</target-owner>
         <webspace>
            <name>example.com</name>
         </webspace>
      </migrate-webspaces>
   </selected-objects>
</start>
</migration>
</packet>

 

1.2. Migrating multiple subscriptions to a single owner

This packet migrates mail content and configuration of domains example.com and sample.com from remote server running Linux. The data will be transferred using the rsync transport protocol. When the migration is completed, the domains will belong to Plesk administrator.

<packet>
<migration>
<start>
   <host>192.0.2.221</host>
   <login>admin</login>
   <password>jkSGtvbg55</password>
   <destination-host-directory/>
   <system-type>unix</system-type>
   <content-transport>rsync</content-transport>
   <only-mail/>

   <selected-objects>
      <migrate-webspaces>
         <target-owner>admin</target-owner>
         <webspace>
            <name>example.com</name>
            <ip>
              <old>
                <ip-type>shared</ip-type>
                <ip-address>192.0.2.110</ip-address>
              </old>
              <new>
                <ip-type>shared</ip-type>
                <ip-address>192.0.2.112</ip-address>
              </new>
            </ip>
            <db-server>
              <old>
                <host>q3.sample.org</host>
                <port>3306</port>
                <type>mysql</type>
              </old>
              <new>
                <host>localhost</host>
                <port>3306</port>
                <type>mysql</type>
              </new>
            </db-server>
         </webspace>
         <webspace>
            <name>sample.com</name>
            <ip>
              <old>
                <ip-type>shared</ip-type>
                <ip-address>192.0.2.109</ip-address>
              </old>
              <new>
                <ip-type>shared</ip-type>
                <ip-address>192.0.2.111</ip-address>
              </new>
            </ip>
            <db-server>
              <old>
                <host>q3.sample.org</host>
                <port>3306</port>
                <type>mysql</type>
              </old>
              <new>
                <host>localhost</host>
                <port>3306</port>
                <type>mysql</type>
              </new>
            </db-server>
         </webspace>
      </migrate-webspaces>
   </selected-objects>
</start>
</migration>
</packet>

 

1.3. Migrating multiple subscriptions to multiple owners

This packet starts migration of three subscriptions called meaning-of-life.net, holy-grail.net and gold-member.net from server running Microsoft Windows. The data will be transferred using the rsync transport protocol. After the migration, the first two subscriptions will belong to user with login name "monty_python", and the last, to user with login "austin_powers".

<packet>
<migration>
<start>
   <host>192.0.2.200</host>
   <login>admin</login>
   <password>jkSGtvbg55</password>
   <destination-host-directory/>
   <system-type>windows</system-type>
   <content-transport>rsync</content-transport>
   <selected-objects>

      <migrate-webspaces>
         <target-owner>monty_python</target-owner>
         <webspace>
            <name>meaning-of-life.net</name>
         </webspace>
         <webspace>
            <name>holy-grail.net</name>
         </webspace>
      </migrate-webspaces>

      <migrate-webspaces>
         <target-owner>austin_powers</target-owner>
         <webspace>
            <name>gold-member.net</name>
         </webspace>
      </migrate-webspaces>

   </selected-objects>
</start>
</migration>
</packet>

  

2. Starting migrations in Plesk for Unix

2.1. Migrating a single subscription

This packet migrates only Web site hosting data of subscription called example.com, with mapping rules for the IP address on which the domain is hosted and for two databases (MySQL and PostgreSQL) used on the domain. The data will be transferred using the rsync transport protocol. When the migration is completed, the domain will belong to a user with login name "john-doe".

<packet>
<migration>
<start>
   <host>192.0.2.220</host>
   <login>admin</login>
   <password>jkSGtvbg55</password>
   <destination-host-directory>/tmp</destination-host-directory>
   <content-transport>rsync</content-transport>
   <only-hosting/>
   <selected-objects>

      <migrate-webspaces>
         <target-owner>john-doe</target-owner>
         <webspace>
            <name>example.com</name>
            <ip>
               <old>
                  <ip-type>shared</ip-type>
                  <ip-address>192.0.2.228</ip-address>
               </old>
               <new>
                  <ip-type>shared</ip-type>
                  <ip-address>192.0.2.15</ip-address>
               </new>
            </ip>
            <db-server>
               <old>
                  <host>localhost</host>
                  <port>3306</port>
                  <type>mysql</type>
               </old>
               <new>
                  <host>mysql3.sample.net</host>
                  <port>3306</port>
                  <type>mysql</type>
               </new>
            </db-server>
            <db-server>
               <old>
                  <host>localhost</host>
                  <port>5432</port>
                  <type>postgresql</type>
               </old>
               <new>
                  <host>localhost</host>
                  <port>5432</port>
                  <type>postgresql</type>
               </new>
            </db-server>
         </webspace>
      </migrate-webspaces>
   </selected-objects>
</start>
</migration>
</packet>

2.2. Migrating multiple subscriptions to a single owner

This packet migrates mail content and configuration of subscriptions example.com and sample.com from remote server running Linux. The data will be transferred using the rsync transport protocol. When the migration is completed, the domains will belong to Plesk administrator.

<packet>
<migration>
<start>
   <host>192.0.2.221</host>
   <login>admin</login>
   <password>jkSGtvbg55</password>
   <destination-host-directory>/temp/mgr</destination-host-directory>
   <content-transport>rsync</content-transport>
   <only-mail/>

   <selected-objects>
      <migrate-webspaces>
         <target-owner>admin</target-owner>
         <webspace>
            <name>example.com</name>
            <ip>
              <old>
                <ip-type>shared</ip-type>
                <ip-address>192.0.2.110</ip-address>
              </old>
              <new>
                <ip-type>shared</ip-type>
                <ip-address>192.0.2.112</ip-address>
              </new>
            </ip>
            <db-server>
              <old>
                <host>q3.sample.org</host>
                <port>3306</port>
                <type>mysql</type>
              </old>
              <new>
                <host>localhost</host>
                <port>3306</port>
                <type>mysql</type>
              </new>
            </db-server>
         </webspace>
         <webspace>
            <name>sample.com</name>
            <ip>
              <old>
                <ip-type>shared</ip-type>
                <ip-address>192.0.2.109</ip-address>
              </old>
              <new>
                <ip-type>shared</ip-type>
                <ip-address>192.0.2.111</ip-address>
              </new>
            </ip>
            <db-server>
              <old>
                <host>q3.sample.org</host>
                <port>3306</port>
                <type>mysql</type>
              </old>
              <new>
                <host>localhost</host>
                <port>3306</port>
                <type>mysql</type>
              </new>
            </db-server>
         </webspace>
      </migrate-webspaces>
   </selected-objects>
</start>
</migration>
</packet>

 

 

2.3. Migrating subscriptions to multiple owners

This packet starts migration of three subscriptions called meaning-of-life.net, holy-grail.net and gold-member.net from server running Microsoft Windows. The data will be transferred using the rsync transport protocol. After the migration, the first two domains will belong to user with login name "monty_python", and the last, to user with login "austin_powers".

<packet>
<migration>
<start>
   <host>192.0.2.200</host>
   <login>root</login>
   <password>jkSGtvbg55</password>
   <destination-host-directory>/temp/mgr</destination-host-directory>
   <content-transport>rsync</content-transport>
   <selected-objects>

      <migrate-webspaces>
         <target-owner>monty_python</target-owner>
         <webspace>
            <name>meaning-of-life.net</name>
         </webspace>
         <webspace>
            <name>holy-grail.net</name>
         </webspace>
      </migrate-webspaces>

      <migrate-webspaces>
         <target-owner>austin_powers</target-owner>
         <webspace>
            <name>gold-member.net</name>
         </webspace>
      </migrate-webspaces>

   </selected-objects>
</start>
</migration>
</packet>