We Are Volume

Post Sync Manager lets you move posts between your local, staging, and production WordPress sites with a single click — directly from the Gutenberg editor.
Free features: 
* Push and pull posts, pages, and custom post types between environments 
* Sync status indicator (in sync, remote newer, local newer, conflict) 
* Secret-key authentication between sites 
* Full sync log with pagination
<a href="https://postsyncmanager.com" rel="nofollow ugc">Pro version</a> features: 
* Bulk sync page with per-row push, pull, and status check
<h3>External Services</h3>
This plugin communicates only between your own WordPress sites when pushing or pulling posts. No data is routed through any third-party server.
<ul>
<li>What is sent: post content, post meta, and media attachments belonging to the post being synced</li>
<li>Where it goes: directly to the remote WordPress site URL you configure in Settings</li>
<li>Authentication: requests are authenticated with a secret key you set — no external accounts required</li>
</ul>

Volume Post Sync Manager

Push and pull individual posts between WordPress environments.

Khokan Sardar

WordPress full-site-editing structure — patterns, templates, template parts, global styles, and navigation — lives in the database. Moving some of it from staging to production today means either a full database sync (which is destructive to production-only data like orders, users, and form entries) or tedious manual copy-paste.
SiteCargo packs exactly what you choose into a portable, reviewable bundle and applies it to another site with stable identity, ID remapping, and media handling — never touching the data you didn’t select.
It is currently a WP-CLI tool (an admin user interface is on the roadmap).
<h4>How it works</h4>
<ul>
<li>Export the entity types you choose into a self-describing bundle (a folder containing a manifest, one JSON file per entity, and the referenced media).</li>
<li>Diff a bundle against a target site to preview exactly what would be created, updated, or left unchanged — without writing anything.</li>
<li>Apply the bundle to the target: standalone posts (patterns, navigation) are matched by a stable identifier so re-applying updates the same item instead of duplicating it; templates, parts, and global styles are matched by theme and slug. Numeric IDs baked into block markup (images, reusable-block and navigation references) are remapped to the target site, and referenced media is imported and de-duplicated by content hash.</li>
</ul>
<h4>Supported entity types</h4>
<ul>
<li>Patterns (<code>wp_block</code>)</li>
<li>Templates (<code>wp_template</code>)</li>
<li>Template parts (<code>wp_template_part</code>)</li>
<li>Global styles (<code>wp_global_styles</code>)</li>
<li>Navigation menus (<code>wp_navigation</code>)</li>
</ul>
Only templates/parts that have been customized in the database are exported; unedited theme-file templates already ship with the theme.
<h4>External services</h4>
This plugin does not connect to any external service, send any data off-site, or phone home. Bundles are plain files on your own server that you move between environments however you like.

SiteCargo

Selectively promote WordPress full-site-editing structure and content between environments — without a full database migration.

Volume Post Sync Manager vs SiteCargo