Migration guide

Keep the store flows. Drop the per-profile bill.

Profiles, properties and store data export from Klaviyo, and Bluey's Shopify integration replaces the event feed the flows depend on. The rebuild is the flows themselves — and the store connection is what makes them possible.

On Klaviyo~$400/mo
On Bluey$36/mo

25,000 profiles, 100,000 emails/month · Typical migration: 3–5 days of work, over 1–2 weeks

In short

Migrating from Klaviyo to Bluey means moving two things: the profile data, which exports as CSV, and the store event feed, which is replaced by connecting Shopify or WooCommerce directly to Bluey. Once the store is connected, cart, browse and purchase events flow in and the pre-built cart, post-purchase and win-back flows can be turned on. Flows themselves are rebuilt, not imported. Budget three to five days of work across a week or two. At 25,000 profiles sending 100,000 emails a month, Klaviyo's email plan is around $400 against $36 on Bluey Grow — the difference being that Klaviyo bills per profile stored and Bluey bills per email sent.

What transfers, and what you rebuild

Stated up front, because finding out mid-migration is how a two-day job becomes a two-week one.

WhatStatusDetail
Profiles & propertiesTransfersExport profiles with custom properties as CSV; properties map to Bluey custom fields.
Lists & segmentsPartialList membership exports. Segment definitions are rebuilt, but on the same underlying data.
Suppressions & unsubscribesTransfersExport the suppression list separately and import it first.
Store events (cart, browse, purchase)RebuildNot exported — replaced by connecting Shopify or WooCommerce directly to Bluey. Historical events do not backfill.
FlowsRebuildRebuilt in Bluey. Cart, browse, post-purchase and win-back are templated.
Email templatesPartialExport HTML and import. Klaviyo's dynamic product blocks need rebuilding with Bluey's equivalents.
Signup forms & popupsRebuildRebuild in Bluey and swap the embed on your store theme.
Historical revenue attributionRebuildStays in Klaviyo. Export the reports you need before closing the account.

The migration plan, in order

  1. 1Day 1 — before any send
    Authenticate your sending domainPublish SPF, DKIM and, if you use one, DMARC records for the domain you will send from. Gmail and Yahoo have required authentication and one-click unsubscribe from bulk senders since February 2024, and an unauthenticated first send from a new platform is the fastest route to the spam folder. This is a DNS change and takes about fifteen minutes; allow up to a few hours for propagation.
  2. 2Day 1
    Connect your store to Bluey before anything elseThe Shopify or WooCommerce integration is what makes the flows possible, and it takes ten to fifteen minutes. Connect it first so events are already arriving by the time you start building — you cannot test an abandoned-cart flow without cart events.
  3. 3Day 1
    Export profiles and suppressions from KlaviyoExport profiles with their custom properties, and export the suppression list separately. Import suppressions into Bluey before profiles, so opted-out contacts arrive already suppressed.
  4. 4Day 2
    Rebuild the flows that earnFor most stores that is abandoned cart, post-purchase and win-back, in that order. Bluey templates all three. Look at Klaviyo's own attribution before you rebuild — it will tell you which flows to prioritise and which to quietly drop.
  5. 5Day 2–3
    Rebuild segments and formsSegment definitions are rebuilt rather than imported, but the underlying properties came across, so the logic translates. Rebuild signup forms and popups in Bluey and update your store theme.
  6. 6Week 1–2
    Run Bluey and Klaviyo in parallelSplit the audience rather than duplicating it: send to one segment from Bluey and leave the rest on Klaviyo. You get a like-for-like comparison of delivery, engagement and cost on your own data, and nobody receives the same campaign twice. Do not run both against the same contacts — that is the one way to make a careful migration look sloppy to your readers.
  7. 7Week 2 — gradually
    Ramp volume rather than switching itStart with your most engaged segment — people who opened or clicked in the last 30 days — and increase volume over several days. Receiving servers judge a new sending pattern partly on engagement, so leading with your best contacts builds reputation, while leading with your whole list including two-year-dormant addresses damages it. If you were on a dedicated IP, treat the new one as cold and warm it deliberately.
  8. 8Week 3
    Compare attribution before you cancelYou now have per-step revenue attribution on both platforms for the same period. Compare them on the segment you moved, confirm the flows are performing, then close the Klaviyo account.

Mistakes people make leaving Klaviyo

Each of these is recoverable, and each is much cheaper to avoid than to fix.

Leaving the suppression list behindExporting subscribers without also exporting unsubscribes, bounces and complaints is the single most common migration error. The result is that people who opted out of Klaviyo receive your first Bluey campaign — which is a compliance breach in most markets and a fast way to breach Gmail's 0.3% complaint threshold on your very first send. Export suppressions and import them before anything else.
Expecting historical store events to come with youProfile data exports; the event stream does not. Once Bluey is connected to your store, events flow from that moment forward. Flows that depend on 'viewed this product in the last 30 days' will need those thirty days to accumulate, so connect the store early rather than on cutover day.
Rebuilding every flow instead of the ones that earnKlaviyo accounts accumulate flows. Before rebuilding, sort them by attributed revenue — most stores find three or four are producing almost everything, and the rest are sending email for no measurable return. A migration is a good moment to stop sending those.
Importing the whole list, including the dead partA migration is the best opportunity you will get to drop contacts who have not engaged in a year or more. Bringing them across because storage is free is a mistake: they do not open, some addresses have gone stale and now hard-bounce, and a few have become spam traps. They will not cost you money on send-based billing, but they will cost you deliverability on the send that matters most — your first.

Migration FAQ

Will I lose my abandoned cart flow?

You will rebuild it, and Bluey ships a template for it. What you need in place first is the store connection, because the flow triggers on checkout-started events coming from Shopify or WooCommerce. Connect the store, confirm events are arriving, then build.

Do my Klaviyo store events transfer?

No. Profile data exports as CSV, but the historical event stream does not move between platforms. Bluey starts collecting cart, browse and purchase events the moment your store is connected, which is why connecting it on day one rather than at cutover matters.

How much cheaper is Bluey than Klaviyo?

At 25,000 profiles sending 100,000 emails a month, around $400 on Klaviyo's email plan against $36 on Bluey Grow. The reason is structural: Klaviyo charges for profiles stored, so every trial signup and lapsed customer is billable, while Bluey charges for emails sent.

What do I actually give up?

Klaviyo's predictive analytics, its SMS channel, and the depth of its store-native integrations. If SMS is part of your recovery strategy or you rely on predicted lifetime value in your segments, those are real losses and worth weighing honestly before you move.

Can I run both during the switch?

Yes, and you should. Split the audience — Bluey flows on one segment, Klaviyo on the rest — so you get a genuine comparison of recovered revenue without anyone receiving both. Do not run both against the same customers.

Free · 7 days

Run both in parallel. Then decide.

Seven days of full access, no credit card. Import a segment, send from Bluey while Klaviyo handles the rest, and compare delivery and cost on your own data before you move the domain.