This plugin hasn’t been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

WP Clone by WP Academy


WP Clone is the easiest, fastest and most secure way to move or copy a WordPress site to another domain or hosting server. You can also use it to move your site to/from local server hosting, to create copies of your site for development or testing purposes, to backup your site, and to install pre-configured versions of WordPress.

WP Clone is a superior solution to even commercial WordPress cloning plugins for the following reasons:

  • Does not require FTP access to either the source or destination site – just install a new WordPress on the destination site, upload and activate WP Clone plugin, and follow the prompts
  • It does not backup or restore the WordPress system files (just the user content and database) – reducing upload time and improving security of your site
  • It fetches the site backup via your host's direct http connection, which saves you from needing to upload large files through your internet connection

Update January 2017

WP Clone fails to restore in approximately 10% of installations (particularly larger installations),
as reflected in the negative reviews. Please carefully read the section below NO SUPPORT AND DISCLAIMER before you attempt to use this plugin.
You also may use our Paid Site Transfer Service.

Help Video


As mentioned above, WP Clone fails in 10-20% of installations. As such it is NOT intended as a regular backup method, its strength consists in migrating WordPress installations. The failures appear to be related to the multiplicity of WordPress hosting platforms and the size of the installation rather than the WordPress version (so please don’t feedback “WP Clone does not work for my version of WordPress”, this is most probably false). Do however, leave negative reviews and open a discussion on the support forum if you get a failure, providing as much detail as possible, including your hosting system and the size of your site. We will likely not be able to respond, but the information will be useful in helping to isolate the problems with the different hosting systems. Thank you.

Recommendations for using (or not) WP Clone

  • NEVER overwrite an installation for which you do not have an alternate backup source (i.e. a cPanel backup). Normally you would restore onto a fresh WP installation on another host or on a subdomain. If the restore fails your destination site might become unusable, so be prepared to enter cPanel and then destroy / recreate the new installation if necessary.
  • There is never an issue in damaging the source installation. So backup sites at your pleasure. If your backup succeeds it is probable that your restore will also succeed. But don’t take any chances.
  • Large sites (>2GB) might take as long as an hour to backup. Sites of 250 MB or less should take no more than a minute or two, depending on your server.
  • We recommend you deactivate and delete page caching, security and maybe redirection plugins and re-install them on the new site, if necessary. In general, delete all unnecessary plugins and data from your site before you backup. You can also use the “Exclude directories” option if you have large media files, which you can then copy back to the new site with FTP.
  • An alternate method that should work in 99% of installations is to do a “Database Only” backup (use “Advanced Settings”), transfer the wp-content directory over with FTP, and then restore new site.
  • Note also that WP Clone should NOT be used on WP Engine or any hosting system with proprietary operating system. Instead, use their built-in tools.

You can also try the Duplicator plugin or All-in-One WP Migration, both of which work pretty good, but are not as fast as WP Clone to migrate sites; or use the manual method described here


Although we are not able to provide support to every installation, we have spent countless hours improving the plugin and responding to user feedback.
We believe that WP Clone is far and away the easiest WordPress restoration plugin and intend to continue to develop it.
If you are able to support our efforts, use the Donations Page.

Additional documentation

Additional documentation, including supported hosts, at the WP Clone FAQ Page

Other contributors

WP Clone uses functions from the “Safe Search and Replace on Database with Serialized Data” script first written by David Coveney of Interconnect IT Ltd (UK) or and
released under the WTFPL Partial script with full changelog is placed inside ‘lib/files’ directory.

If you are able to help out with plugin development or wish to contribute insights into improving the product, we would also appreciate that very much. Write to


  1. Navigate to Plugins > Add New
  2. Search for “WP Clone”
  3. Install and activate the plugin
  4. Follow remaining instructions in the help video


Review FAQ’s and Help Video at the WP Clone FAQ Page


May 30, 2019
Easist way for archiving and migration to other Hosting/ Самый простой способ сделать архив сайта для миграции на другой хостинг.
Jan 13, 2019
I wasted my 2 days on a plugin that have 1+ Millions active installs but nothing work. Then I find this, I was thinking that it will also not work for me as its not tested with the latest versions on WordPress but It works. Recommended.
Aug 4, 2018
I've used WP Clone for several years, both at the office and at home. This is an absolutely brilliant product that, depending on the size of your site and other factors, can clone your entire site in just seconds! As such, it is a brilliant, wonderful solution if you want to copy your entire site simply and easily with very little effort. I've been using this product for several years now, including when I worked in an IT setting and handled WordPress-based websites. Is this product "perfect"? Well, what product is "perfect", I wonder? So, the answer is "no", it's not absolutely perfect. Now and then, it does not work. This could be due to a variety of factors. However, mostly (I would say 90% of the time), it has worked perfectly for me. So, what does one do if WP Clone doesn't appear to want to work, giving you an error message? First of all, read the official documentation and other comments on the support page. And, let me offer some ideas, here: 1. I've found if you try it once, and get an error message, you should try using it again. I just recently cloned sites from live sites to a localhost installation using XAMPP and in one instance, WP Clone balked and gave me an error message. I simply tried it a second time and this time the backup was restored (i.e., the complete website was cloned to the other location). This worked perfectly! 2. Going from an offline site (localhost using XAMPP) I also had an issue in one instance. It did not appear to want to work at all. So, I did something I read about here or elsewhere on the Web a few years ago: I took the backup package, the zipped file created by WP Clone, copied it to my desktop and then uploaded it to the correct folder on my live hosting. This is under wordpress > wp-content > uploads > wp-clone. Then, I just changed the path for the backup file to match the location on the live server (as opposed to the path generated by the offline, localhost installation). This was made easier for me, because I already had WP Clone installed on the live site and had a previous WP Clone backup there. So, I simply copied the path to the live WP Clone backup that was already there (shown via the WP Clone screen). I copied and pasted that text into a text program, deleted the end of that old file, and then replaced it with the remainder of the name of the new file from WP Clone on my offline, localhost site. So, now I had the new WP Clone backup package (the zipped file, taken from my offline site) in the correct folder on my live system. And, I now had the path and file name of the WP Clone backup file ready to go. I simply copied and pasted the location of the file into the restore function of WP Clone, selected the required radio button and check box and clicked on restore. A few moments later, the offline site had been successfully copied to the live server location! Brilliant! Absolutely perfect! So, those are my two pieces of advice if you have issues with the WP Clone product. First, simply try to restore it again the "normal" way. Just repeat that process. That may be all you need. Second, if you still have issues, copy the zipped backup file to the new desired location (offline, live or wherever). Put it into the wp-clone folder and then, adjusting the path as needed, restore (clone) your site to its new location in that manner. I don't recall now if it ever did not work after following these work-arounds, although it's not impossible. I did some manual site cloning years ago (time consuming) and have used another free plugin (also time consuming and more complex), so WP Clone is what I have used, essentially, all of the time for the past several years. It works for me, I would say 90% of the time! And that is really amazing. I mean, this is a completely free product that can restore or clone your entire site to a new location in just seconds. So, it's not absolutely perfect, but it is, in my experience, a really good, even amazingly good, product! And, if it does not work right away, the little work-arounds I've suggested seem to do the trick and they are easy to do. That's my experience with WP Clone. I have to give it five stars based on my experiences using it.

Contributors & Developers

“WP Clone by WP Academy” is open source software. The following people have contributed to this plugin.


Change log

2.2.4 – 2017-01-28

  • Updated: Admin area.
  • Updated: Tested up to tag.

2.2.3 – 2016-11-29

  • Added: PHP7 support
  • Added: a multisite check during restore.
  • Fixed: failed backups due to unreadable files.

2.2.2 – 2015-12-30

  • Fixed: A bug introduced in 2.2.1 which caused the file archiver to use the wrong zip library on installations where ziparchive is disabled.

2.2.1 – 2015-12-29

  • Fixed: Backup names will use the time zone selected in general settings.
  • Added: basic backup/restore logs.
  • Added: An option to exclude files based on size (files larger than 25MB will be excluded by default)
  • Added: An option to ignore the wordpress table prefix during backup/restore.
  • Added: An option to check the mysql connection during restore.
  • Added: A search and replace tool into the plugin dashboard.
  • Changed: A .htaccess file will be placed in the temporary directories to prevent external access to the files.
  • Changed: Files are no longer copied to a temporary location during backup.
  • Changed: Database import is done before the rest of the files are extracted.
  • Changed: siteurl option is updated during the database import.
  • Changed: search and replace will not run when the URLs are similar.
  • Changed: Increased the default values for memory_limit and max_execution_time from 512MB/300 to 1024MB/600.
  • Removed: The use of wordpress’ unzip_file (ziparchive will be used when available with pclzip as fallback)

2.2 – 2015-11-16

  • Fixed: Missing backups that some users encountered after upgrading to 2.1.9
  • Added: An option to refresh the backup list.
  • Added: An option to remove the database entry and delete all the backup files.
  • Added: A section that shows the uncompressed database size and the uncompressed size and the number of files that will be archived during a full backup.
  • Added: Notes in the advanced settings section regarding the Maximum memory limit and the Script execution time fields.
  • Added: The report returned from the search and replace process into the restore successful page.
  • Changed: Moved the backup list location from the custom table to the wp_options table. (previous backups will be imported and the custom table will be removed on existing installations)
  • Changed: Moved the system information block from the advanced settings section into the “normal” dashboard page.
  • Changed: Only the tables with the wordpress table prefix will be altered during a restore.
  • Changed: Only the tables with the wordpress table prefix will be saved during a backup.
  • Changed: Backup deletion is now handled using AJAX.

2.1.9 – 2015-11-10

  • Disabled heartbeat on wpclone’s admin page.
  • DB_CHARSET in wp-config.php is used during direct database transactions.

2.1.8 – 2014-09-18

  • Updated: Readme description.

2.1.7 – 2014-07-30

  • Changed: Admin page links.

2.1.6 – 2013-07-07

  • Added: An option to exclude specific directories during backup.
  • Added: An option to only backup the database.
  • Added: An admin notice for multisite users.
  • Changed: File operations during backup are now handled directly instead of using the WP filesystem abstraction class.

2.1.5 – 2013-06-05

  • Changed: UI Twitter feed from rss to the official twitter widget.
  • Changed: UI Sidebar link attributes.

2.1.4 – 2013-03-18

  • Fixed: When javascript is disabled,submit button shows “Create Backup” but the plugin attempts to do a restore.
  • Changed: The temporary directory location during the restore process from ‘/wp-content/’ to ‘/wp-content/wpclone-temp/’.

2.1.3 – 2013-03-17

  • Fixed: The ‘copy’ link in the ‘backup successful’ screen which stopped working after the 2.1.2 update.
  • Added: An option to backup the database using WordPress’ WPDB class.
  • Removed: The need to keep the original backup names intact.
  • Removed: ‘lib/DirectoryTree.php’ and ‘lib/class.php’.
  • Changed: The backup name structure.
  • Changed: Backup file downloads are now handled using WP core functions.

2.1.2 – 2013-03-07

  • Fixed: An XSS vulnerability caused by an older version of the ZeroClipboard library.

2.1.1 – 2013-02-16

  • Fixed: a missing nonce action which was causing a wp_nonce_ays loop on some hosts.
  • Fixed: a couple of UI issues.

2.1 – 2012-12-25

  • Added: WP Academy sidebar.

2.0.6 – 2012-08-05

  • Added: WP Filesystem integration
  • Added: Alternate zip method for better compatibility with hosts that haven’t enabled PHP’s zip extension

2.0.5 – 2012-06-25

  • Fixed: A secondary search and replace that was corrupting serialized entries

2.0.3 – 2012-05-16

  • Fixed: ignoring trailing slashes in the site URLs

2.0.2 – 2012-04-12

  • Initial release