Export and import posts, options and menus. Clone posts with meta. Search and replace URLs across the database with serialized data support.
Moving a site is mostly URL replacement, and URL replacement is where serialized data quietly breaks. Getting that right matters more than doing it quickly.
A naive find-and-replace corrupts serialized arrays. This one adjusts the string lengths.
Export and import posts with what belongs to them.
Move configuration, not just content — the part manual migrations forget.
Export and import navigation menus with their structure intact.
Duplicate a post with its meta, useful for templates and staging.
Replace URLs across the database when a domain or protocol changes.
Describe the move and the Migration Toolkit handles the mechanics — content, options, menus and every URL that has to change with them.
Move content and settings across, rewriting every URL on the way.
Switch domain or protocol without leaving broken references behind.
Duplicate a well-built post as the starting point for the next one.
Carry menus across instead of rebuilding them by hand.
The Migration Toolkit is built into NibWP and lets any MCP-compatible AI agent — Claude, Cursor, Claude Code and others — move content, configuration and navigation between WordPress sites.
The hard part of a migration is rarely the content. It is the thousand references to the old domain scattered through post content, options and meta, many of them inside serialized arrays that a plain SQL find-and-replace corrupts without warning.
Replacements adjust the recorded string lengths inside serialized values, which is the difference between a migration that works and one that quietly breaks a dozen widgets. Destructive operations are flagged as such, and a dry run shows the scale before anything changes.
| Tool | Type | What it does |
|---|---|---|
| nibwp/migration-export-content | read | Export posts and their data. |
| nibwp/migration-import-content | write | Import posts into this site. |
| nibwp/migration-export-options | read | Export configuration options. |
| nibwp/migration-import-options | write | Import configuration options. |
| nibwp/migration-export-menus | read | Export navigation menus with their structure. |
| nibwp/migration-import-menus | write | Import navigation menus. |
| nibwp/migration-clone-post | write | Duplicate a post with its meta. |
| nibwp/migration-search-replace-urls | destructive | Replace URLs across the database, serialized data included. |
No. The Migration Toolkit is built into NibWP and available on every plan, including Free.
PHP serialized arrays store the length of each string. Replace a URL with a longer one using plain SQL and the lengths no longer match, which silently breaks widgets, options and meta. This handles the lengths.
It is flagged destructive because it is not. Take a backup first, and use a dry run to see the scale of the change before applying it.
No. This moves content, options and menus between sites. Backing up the whole install is a different job and you should still have one.
Activate the integration and it's live on your MCP endpoint instantly.