How to export your contacts from Klaviyo

Klaviyo's data model is one of its strengths, and most of what matters for a move — profiles, properties, and consent — comes out cleanly. Here's the shape of it.

What exports from Klaviyo

Lists and segments export to CSV, each including the profile properties you select. As of August 2026 the export sits in the list/segment view; Klaviyo's help center has the current steps. What to get right:

1. Export consent per channel. Email consent and SMS consent are separate fields on a Klaviyo profile — make sure both come out. On import elsewhere, each channel's opt-in should be recorded separately too (that's how we handle it).
2. Property-based segments travel; behavior-based ones rebuild. A segment defined by profile properties re-creates as rules on the other side in minutes. Segments built on store events — browsed, carted, purchased — depend on data only Klaviyo has, and that's the honest limit of any migration.
3. Export segments you'd hate to rebuild even if you're not sure you'll use them. A CSV per key segment costs a minute now.

What doesn't carry over

Flows don't transfer — no automation does, anywhere. Welcome, reminder, and win-back flows rebuild quickly on any platform; deep order-triggered flows are Klaviyo's home-turf advantage, and if they drive your revenue, that's a reason to stay, not a migration problem to solve.

Importing your list into AutoCampaign.ai

Wherever you land, the import side is the easy half here: upload the CSV or Excel file, map your columns once, and tags and custom fields become attributes you can segment on immediately. Opt-in status is recorded on every imported contact, STOP requests are honored automatically from the first send, and your first campaign shows its estimated cost before you press send.

If you're still deciding where to go, our Klaviyo comparison is the honest version — including the cases where staying put is the right call. The pricing grid is public, so you can do the math before you create an account.