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

Import
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.
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.
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.
How the columns work
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.
Migrating from another app
The import process is the same as above, with two additional recommendations:
Import without activating the option sets. Review them first, then activate them when you're ready.
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:
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.
Last updated
Was this helpful?