For the complete documentation index, see llms.txt. This page is also available as Markdown.

Import and export

Move option sets between stores using CSV files, create backups, or migrate from another product options app.

Export option sets creates a CSV file containing your option sets. Import option sets lets you upload a CSV file created by this app or exported from another supported product options app.

Use these tools to back up your option sets before making major changes, move a setup from a development store to a live store, or migrate from an app you are replacing.

Both actions are available next to Create option set on the Option Sets page. Import and export are controlled separately by your plan, so you may have access to one without the other.

Export

1

Select the option sets you want to include if you only want to export specific sets.

Skip this to export everything.

2

Select Export option sets, then choose the scope

Choice
Includes

Current page

Every option set on the page you are looking at

All option sets

Every option sets in your store

Selected: N option sets

Only selected rows. Unavailable when nothing is chosen.

The format is a Plain CSV file.

3

Select Export option sets again

Your browser downloads OptionsExport.csv.

The export dialog with scope choices and the CSV format option
Export the current page, everything, or just your selection.

Export your option sets before making any changes you are unsure about. The exported file serves as a backup and is the only way to restore an option set after it has been deleted.

Import

1

Select Import option sets and add your file

Select Import option sets, then upload your file by dragging it into the drop zone or browsing your device.

Supported file formats: .csv, .txt, .xlsx, and .xls. The maximum file size is 10 MB.

Creating a file manually? Use the sample CSV template provided in the dialog instead of creating the file structure from scratch.

2

Select the source app

Select app for import tells the app how to interpret the columns in your file. It defaults to Globo Product Options, Variant and also supports files from Easify, Avis, OPTIS, Qikify, Hulk, and APO.

Selecting the wrong app is the most common cause of import errors or incorrectly mapped data.

3

Leave "Set all imported option sets as Active" off

By default, imported option sets are saved as Draft, so you can review them before they become visible to customers. Enable this option only when you are sure the imported sets are ready to go live.

4

Select Upload and continue, then review the imported sets

Open each imported option set and check its options, Name fields, add-on configuration, and product rules.

Building the file yourself

If you are not exporting from another app, start from the sample file. It contains one working example of each of the main option types, so you can see the exact column layout rather than guessing it.

A sample option set, with one example of each of the main option types.

How the columns work

Column
Holds

option_id

Identifies the option. Repeat it on extra rows to add more values to the same option

option_type

text, select, checkbox, color-swatches, and so on

option_label, option_name

What the customer reads, and what appears on the order. See Label and Name

required, min, max

Yes or No, and the limits for that option type

placeholder, helptext

The hint inside the field, and the text beside it

option_value

One choice. Selection types need one row per choice

addon

The add-on price for that row

swatch_value

A hex color such as #FF0000 for color swatches, or an image URL for image swatches

paragraph

The content of a Paragraph element

products

The product the option set applies to

The pattern to copy is the one used by every selection type in the sample: put the option's own columns on its first row, then add a row per extra value that fills in only option_id and option_value.

Export one option set you have already built and open that file too. It shows your own products, prices, and swatches in the same format, which is usually quicker to adapt than the sample.

Migrating from another app

The import process is the same as above, with two additional recommendations:

  1. Import without activating the option sets. Review them first, then activate them when you're ready.

  2. Test at least one imported set on a real product before uninstalling the old app. Uninstalling the old app first can leave a gap that is immediately visible to customers.

Some cleanup may be needed because different apps structure options differently. Pay particular attention to:

Check
Why

Add-on pricing

Pricing from the other app may not map exactly. Review each price and choose the appropriate pricing mode. See Add-on pricing

Conditional logic

Operators can differ between apps, so some conditions may need to be rebuilt.

Option Name fields

Make sure they are readable and unique. See Label and Name

Product rules

Confirm that each option set targets the products you expect.

Swatch images

You may need to upload them again if the previous app hosted the images itself.

What travels, and what does not

Exported option sets contain their own configuration. Store-wide settings are handled separately:

  • Colors, borders, typography, custom CSS, widget position and behavior — export from Settings. See Import and export settings.

  • Widget text and validation messages — Settings > Translations.

  • Automations — configured per store.

  • Add-on products — the file records which product an add-on was linked to, but that product may not exist in the destination store. Reconnect add-ons after importing between stores.

Notes

  • Imported option sets are added as new sets; existing sets are never merged or overwritten. Importing the same file twice creates two copies.

  • Import respects your plan limits and features. If the file contains features that your plan does not support, the import is rejected rather than partially applied.

  • Files exported from older versions of the app are still supported. The app automatically detects the older column format.

What the exported CSV contains, column by column

You only need this if you intend to read or edit the file by hand.

The file has one row per option value. Options without values, such as text fields, get a single row. Columns describing the whole option set or the whole option are filled on the first row only and left blank on the rest.

Column
Contains

option_set_id

The option set's ID, repeated on every row of that set

option_set_name

The option set's name. First row only

option_id

The option's internal ID within the set

option_type

The option's type

option_label

The option's Label, including any translations

option_name

The option's Name

required

yes when Required field is on

allow_multiple

yes when multiple selection or multiple file upload is on

min, max

The option's minimum and maximum, whatever they measure for that type

placeholder

The option's Placeholder

helptext

The option's Help text and its position

option_value

The value on this row, with its own help text where it has one

addon

The add-on configuration: which mode, which product and variant, and the price

swatch_name

The swatch's internal name

swatch_value

The color, the two colors of a split swatch, or the image address

swatch_asset_name

The uploaded image's file name

default_value

The option's default value

rich_text_value

Rich-text content for Paragraph, Pop-up modal, HTML, Size chart, and Tabs

advanced_settings

Everything from the Advanced and Personalizer tabs, in one cell

columnWidth

The option's Column width

conditionalField

yes when conditional logic is on for this option

condition_logic

The conditional logic rule itself

products

The product rule. First row only

customers

The customer rule. First row only

countries

The country rule. First row only

settings

Option set settings, including the Personalizer background. First row only

Last updated

Was this helpful?