NR Post Exporter
v1.0.1
WordPress plugin
Export a single post or page to JSON — custom fields, taxonomy terms, and the full revision history — then import it on another site.
{ "post_title": "Spring release notes", "post_type": "post", "post_status": "publish", "post_name": "spring-release-notes", "post_content": "<!-- wp:paragraph -->…",
"post_meta": { "_thumbnail_id": "1184", "reading_time": "6" },
"terms": { "category": ["announcements"], "post_tag": ["release", "changelog"] },
"revisions": [ { /* oldest draft, same shape */ }, { /* … replayed in order on import */ } ] }
The payload
The export is a plain JSON file. Read it, diff it, keep it in a ticket — it is the whole record of the post at the moment you exported it.
On the source site
No settings to configure. The plugin adds one row action to every public post type.
You need the export capability.
Custom post types work too, as long as they are public.
The link sits next to Edit and Trash. It opens in a new tab and starts the download.
The filename records the post type, ID, site, and export time, so a folder of exports stays readable.
On the destination site
Install the plugin on the destination site too, then upload the file.
You need the edit_posts capability.
One screen, one field.
Files are capped at roughly 1 MB. Larger exports are rejected rather than truncated.
The title is prefixed with Imported: so it is easy to spot. Revisions are
replayed oldest to newest, so the history reads the same as it did on the source site.
Missing terms are created from their slugs.
Before you share a file
post_password field.Open the file before you attach it to a ticket, commit it, or send it on. Anyone who can read the file can read everything the post held.
Setup
Install on both sites — the source site for exporting, the destination site for importing.
Download the release zip, then go to Plugins → Add New → Upload Plugin, and activate.
composer require nikolareljin/nr-post-exportercd wp-content/plugins
git clone https://github.com/nikolareljin/nr-post-exporter.git
wp plugin activate nr-post-exporter| WordPress | 5.8 or newer |
|---|---|
| PHP | 7.4 or newer |
| Export capability | export |
| Import capability | edit_posts |
| Current version | 1.0.1 |
Details
No. The native WXR export moves a whole site or a whole post type. This moves one post at a time, and keeps meta and revisions intact while doing it.
Yes, any post type registered as public gets the Export row action.
So a fresh import is obvious in the posts list, and so it never silently collides with a post that is already there. Rename it once you have checked it.
Attachment references travel inside the content and meta, but the files themselves do not. Move the uploads separately, or re-point the references after import.
The user running the import. Post authorship is not carried across, because user IDs rarely match between sites.
Yes. Each import creates a new post — nothing is overwritten or matched by ID.
Imports are capped at about 1 MB. Posts with long revision histories are the usual reason to hit it.
WordPress projects
Small, focused tools for publishing and working with WordPress content.
History
Generated from CHANGELOG.md by bin/update-docs.sh.
Do not edit this section by hand.
docs/, published with GitHub Pages: export and import walkthroughs, the JSON payload structure, install steps, requirements, and FAQ.bin/update-docs.sh to sync the site's version and changelog from nr-post-exporter.php and CHANGELOG.md. Run with --check to fail on drift.docs/ from the distributed plugin package.test directory from distributed plugin packages.nrpexp prefix to avoid collisions.readme.txt metadata: added contributor nreljin, trimmed tags to five, and shortened the description to WordPress.org limits.error_log() call for the nrpexp_export_terms_error action to surface term export failures without shipping debug logging.