How to Export Page Builder Pages and Templates in Magento 2

Magento 2 Page Builder makes it easy to create attractive CMS pages, reusable templates, and custom content blocks. But what happens when you need to move these elements to another website? Unfortunately, Magento 2 doesn’t provide a built-in export option for Page Builder pages or templates.
You can still transfer your content without recreating every layout manually. One option involves exporting template records directly from the database. Another, more flexible approach uses the Improved Import & Export extension to move CMS pages and blocks created with Page Builder between Magento 2 installations.
Below, we explain both methods, their limitations, and how to choose the right one for your workflow.
Table of contents
- Can You Export Page Builder Pages or Templates in Magento 2 by Default?
- How to Export Page Builder Pages and Templates Between Magento 2 Websites Manually
- How to Export Page Builder Content Automatically with Improved Import & Export
- What to Check After Exporting Magento 2 Page Builder Content
- Final Words: Simplify Magento 2 Page Builder Export
- Magento 2 Page Builder Export FAQ
Can You Export Page Builder Pages or Templates in Magento 2 by Default?
Magento 2 Page Builder lets you save layouts as reusable templates and apply them to other content areas. However, saving a template is not the same as exporting it to another Magento installation.
Although you can manage saved layouts under Content → Elements → Templates, Magento’s native import/export tools do not support transferring these records between websites.
There is also an important distinction between two types of Page Builder data:
- Page Builder templates are reusable content layouts saved within Magento. They can be applied to CMS pages, blocks, and other compatible content areas.
- Page Builder CMS pages and blocks are actual storefront content records containing Page Builder layouts, text, images, and other elements.
Both can be transferred, but the methods differ. You can move saved templates manually through the database, while the Improved Import & Export extension provides a more convenient solution for exporting and importing Page Builder-based CMS pages and blocks.
For more information about native template functionality, see the.
How to Export Page Builder Pages and Templates Between Magento 2 Websites Manually
The original solution comes from a, where asked how to move Page Builder pages or templates from one Magento website to another.
suggested a practical workaround: save the required Page Builder content as a template, export its database record, and import it into the destination website.
Here’s how this method works:
- Save your Page Builder content as a template. Open the required CMS page in the Magento 2 admin panel. In the Page Builder editor, click Save as Template and provide a recognizable name.
- Access the source website’s database. Open phpMyAdmin or another MySQL management tool and locate the pagebuilder_template table.
- Export the required template records. Find the templates you want to transfer and export the relevant database rows into a CSV or SQL file.
- Import the records into the destination database. Open the second Magento installation’s database, locate its pagebuilder_template table, and import the records. Check for existing template IDs and possible conflicts before proceeding.
- Apply the imported template. Return to the destination website’s Magento admin, open the required CMS page, and use Apply Template to insert the transferred layout.
This approach was originally tested with Magento 2.4.3-p1. It may also work with other versions, but you should verify database compatibility before attempting the transfer.
Important: This method transfers saved Page Builder templates, not complete CMS page records with all their settings and metadata. You may also need to move images and other media separately or update their references.
Since the process involves direct database manipulation, back up both installations and test the procedure in a staging environment first.
For occasional transfers, the workaround can be sufficient. However, copying database records manually becomes inconvenient when you need to move dozens of pages, synchronize content regularly, or manage multiple Magento websites.
How to Export Page Builder Content Automatically with Improved Import & Export
If you regularly transfer Page Builder content between Magento 2 websites, consider using the Improved Import & Export extension.
Instead of accessing database tables manually, the extension lets you export and import CMS pages and blocks created with Page Builder through configurable jobs in the Magento admin panel.
It preserves Page Builder content stored within the supported CMS entities, allowing you to reuse existing layouts without rebuilding them from scratch.
Step 1: Create a Page Builder Export Job
Install Improved Import & Export on the source and destination Magento installations.
On the source website, navigate to:
System → Improved Import / Export → Export Jobs
Click Add New Job and configure its general settings.

Next, open the Export Settings section and choose the required entity:
- CMS Pages to export pages created with Magento 2 Page Builder.
- CMS Blocks to export reusable content blocks, including blocks designed with Page Builder.

Step 2: Configure the Export and Run the Job
Choose the export format and destination that match your requirements.
Improved Import & Export supports several data formats, including CSV, XML, JSON, XLSX, and ODS. You can also use destinations such as Google Drive, Dropbox, or FTP/SFTP.

Additional options include export filters, attribute mapping, and scheduled execution.
Once the settings are ready, save and run the job to generate the export file containing your Page Builder-based CMS content.
Step 3: Import Page Builder Content into Another Magento Website
On the destination website, navigate to:
System → Improved Import / Export → Import Jobs → Add New Job
Select the corresponding entity — CMS Pages, CMS Blocks, or Widgets — and provide the exported file or configure its import source.

If necessary, use the extension’s mapping tools to match incoming fields to Magento attributes. Validate the file, configure the import behavior, and run the job.
Your CMS pages or blocks, including their stored Page Builder content, can now be transferred to the new Magento website.
Note: This procedure transfers Page Builder content through CMS page and block entities. It should not be confused with direct export of standalone records from the pagebuilder_template database table.
For a more comprehensive explanation, see our dedicated guide: How to Import and Export Magento 2 Page Builder Data.
Why Use Improved Import & Export for Page Builder Content?
Compared with manual database transfers, Improved Import & Export offers several practical advantages:
- Bulk content migration. Export and import multiple Page Builder CMS pages or blocks instead of processing individual template records.
- More file formats. Work with CSV, XML, JSON, XLSX, and ODS without manually converting every source file.
- Automated transfers. Schedule import and export jobs to synchronize CMS content between Magento installations.
- Flexible data sources. Exchange content through local files, Google Sheets, Dropbox, Google Drive, and supported remote connections.
- Mapping and filtering. Adapt imported data to the destination store’s structure or export only the records you need.
These capabilities are particularly useful when moving content from staging to production, launching additional storefronts, or maintaining similar layouts across multiple Magento websites.
What to Check After Exporting Magento 2 Page Builder Content
Regardless of the method you choose, a successful data transfer doesn’t always guarantee that the page will look identical on the destination website.
Pay attention to three things:
- Images and media files. Ensure that referenced images and videos are available on the destination website. Transferring CMS content does not necessarily copy the underlying media files.
- Content dependencies. Check that referenced products, CMS blocks, widgets, and custom Page Builder content types exist and work correctly on the new installation.
- Store configuration and layout. Verify store-view assignments, CMS page identifiers, URLs, and any theme-specific styling.
Finally, preview the imported pages on the storefront. This simple check can reveal missing assets or layout differences before the content goes live.
Final Words: Simplify Magento 2 Page Builder Export
Exporting Page Builder pages or templates between Magento 2 websites requires more than the platform’s default tools provide.
If you need to transfer a few saved templates, the manual database method described on Stack Exchange offers a possible solution. However, it requires technical knowledge and careful handling of database records.
For larger or recurring transfers, Improved Import & Export provides a more convenient way to migrate Page Builder-based CMS pages and blocks. With bulk processing, multiple file formats, flexible sources, mapping, and scheduling, you can move existing storefront content without rebuilding every layout manually.
Get Improved Import & Export for Magento 2 to simplify your CMS migration workflow, or contact us if you need assistance with a specific Page Builder transfer.
You can also explore our Magento 2 Developer’s Cookbook for more Magento development tips and practical solutions.
Magento 2 Page Builder Export FAQ
1. Can You Export Page Builder Pages in Magento 2?
Yes, but not through Magento’s default export interface. You can export CMS pages created with Page Builder using a third-party extension such as Improved Import & Export. It supports transferring the stored Page Builder content along with the corresponding CMS page data.
2. How Do You Export Page Builder Templates in Magento 2?
One manual approach is to save the content as a Page Builder template, export the relevant records from the pagebuilder_template database table, and import them into another Magento installation. This requires database access and careful handling of record IDs.
3. Does Magento 2 Have a Built-In Page Builder Export Feature?
No. Magento lets you save and reuse Page Builder templates within an installation, but it doesn’t provide a dedicated native interface for exporting those templates or Page Builder-based CMS pages to another website.
4. Can You Transfer Page Builder Content Between Two Magento 2 Websites?
Yes. You can transfer saved templates manually through the database or use Improved Import & Export to move CMS pages and blocks containing Page Builder content. The appropriate method depends on which records you need to transfer.
5. Does Improved Import & Export Support Magento 2 Page Builder?
Yes. Improved Import & Export supports importing and exporting CMS pages and CMS blocks created with Page Builder. This allows you to migrate their stored content and layouts between Magento 2 installations without manually recreating them.
6. Can You Export Magento 2 Page Builder Content to CSV or Excel?
Yes. Improved Import & Export supports exporting Page Builder-based CMS pages and blocks to CSV and Excel XLSX files, along with other supported formats such as XML, JSON, and ODS.
7. Can You Automate Magento 2 Page Builder Exports?
Yes. Improved Import & Export lets you configure scheduled export and import jobs for supported CMS entities. This is useful for recurring content transfers between staging and production environments or multiple Magento stores.
8. Are Images and Other Media Automatically Transferred with Page Builder Content?
Not necessarily. Page Builder content can contain references to images, videos, and other assets stored separately. After importing the content, make sure those resources are available and their paths are valid on the destination website.
9. What Is the Difference Between Exporting Page Builder Templates and CMS Pages?
A Page Builder template is a reusable layout stored separately in Magento, while a CMS page is a complete content record that may include Page Builder-generated content, page settings, and SEO metadata. Exporting a template doesn’t automatically transfer the complete CMS page, and exporting a CMS page doesn’t necessarily create a reusable template record on the destination website.




