rosvit / module-cms-content-sync

1.0.0 2026-10-05 23:29 UTC

Requires

• php: ~8.2.0||~8.3.0||~8.4.0||~8.5.0
• magento/framework: ^103.0
• magento/module-backend: ^102.0
• magento/module-cms: ^104.0
• magento/module-store: ^101.1
• magento/module-ui: ^101.2

MIT

• Rosvit

• import
• cms
• export
• magento
• magento2
• page-builder

Published on Packagist.org on 2026-10-05 23:32 UTC

README

Export and import Magento 2 CMS Pages and Blocks between environments as JSON.

Move content from staging to production (or between any two installs) without copying databases: select pages or blocks in the admin grid, download a JSON file, upload it in the other environment, review a preview and import.

Features

• Mass export from the CMS Pages and CMS Blocks grids into a single JSON file.
• Preview before import: every row shows whether it will be created, updated, left unchanged or fails, and you choose which rows to import.
• Portable store scopes: store views travel by code, not by id.
• Portable block references: blocks used inside pages or other blocks ({{widget type="Magento\Cms\Block\Widget\Block" ...}}, {{block id="..."}}, Page Builder) are exported by identifier and mapped back to the local block id on import. Missing blocks are reported in the preview and after the import.
• Blocks are imported before pages, so one file can carry a page and the blocks it uses.

Requirements

• Magento Open Source / Adobe Commerce 2.4.x
• PHP 8.2 – 8.5

Installation

composer require rosvit/module-cms-content-sync
bin/magento module:enable Rosvit_CmsContentSync
bin/magento setup:upgrade
bin/magento cache:flush

Usage

1. Export: go to Content → Pages (or Blocks), select the rows, and choose Actions → Export to JSON.
2. Import: in the target environment go to Content → CMS Content Sync, upload the file, review the preview and click Import Selected.

Access is controlled by two ACL resources, Export CMS Content and Import CMS Content, under Content → CMS Content Sync.

License

MIT