WP Migrate

As a migrator who is configuring a profile, I propose that migrating "all tables except those selected" should be an option so I don't have to uncheck the same tables every time. In the attached screenshot, only the wp_commentmeta and wp_comments tables would be excluded. This profile could then be saved and reused with the confidence that all tables that exist now or in the future will be included with the exception of those selected tables.

A possibility to add or overwrite WP Options in the wp_options table. It is not that easy or nearly impossible to search and replace settings within (plugin) options because they are stored as serialised objects or arrays that get unserialised during the search and replace process of WP Migrate. So setting an 'on' to 'off' is not possible because it will replace things globally. Here I suggest a static overwriting of the complete value (or inserting when the entry does not exist). But it would be also a nice feature when you could do a search and replace within a option_value focused on one option_name.

As a migrator who works alongside other team members, I want the ability to export and import profiles so my team can quickly share profile configurations and trust that they are identical. This may involve defining profiles as JSON which can be stored in version control and leveraged by teams and agencies when spinning up new sites using a standard configuration.

It would be extremely helpful to be able to the differences between the two sites. We try to pull the live site down to staging whenever we start a new project so that we can push staging up to live when we are done without worrying about overwriting anything on live. We have a lot of clients, so keeping up with whether or not we have projects sitting on the staging site and trying to figure out if the client has made any changes on the live site proves difficult. Being able to see the differences between the two sites before merging would be extremely helpful; even if it's just the sql tables.

In order to deploy from Staging to Production during low traffic times, it would be incredibly helpful if there was a feature to set a time for the copy/deployment to occur.

As a developer who migrates large sites, I want the migration to be capable of running in the background so the migration can continue even if my browser is closed or my network connection is interrupted.

Can I exclude users, so on import the users on the live site don't get overwritten by users in the backup?