Migro Content Migrator

Description

Migro Content Migrator makes content deployment simple. Migrate individual posts, pages, and content from staging to production or vice versa. Every migration includes all metadata: categories, tags, and featured images.

Features:
* Migrate posts and pages between environments
* Categories and tags included automatically
* Featured images migrated with deduplication
* Batch migration for multiple items at once
* Pre-migration backups with one-click restore
* Direct database connection for reliable transfers
* Clean, modern interface
* Setup wizard for easy configuration

How It Works:
1. Install Migro on both your staging and production sites
2. Configure the connection between environments
3. Select content to migrate and click deploy
4. Content arrives with all metadata intact

Screenshots

  • Migration interface — select and deploy content
  • Content selection with filters

Installation

  1. Upload the plugin files to /wp-content/plugins/migro-content-migrator
  2. Activate the plugin through the ‘Plugins’ screen
  3. Follow the setup wizard to configure your connection
  4. Start migrating content!

FAQ

Do I need to install Migro on both sites?

Yes. Migro needs to be active on both the staging and production site.

Does Migro work with multisite?

Migro is designed for single-site installations. Multisite support is not currently available.

What happens to images that already exist on the destination?

Migro uses MD5 hashing to detect duplicate images. If an identical image is already in the destination’s Media Library, Migro links to the existing attachment instead of uploading a copy.

Can I migrate from production to staging?

Yes. Pull and Push work in both directions. You can pull content from production into staging just as easily as pushing from staging to production.

Will migrating a post update its URL on the destination?

Migro preserves the original slug. The URL on the destination will match the URL on the source site, unless the permalink structure differs between environments.

What’s the difference between Overwrite and Duplicate?

Overwrite updates the existing item in place — same post ID, same URL, updated content. Duplicate creates a brand new post with a new ID.

Does Migro migrate users?

No. User accounts are not migrated. If a post author doesn’t exist on the destination, the post is assigned to the admin who ran the migration.

Is my database password stored securely?

Database passwords are encrypted before being saved to the WordPress options table. They are never stored or transmitted in plain text.

What’s the minimum WordPress version required?

WordPress 5.6. This is the version that introduced Application Passwords, which Migro uses for REST API authentication.

Can I use Migro with a staging environment on a different server?

Yes, as long as you have the remote site’s database credentials and can create an Application Password on that site.

What if the migration fails halfway through?

Each item is migrated independently. If one item fails, the others continue. The Logs page shows exactly which items succeeded, which were skipped, and which failed with an error message.

Does Migro handle WooCommerce product variations?

Yes. Variable products and all their variations are fully migrated including pricing, stock, attributes, and images. This requires the Pro version.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Migro Content Migrator” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

2.2.5

  • General security improvements to strengthen the plugin
  • Usability improvements and stability fixes

2.2.4

  • General security improvements to strengthen the plugin
  • Usability improvements and stability fixes

2.2.3

  • Initial release
  • Posts and pages migration
  • Categories and tags support
  • Featured images with deduplication
  • Batch migration
  • Pre-migration backups
  • Setup wizard
  • Modern interface