Verdant TCS

Cloning One Entire Server to Another

2 min read


Same-domain multisite cloning is now fully operational. We've also made improvements to our cloning scripts, and replaced WP-CLI Search Replace with Interconnectit Search Replace, and MySQLDump and import with MyDumper/MyLoader.
Multisite staging/cloning to a new domain is coming soon!
*Developer plan and above only


If you've had WP_DEBUG active on any of your websites, be sure to deactivate it before you proceed as it may cause a fatal error on the destination site.

Getting Started

Before you begin, ensure that your destination server has ample disk space. This means that should you have at least double enough for all your sites, with space left over.

Cloning one server to another is quite easy. Go to Tools in the top menu bar, select the Server Clone in the Tools. Select your Origin server and your Destination server, and click start task.

Once the process completes, check your sites, and flip DNS to the new server. As a recommendation, we would suggest keeping your old servers for two weeks to ensure that everything is good before decommissioning them. 

The Cloning Process 

The server cloning process follows the same procedure as cloning a site with the same URL from one server to another. You can read our full article here:

Cloning a duplicate site with the same URL to a different server

Specifically, it will copy all production websites across, including the following settings:

  • WordPress Core
  • WordPress Database structure
  • SSL
  • System User (this will be created if it doesn’t already exist)
  • PHP version and settings
  • All General customizer settings including caching
  • All Security customizer settings
  • SMTP
  • Routing (www or none/root)

We will also duplicate your site-specific PHP in settings and PHP process manager settings that GP-CLI manages, alongside the GP-CLI adjusted site-specific Nginx settings and any includes in your site level Nginx directory.

There are 2 things that don’t currently transfer over when cloning. These are: –

  • HTTP Auth
  • AutoSSL


Staging and Canary sites are skipped during the cloning process and so are not transferred from your origin server over to your destination server.

Safety First

Please ensure that all of your sites have cloned correctly before deleting your origin server, and consider keeping all of the original sites for 1-2 weeks while backups have time to take place.

Search the Knowledge Base

New to vCanopy?

Get started with our FREE Core plan today! We bring the software, you bring the hardware.