Constructor backup (PRO)

Export everything you built in the constructor as one file — and deploy it on another site.

The "Constructor backup" button in the component header, with two entries: export and import.

What goes into the file

Blocks, tables, sections, tabs, fields, columns, menus, routes, languages, translators, UTM tags and migrations. The whole construction, in other words.

There is no content in the file

No block data, no table rows, no uploaded files. What is exported is how the site is built, not what is written on it.

For moving content this is the wrong tool.

You cannot choose what to include: everything is exported.

Import replaces, it does not merge

The file is deployed over what is there: the current construction is replaced entirely, which is why the import asks for confirmation. Before writing, the server saves a snapshot of what was there — in case the wrong file was deployed.

A foreign JSON will not get through: the file is checked for belonging to PageBlocks.

What it is for

You build the constructor on a development site, check it, and move it to production as one file, instead of repeating fifty settings by hand and then hunting for the one you got wrong.

The same file is a way to ship starting points: a set of blocks for a typical site is built once and then deployed onto every new project.