Migrates your database by running find & replace on URLs and file paths, handling serialized data, and saving an SQL file.
WP Migrate DB exports your database as a MySQL data dump (much like phpMyAdmin), does a find and replace on URLs and file paths, handles serialized data, then allows you to save it to your computer as an SQL file. To complete the migration, you need to use a database management tool (e.g. phpMyAdmin) to import the SQL file to your database, replacing your existing database. It is perfect for developers who need to migrate fresh data from the production site to their local install, or migrate their locally developed site to a staging or production server.
WP Migrate DB handles serialized data (both arrays and objects) by unserializing the data and going through it, identifying strings and running a find & replace on them. Once it has gone through all the data, it serializes it again and sticks it back in the database.
PRO Version with Email Support and More Features
See the video below or visit the web site to learn more about the pro version.
WP Migrate DB will migrate your entire WordPress database, WordPress’ built-in tools will not. For more details, please see our blog post, WordPress XML Export/Import vs. WP Migrate DB Pro.
Sorry, but we do not offer site migration services at the moment.
It is likely you have a download manager plugin or extension installed in your web browser. You will need to disable it for the SQL download to work properly.
Yep, it will run a find & replace on your serialized data and migrate it without corrupting it. See our documentation for details.
They are the same as the requirements for WP Migrate DB Pro.
If you upgrade to WP Migrate DB Pro, we will gladly provide you with email support. We take pride in delivering exceptional customer support. We do not provide email support for the free version.
WP_Filesysteminitialized on all wp-admin pages
wp_blogstables on multisite
font-familydeclarations from stylesheets
BINARYdata not exported properly
BITdata not exported properly
post_max_sizeis set to 0 (unlimited),
_mig_prefix to wpmdb_alter_statements table
WP_HTTP_BLOCK_EXTERNALconstant is set to true
wpmdb_error_logoption is auto loading
errordoes not exist