Skip to main content

Migrating from Klaviyo: what Spoks imports automatically

How Klaviyo flows are copied into Spoks, and how people, consent, and purchases already come from Shopify.

Written by Alva Dahl

During onboarding, Spoks asks if you are coming from Klaviyo. Enter your Klaviyo API key and we copy your supported flows into Spoks automatically.

Which Klaviyo API key to use

Spoks needs your Klaviyo private API key. A public API key is Klaviyo's short site ID and cannot read your flows, so it will be rejected.

If you skipped the Klaviyo step during onboarding, or started fresh, you can still add the key later. Go to Settings then Integrations and click the Klaviyo badge.

Your flows are migrated

Supported Klaviyo flows land in the Flows screen on their own. This can take up to 1 hour. Refresh if they are not there yet. If they are still missing after an hour, reach out to support so we can take a look.

We copy up to 15 active flows automatically. If you have more than that and want the rest, contact support and name the flows you want, and we will migrate them for you.

The Klaviyo import is a one-time job. If a flow was missed, or you've changed your Klaviyo API key, contact support and ask to talk to a person.

For the rest of getting started, see Introduction — How to get started with Spoks.

People, consent, and purchases come from Shopify

Profiles, email and SMS subscription status, orders, and purchase history sync from your Shopify store. You do not need a historic contact export from Klaviyo for that. The first sync of your existing contacts can take a while on a large store. After that, new contacts and events usually appear in Spoks within seconds, so segments and flow filters can use live store data.

What you set up in Spoks

A few things are built in Spoks so they match the current editor, Looks, and Shopify.

  • Templates. Recreate the emails you still send in the Spoks editor. They pick up your Looks, blocks, and Shopify coupons, instead of arriving as a Klaviyo layout built for a different designer.

  • Conditional splits become step filters on the email or SMS steps. A common abandoned-checkout version is Total orders = 0 vs Total orders > 0.

  • Translations. A flow sends in the language it's written in. To reach contacts in several languages, build one flow per language and add a Language filter to each.

  • Inactive Klaviyo flows are skipped in the automatic copy.

  • Short extra delays (for example a 1-minute wait that was not in Klaviyo) can appear on copied flows. Remove them if you do not want that pause.

Coming from Omnisend, Flodesk, or Shopify Email

Skip the Klaviyo step. Then import unsubscribed profiles from your previous tool, unless you came from Shopify Email, in which case the Shopify integration handles consent.

Did this answer your question?