Everything you need to write about Migro

For immediate release

Migro takes WordPress content deploys off the developer's desk

A free plugin that pushes individual posts and pages from staging to production, and lets editors run the deploy themselves instead of queuing behind whoever has database access.

22 July 2026

A client approves three edited pages on staging. Getting them live has meant picking the least bad of three options: recreate the pages by hand and re-upload the media, hoping nothing was missed; clone the staging database over production and wipe out two weeks of comments, orders, and new posts; or write a custom WP-CLI script that handpicks database tables, which works fine until you remember only a developer can run it.

That last detail is where the real damage happens, and it rarely gets counted. Because none of those options can be handed to the person who actually wrote the content, editors stop asking. They make the small updates directly on production instead, and the staging site drifts out of date until nobody trusts it. The deploy process did not just cost developer time; it quietly trained everyone to bypass staging altogether.

Migro is a WordPress plugin built for that one job. An administrator sets up the link between the two sites once, in a wizard that asks for the destination's database credentials and a WordPress Application Password. Content and its metadata then move over a direct database connection, and media files upload through the REST API. The credentials are encrypted in the options table and entered exactly once.

After that, anyone with the right role can select individual posts, pages, or batches and push them. Taxonomies, featured images, embedded media, custom fields, author attribution, and alt text move with the content. Everything not selected stays exactly as it was on the destination. Pulling works the same way in reverse.

Deploys that do not need a developer

Setting up the connection needs an administrator, and it needs real credentials. Running a deploy afterwards does not. Migro gates migrations on the capability WordPress grants to the Editor role, rather than on Administrators. Editors and content teams move their own approved work to production without ever seeing a database password, without shell access, and without filing a ticket.

Settings, connections, and backups stay administrator-only. The split is the whole point: credentials are configured once by the person responsible for the infrastructure, and after that the person who wrote the page can ship the page.

Migro does ship a WP-CLI command, in Pro, for teams that want deploys running from CI. The point is not that command lines are bad. It is that when the command line is the only door, routine content updates inherit a developer's calendar.

Under the hood

• Sync keys. Re-deployments update in place instead of creating duplicates when IDs or slugs drift between environments.
• Pre-overwrite backups. A local backup runs before anything is overwritten. On restore, each post is rewritten inside a database transaction, so a failure partway through cannot leave a half-written post behind.
• Media deduplication. Files are hashed with MD5, so an image already present on the destination links to the existing attachment instead of uploading a second copy.
• Resumable transfers. Deploys run in chunks and media is streamed from disk rather than loaded into memory, which is what keeps large batches from dying on shared hosting time limits.
• Structure preserved. Parent and child page relationships, attached PDFs and videos, and core page designations such as the front page and privacy policy carry over automatically.
• Alt text via the AI Connector. Missing alt text can be generated through the WordPress AI Connector using your own provider key. It updates the media library, so the change follows the image everywhere it is used. Existing alt text is never overwritten.

The plugin has been on WordPress.org since April 2026 and is free with no usage caps: no deployment limit, no nag screen, no ceiling that turns into a paywall. What is gated to Pro is a specific commercial feature set, never volume: custom post types, ACF, Yoast SEO, WooCommerce, scheduling, WP-CLI, safe page-builder migration, and AI SEO metadata.

Every tool in this category was built for developers, so the deploy button ended up behind database access. The result is that clients edit production directly, because that is the only door left open to them. I wanted the person who wrote the page to be able to ship the page, without handing them the keys to the server.

Al Auad, developer of Migro

Availability and pricing

Migro is available now from the WordPress.org plugin directory. Pro is in public preview with founding-customer pricing: 69 USD per year for one site, 249 USD for five, 499 USD for fifteen, and custom terms above that. Founding prices stay locked at renewal. All paid plans carry a 30-day money-back guarantee.

About Migro

Migro is an independent WordPress plugin built and maintained by a solo developer. It does one thing: it moves selected content between WordPress environments without touching the rest of the site. More at migro.dev.