> ## Documentation Index
> Fetch the complete documentation index at: https://openemail-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Move from Klaviyo

> Bring your Klaviyo consent, do-not-email list, lists and designs into OpenEmail, then switch Klaviyo off.

From Klaviyo to your own copy:

* **Outcome:** everyone who unsubscribed, bounced or complained in Klaviyo blocked here, your subscribers in as contacts, your lists and designs carried over, and Klaviyo switched off for email.
* **Before you start:** the first pull of your Shopify customers has finished. Your agent can't start a migration before it does.
* **You'll touch:**
  * Klaviyo: one read-only API key, then the cutover (setting flows and forms to draft)
  * The OpenEmail app: **Settings > Klaviyo**, and one approval page

> [!WARNING]
>
> **Nothing sends until Klaviyo is settled.** From install, OpenEmail holds every email until an approved migration has brought over your Klaviyo do-not-email list, or a staff member confirms there's no Klaviyo account to bring over. Shopify can show someone as subscribed who complained or hard-bounced in Klaviyo, and this hold keeps them safe. Your agent's status names it, and once your sending domain passes its first check the store owner gets one email about it. Once lifted, it never comes back.

## What moves, and what doesn't

OpenEmail only reads Klaviyo. It never changes anything in your Klaviyo account.

| From Klaviyo | In OpenEmail |
| - | - |
| Unsubscribes, bounces, complaints and Klaviyo's own hand-added suppressions | The do-not-email list, first, with Klaviyo's dates. A suppression on one list counts as unsubscribed from everything. |
| The same people, if they're Shopify customers | Marked unsubscribed in Shopify, with the date they unsubscribed in Klaviyo. |
| Subscribed profiles | Contacts, with their consent date, how they subscribed and their names. If they declined open or click tracking in Klaviyo, tracking is declined here. |
| Profiles never subscribed | Don't come over. |
| Profiles with SMS consent | Kept in the Klaviyo copy. OpenEmail doesn't send SMS. |
| Lists | Lists under their Klaviyo names. |
| Segments | Fixed lists of their members at the time of the read, named after the segment with "from Klaviyo" and the date. They don't update afterwards. |
| Templates, flow emails and campaign emails | Kept as Klaviyo designs. Your agent can study them, or turn one into an OpenEmail email with Klaviyo's tags converted. |
| Every profile, whole | The Klaviyo copy, kept as Klaviyo returned it for as long as your copy runs. |
| Flows | Not rebuilt. They're read so the approval page can show which flows each list triggers, and so the cutover checklist can list what's still live. Your agent [builds your flow](https://openemail-docs.mintlify.site/use/flows.md) in OpenEmail. |
| Scheduled campaigns and signup forms | Stay in Klaviyo, listed on the cutover checklist for you to switch off. |
| Engagement history | No last-engaged date comes over. OpenEmail works it out from your Shopify orders and its own events. |

Expect fewer contacts than Klaviyo has profiles. The approval page counts every profile left out, and why.

> [!NOTE]
>
> **Double opt-in.** OpenEmail has no double opt-in step. The approval page lists your Klaviyo lists that use it, so you know which ones had a confirmation email.

## Run the migration

**1. Connect Klaviyo**

* In Klaviyo, go to your account's settings, then **API keys**, and create a private API key with read-only access.
* In the OpenEmail app, open **Settings > Klaviyo** and paste it into **Klaviyo private API key**.
* Choose **Check account**. OpenEmail asks Klaviyo whose key it is and shows the organization, website and account ID. Nothing is saved yet.
* Make sure it's your store's Klaviyo account. A key from another store's account would bring over that store's contacts.
* Choose **Connect account**. The key is stored encrypted. No agent can see it, and no agent tool can connect or disconnect Klaviyo.

> [!TIP]
>
> **Checkpoint:** **Settings > Klaviyo** shows **Connected** and your Klaviyo account. Connecting alone doesn't lift the hold or bring anything over.

**2. Ask your agent to read your account**

* Ask your agent: "Bring my Klaviyo data over to OpenEmail." It starts a migration run with `prepare_klaviyo_migration`.
* The run reads first: every profile, every list with its members, the chosen segments' members, the flows, the designs and the account. The read needs no approval and changes nothing else.
* By default it reads Klaviyo's **Engaged (30 Days)**, **Engaged (60 Days)** and **Engaged (90 Days)** segments, where you have them. Tell your agent if you want other segments, or none.
* A large account takes a while to read. Your agent follows it with `get_klaviyo_migration`, and **Migration run** on **Settings > Klaviyo** shows each phase with its progress.
* One run is open at a time. Starting a new one ends any run that hasn't been applied.

> [!TIP]
>
> **Checkpoint:** the run reads **Read**, and your agent can show you its preview.

**3. Review and approve**

* Your agent asks for your approval and gives you the link. One approval covers the whole run.
* The page, **Bring over your Klaviyo account**, shows the Klaviyo account and when it was read, then what the read found: addresses going on the do-not-email list by reason, Shopify customers to be marked unsubscribed, contacts arriving subscribed, existing contacts whose consent moves, profiles left out by reason, your lists, the lists on double opt-in, the Klaviyo flows each list triggers, the segments saved as lists, and the designs.
* The approval is bound to **Contacts made subscribed**: the run can't make more contacts subscribed than the page shows.
* Check the account name and website one more time, then choose **Approve**.
* A read more than 7 days old can't be approved. Ask your agent for a new one.

> [!TIP]
>
> **Checkpoint:** the run moves to **Applying**.

**4. Let it apply**

* The run applies only what the read found, in this order:
  1. Anyone who unsubscribed, complained or bounced in Klaviyo since the read began.
  2. The do-not-email list. The Klaviyo hold lifts once this is in.
  3. The Shopify customers on that list, marked unsubscribed in Shopify.
  4. Contacts and their consent. Anyone who unsubscribed here more recently stays unsubscribed.
  5. Lists, and segments as lists.
  6. The Klaviyo copy, designs included.
* If the run would make more contacts subscribed than you approved, it stops and needs a fresh approval.

> [!TIP]
>
> **Checkpoint:** the run reads **Applied**, and the Klaviyo hold is gone from your agent's status.

**5. Switch Klaviyo off**

* The **Cutover checklist** on **Settings > Klaviyo** lists what's still on in Klaviyo: **Live flows** (with any abandoned-checkout flow marked), **Scheduled campaigns** and **Live forms**. Your agent sees the same list.
* In Klaviyo, set flows and forms to draft rather than deleting them, and cancel scheduled campaigns.
* The checklist reads Klaviyo again every 15 minutes, so an item drops off soon after you switch it off.

> [!TIP]
>
> **Checkpoint:** the cutover checklist is empty.

> [!WARNING]
>
> **Two abandoned-checkout emails.** While Klaviyo's abandoned-checkout flow and yours are both live, a shopper gets two emails for one checkout. Your flow's approval page names any Klaviyo abandoned-checkout flow still live.

![Settings > Klaviyo: the connected Klaviyo account and the Klaviyo hold, lifted.](https://mintcdn.com/openemail-docs/OnJRIGCNyk9zxe6d/images/use/klaviyo-settings.png?fit=max\&auto=format\&n=OnJRIGCNyk9zxe6d\&q=85\&s=0217484c1e229c87e6d80e0e58d64896)

**6. Keep Klaviyo connected for 30 days, then disconnect**

* Emails Klaviyo already sent carry Klaviyo's unsubscribe links, and the law expects them to keep working for 30 days. Keep Klaviyo open and connected for 30 days after the last email it sends.
* While it's connected, OpenEmail reads Klaviyo once a day for new unsubscribes, spam complaints and hard bounces and puts them on your do-not-email list. Unsubscribes and complaints are also written to the matching Shopify customer. This needs no approval, because it only means less email, and it never adds a subscriber.
* Then choose **Disconnect Klaviyo**. It deletes the saved key, so the checklist and the daily read stop. Everything already brought over stays. You can't disconnect while a run is reading or applying.

> [!TIP]
>
> **Checkpoint:** **Settings > Klaviyo** shows **Not connected**.

## Cancel or run it again

Your agent can cancel a run with `cancel_klaviyo_migration`, and needs no approval to do it:

* **While it reads:** the run ends and what it read is deleted.
* **While it applies:** it stops at its next chunk and keeps what it already brought over. Nothing is rolled back.
* **Once applied:** it can't be cancelled.

A rerun is a new run, with its own read and its own approval. It adds nothing twice, keeps a list you deleted here deleted, keeps a list's name if you renamed it here, and never re-subscribes someone who unsubscribed here since. After you disconnect Klaviyo, a rerun reads from the Klaviyo copy instead, without lists or segment members.

A read that's never applied is deleted: when it's cancelled or declined, when a newer run replaces it, or when it sits 7 days with no open request.

## No Klaviyo account to bring over

If your store never used Klaviyo, open **Settings > Klaviyo** and choose **Confirm no Klaviyo account**. This is an approval: it's checked with Shopify, recorded with your name and listed on **Approvals**. Your agent can neither ask for it nor give it. The Klaviyo hold lifts, and email can go out once nothing else holds it. If Klaviyo is connected, disconnect it first.

Next, [build your abandoned checkout flow](https://openemail-docs.mintlify.site/use/flows.md), or see [why a send is held](https://openemail-docs.mintlify.site/help/a-send-is-held.md) if email still isn't going out.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.