Do you have paper beside your keyboard right now with a list of changes you need to make in the WordPress dashboard right after deploying your site to production? You wouldn’t be the first. This is what responsible developers have been doing since the very first sites were built on WordPress.
What if you forget to write down a change? Or when deploying you accidentally skip an item? A little mistake could be costly. And you’ll probably be performing the deployment at an ungodly hour, feverishly comparing the data on your dev site to your live site, and rushing to get the site back online. Pressure is high and you’re tired and stressed out. There’s a good chance you’ll make that costly mistake.
Mergebot takes the stress out of WordPress database deployments and reduces the likelihood of human error to nearly zero.
From the team behind WP Migrate DB Pro
With the Mergebot plugin installed on your dev/staging site, changes that you make in the WordPress dashboard are saved to the Mergebot cloud app and ready to be deployed. At any time, you can refresh your dev/staging site with the latest production database and deploy the changes from the cloud app. When you’re ready to deploy to production, you do the same thing, deploy the changes from the cloud app.
Every time you refresh your dev/staging database and apply your saved changes from Mergebot, you’re also testing a deployment. You’re deploying your changes to the production database, it just happens to be a copy of it in your dev/staging environment. The more times you refresh your dev/staging database and apply changes from Mergebot, the more you test your final deployment. By the time you apply the changes to production, it should feel boring. You’ll have a newfound confidence in your deployments.
Been banging your head against the wall trying to figure out how you’re going to deploy the database changes to a WooCommerce site you’ve been working on for the past six months without losing orders, customer reviews, etc? Yikes! Unfortunately, if you’re currently in this pickle, Mergebot can’t help you. But next time, when you start working on the site, you can set up Mergebot and have it save the changes you make to your dev site and deploy those changes without affecting orders, customer reviews, etc. #winning
The database of a membership site is constantly changing. New members are being added, current members are logging in, and activity is being tracked. To work on the site, you can’t just copy the database to dev/staging, make changes, and copy it back to production. Data would be lost. You need a solution that will merge your dev/staging changes into production. Whether you’re using Membermouse, Restrict Content Pro, S2Member, or another WordPress membership plugin, Mergebot is that solution.
With blogs, news sites, or any kind of publishing, new articles are regularly added to the live site and new comments are rolling in from visitors. If you have plugins installed, they’re likely collecting data as well. Meanwhile, you are doing some development on the site, adding new pages and posts, changing settings, configuring new plugins, updating widgets, etc. How do you deploy those development database changes without overwriting the data changes that have been happening on the live site? Mergebot.
Most plugins just work with Mergebot, while others need to be configured. We’ve preconfigured Mergebot for the most common WordPress plugins so you don’t have to. In the rare case that you’re using a plugin that needs configuration, you can add a schema.
Although you don’t need to use WP Migrate DB Pro, we have integrated it with Mergebot and the two work very well together. For example, Mergebot ignores any WP Migrate DB Pro queries, like saving settings and any temporary migration data. And when you pull your production database down and replace your dev/staging database, WP Migrate DB Pro will preserve your Mergebot settings. All Mergebot subscriptions include a WP Migrate DB Pro license (valid as long as your Mergebot subscription is active).
If you’ve written a custom plugin or theme that creates its own database tables, shortcodes, etc., you can tell Mergebot about it by defining a [schema](link to docs). Once Mergebot understands your custom data, it can handle any changes to it just like the rest.
Mergebot provides a very smooth and quick process for merging databases between development and production environments without losing any data.
Highly recommend @dliciousbrains Wordpress plugins, their customer support is excellent.
Have I mentioned how awesome the folks @dliciousbrains are? Well they are! <3
Why just 50? We’re excited that we’re coming out of beta and we want to make sure we’re supporting our new users with enough bandwidth on support.
As of the moment you’re reading this, there are 50 out of 50 seats left. When we’re out, we’re out. Will we open more in the future? Most likely, but we don’t know exactly when.
So if merging databases in WordPress is painful for you and you’d like to ease some of that pain, grab one of the seats available while you still can.
No Risk 30-Day Money-Back Guarantee
If for any reason you are not happy with our product or service, simply let us know within 30 days of your purchase and we'll refund 100% of your money. No questions asked.
The Mergebot WordPress plugin requires PHP 5.3+ and WordPress v4.0+.
All of the schemas for our preconfigured plugins can be found in our public GitHub repo. We are actively working to add more plugins. If you need Mergebot to work with a widely used plugin, let us know and we’ll help.
Not at the moment, but we do plan to support this in the near future.
Nope. To work on a new site, you have to disconnect the site that’s already connected and all data for that site will be deleted.
Communication between the plugin and app is securely encrypted over HTTPS. Site data stored by the app is not encrypted for performance reasons.
To remove your data from the Mergebot app simply login and disconnect any sites from the "Sites" dashboard. The process of disconnecting a site will remove any data stored in the app associated with that site.
Nope. It’s currently limited to one dev or staging environment and one production environment. We are working to support multiple environments.