Different Table Prefixes

In versions of WP Migrate DB Pro older than 2.2.0, one of the limitations was that the site you were migrating to/from had to have the same table prefix. However, WP Migrate DB Pro 2.2.0 includes an update that removes this limitation.

Here’s how it works:

  1. The table prefix is retrieved from the destination site’s wp-config.php file.
  2. On the destination site, new temporary database tables are created. The temporary table names include the destination prefix.
  3. The data is copied from the source site to the temporary tables on the destination site. During this process, values within the temporary options and usermeta tables are updated for compatibility with the prefix of the destination site.
  4. Once the data transfer is complete, the destination site’s tables are dropped and the temporary tables are renamed with the correct destination prefix for the site to function correctly. This completes the migration.

It is important to note that no changes are made to either site’s wp-config.php file. Only the prefixes of the temporary database tables are changed to match the prefix configured in the destination site.

Pre 2.2.0

If you are using an older version of WP Migrate DB Pro, and you migrate between sites with different table prefixes, you will still be presented with the warning message similar to the image below.

Different table prefixes warning

Each warning message is different depending on the situation, so you should follow the instructions showing in your plugin. In most cases, this should resolve the issue.

If you are still having issues, you may want to try changing your table prefix using a plugin like Change Table Prefix.