Guide

Importing and exporting a configuration

A whole configuration — its layers, views and choices — can be exported to a file and imported into another product. This is the way to reuse a configuration on a product that is not part of a shared setup, or to move one between sites.

Both actions live in the Import / Export section of the configurator sidebar.

Exporting

Open the product's configurator, go to Import / Export, and press Export configuration data.

Your browser downloads a JSON file named after the product and the date, along the lines of:

configurator-data--product-60--2026-08-22T09:14:22.000Z.json

The file contains the product's layers, views and content — the choices inside each layer. If the Conditional logic add-on is active, its conditions are included too.

Importing

Open the configurator of the product you want to import into, go to Import / Export, press Import configuration, and choose a previously exported JSON file.

The imported layers, views and choices replace what the product currently has, so import into a product you are building rather than one already selling. Nothing is written until you save.

Images need attention afterwards

This is the part that surprises people.

The export records which images each choice uses, not the images themselves. Importing into another product on the same site usually keeps working, because the images are still in the media library. Importing into a different site does not: the images are not there, and the choices end up pointing at nothing.

After importing to a new site:

  • Add the configurator images to that site's media library,
  • Go to Product Configurator > Settings > Tools,
  • In the Fix images section, select the product you imported into,
  • Run the tool.

This is covered in full in Fixing images after importing a configuration.

Choosing between export and sharing

Export gives each product an independent copy. Once imported, the two are unrelated — changing one does not affect the other.

If what you actually want is for several products to stay in step, use a shared setup instead:

Export and import are the right tool for a one-off copy, a starting point, or moving between sites. They are the wrong tool for keeping products synchronised — that is what the global features are for.