Title: WPMove Migration Connector
Author: xuxu.fr
Published: <strong>2 يوليو، 2026</strong>
Last modified: 3 أكتوبر، 2026

---

البحث عن الإضافات

![](https://ps.w.org/wpmove-migration-connector/assets/banner-772x250.png?rev=3594328)

![](https://ps.w.org/wpmove-migration-connector/assets/icon-256x256.png?rev=3594328)

# WPMove Migration Connector

 بواسطة [xuxu.fr](https://profiles.wordpress.org/xuxufr/)

[تنزيل](https://downloads.wordpress.org/plugin/wpmove-migration-connector.2.1.11.zip)

 * [تفاصيل](https://ar.wordpress.org/plugins/wpmove-migration-connector/#description)
 * [المراجعات](https://ar.wordpress.org/plugins/wpmove-migration-connector/#reviews)
 *  [التنصيب](https://ar.wordpress.org/plugins/wpmove-migration-connector/#installation)
 * [التطوير](https://ar.wordpress.org/plugins/wpmove-migration-connector/#developers)

 [الدعم](https://wordpress.org/support/plugin/wpmove-migration-connector/)

## الوصف

WPMove Migration Connector exports the posts, pages and custom post types of a WordPress
site to a portable `.json` file, and imports such a file into another site. It runs
entirely on your own server — no sign-up, no API key, and no external service is
contacted.

 * **Export** the posts, pages and custom post types of this site to a portable 
   file you download.
 * **Import** a previously exported file into another WordPress site. Imported items
   are **added as new posts** — nothing existing is overwritten or deleted.
 * **Receive a direct migration.** Another WordPress site you control can send content
   to this site, or read content from it, without any file changing hands.

Text, public custom fields and taxonomy terms (categories, tags and custom taxonomies)
travel with each post. An optional export setting preserves the full taxonomy structure—
all terms with their descriptions and parent-child hierarchy — so the target site
is ready before posts are imported. The plugin is fully functional on its own, with
no account required.

When it receives a direct migration, this plugin also accepts the custom fields 
that the REST API normally leaves behind — Elementor layouts, ACF fields, SEO metadata—
which are otherwise lost in transfer. The other site does the work; this one only
answers, and only to requests carrying a valid WordPress application password for
an account allowed to edit the content concerned.

#### Need to migrate directly between two live sites, with media?

Moving content as a file is perfect for a one-off transfer. If you instead need 
to copy content **directly between two running WordPress sites over their REST APIs**—
including media (featured images and inline files), pull/push modes, post-by-post
selection and resumable runs — there is a separate premium add-on, **WPMove Migration
Connector Premium**, available from [wpmove.app](https://wpmove.app/why-upgrade/).
It pairs with a wpmove.app account and is the practical option when one of the two
sites cannot be reached from the internet (localhost, a firewall, a private network).
The premium add-on is optional and is **not** required to use this free plugin.

#### Features

 * Free, offline export of posts, pages and custom post types to a portable file.
 * Free import that appends content — no overwrite, no ID conflicts.
 * Public custom fields and taxonomy terms included.
 * Optional: export the full taxonomy structure (all terms with descriptions and
   parent-child hierarchy) so it is recreated correctly on import.
 * No account, no API key, no external connection.

### External services

This plugin contacts no external services. It never sends your data anywhere on 
its own, and requires no account.

It does expose an authenticated endpoint under `/wp-json/wpmvc/v1/` so that another
WordPress site you control can migrate content to or from this one. Any such traffic
happens only between your own sites, at your initiative, and only with a valid application
password.

## لقطات الشاشة

[⌊Export to file: choose post types and status, then download a portable .json file.
No account needed.⌉⌊Export to file: choose post types and status, then download 
a portable .json file. No account needed.⌉[

Export to file: choose post types and status, then download a portable .json file.
No account needed.

[⌊Import from file: upload a previously exported file and add its posts. Nothing
is overwritten.⌉⌊Import from file: upload a previously exported file and add its
posts. Nothing is overwritten.⌉[

Import from file: upload a previously exported file and add its posts. Nothing is
overwritten.

## التنصيب

 1. Install and activate the plugin, then open **WPMove Migration Connector** in the
    admin menu.
 2. **To export:** choose _Export to a file_, pick the post types, status and options,
    and download the file.
 3. **To import:** choose _Import from a file_, select the file, and import. Items 
    are added as new posts.

## الأسئلة المتكررّة

### Do I need an account?

No. The export and import work fully offline with no account and no API key. This
plugin never contacts any external service.

### Does the import overwrite my existing content?

No. The import is append-only: every item becomes a new post. Nothing on the destination
site is overwritten or deleted.

### Does the export include media?

No. The file export contains posts, pages and custom post types (text, public custom
fields and taxonomy terms). Migrating media files directly between two live sites
is handled by the optional premium add-on.

### How do I migrate media or copy content directly between two live sites?

That is what the premium add-on, WPMove Migration Connector Premium, does. It is
distributed from wpmove.app and replaces this free plugin once installed.

### Is anything sent over the internet?

This plugin never starts a connection of its own: it contacts no external service,
and the file you export stays on your computer until you import it elsewhere yourself.

It does answer one kind of incoming request. Since version 2.1.0 it exposes a migration
endpoint so that another WordPress site you control can send content to this site
or read content from it. Requests without a valid application password are refused.

### Who can use the migration endpoint?

Only someone holding a WordPress application password for an account on this site
that is allowed to edit the content concerned. Application passwords are created
by you, from your own user profile, and can be revoked there at any time. Unauthenticated
requests get a 401, and an account without editing rights gets a 403 — nothing is
readable or writable by the public.

## المراجعات

لا توجد مراجعات لهذه الإضافة.

## المساهمون والمطوّرون

“WPMove Migration Connector” هو برنامج مفتوح المصدر. وقد ساهم هؤلاء الأشخاص بالأسفل
في هذه الإضافة.

المساهمون

 *   [ xuxu.fr ](https://profiles.wordpress.org/xuxufr/)

لقد تم ترجمة ”WPMove Migration Connector“ إلى لغة واحدة. شكراً إلى جميع [المُترجمين](https://translate.wordpress.org/projects/wp-plugins/wpmove-migration-connector/contributors)
لمُساهماتهم.

[ترجمة ”WPMove Migration Connector“ إلى لغتك.](https://translate.wordpress.org/projects/wp-plugins/wpmove-migration-connector)

### مُهتم بالتطوير؟

[تصفّح الشفرة](https://plugins.trac.wordpress.org/browser/wpmove-migration-connector/)،
تحقق من [مستودع SVN](https://plugins.svn.wordpress.org/wpmove-migration-connector/)،
أو الاشتراك في [سجل التطوير](https://plugins.trac.wordpress.org/log/wpmove-migration-connector/)
بواسطة [RSS](https://plugins.trac.wordpress.org/log/wpmove-migration-connector/?limit=100&mode=stop_on_copy&format=rss).

## سجل التغييرات

#### 2.1.11

 * Fix: the “Unlock direct site-to-site migration” popin (shown when clicking a 
   locked Premium card) rendered inline in the page instead of as a centered overlay—
   the wrapper styling had never been added to this plugin’s stylesheet, even though
   the popin’s own content was. Purely visual, no functional impact.

#### 2.1.10

 * New: pre-import report. Choosing an export file now shows, under it, what the
   file contains and what the import would do on THIS site: how many items already
   exist here under the same address (the import only adds, so they would be created
   again as duplicates), content types or taxonomies this site does not have, page-
   builder layouts (Elementor, Divi, Beaver Builder) whose builder is not active
   here, reusable blocks that will be created. Nothing is written, and the file 
   is not kept.
 * New: the receiver endpoint gains `GET|POST /wpmvc/v1/preflight` (announced as`
   preflight` by `/ping`, administrator only): an exact, read-only analysis of this
   site — counts by content type, media, comments, page builders, reusable blocks,
   content types and taxonomies not exposed to the REST API — used by wpmove.app
   and by the Premium plugin to build their pre-migration report.

#### 2.1.9

 * New: the “Taxonomy REST visibility” setting becomes “REST API visibility” and
   also covers custom post types registered without REST API support — the same 
   opt-in, per type, with the same caveat (an exposed type becomes readable through
   this site’s public REST API).
 * Fix: an item already opted in disappeared from the list at the next page load(
   it now had REST support), so it could never be unticked again. Opted-in items
   stay listed.

#### 2.1.8

 * New: “Taxonomy REST visibility” setting. A custom taxonomy that a plugin or theme
   registered without REST API support (`show_in_rest`) is invisible to WPMove —
   this new opt-in list lets you expose one specifically, on a per-taxonomy basis.
   Nothing is exposed automatically.

#### 2.1.7

 * New: the receiver endpoint gains `POST /wpmvc/v1/comments` (announced as `comments.
   write` by `/ping`). A migration driven by wpmove.app or by the Premium plugin
   now writes comments on this site through `wp_insert_comment()` instead of the
   core REST route — so a migrated comment is no longer treated as a new one: no
   moderation heuristics, no duplicate rejection, and no notification email to the
   post author for each comment. Administrator account required, and a parent comment
   must belong to the same post (the core does not check).

#### 2.1.6

 * Security: reading meta through the receiver endpoint now requires an administrator
   account too (it returns every meta of a post, protected keys included).
 * Fix: a post status the target does not know is imported as a draft instead of
   being stored as-is and hidden from every listing.

#### 2.1.5

 * Fix: the file export/import dropped every protected meta key (`_elementor_data`,`
   _wp_page_template`, …): a page built with a page builder came back without its
   layout. Those keys now travel like in direct migrations (ID references still 
   left out, since a file cannot remap them), with the source domain swapped inside
   them — JSON included.
 * Fix: the file carried the post date in the source site’s local time only; imported
   on a site in another timezone, a recently published post could turn into a scheduled
   one. The GMT date is now exported and used on import (older files still import
   with their local date).

#### 2.1.4

 * Security: writing meta through the plugin’s receiver endpoint now requires an
   administrator account. Any account allowed to edit a post could previously write
   arbitrary meta on it, protected keys included.

#### 2.1.3

 * New: the file export now bundles any reusable Gutenberg block referenced by the
   exported items (a “pattern” is never itself selectable for export, but its content
   can be hidden inside another item’s content). Import recreates those blocks and
   rewrites the references to point at them, instead of importing content whose 
   blocks point at nothing on the new site.

#### 2.1.2

 * Fix: another plugin’s admin notice no longer lands in the middle of this page’s
   header, splitting the title from the text below it.

#### 2.1.1

 * Improvement: when this site is the source of a direct migration, image and gallery
   fields now carry enough information for the other site to attach the right file.
   Previously those fields could be skipped rather than risk pointing at the wrong
   image.

#### 2.1.0

 * New: this plugin can now receive a direct migration from another WordPress site
   you control — content is sent straight from one site to the other, with no file
   to download and re-upload. Crucially, the custom fields that the REST API normally
   drops (Elementor layouts, ACF fields, SEO metadata) now travel too, so a page
   arrives laid out the way it left. The other site drives the migration; this one
   answers, and only to requests carrying a valid application password from an account
   allowed to edit the content. This plugin still contacts no external service on
   its own.

#### 2.0.5

 * Improvement: unchecking every content type is no longer possible — at least one
   is always kept selected, and the server now rejects an empty selection instead
   of silently defaulting to Posts.
 * Improvement: choosing a file to import now shows a quick preview (source site,
   export date, item count) before you import, with a clear message if the file 
   isn’t a recognized export.
 * Improvement: items skipped during import (a type you didn’t select) now appear
   individually in the import log, not just in the summary count.
 * Smaller plugin download — removed unused CSS left over from a shared codebase
   with the Premium add-on.

#### 2.0.4

 * Fix: “Media” is no longer offered as a selectable content type in file export/
   import. This plugin never transfers the underlying file (media migration between
   live sites is a premium feature), so selecting it previously created a broken
   media entry with no file attached on import.

#### 2.0.3

 * Fix: Lite plugin now activates correctly when the Premium add-on is installed
   but deactivated on the same site.

#### 2.0.2

 * New option to export the full taxonomy structure (all terms with descriptions
   and parent-child hierarchy). On import, terms are recreated before posts so hierarchy
   is preserved correctly.

#### 2.0.1

 * Post type selector now lists all public post types registered on the site, not
   just Posts and Pages.

#### 2.0.0

 * This plugin is now file export/import only — free, offline, with no external 
   connection.
 * Direct site-to-site migration (pull/push) and media transfer have moved to the
   separate premium add-on, WPMove Migration Connector Premium, available from wpmove.
   app.

#### 1.2.0

 * Import categories, tags and other taxonomy terms.
 * Refined admin interface.

#### 1.1.0

 * Free, offline file export and import of posts and pages. Imports are append-only.

#### 1.0.0

 * Initial release.

## ميتا Meta

 *  Version **2.1.11**
 *  Last updated **قبل أسبوعين**
 *  Active installations **أقل من 10**
 *  WordPress version ** 6.0 أو أعلى **
 *  Tested up to **7.0.7**
 *  PHP version ** 8.1 أو أعلى **
 *  Languages
 * [English (US)](https://wordpress.org/plugins/wpmove-migration-connector/) و [French (France)](https://fr.wordpress.org/plugins/wpmove-migration-connector/).
 *  [ترجمة إلى لغتك](https://translate.wordpress.org/projects/wp-plugins/wpmove-migration-connector)
 * Tags
 * [content](https://ar.wordpress.org/plugins/tags/content/)[export](https://ar.wordpress.org/plugins/tags/export/)
   [import](https://ar.wordpress.org/plugins/tags/import/)[migrate](https://ar.wordpress.org/plugins/tags/migrate/)
   [migration](https://ar.wordpress.org/plugins/tags/migration/)
 *  [عرض متقدم](https://ar.wordpress.org/plugins/wpmove-migration-connector/advanced/)

## التقييم

لم يتم تقديم أي مراجعات بعد.

[Your review](https://wordpress.org/support/plugin/wpmove-migration-connector/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/wpmove-migration-connector/reviews/)

## المساهمون

 *   [ xuxu.fr ](https://profiles.wordpress.org/xuxufr/)

## الدعم

لديك شيء لتقوله؟ بحاجة الى مساعدة؟

 [عرض منتدى الدعم](https://wordpress.org/support/plugin/wpmove-migration-connector/)