Move Magento CMS Blocks and Pages by CSV: Scope, HTML and Media
B2B & Operations

Move Magento CMS Blocks and Pages by CSV: Scope, HTML and Media

• 5 min read • 6 views

A Magento CMS handover needs more than copied HTML. Keep the record identifier, store assignment and active state together; for pages, retain metadata and layout as well. Move image files separately and check the result in the target storefront.

CMS Block Import / Export and CMS Page Import / Export provide related CSV workflows, but they are separate modules handling separate entities. The current direct-store versions are 1.0.3 for blocks and 1.0.4 for pages. Use the relevant module for each file rather than treating one CSV as a complete website backup.

Choose manual editing, a deployment patch or CSV

Magento's native Content → Elements screens remain useful for a small number of changes. A developer-managed data patch may suit content that belongs in a controlled software release. A CSV workflow helps when editors need to review many records or hand content between environments without replacing live database tables.

Content staging in Adobe Commerce serves a different job from portable CSV records. It does not remove the need to agree which environment owns each piece of content and how conflicting edits will be resolved.

CMS blocks: reusable pieces of content

Use CMS Block Import / Export for reusable notices, supporting content and other block records. The block columns are identifier,title,is_active,stores,content. The identifier and scope determine which existing record an update targets.

Export from the block import/export screen or the buttons on the Blocks grid. Preserve the file before editing. Keep the identifier when updating the same block; use a new identifier for genuinely new content. Importing a block does not automatically place it on every page: inspect the CMS page, widget or theme location that consumes it.

CMS pages: content plus page settings

Use CMS Page Import / Export for standalone pages. The page file includes the shared content columns plus supported fields such as content heading, page layout, meta title, meta keywords, meta description and sort order. Start with its own export so you retain the exact header names.

Enable the feature under Stores → Configuration → AgenticEcom · SEO & Content → CMS Page Import / Export, then use the Import CSV and Export CSV buttons on Content → Elements → Pages. A page file is not a block file, even where the content cells look alike.

Identifiers, store codes and import behaviour

The stores cell uses store-view codes separated by |, such as default|fr, or all for All Store Views. Map those codes to the target store before importing. An import option can force rows into a selected store view; review that override as carefully as the CSV itself.

Add/Update updates matching identifiers within scope and creates new ones. Add Only creates new records and skips existing matches. Use Add Only when preserving an existing record is intentional; do not mistake a skipped record for an updated one. “All Store Views” overlaps individual store scopes, so review existing identifiers and assignments before a handover to avoid updating the wrong content.

Illustrative round-trip: punctuation and an image reference

The following block row illustrates CSV quoting. It has not been imported in this content exercise. Replace the store code and image with real staging values.

identifier,title,is_active,stores,content
inspection_notice,Inspection information,1,default,"<p>Manuals, drawings and ""quick-start"" notes.</p>
<p><img src=""/media/cmspages/inspection-guide.jpg"" alt=""Inspection guide cover""></p>"

The content cell is enclosed in quotes; quotes inside it are doubled. The line break stays inside the cell. Use a CSV-aware editor and export with the expected delimiter. Pasting HTML with commas into an unquoted cell can turn one record into the wrong number of fields.

  1. Export one existing staging block and one staging page, keeping their files separate.
  2. Make a small text change containing a comma, a quote and a line break. Retain identifiers and deliberate scope.
  3. Import with Add/Update and read created, updated, skipped and warning counts. These tools report rows independently; one failed row does not mean other rows were rolled back.
  4. Reopen each record and inspect its saved content. For the page, compare metadata, layout and active state too.
  5. Re-import and confirm that the intended records update rather than multiply. Open the consuming page and the page's own public URL in each relevant store view.

What the file does not carry

The CSV carries HTML references to images, not image binaries. Transfer the required public media separately, preserve the intended paths and check image delivery on the target domain. Review absolute links to staging, embedded videos, widgets and other dependencies that may not exist in production.

The importers filter common active script patterns. That is basic filtering, not complete HTML sanitisation or a guarantee against stored XSS. Grant access to trusted CMS editors, review imported HTML and use the appropriate module and native CMS permissions. Do not use import access as a way to let untrusted authors publish arbitrary markup.

Before using the handover with customers

Confirm the exact package's Magento and PHP requirements. The block product records checks on Magento Open Source 2.4.9 / PHP 8.5.10; the page guide asks for exact-release qualification. This article supplies no new install, import or security test. Test your PHP version's CSV handling and your theme's rendered content before a production batch.

Keep backups of the current destination records and database, agree a content freeze or conflict-resolution process, and compare the target storefront after importing. A successful upload alone does not prove that every page, store assignment and media reference is correct.

Use the block workflow guide and page field reference for setup. Read their filtering claims with the limits above: these are portability tools for trusted editors, not a complete media migration or security boundary.

This article describes AgenticEcom's own modules. Reviewed for accuracy on 4 November 2026.

Product information reviewed 4 November 2026 by AgenticEcom. Illustrative examples are not customer results or new runtime tests.