Migro – Content Migration & Deployment

You changed one post. Why clone the whole site?

Traditional WordPress migration plugins were built for moving hosts: export the database, overwrite production, hope nothing breaks.

Migro was built for editorial deployment.

Push individual posts and pages between staging and production without touching the rest of the live site. Deploy exactly what changed (including media, taxonomies, metadata, and author attribution) and leave everything else untouched.

Built for agencies, publishers, freelancers, and editorial teams running real staging workflows.

What Migro does

Migro is a selective WordPress migration plugin that deploys content between environments. Choose a post or page, click Push, and Migro transfers only that content and its dependencies:

• Post content, excerpts, slugs, statuses, dates, comment status, and ping status
• Categories and tags with hierarchy preservation
• Featured images and embedded media
• Image alt text, kept in sync between the Media Library and post content
• Custom fields and post meta
• Author attribution (falls back to the deploying admin if the source author does not exist on the destination)
• Attached PDFs, videos, and inline assets

Pull works the same way in reverse, syncing live content back into staging for testing and revision.

Why Migro exists

Site-migration tools solve infrastructure problems. Migro solves editorial workflow problems.

Most WordPress teams do not want to:

• clone production databases
• overwrite unrelated content
• freeze publishing workflows
• manually recreate approved edits
• risk breaking live sites for a single article update

They just want to safely deploy finished content. Migro is built specifically for that workflow.

Built for staging-to-production workflows

Whether you are an agency managing client sites or a publisher coordinating editors and reviewers, Migro fits directly into modern WordPress workflows.

• Selective deployment. Deploy individual posts and pages instead of cloning entire sites.
• Push and Pull synchronization. Push staging changes to production or pull live content back into staging.
• Sync-key tracking. Re-deployments update existing content in place, even if slugs or IDs changed between environments.
• Safe overwrite protection. Every overwrite creates a local backup before deployment, with one-click restore.
• Editor-friendly permissions. Editors can deploy approved content without requiring Administrator access.
• Unlimited deployments. No monthly caps, throttles, or upgrade prompts.

Headline features

• Selective Push and Pull between WordPress environments
• Sync-key redeployment without duplicate posts
• Automatic backups before overwrite operations
• Migration logs with per-item status tracking
• Encrypted credential storage at rest
• Media deduplication using MD5 hashing
• Local development support including Local by WP Engine
• REST API authentication using Application Passwords
• Direct database transport for reliability
• Multilingual support (English, Brazilian Portuguese, Spanish)

Smart page builder detection

Modern page builders store layouts as serialized data containing environment-specific URLs and generated assets. Unsafe migrations can corrupt layouts or break rendering.

Migro detects content created with Elementor, Divi, Beaver Builder, Bricks, Oxygen, Breakdance, Droip, and WPBakery. The free version warns before deployment when builder content is detected, so a deployment cannot silently break a destination layout.

Migro Pro adds serialized data rewriting, safe builder migration, CSS regeneration, and environment-aware asset handling.

AI-powered alt text

Migro can generate alt text for images missing accessibility metadata using the WordPress 7.0 AI Connector and your own provider account.

Supported providers: Anthropic, OpenAI, and Google Gemini.

Existing alt text is never overwritten. Requests are sent directly from your WordPress site to the provider using your own API key. Migro never proxies the call and never sees your key.

Built for production use

• Conflict handling. Choose between Overwrite (update existing content in place) and Skip (leave existing destination content untouched).
• Reliable backups. Stored locally before overwrite operations and retained for 30 days by default.
• Deployment logging. Review successful, skipped, and failed deployments with detailed error reporting and retry support.
• Secure credential handling. Database credentials are encrypted before being stored in the WordPress options table.
• Local development support. Custom sockets, SSL verification toggles, and configurable timeouts for local and hybrid environments.

How Migro compares to site-migration plugins

Traditional migration plugins move entire WordPress installations. Migro deploys content changes.

• Scope. Traditional tools clone the full database. Migro deploys only the selected content.
• Workflow. Traditional tools run a one-shot host migration. Migro supports continuous editorial deployment.
• Side effects. Traditional tools overwrite entire environments. Migro leaves unrelated content untouched.
• Direction. Traditional tools are one-way import/export. Migro is bidirectional Push and Pull synchronization.
• Re-runs. Traditional re-imports create duplicates. Migro uses sync-keys to update content in place.
• Focus. Traditional tools are infrastructure-focused. Migro is editorial-workflow-focused.

How it works

1. Install Migro on both WordPress environments
2. Connect staging and production using the setup wizard
3. Select the posts or pages to deploy
4. Click Push or Pull
5. Review the deployment summary
6. Restore from backup instantly if needed

No command line required. WP-CLI is available in Migro Pro for automation and CI/CD pipelines.

Migro Pro

Migro Pro adds advanced workflow and commerce support:

• Custom Post Types
• Advanced Custom Fields (ACF)
• Yoast SEO migration
• WooCommerce products and variations
• Scheduled migrations
• WP-CLI support
• Full page builder migration
• Gutenberg Quick Migrate sidebar
• AI-generated SEO metadata

The free version remains fully functional with no deployment limits and no nag screens.

External Services

Migro can connect to two categories of external services. Both are off by default and are never contacted unless you take an explicit action.

1. AI provider for alt-text generation (optional, opt-in, your own account).

If you enable the AI Enhancements feature on the AI tab and configure a provider via the WordPress 7.0 AI Connector, Migro sends a single image (as a base64-encoded request payload) plus a short prompt to your configured AI provider in order to generate alt text for that specific image. Supported providers in the free version are Anthropic, OpenAI, and Google Gemini. The request is sent directly from your WordPress site to the provider using your API key; Migro never proxies the call and never sees your key. No request is ever made unless you explicitly trigger an alt-text generation, and existing alt text is never overwritten. Each provider’s terms apply to your account independently:

• Anthropic: terms https://www.anthropic.com/legal/consumer-terms — privacy https://www.anthropic.com/legal/privacy
• OpenAI: terms https://openai.com/policies/terms-of-use — privacy https://openai.com/policies/privacy-policy
• Google Gemini: terms https://policies.google.com/terms — privacy https://policies.google.com/privacy

2. Anonymous usage telemetry to Migro (optional, opt-in, off by default).

After installation Migro shows a one-time prompt asking whether you want to share anonymous usage data. Nothing is sent unless you choose Yes. If you decline or ignore the prompt, no data ever leaves your site, and you can change your choice at any time on the Settings page. When enabled, Migro sends anonymous, non-personal information (plugin version, WordPress version, PHP version, and aggregate deployment counts) to https://migro.dev to help prioritize roadmap work. It never sends post content, URLs, credentials, or personally identifiable information.

• Migro privacy policy: https://migro.dev/privacy
• Migro terms of service: https://migro.dev/terms