Title: Migro – Content Migration & Deployment Author: migro Published: 20.04.2026 Last modified: 10.07.2026 --- Шукати плагіни ![](https://ps.w.org/migro-content-migrator/assets/banner-772x250.png?rev=3603434) ![](https://ps.w.org/migro-content-migrator/assets/icon-256x256.png?rev=3511002) # Migro – Content Migration & Deployment Від автора [migro](https://profiles.wordpress.org/migro/) [Завантажити](https://downloads.wordpress.org/plugin/migro-content-migrator.2.4.1.zip) * [Деталі](https://uk.wordpress.org/plugins/migro-content-migrator/#description) * [Відгуки](https://uk.wordpress.org/plugins/migro-content-migrator/#reviews) * [Встановлення](https://uk.wordpress.org/plugins/migro-content-migrator/#installation) * [Розробка](https://uk.wordpress.org/plugins/migro-content-migrator/#developers) [Підтримка](https://wordpress.org/support/plugin/migro-content-migrator/) ## Опис 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 ## Скріншоти [⌊Selective content deployment: pick exactly what should move⌉⌊Selective content deployment: pick exactly what should move⌉[ Selective content deployment: pick exactly what should move [⌊Connection setup with the staging/production wizard⌉⌊Connection setup with the staging/production wizard⌉[ Connection setup with the staging/production wizard [⌊Per-item deployment results with the full operation summary⌉⌊Per-item deployment results with the full operation summary⌉[ Per-item deployment results with the full operation summary [⌊Backups page with one-click restore⌉⌊Backups page with one-click restore⌉[ Backups page with one-click restore ## Встановлення 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 deploying content! ## Часті питання ### How is Migro different from Duplicator or All-in-One WP Migration? Those are _site migration_ tools, built for moving an entire WordPress install from one host to another in a one-shot, all-or-nothing transfer. Migro is a _content deployment_ tool, built for the ongoing workflow of pushing individual posts from staging to production while leaving the rest of the live site alone. Different problem, different product. ### Do I need to install Migro on both sites? Yes. Migro needs to be active on both the source and destination site. ### Can content go both ways? Yes. Push and Pull are both first-class operations. You can pull live content back to staging just as easily as pushing staging drafts to production. ### What happens to images that already exist on the destination? Migro hashes incoming media with MD5. If an identical file already exists in the destination’s Media Library, Migro links to the existing attachment instead of uploading a duplicate. ### Will deploying a post change its URL on the destination? Migro preserves the original slug. The destination URL will match the source unless the permalink structure differs between environments. ### What’s the difference between Overwrite and Skip? Overwrite updates the existing item in place: same post ID, same URL, updated content. Skip leaves any existing destination post untouched. You pick the mode at deployment time. ### What if I deploy something by mistake? Every deployment that overwrites existing content creates a local backup first. The Backups page lets you restore the previous version with one click. Backups are retained for 30 days by default. ### Does the AI alt-text feature cost anything? Migro’s AI integration uses the WordPress 7.0 AI Connector. You bring your own API key (Anthropic, OpenAI, or Google Gemini) and pay your provider directly. Migro never charges you for AI usage, never proxies the requests, and never sees your key. Generated alt text is cached locally so re-deploying the same content doesn’t re-call the provider. Existing alt text is never overwritten. ### Can Editors deploy content, or only Admins? Editors can run deployments. This is intentional. For agencies, it lets your client push their own finished drafts without you needing to give them admin access. ### Are there any usage limits? No. Migro is unlimited. There’s no monthly cap and no nag screen. The Pro version adds features (Custom Post Types, ACF, Yoast, WooCommerce, scheduling, WP-CLI), not volume. ### Does Migro work with multisite? Migro is designed for single-site installations. Multisite is not currently supported. ### 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 deployment. ### 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. ### 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. Migro also supports custom sockets (for Local by WP Engine and similar), custom timeouts, and SSL verification toggles for tricky local environments. ### What if a deployment fails halfway through? Each item is deployed independently. If one fails, the others continue. The Logs page shows exactly which items succeeded, which were skipped, and which failed with the error message and a retry option. ### Does Migro handle WooCommerce product variations? Yes, but WooCommerce migration requires the Pro version. Variable products and all their variations are fully migrated including pricing, stock, attributes, and images. ### Does Migro work with page builders? The free version detects page builder content (Elementor, Divi, Beaver Builder, Bricks, Oxygen, Breakdance, Droip, WPBakery) and leaves those pages out of the deployment, because page builders store their layouts as serialized data with hardcoded URLs that don’t survive a host change without specialized handling. Safe page builder migration, including serialized data rewriting and CSS regeneration, is part of Migro Pro. ### Is Migro translated into other languages? Yes. English, Brazilian Portuguese (pt_BR), and Spanish (es_ES) are bundled. The non-English translations started as machine translations and improve with community contributions. ### Does Migro collect any usage data? Only if you explicitly opt in. 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 such as the plugin version, WordPress/ PHP version, and aggregate deployment counts. It never sends post content, URLs, credentials, or any personally identifiable information. ### 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. ## Відгуки Для цього плагіна немає відгуків. ## Учасники та розробники “Migro – Content Migration & Deployment” — проект з відкритим вихідним кодом. В розвиток плагіну внесли свій вклад наступні учасники: Учасники * [ migro ](https://profiles.wordpress.org/migro/) [Перекладіть “Migro – Content Migration & Deployment” на вашу мову.](https://translate.wordpress.org/projects/wp-plugins/migro-content-migrator) ### Цікавитесь розробкою? [Перегляньте код](https://plugins.trac.wordpress.org/browser/migro-content-migrator/), перегляньте [сховище SVN](https://plugins.svn.wordpress.org/migro-content-migrator/) або підпишіться на [журнал розробки](https://plugins.trac.wordpress.org/log/migro-content-migrator/) за допомогою [RSS](https://plugins.trac.wordpress.org/log/migro-content-migrator/?limit=100&mode=stop_on_copy&format=rss). ## Журнал змін #### 2.4.1 – 2026-07-10 * Deployment results now show the exact reason when a media file fails to upload to the remote site. * More reliable AI alt-text generation: longer provider timeouts for large images, automatic retry when the provider is temporarily rate-limited or overloaded, and provider errors are now reported instead of silently dropped. * Security hardening for remote requests, background polling, and database queries. * Refreshed user-facing copy and updated translations. * General stability improvements. #### 2.4.0 – 2026-05-29 * New AI Enhancements tab with optional AI alt-text generation for images missing alt, powered by your WordPress 7.0 AI Connector (Anthropic, OpenAI, Google Gemini). Existing alt text is never overwritten, and responses are cached locally so re- migrating the same content does not re-call the provider. * When multiple AI providers are configured, each AI-powered feature can be routed to a specific provider. * New Alt Text Sync keeps inline alt in post content aligned with the Media Library during migration, with skip and overwrite options for existing values. * PDFs, videos, and other attached media referenced by your posts now migrate automatically alongside featured images. * Improved deduplication for large images prevents duplicate uploads of scaled variants. * More accurate progress reporting during long AI-assisted migrations, so the bar no longer appears stuck. * Batch result cards now reveal the full per-item operation summary behind a View details toggle. * Settings page self-heals previously saved empty values, and Passive Mode no longer locks on for production sites running on local domains. * Refreshed Quick Guide covering AI Enhancements, scheduled migrations, and WP- CLI. * General stability improvements, translation updates, and security hardening. #### 2.3.4 * Fully tested on WordPress 7.0 #### 2.3.3 * Improved post parent remapping to preserve hierarchical relationships accurately. * Normalized database draft date handling for modern MySQL strict mode environments. * Corrected documentation and setup flow to clarify that the Free tier has unlimited migrations. * Improved migration logs and failure status reporting. * Minor translation updates and stability fixes. #### 2.3.2 * Internal reliability and maintenance improvements. * Small translation updates and improvements. #### 2.3.1 * Strengthened encryption of stored connection credentials and other at-rest secrets. * Migrations now abort safely if a requested pre-migration backup cannot be created, so content is never deployed without its backup. * Fixed the setup wizard not showing correct messages. * Fixed an issue where users with the Editor role were blocked from accessing the migration screen. * General security hardening and stability improvements. #### 2.3.0 * Full internationalization: every user-facing string in the plugin is now translatable. * Added Brazilian Portuguese (pt_BR) and Spanish (es_ES) translations. These are initial machine translations. Community review and contributions are very welcome. * Improved translation consistency across the plugin. * General stability improvements and minor bug fixes. #### 2.2.9 * Improved admin menu navigation with a dedicated Backups page. * Added pre-migration compatibility checks for posts containing page builder content. * Improved page builder data handling for more reliable migrations. * Hardened security with additional rate limiting and prepared database queries. * General stability improvements and minor bug fixes. #### 2.2.8 * Added optional, opt-in telemetry to help improve the plugin. It is off by default. No data is ever sent unless you explicitly consent to the prompt, and declining keeps it permanently disabled. See the FAQ for what is collected. * Improved Media Path Preservation to ensure folder structures are maintained during transfers. * Hardened Beaver Builder support for more reliable complex layout migrations. * Implemented a promotional UI for the Migro Beta program for Free users. * General stability improvements and minor bug fixes. #### 2.2.6 * Enhanced remote connection authentication with advanced Sodium encryption capabilities. * Improved media deduplication logic to prevent redundant file uploads during complex migrations. * Resolved minor issues to ensure complete media metadata preservation during transfers. #### 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 ## Мета * Версія **2.4.1** * Останнє оновлення **5 днів тому** * Активних встановлень **Менше 10** * Версія WordPress ** 5.6 або вище ** * Tested up to **7.0.1** * Версія PHP ** 7.4 або вище ** * Мова * [English (US)](https://wordpress.org/plugins/migro-content-migrator/) * Позначки * [backup](https://uk.wordpress.org/plugins/tags/backup/)[deployment](https://uk.wordpress.org/plugins/tags/deployment/) [migration](https://uk.wordpress.org/plugins/tags/migration/)[push pull](https://uk.wordpress.org/plugins/tags/push-pull/) [staging](https://uk.wordpress.org/plugins/tags/staging/) * [Розширений перегляд](https://uk.wordpress.org/plugins/migro-content-migrator/advanced/) ## Оцінки No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/migro-content-migrator/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/migro-content-migrator/reviews/) ## Учасники * [ migro ](https://profiles.wordpress.org/migro/) ## Підтримка Є що сказати? Потрібна допомога? [Перейти в форум підтримки](https://wordpress.org/support/plugin/migro-content-migrator/) ## Пожертвування Ви хотіли б підтримати розвиток цього плагіна? [ Пожертвувати на розвиток плагіна ](https://buymeacoffee.com/migro)