migro

<p><strong>Stop using site-migration tools for editorial work.</strong></p>
<p>Plugins like Duplicator and All-in-One WP Migration were built for moving hosts. Clone the whole database, overwrite everything, hope nothing breaks. That’s the wrong tool for the weekly grind of pushing finished posts to production.</p>
<p>Migro is built for that weekly grind.</p>
<p>Pick a post. Click Push. Migro deploys <em>only</em> that post (with its categories, tags, featured image, embedded media, and alt text) and leaves the rest of the destination site untouched. Pull works the same way in reverse: grab live content back to staging for testing.</p>
<h4>Built for agencies and freelancers</h4>
<p>You’re managing client sites with a staging-to-production workflow. The writer drafts on staging, you review, you deploy. Maybe the client wants to push their own finished drafts. Migro handles all of it:</p>
<ul>
<li><strong>Selective deployment.</strong> Pick exactly the posts that should move. Nothing else on the destination changes.</li>
<li><strong>Bidirectional Push and Pull.</strong> Push staging to production, or pull production back to staging. Same flow either way.</li>
<li><strong>Sync-key tracking.</strong> Re-deploying the same post updates it in place, even if its slug or ID differs on the destination.</li>
<li><strong>Backups before every overwrite.</strong> One-click restore if a deployment was wrong.</li>
<li><strong>Editor role can deploy.</strong> Let your client push their own finished drafts without giving them admin access.</li>
<li><strong>Unlimited.</strong> No monthly cap, no upsell prompts blocking your work.</li>
</ul>
<h4>Headline features</h4>
<ul>
<li><strong>Selective Push and Pull</strong> between any two WordPress environments.</li>
<li><strong>AI-powered alt text</strong> for images missing it. Bring your own Anthropic, OpenAI, or Google Gemini key via the WordPress AI Connector. Existing alt text is never overwritten.</li>
<li><strong>One-click backup and restore</strong> before every overwrite.</li>
</ul>
<h4>What comes with a deployment</h4>
<p>When you push a post, Migro brings everything attached to it:</p>
<ul>
<li>Post content, excerpt, slug, status, dates, notes and ping settings</li>
<li>All post meta (custom fields)</li>
<li>Categories and tags, with hierarchies preserved</li>
<li>Featured images, with smart MD5 deduplication so identical files aren’t re-uploaded</li>
<li>Embedded inline images, PDFs, videos, and other attached media</li>
<li>Image alt text, in both the Media Library and inside post content (kept in sync)</li>
<li>Author attribution (falls back to the deploying admin if the source author doesn’t exist on the destination)</li>
</ul>
<h4>Using a page builder?</h4>
<p>Page builders like Elementor, Divi, Beaver Builder, Bricks, Oxygen, Breakdance, Droip, and WPBakery store layouts as serialized data with hardcoded URLs, which doesn’t survive a staging-to-production move without specialized handling. The free version detects page builder content in your posts and warns you before deployment, so you don’t accidentally break a destination layout. Safe page builder migration (serialized data rewriting and CSS regeneration) is part of Migro Pro.</p>
<h4>Built for real production workflows</h4>
<ul>
<li><strong>Two conflict modes.</strong> Overwrite (update in place, same post ID and URL) or Skip (don’t touch existing content).</li>
<li><strong>Pre-deployment backups</strong> stored locally, retained for 30 days, restorable in one click.</li>
<li><strong>Migration logs</strong> with full status, error messages, and configurable retention.</li>
<li><strong>Direct database connection</strong> for reliable transfers, plus WordPress REST API authentication via Application Passwords.</li>
<li><strong>Encrypted credentials at rest.</strong> Database passwords are encrypted before they’re saved to the options table.</li>
<li><strong>Works with local development environments</strong> including Local by WP Engine, with custom sockets, configurable timeouts, and SSL verification toggles.</li>
<li><strong>Available in English, Brazilian Portuguese (pt_BR), and Spanish (es_ES).</strong></li>
</ul>
<h4>How it compares to site-migration tools</h4>
<p>Full-site migrators are built for moving hosts: one-shot, all-or-nothing, clone everything. Migro is built for ongoing editorial deployment: pick the post, click Push, leave the rest alone.</p>
<p>Specifically, Migro gives you:</p>
<ul>
<li>Single-post granularity instead of whole-site cloning</li>
<li>Bidirectional Push and Pull instead of one-way export/import</li>
<li>Sync-key tracking so re-deploying the same post updates in place instead of duplicating</li>
<li>Automatic backup before every overwrite, with one-click restore</li>
<li>No monthly cap on deployments</li>
</ul>
<h4>How it works</h4>
<ol>
<li>Install Migro on both your staging and production sites</li>
<li>Run the setup wizard to connect the two</li>
<li>Pick the posts to deploy and click Push (or Pull)</li>
<li>Review the per-item operation summary, and restore from backup if anything looks wrong</li>
</ol>
<h4>Need more?</h4>
<p>Migro Pro adds Custom Post Types, ACF, Yoast SEO, WooCommerce, scheduled migrations, WP-CLI, full page builder migration, the Quick Migrate sidebar in Gutenberg, and AI-generated SEO metadata. The free version is fully functional on its own. No usage caps, no feature locks, no nag screens.</p>


Migro Content Migrator

You changed one post. Why clone the whole site? Migro deploys individual posts and pages between staging and production.

Nahid Ferdous Mohit

<p>Instead of going into <a href="https://netlify.com" rel="nofollow ugc">Netlify</a> and triggering a deploy everytime you make a change in WordPress, automate and make things easier with the <strong>Deploy with NetlifyPress</strong> plugin. <strong>Deploy with NetlifyPress</strong> lets you trigger deploys in <a href="https://netlify.com" rel="nofollow ugc">Netlify</a> (automatically!) without having to leave your WordPress Dashboard.</p>
<h3>Use Cases</h3>
<p>So, you’ve build a headless static front-end for your WordPress site and hosted it on <a href="https://netlify.com" rel="nofollow ugc">Netlify</a>, good job! Wondering how would you trigger a deploy in <a href="https://netlify.com" rel="nofollow ugc">Netlify</a> everytime someone updates a post in WordPress? Forget going inside everytime an update is made and triggering a build manually, install <strong>Deploy with NetlifyPress</strong> and let it run a deploy for you automatically on each update.</p>
<p>If you’re looking for a real-life example, I’ve build my personal site <a href="https://nahid.dev" rel="nofollow ugc">nahid.dev</a> (<a href="https://github.com/nfmohit/nahid.dev" rel="nofollow ugc">GitHub</a>) using <a href="https://www.gatsbyjs.org/" rel="nofollow ugc">GatsbyJS</a> with its source as WordPress and am hosting it on <a href="https://netlify.com" rel="nofollow ugc">Netlify</a>. I use <strong>Deploy with NetlifyPress</strong> to automate deploys when I update pages and posts.</p>
<h3>Core Features</h3>
<p>The core features of the plugin include the abilities to:<br />
* Automatically trigger deploys on post publish<br />
* Automatically trigger deploys on post update<br />
* Automatically trigger deploys on post trash<br />
* Filter the post types for which you want automatic deploys to run<br />
* Add a button for manual deployments on the top admin toolbar.</p>
<h3>Requirements</h3>
<p>This plugin requires you have a site hosted on Netlify and a Build Webhook URL set up. Here’s how you can get a Build Hook URL:<br />
1. Log into <a href="https://app.netlify.com/" rel="nofollow ugc">Netlify</a>.<br />
2. From the list of sites, enter the site you want to set up <strong>Deploy with NetlifyPress</strong> for.<br />
3. Go to <em>Site settings</em>.<br />
4. From the left sidebar, go to <em>Build and deploy<span aria-hidden="true" class="wp-exclude-emoji">→</span>Continuous Deployment</em>.<br />
5. Scroll down to the “<em>Build hooks</em>” section.<br />
6. Click the “<em>Add build hook</em>” button, enter a preferred name for the webhook (e.g. “Deploy from WordPress”), choose the <a href="https://git-scm.com/" rel="nofollow ugc">Git</a> branch to build and hit <em>Save</em>.<br />
7. You’ll be given a Build Hook URL that can be used in <strong>Deploy with NetlifyPress</strong>.</p>
<h3>Installation</h3>
<p>Installation of the <strong>Deploy with NetlifyPress</strong> plugin is very simple. Follow along with the installation procedure in the dedicated <a href="#installation" rel="nofollow ugc"><strong>Installation</strong> tab</a>.</p>
<h3>Usage</h3>
<ol>
<li><a href="#installation" rel="nofollow ugc">Install</a> and activate the plugin</li>
<li>Go to your <em>WordPress Dashboard<span aria-hidden="true" class="wp-exclude-emoji">→</span>NetlifyPress</em></li>
<li>On the “<em>Connect with Netlify</em>” tab, enter your Netlify Build Hook URL.</li>
<li>On the “<em>Automatic Deployment</em>” tab, choose if you want to use Automatic Deployment, on which actions should it trigger and which post types the actions should apply to.</li>
<li>On the “<em>Manual Deployment</em>” tab, choose if you want to add a “Trigger Netlify Deploy” manual trigger button in the top admin toolbar.</li>
</ol>
<h3>Support</h3>
<p>If the above usage steps don’t answer your question(s), if you want to report an issue or if something is not working as expected, please create a topic in the <a href="https://wordpress.org/support/plugin/deploy-netlifypress/" rel="ugc">Support Forum</a>.</p>
<h3>Roadmap</h3>
<p>I have plans for the following features/improvements in the coming days (subject to user feedback and usage):<br />
1. Admin options migration to Settings API with Ajax support.<br />
2. Success/failure message on auto deploy trigger.<br />
3. Success/failure message on auto deploy status (after completion).<br />
4. Scheduled deployments.<br />
5. Deployment logs.</p>
<h3>Contribute</h3>
<p>If you want to contribute to the plugin by reporting issues, implementing new features and so on, <a href="https://github.com/nfmohit/deploy-netlifypress" rel="nofollow ugc">here’s its development repository on Github</a>.</p>
<h3>Sponsor</h3>
<p>You can sponsor this project and support my open-source development by <a href="https://www.patreon.com/nfmohit" rel="nofollow ugc">becoming a Patron</a>!</p>


Deploy with NetlifyPress

Seamlessly trigger deploys in Netlify from WordPress.

Migro Content Migrator vs Deploy with NetlifyPress