Export and import campaigns
Export campaigns to a portable file and import them into another store as drafts. Useful for moving work between a staging and a live store, sharing a setup, or keeping a backup.
Stackable can save your campaigns to a file and read them back on any store where Stackable is installed. This is how you move a campaign from a test store to your live store, hand a setup to a colleague, or keep a backup before a big change. It is a Stackable file, not a Shopify export, so it only works with Stackable on both ends.
Exporting
On the Campaigns page, use Export all to save every campaign in the current view, or Export from a single campaign’s menu to save just that one. Your browser downloads a .json file named like stackable-campaigns-2026-07-13.json. Exporting never changes anything on your store; it only reads.
What is not included
The file describes your campaigns and their rules only. It never contains anything tied to a specific live discount on a specific store, so importing it elsewhere can never disturb that store’s live discounts.
Importing
- Open Campaigns, then Import.
- Drop the .json file onto the page, or click to choose it.
- Review the preview: each campaign is checked and shown with any notes, and you tick the ones you want.
- Confirm. The selected campaigns are created as drafts.
Imports are always drafts
Nothing an import brings in goes live on its own. Every campaign lands as a draft you review and publish yourself, so an import can never change what your customers currently see.
The file format
The file is a plain-text .json file you can open in any editor. At the top it records the format name and version and where it came from (store, currency, timezone); then it lists each campaign with its name, schedule, and offer rules. You do not need to understand the internals to use it: the normal way to get a valid file is to export one. If you want to see the shape, or build one by hand or with another tool, download the sample from the Import page and use it as a starting point. Every file is re-checked on import with the same rules the campaign builder uses, so an invalid or hand-broken file is caught and explained before anything is created.
Moving between different stores
A campaign that targets specific products or collections refers to them by both an id and a handle. On import, Stackable first tries to match the exact item; if that is not found on this store, it re-matches by handle. Anything it still cannot match is safely left out and flagged in the preview, so an import never publishes a discount pointing at products that do not exist here. Prices are kept in the original store’s currency and never converted automatically, so a file from a different-currency store is flagged for you to review and adjust before publishing.