nreljin

A lightweight tool to move content between WordPress sites with precision.
Features 
– Export a single post or page to JSON (includes meta, terms, and revisions) 
– Import a previously exported JSON to recreate the post on another site 
– Works with all public post types; sets current user as the author on import 
– Adds an Export action in Posts/Pages list rows 
– Adds Tools → Post Import with a file upload form 
– Robust UTF-8 handling: exports HTML‑entity encode content/meta; imports decode to avoid double‑encoding
Perfect for 
– Migrating content between environments 
– Duplicating complex posts across sites 
– Archiving rich post data including revision history

NR Post Exporter

Export/import individual posts with meta, terms, and revisions. Adds Export row action and Import screen.

Steve Grunwell

Unless post revisions are explicitly limited, WordPress will build up a hefty sum of revisions over time. While it’s great to have revision history for some recent content, the chances that old revisions will be necessary diminish the longer a post has been published. Revision Strike is designed to automatically remove these unneeded revisions on older, published posts.
<h4>How does it work?</h4>
First, a threshold is set, with a default of 30 days. Once a day, Revision Strike will run and find any post revisions in the database attached to published posts with a post date of at least 30 (or your custom threshold) days ago, and “strike” (tear-down and remove) them from the WordPress database.
<h4>Contributing</h4>
If you’d like to help build Revision Strike, please <a href="https://github.com/stevegrunwell/revision-strike" rel="nofollow ugc">visit the plugin’s GitHub page</a>. Contributors are welcome, and <a href="https://github.com/stevegrunwell/revision-strike#contributing" rel="nofollow ugc">details can be found in the repo’s README file</a>.

Revision Strike

Periodically purge old post revisions via WP Cron.

NR Post Exporter vs Revision Strike