Move your Klaviyo waitlist to STOQ with a CSV

If you ran back in stock through Klaviyo before switching to STOQ, the customers still waiting live in Klaviyo. This guide moves them over as a CSV: export the list or segment from Klaviyo, add the product each person is waiting on, and import it into STOQ so everyone still gets alerted when the product restocks.

Before you begin

Requirement	Detail
STOQ installed	STOQ is on your Shopify store. You import from Back in stock alerts → Settings → Integrations → Import data.
A Klaviyo export role	Only Owner, Admin, or Analyst users can export a Klaviyo list or segment.
One list or segment per product or variant	STOQ needs to know which variant each customer is waiting on, and a Klaviyo CSV export can’t include that (see below). This route works when your Klaviyo signups are organised as a separate list or segment for each product or variant.

Does this route work for your setup?

STOQ’s import needs the variant each customer is waiting on (its SKU or Shopify variant ID) on every row. A Klaviyo list or segment export gives you the profiles (email, phone, name, consent, date added) but not which product they signed up for, because that lives in Klaviyo’s back in stock events, which a list or segment CSV can’t export.

So:

• If each product or variant has its own Klaviyo list or segment, this CSV route works. You export one list at a time and add that product’s SKU to every row, since the whole list is waiting on the same variant.
• If your back in stock signups only exist as Klaviyo events (one big list, or no per-product lists), a CSV export can’t tell you who wanted what. Use the developer API migration instead, which reads the variant from the events.

What carries over

Importing doesn’t email anyone. Each row just rejoins the waitlist for its variant, exactly as if the customer had signed up on your store, and gets your normal restock alert later when the product is back and meets your delivery settings. You can bring across the customer’s email or phone, name, signup date, consent, and language.

Set it up

Do this once per Klaviyo list or segment (that is, once per product or variant).

1. Export the list or segment from Klaviyo

   In Klaviyo:

   1. Go to Audience > Lists & segments and open the list or segment for the product.
   2. Open the Manage list (or Manage segment) dropdown and choose Export list to CSV (or Export segment to CSV).
   3. Choose the properties to include: at least Email, and Phone number, first name, date added, and email/SMS consent if you have them.
   4. Click Start export. The CSV downloads to your computer automatically once it’s ready (large exports take a few minutes).

   

   

   

2. Add the variant and match STOQ’s columns

   Klaviyo’s export has no variant column, so open the CSV in your spreadsheet tool and add one. Everything else can stay as exported, because you match columns during the import:

   1. Add a SKU column and fill it with this product’s variant SKU or Shopify variant ID on every row. The whole list is waiting on that variant, so the value is the same down the column.
   2. In STOQ’s mapping step, match Klaviyo’s columns to STOQ’s: email to Email, phone to Phone, first name to Name, date added to Date, and marketing or SMS consent to Accepts marketing and GDPR confirmed. Add Language if you have a locale.

   See Import your waitlist for exactly what each STOQ column expects.

3. Import the CSV into STOQ

   In STOQ, go to Back in stock alerts → Settings → Integrations, open the Import data card, and upload your CSV. STOQ matches your columns to its fields, you confirm the mapping, and it recreates the waitlist entries in the background. Repeat for each product’s list. Full steps: Import your waitlist.

   

Check your setup

The import runs in the background and STOQ emails a status report to your report email address when it finishes. Open a product a customer was waiting on and confirm they now appear on its STOQ waitlist. You can also click View imports on the Import data card to see each import’s status and how many rows succeeded.

FAQ

My Klaviyo export doesn't show which product each person waited on

That’s expected. A Klaviyo list or segment CSV can’t include event data, and the back in stock variant lives in an event. Either export a separate list per product and add its SKU yourself, or use the API migration, which reads the variant from Klaviyo’s events.

Do imported customers get an alert right away?

No. Importing only recreates the pending waitlist entries. Alerts go out later, when the product restocks and meets your delivery settings, the same as a normal signup.

Will re-importing create duplicate signups?

No. A customer already on the waitlist for that same variant is skipped, so re-uploading a file or importing overlapping lists won’t create duplicates.

I can't export the list in Klaviyo

Exporting a list or segment needs the Owner, Admin, or Analyst role in Klaviyo. Ask an account admin to export it or grant you the role.

Can I bring over consent and the original signup date?

Yes. Map Klaviyo’s consent columns to Accepts marketing and GDPR confirmed, and its date added to Date, so imported customers keep their consent status and their place in the queue.

Related guides

Import your waitlist from another appThe full CSV import flow and what each STOQ column expects.

Migrate your Klaviyo back in stock signupsThe developer API route, for when signups only exist as Klaviyo events.

Connect Klaviyo for back in stockSend your STOQ restock alerts through Klaviyo going forward.

Delivery settingsControl when and how restock alerts reach your waitlist.