• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Moving a Client (and domains) to a new server.

S

seanstephens

Guest
Hi all;

Got a question regarding DNS, migration and downtime. I have a client on one plesk server with about 10 domains. He wants to move to his own server with plesk (same version). Also he wants to minimize the downtime and if at all possible have no downtime at all.

Now all his TLDs are currently pointed at my server. If I use the migration manager and transfer all his domains to a new server, will the domains remain on the old server until I remove them?

If this is the case then would I be able to change the TLD's to point at the new server, and change the NS records on the old server to point at the new server?

Then hopefully any old requests will get redirected and any new ones will get directed to the new server?

Finally after a couple of days then remove the old domains off the old server?

Will this work?
 
Back
Top