ContentBridge

Move a store's content, catalog structure and configuration from staging to production as a deliberate, reviewable action — no database dumps, no filesystem sync, and no window where production is offline.

Latest version: 1.0.0 — changelog

Why it matters

• Stop rehearsing releases twice. Content built and approved on staging goes live as-is, instead of being retyped into production and re-checked for typos.
• Nothing moves that you did not look at. Every merge runs a mandatory dry-run first and lists each item it would create, so a duplicate category is caught before it exists rather than after.
• A wrong reference fails loudly instead of quietly. Entities are matched by natural key — a code, a SKU, a URL path — never by database id, so a promoted price rule cannot end up discounting a different product because the two instances number their rows differently.
• Production data stays production data. Deletes never propagate, orders and customers never travel, and encryption keys, base URLs and payment credentials are refused even if someone widens the allow-list.
• Every promotion is on the record. Pairing, pushes and merges are written to an audit log with the acting admin, the connection and a structured summary.

What it moves

Feature	Benefit
Merge Wizard (eighteen entity types)	Promote store structure, catalog and pricing one type at a time, in a dependency order the wizard works out for you
Sync profiles	Push CMS pages, blocks and allow-listed configuration on demand, sending only what actually changed since the last run
Products of every type	Simple, virtual, grouped, configurable, bundle and downloadable products move by SKU, carrying tier prices, links, custom options and their gallery
Connections and pairing	Establish trust between two instances with a one-time code; each connection gets its own HMAC secret and can be time-boxed, disabled or revoked
Protected configuration paths	Payment, shipping and mail-transport settings, encryption keys and base URLs are hardcoded as non-transferable
Audit log	See who promoted what, when, and to which instance

Runs entirely between your own two Magento instances over a signed HTTP channel — there is no third-party service in the path, and no store data leaves infrastructure you control.

Supported: PHP 8.1 – 8.5, on magento/framework >=103.0.8 <104.0.0 (Magento Open Source, Adobe Commerce and Mage-OS builds on that framework line).

Ready to set it up? Start with installation, then configuration.