WP STAGING – DB & File Duplicator & Migration


WP STAGING for WordPress Migration & Cloning

With this duplicator plugin, you can create an exact copy of your entire website in seconds for staging, backup or development purposes.
(Exact backup time depends on the size of your website)

It creates a clone of your website into a subfolder of your main WordPress installation including an entire copy of your database.

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

All the time-consumptive database and file copying operations are done in the background. The plugin even automatically does an entire search & replace of all serialized links and paths.

This staging and backup plugin works even on the smallest shared hosting servers.

WP Staging can protect your website from being broken or unavailable because of installing untested plugin updates!

Hinweis: WordPress 5.0 wird mit einem neuen Editor namens Gutenberg ausgeliefert.
Benutze WP Staging um zu überprüfen ob Gutenberg wie erwartet auf Deiner Webseite funktioniert und ob alle verwendeten Plugins mit Gutenberg kompatibel sind.

Haupt Features

  • WP STAGING creates the staging website into a subfolder of your production site like example.com/staging-site.
  • No SASS service. All data belongs to you and stays on your server.
  • Easy to use! Create a clone of your site by clicking one button „CREATE NEW STAGING SITE“.
  • No server timeouts on huge websites or/and small hosting servers
  • Very fast – Migration process takes only a few seconds or minutes, depending on the website’s size and server I/O power.
  • Only administrators can access the staging website. (Login with the same credentials you use on your production site)
  • SEO friendly: The staging website is unavailable to search engines due to a custom login prompt and no-index header.
  • The admin bar on the staging website is orange colored and shows clearly when you work on the staging site.
  • All duplicated database tables get a new prefix beginning with wpstg(int)_.
  • Extensive logging features
  • Supports all main web servers including Apache, Nginx, and Microsoft IIS
  • [Premium]: Choose a separate database and select a custom directory for cloning
  • [Premium]: Make the staging website available from a subdomain like dev.example.com
  • [Premium]: Push & migrate entire staging site inc. all plugins, themes, and media files to production website.
  • [Premium]: Define user roles that get access to the staging site only. For instance, clients or external developers.
  • [Premium]: Migration and cloning of WordPress multisites

Note: Some features are Premium. Which means you need WP Staging Pro to use those features. You can get WP Staging Premium here!

  • New: Compatible with WordFence & All In One WP Security & Firewall

Additional Features WP STAGING PRO Edition

  • Cloning and migration of WordPress multisites
  • Define a separate database and a custom directory for cloning
  • Clone your website into a subdomain
  • Specify certain user roles for accessing the staging site
  • Copy all modifications from staging site to the production website

Ändere Deinen Workflow um Themes und Plugins zu aktualisieren.

  1. Use WP Staging to clone a production website for staging, testing or backup purposes
  2. Create a backup of your website
  3. Verändere Themes, Konfigurationen und Plugins oder installiere neue Plugins.
  4. Test everything on your staging site and keep a backup of the original site
  5. If everything works on the staging site start the migration and copy all modifications to your production site!

Warum sollte ich eine Staging Webseite verwenden?

Plugin updates and theme customizations should be tested on a staging platform first before they are done on your production website.
It’s recommended having the staging platform on the same server where the production website is located to use the same hardware and software environment for your test website and to catch all possible errors during testing.

Before you update a plugin or going to install a new one, it is highly recommended to check out the modifications on a clone of your production website.
This makes sure that any modifications work on your production website without throwing unexpected errors or preventing your site from loading. Better known as the „WordPress blank page error“.

Plugins und deren Updates zu Testen bevor diese auf der Produktionswebseite installiert werden, wird nicht sehr oft gemacht weil bisherige Staging Lösungen zu komplex sind und es eine Menge Arbeitszeit bedeutet eine aktuelle Kopie der Webseite zu erstellen.

Some of you might be afraid of installing plugins updates because Your follow the rule „never touch a running system“ with having in mind that untested updates are increasing the risk of breaking Your site.
This is one of the main reasons why WordPress installations are often outdated, not updated at all and insecure because of this non-update behavior.

It’s time to change this, so use „WP Staging“ for cloning, backup and migration of WordPress websites

Can´t I just use my local wordpress development system like xampp / lampp for testing and backup purposes?

You can test your website locally but 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 production website exactly as you 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 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 platform only without creating a backup staging site.

Hier kommt WP Staging ins Spiel: Webseiten Klonen und Staging Seiten erstellen vereinfacht!

Ich möchte nur die Datenbank von einer Installation auf die andere Übertragen.

Um Deine lokale Datenbank auf die Live Datenbank zu migrieren kann ein Werkzeug wie WP Migrate DB verwendet werden. WP Staging und WP Migrate DB arbeiten ausgezeichnet zusammen.

Was sind die Vorteile zu einem Plugin wie Duplicator?

I really the Duplicator plugin. It is a great tool for migrating from a development site to production one or from production site to development one and a good tool to create a backup of your WordPress website.
The downside is that before you can even create an export or backup file with Duplicator a lot of adjustments, manually interventions and requirements are needed before you can start the backup process.
Duplicator also needs some skills to be able to create a backup and development/staging site, where WP Staging does not need more than a click from you.
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.

Wenn Du eine lokal oder gehostete neue Webseite erstellt hast und Du möchtest diese Webseite das allererste Mal auf deine Produktionsdomain übertragen, machst Du nichts falsch, wenn Du das Plugin Duplicator verwendest. Wenn Du regelmäßig eine aktuelle Webseite zum Testen erstellen musst, welche ein aktuelles Abbild Deiner Live Webseite ist, dann empfehle ich Dir WP Staging.

Can I give You some Feedback?

This plugin has been created in thousands of hours and works even with the smallest shared web hosting package.
We also use enterprise level approved testing coding structures to make sure that the plugin runs rock solid on your system.
If you are a developer you will probably like to hear that we use Codeception and PHPUnit for our software.

As there are infinite numbers of possible server constellations it still might happen that something does not work for you 100%. In that case,
please open a support request and describe your issue.


Permalinks are disabled on the staging / backup site after first time cloning / backup creation
Read here how to activate permalinks on the staging site.

Installation und 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



  • Schritt 1. Erstelle eine neue WordPress Staging Seite
  • Schritt 2. Scannen der Webseite nach Dateien und Datenbank Tabellen
  • Schritt 3. WordPress Staging Seiten Erstellungsprozess
  • Finish - Access your backup / staging site


  1. Lade die Datei „wp-staging.zip“ herunter und installiere die Datei über wp-admin > Plugins > Neuer Upload
  2. Hochladen und Installieren via WordPress plugin backend wp-admin > plugins > add new > uploads
  3. Aktiviere das Plugin im Menü ‚Plugins‘ im WordPress Backend.


  • Ich kann mich nicht auf der Staging Seite anmelden
    Wenn Du ein Sicherheits Plugin wie zB. All in One WP Security Firewall verwendest, solltest Du die aktuelleste Version von WP Staging installieren.
    Gehe zu WP Staging > Einstellungen und hinterlege dort die URL zu der Login Seite


27. November 2020
The Pro and even Free versions of helped me so many times. Their support, that is what shines even brighter! Whenever I've needed help, they reply so quickly, and go above and beyond expectations. Highly Recommended!
25. November 2020
Before using staging plugin, i always used to have second thought on upgrading any plugin or wordpress itself, wp-staging solves all these problems. I love this plugin and use it regularly.
24. November 2020
I honestly don't know how you can be a WordPress site developer and *not* use this plugin. It is the best! I have the Pro version with a 5-site license so I can manage various staging sites at once. My clients love being able to log in and see the work I'm doing and when we're ready to launch, it's just a matter of clicking the button to push the changes to the live site.
Lies alle 1.627 Rezensionen

Mitwirkende & Entwickler

„WP STAGING – DB & File Duplicator & Migration“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:


„WP STAGING – DB & File Duplicator & Migration“ wurde in 4 Sprachen übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „WP STAGING – DB & File Duplicator & Migration“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.



  • New: Add special admin notice if plugin is not tested with latest WordPress version
  • New: Compatible up to WordPress 5.5.2
  • New: Allow deleting of orphaned staging site entries if staging site was deleted manually before

  • Fix: Activation hook is not fired after first time installation and wpstg optimizer and cron tasks are not set up

  • Fix: Staging site does not work if database password contains dollar sign in password
  • Fix: Prevent fatal error when the plugin is activated, but there is no permission to create folder wp-content/uploads/wp-staging or wp-content/uploads/wp-staging/logs.

  • Dev: Add new DI container implementation

  • Dev: Add composer 2


  • Fix: Fatal error on activation in pro version (Syntax error)


  • New: Compatible up to WordPress 5.5.1
  • New: Add WP_ENVIRONMENT_TYPE constant for staging site
  • New: Better and wider test coverage
  • New: Implementing of automated CI tests
  • New: Huge code base refactor for cleaner code
  • New: Updated authentication mechanism for ajax requests
  • New: Show welcome video message
  • New: Show message asking for admin credentials on login form
  • New: Move WP STAGING menu down below the menu Plugins
  • New: Selected tables are highlighted with a blue background color
  • Fix: Show access denied message if a non but existing user tries to access the staging site
  • Fix: Remove wp_logout() in staging site login form to prevent multiple login log entries with plugin WP Activity Log
  • Fix: Wrong german translations
  • Fix: Cloning fails if there is no underscore in table prefix


  • New: Compatible up to WordPress 5.4.2
  • Fix: Remove beta notice
  • Fix: Error if views are cloned
  • Fix: Fatal error if WordPress is older than 4.5
  • Fix: Merge pro/free version
  • Fix: Step switching logic does not work properly
  • Fix: Fix progress bar when certains steps are skipped
  • Fix: Change german translation for REPORT ISSUE




  • New: Compatible up to WordPress 5.4.1
  • New: Allow filtering of staging site title
  • Fix: Since WordPress WP 5.4 cloning fails if WordPress is installed in subfolder
  • Fix: Loading icon not shown when disk space is checked
  • Fix: Can not copy tables if prefix is capitalized & has no underscore


  • New: Compatible up to WordPress 5.4
  • Fix: Fatal error on WordPress 4.6 and older


  • HotFix: Prefix hotfix failed


  • HotFix: Fix fatal error in step 6 after updating to WordPress 5.4


  • Fix: Can not login to staging site under certain circumstances
  • Fix: Use user selected language setting instead global site based one
  • Fix: Fatal Error: curl_version() not defined in SystemInfo.php
  • New: Refactored structure for easier maintenance
  • New: Core support for WP Staging snapshots
  • New: Implementing of UnitTests


  • Fix: If server is windows it will result in missing files after cloning and can lead to fatal errors of the staging site


  • Fix: Update function adds duplicate string to internal urls like https://example.com/staging/staging/wp-content/*
  • New: Support for WP 5.3.2


  • Fix: Fatal error: Cannot redeclare wpstgpro_overwrite_nonce() and wpstg_overwrite_nonce() after activating pro version on top of this free one
  • Fix: wpdb->prepare() warning after initial cloning


  • New: Support for WordPress 5.3.1
  • New: Refactoring code base and remove app folder
  • New: Add french language files
  • New: Add WP Staging logo to login form
  • New: Set 24 hours expiration date to process lock
  • New: Add link URL to staging site title
  • Fix: Fatal error: Invalid serialization data for DateTime object #91
  • Fix: Add missing string language location
  • Fix: Function fnmatch() not available in all systems
  • Fix: Warning in staging site after initial cloning in db row rewrite_rules
  • Fix: Wrong staging site is selected when delete function is executed and there are more then 10 staging sites


  • Fix: Broken image folder with duplicate leading slash after cloning


  • New Support for WordPress 5.2.4
  • New: Allow wildcards for excluding files
  • New: Add hook „wpstg_clone_action_staging“ to execute code on staging site after cloning
  • Tweak: Improved support for custom uploads folder if user customized UPLOADS constant or upload_path in DB
  • Fix: Better compatibility with Windows IIS server
  • Fix: External links are broken after cloning if ABSPATH is equal to /www/
  • Fix: use an alternative method for file_put_contents as it is not supported on all systems due to file permission issues
  • Fix: Redundant and duplicated update comments in wp-config.php in staging site


  • Fix: Do not show warning „Preparing Data Step3: Failed to update rewrite_rules in wpstg0_options“
  • Fix: Change error „Table wpstgtmp_options does not exist“ to warning
  • New: Add arguments for hook wpstg_cloning_complete
  • New: Setup server environment variables per process and not globally (e.g. set_time_limit)
  • New: Add support for custom uploads folder if user customized UPLOADS constant or upload_path in DB


  • New: Improve styling of login form. Thanks to Andy Kennan (Screaming Frog)
  • New: Add ‚password lost‘ button to login form
  • New: Change welcome page CTA
  • New: Add feedback option when plugin is disabled
  • Fix: PDO instances can not be serialized or unserialized
  • Fix: Can not update staging site db table if there are constraints in it


  • New: Compatible up to WordPress 5.2.2
  • New: Performance improvement for directory iterator using less server ressources
  • New: Add filter wpstg_folder_permission to set a custom folder permission like 0755, allows to overwrite FS_CHMOD_DIR if it has been defined.
  • Fix: Error conditions in class Data does not compare type strict (== vs. ==) resulting in interruption of clone process
  • Fix: Excluded folders under wp-content level are not take into account on microsoft IIS servers

Komplettes Änderungsprotokoll: https://wp-staging.com/wp-staging-changelog