Response Samples
A positive response received from server upon successful start of migration task looks as follows:
<packet version="1.6.0.2">
<migration>
<start>
<result>
<status>ok</status>
<migration_id>29054</migration_id>
</result>
</start>
</migration>
</packet>
Such response is received in case the subscription being migrated already exists in destination Plesk.
<packet version="1.6.0.2">
<migration>
<start>
<result>
<status>error</status>
<errcode>15006</errcode>
<errtext>subscription "d1.qa" already exists</errtext>
</result>
</start>
</migration>
</packet>
Such response is received in case the user (reseller or customer) being migrated already exists in destination Plesk.
<packet version="1.6.0.2">
<migration>
<start>
<result>
<status>error</status>
<errcode>15012</errcode>
<errtext>Customer with login name "jimmy_jones" already exists.</errtext>
</result>
</start>
</migration>
</packet>Such response is received in case the source host specified in request cannot be accessed.
<packet version="1.6.0.2">
<migration>
<start>
<result>
<status>error</status>
<errcode>1023</errcode>
<errtext>Unable to start migrations process: Host 10.58.102.1 is not accessible</errtext>
</result>
</start>
</migration>
</packet>
Such response is received in case the customer specified to be migrated does not exist on the source host.
<packet version="1.6.0.2">
<migration>
<start>
<result>
<status>error</status>
<errcode>1013</errcode>
<errtext>Unable to start migrations process: The following clients not exist: nec</errtext>
</result>
</start>
</migration>
</packet>Such response is received if the request packet contained a target-owner node with non-existent user specified as its value.
<packet version="1.6.0.2">
<migration>
<start>
<result>
<status>error</status>
<errcode>1023</errcode>
<errtext>Unable to start migrations process: The target owner "neo" does not exist on the destination host</errtext>
</result>
</start>
</migration>
</packet>
Such response is received if IP the request packet maps IP address of 'shared' type to 'exclusive'.
<packet version="1.6.0.2">
<migration>
<start>
<result>
<status>error</status>
<errcode>1019</errcode>
<errtext>The 'shared' IP cannot migrate to the 'exclusive' IP</errtext>
</result>
</start>
</migration>
</packet>Such response is received if the request packet sent to the server intended to start a migration with IP mapping rules in which a non-existent destination IP was specified.
<packet version="1.6.0.2">
<migration>
<start>
<result>
<status>error</status>
<errcode>15007</errcode>
<errtext>IP "192.0.2.1" does not exist on the destination host</errtext>
</result>
</start>
</migration>
</packet> Such response is received if the request packet sent to the server intended to start a migration with IP mapping rules in which wrong IP type was specified.
<packet version="1.6.0.2">
<migration>
<start>
<result>
<status>error</status>
<errcode>15009</errcode>
<errtext>On the destination host, IP "192.0.2.1" type is "exclusive", not "shared"</errtext>
</result>
</start>
</migration>
</packet>