WP Staging – DB & Datei Duplizieren & Migrieren


This cloning and staging plugin is well tested but work in progress.

If you find any issue, please open a support ticket.

Note: For pushing & migrating plugins and theme files to live site, check out https://wp-staging.com/

WP Staging for WordPress Migration

This duplicator plugin allows you to create an staging or development environment in seconds*

It creates a clone of your website into a subfolder of your main WordPress installation including an entire copy of your database.
This sounds pretty simple and yes it is! All the hard time-consumptive database and file copying stuff including url replacements is done in the background.

I created this plugin because all other solutions are way too complex, overloaded with dozens of options or having server requirements which are not available on most shared hosting solutions.
All these reasons prevent user from testing new plugins and updates first before installing them on their live website, so its time to release a plugin which has the potential to be merged into everyone´s wordpress workflow.

* Time of creation depends on size of your database and file size

WP Staging helps you to prevent your website from being broken or unavailable because of installing untested plugin updates!

Note: WordPress 5.0 will be shipped with a new visual editor called Gutenberg. Use WP Staging to check if Gutenberg editor is working as intended on your website and that all used plugins are compatible with that new editor.

Main Features

  • Easy: Staging migration applicable for everyone. No configuration needed!
  • Fast: Migration process lasts only a few seconds or minutes, depending on the site’s size and server I/O power
  • Sicher: Zugang zur geklonten Staging Seite wird nur Administratoren gestattet.

    Auch sicher:

  • Admin bar reflects that you are working on a staging site
  • Extensive logging if duplication and migration process fails.

What does not work or is not tested when running wordpress migration?

  • WordPress migration of wordpress multisites (not tested)
  • WordPress klonen auf einem Windows Server (nicht getestet, dürfte aber funktionieren)
    Änderung: Klonen auf einem Windows Server scheint gut zu funktionieren: Mehr lesen

Change your workflow of updating themes and plugins data:

  1. Use WP Staging for migration of a production website to a clone site for staging purposes
  2. Customize theme, configuration and plugins or install new plugins
  3. Test everything on your staging site first
  4. Everything running as expected? You are on the save side for migration of all these modifications to your production site!

Why should i use a staging website?

Plugin updates and theme customizations should be tested on a staging platform first. Its recommended to have the staging platform on the same server where the production website is located.
When you run a plugin update or plan to install a new one, it is a necessary task to check first the modifications on a clone of your production website.
This makes sure that any modifications is working on your website without throwing unexpected errors or preventing your site from loading. (Better known as the wordpress blank page error)

Testing a plugin update before installing it in live environment isn´t done very often by most user because existing staging solutions are too complex and need a lot of time to create a
up-to-date copy of your website.

Some people are also afraid of installing plugins updates because they follow the rule „never touch a running system“ with having in mind that untested updates are increasing the risk of breaking their site.
I totally understand this and i am guilty as well here, but unfortunately this leads to one of the main reasons why WordPress installations are often outdated, not updated at all and unsecure due to this non-update behavior.

I think its time to change this, so i created „WP Staging“ for WordPress migration of staging sites

Can´t i just use my local wordpress development copy for testing like xampp / lampp?

Nope! If your local hardware and software environment is not a 100% exact clone of your production server there is NO guarantee that every aspect
of your local copy is working on your live website exactely as you would expect it.
There are some obvious things like differences in the config of php and the server you are running but even such non obvious settings like the amount of ram or the
the cpu performance can lead to unexpected results on your production website.
There are dozens of other possible cause of failure which can not be handled well when you are testing your changes on a local staging platform.

This is were WP Staging steps in… Site cloning and staging site creation simplified!

I just want to migrate the database from one installation to another

If you want to migrate your local database to a already existing production site you can use a tool like WP Migrate DB.
WP Staging is only for creating a staging site with latest data from your production site. So it goes the opposite way of WP Migrate DB.
Both tools are excellent cooperating eachother.

What are the benefits compared to a plugin like Duplicator?

At first, i love the Duplicator plugin. Duplicator is a great tool for migrating from development site to production one or from production site to development one.
The downside is that Duplicator needs adjustments, manually interventions and prerequirements for this. Duplicator also needs some skills to be able to create a development / staging site, where WP Staging does not need more than a click from you.
However, Duplicator is best placed to be a tool for first-time creation of your production site. This is something where it is very handy and powerful.

So, if you have created a local or webhosted development site and you need to migrate this site the first time to your production domain than you are doing nothing wrong with using
the Duplicator plugin! If you need all you latest production data like posts, updated plugins, theme data and styles in a testing environment than i recommend to use WP Staging instead!

I need you feedback

This plugin has been done in hundreds of hours to work on even the smallest shared webhosting package but i am limited in testing this only on a handful of different server so i need your help:
Please open a support request and describe your problem exactely. In wp-content/wp-staging/logs you find extended logfiles. Have a look at them and let me know the error-thrown lines.


Per default the staging site will have permalinks disabled because the staging site will be cloned into a subfolder and regular permalinks are not working
without doing changes to your .htaccess or nginx.conf.
In the majority of cases this is abolutely fine for a staging platform and you still will be able to test new plugins and do some theme changes on your staging platform.
If you need the same permalink stucture on your staging platform as you have in your prodcution website you have to create a custom .htaccess for apache webserver
or to adjust your nginx.conf.

How to install and setup?

Installiere es über dein Administrations Dashboard klicke im Punkt ‚Plugins‘ auf ‚Installieren‘ und suche in den Plugins nach ‚Staging‘. Installiere das Plugin ‚WP Staging‘ mit dem ‚Installieren‘-Button.
Gehe nach der Installation auf die Einstellungsseite (oder ‚Settings‘) des Punktes ‚Staging‘ und mache dort deine Einstellungen.

Offizielle Webseite



  • Step 1. Create new WordPress staging site
  • Step 2. Scanning your website for files and database tables
  • Step 3. WordPress Staging site creation in progress
  • Finish!


  1. Downloade die Datei „wp-staging“, entpacke sie und verschiebe den Inhalt in deinen wp-content/plugins/wp-staging Ordner. Alternativ kannst du auch über das WordPress plugin System installieren.
  2. Aktiviere das Plugin im Menü ‚Plugins‘ im WordPress Backend.
  3. Start Plugins > Staging


  1. Downloade die Datei „wp-staging“, entpacke sie und verschiebe den Inhalt in deinen wp-content/plugins/wp-staging Ordner. Alternativ kannst du auch über das WordPress plugin System installieren.
  2. Aktiviere das Plugin im Menü ‚Plugins‘ im WordPress Backend.
  3. Start Plugins > Staging


Great Plugin, it just needs 1 more thing

This plugin is awesome and a real slap on the face of web hosts that can’t provide us a proper staging site (come on, guys!!!). I was really impressed to see how everything went fast and smooth.

The only thing this plugin needs to get a 5 star is not changing the link structure on the staging site. I mean, it’ll be no problem for you if you just want to check something on stage. But if your idea is to get this data back to run on your live site, then you’re in trouble (that was my case)!

I even considered buying the premium plugin (even though is way too expensive if you buy a single license and you’re not going to use it often), but when I realized that even the premium version doesn’t solve that problem I saw no use. Instead, I used the money to pay someone to finish the job for me (btw, it was cheaper than the plugin and he did the full job).

Recommending in a tutorial a third party plugin to do a search & replace (with huge chances of you doing something wrong and messing everything up) and finish the job was really disappointing.

Just keep the link structure as it is and you’ll deserve way more than 5 stars!

Easy to use!

I found the plugin easy to use and very helpful.

Lies alle 508 Rezensionen

Mitwirkende & Entwickler

„WP Staging – DB & Datei Duplizieren & Migrieren“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:




  • Fix: Old staging site is not listed and pushing is not working properly if plugin is updated from wp staging version 1.6 and lower


  • New: Performance improvement increase db query limit to 5000
  • New: Detect automatically if WordPress is installed in sub folder
  • Tweak: Tested up to WP 4.9.4
  • Fix: Updating from an old version 1.1.6 < to latest version deletes the staging sites listing table
  • Fix: Reduce memory size of the logging window to prevent browser timeouts
  • Fix: Can not copy db table if table name contains the db prefix multiple times
  • Fix: Some excluded folders are not ignored during copy process
  • Fix: mod_security is causing script termination
  • Fix: Skip directory listings for symlinks


  • Fix: Increase the max memory consumption


  • Tweak: Return more human readable error notices
  • Fix: Cloning process stops due to file permission issue
  • Fix: Exclude WP Super Cache from copying process because of bug in WP Super Cache, see https://github.com/Automattic/wp-super-cache/issues/505


  • New: increased speed for cloning process by factor 5, using new method of file agregation
  • New: Skip files larger than 8MB
  • Fix: Additional checks to ensure that the root path is never deleted
  • New: Compatible up to WP 4.9.1


  • Fix. Change link to support
  • Fix: Missing files in clone site if copy file limit is higher than 1


  • Fix: Link to the staging site is missing a slash if WordPress is installed in subdir
  • Tweak: Allow file copy limit 1 to prevent copy timeouts


  • New: Add more details to tools->system info log for better debugging
  • New: Add buttons to select all default wp tables with one click
  • New: Show used db table in list of staging sites
  • Fix: Delete staging site not possible if db prefix is same as one of the live site
  • Fix: Edit/Update clone function is duplicating tables.
  • Fix: Other staging site can be overwritten when Edit/Update clone function is executed
  • Fix: Several improvements to improve reliability and prevent timeouts and fatal errors during cloning


  • Fix: Remove LOCK_EX parameter in file_put_contents(). LOCK_EX is not working on several systems which results in cloning process timeouts
  • Fix: Huge Performance improvement in copying process by removing duplicate file entries in the cache file. This also prevents weird timeout issues on some hosted websites
  • Fix: Error 500 when debug mode is activated
  • Fix: Limit maximum execution time to 30 seconds
  • Fix: Sanitize Clone Names and Keys to fix „clone not found“ issue in upgrade routine
  • Fix: Do not clone the plugin wps-hide-login
  • Fix: Staging sites can not be deleted if they are very big
  • Fix: Link to staging site is undefined
  • Tweak: Better admin message for asking for a review
  • Tweak: Remove table wpstg_rmpermalinks_executed when plugin is uninstalled
  • New: New setting to specify the maximum amount of files copied within one ajax call to fix godaddy and bluehost ajax 404 errors. Default 10 per batch


  • New: Add link to tutorial explaining the process of pushing modification to the live site


  • New: Exclude unneccessary files from cloning process: .tmp, .log, .htaccess, .git, .gitignore, desktop.ini, .DS_Store, .svn
  • New: More details for debugging in Tools->System Info
  • Fix: Check if tables in staging site exists before attempting to modify them
  • Fix: WordPress in sub directories were not opening
  • Fix: Nonce check not working if nonce life time is filtered by another plugin WP Bug: https://core.trac.wordpress.org/ticket/41617#comment:1
  • Fix: Access to staging site not working, if WP_SITEURL and WP_HOME is defined in wp-config.php
  • Tweak: Exclude wp-content/cache folder from copying process


  • Skip Version


  • Fix: After update from wpstg 1.6.x to 2.x previous settings were not imported resulting in cancelation of cloning process. Still not fixed in 2.0.7


  • Fix: After update from wpstg 1.6.x to 2.x previous settings were not imported resulting in cancelation of cloning process


  • Fix: Cancel Cloning button not working
  • Fix: Limit max execution time to a maximum of 30sec to prevent high memory consumption and script timeouts


  • New: Major version – Complete rewrite of the code base
  • Neu: Batch-Abarbeitung erlaubt das Klonen von sehr großen Seiten ohne Timeouts.
  • Neu: Vorbereitungen für WP QUADS PRO mit der Möglichkeit, Dateien zurückzukopieren auf die Hauptseite
  • New: Bypass (broken) third party plugins during wp staging related ajax requests to prevent processing errors. Use a mu plugin for this.


  • Neu: Hinzugefügt: Download Link zu New: WP Staging Beta Version 2.0.1


  • Fix: Admin notice is throwing a false positive write permission error
  • New: Move log folder to wp-content/uploads/wp-staging/logs
  • New: Tested up to WP 4.7.3


  • Fix: Fatal error Unsupported operand types


  • New: Tested up to wp 4.7.2
  • Fix: Arrows in drop down for folder selection are distorted
  • Tweak: Show working log as default to make debugging easier


  • Fix: Settings are not deleted when plugin is removed
  • Fix: Staging site is available for non administrators


  • Fix: Change rating url


  • New: Tested up to WP 4.6
  • New: Create a poll and ask what feature is most required


  • Fix: Undefined WPSTG() warning
  • Fix: Change compatibility version to wp 4.5.3


  • Tested up to WP 4.5.2


  • Fix: Activation hook is not fired and staging site is not working properly
  • Performance: Increase default query copy limit to 1000


  • Fix: Uninstalling plugin throwing error
  • Fix: Error permission admin notice although permission issues are correct


  • New: Tested up to WP 4.5
  • Fix: Download system log not working
  • Fix: Click on Optimizer „Select all | none | invert“ links leads to jumping
  • Tweak: Make clear that unselecting a checkbox will exlude table or file from copy process
  • Tweak: Remove unnecessary text
  • Tweak: Change beta notice in dashboard. WP Staging is stable
  • Tweak: Change twitter handle to @wpstg


  • Fix: Missing const MASHFS_VERSION
  • Fix: Remove error „table XY has been created, BUT inserting rows failed.“
  • Fix: Not tested up to 4.4.2 message shown although it’s tested up to WP 4.4.2
  • New: Disable either free or pro version and does not allow to have both version enabled at the same time


  • Tweak: Change setting description of uninstall option
  • Tweak: Lower tags in readme.txt


  • New: Orange colored admin bar on staging site for better visualization and comparision between production live site and staging site
  • Tweak: Remove contact link on multisite notification


  • Fix: Do not follow symlinks during file copy process
  • Fix: css error
  • Fix: Show „not-compatible“ notice only when blog version is higher than plugin tested version.
  • Fix: undefined var $size
  • Fix: Check if $path is null before writing to remaining_files.json
  • Fix: $db_helper undefined message
  • Fix: Skip non utf8 encoded files during copying process

Complete changelog: https://wp-staging.com/changelog.txt