Migrating to Klaviyo: The Step-by-Step Playbook for Switching ESPs Without Losing Revenue

TL;DR: A Klaviyo migration takes 2–4 hours to set up technically and 3–4 weeks to complete correctly. It involves two layers: a technical layer (list export, account setup, store connection, authentication) and a strategic layer (flow rebuild sequencing, deliverability warmup, segment validation, cutover timing). Most brands only do the technical layer — and spend the next two weeks wondering why their email revenue disappeared.

The technical steps are easy: export your Mailchimp list, import it into Klaviyo, connect your Shopify store, rebuild your flows. The problem is that "rebuild your flows" glosses over the part where your welcome series and cart abandonment — the two flows most likely generating real money for you right now — go dark for 7–14 days while you figure out Klaviyo's flow builder.

That gap costs money. We've seen it happen across DTC brands at every revenue level. The brands that migrate cleanly treat it as a 30-day revenue transition project, not a one-afternoon data task. This playbook gives you the exact sequence they follow.

What does a Klaviyo migration actually involve?

Klaviyo is a marketing automation and email platform built specifically for ecommerce, offering event-based segmentation, predictive analytics, and deep integrations with platforms like Shopify. Mailchimp is a general-purpose email marketing platform that uses list-based and tag-based contact management. A Klaviyo migration has two layers: the technical layer (list export, account setup, store connection, authentication) and the strategic layer (flow rebuild sequencing, deliverability warmup, segment validation, cutover timing). The technical layer takes an afternoon. The strategic layer takes 3–4 weeks if you do it right.

Every help doc and how-to guide on the internet covers the technical layer. Export your subscribers from Mailchimp as a CSV. Create a Klaviyo account, connect your Shopify store. Import the list. Rebuild your flows. Done.

What those guides skip is the revenue continuity question: which of your current Mailchimp flows are generating revenue today, and what happens to that revenue while you're rebuilding them in Klaviyo?

The answer, if you don't plan for it, is that the revenue disappears. Your welcome flow is probably your highest-revenue automated sequence. Your cart abandonment is likely generating meaningful daily revenue. Neither fires in Klaviyo until you've rebuilt them — and if you cut over to Klaviyo before they're live, you've created a gap.

This guide treats the migration as what it actually is: a revenue protection project. The technical steps are covered, but the strategic layer is what this playbook is really about.

Before you start: the pre-migration audit

Before touching Klaviyo, spend 30 minutes auditing your current Mailchimp program. You need to know which flows are generating revenue, what your list looks like, and whether it's worth cleaning before you import it. Skipping this audit is how brands import problems into a new platform.

Pull your Mailchimp flow performance report and sort by revenue. Most brands doing results that vary by program+ per year will find that their welcome flow and cart abandonment account for the vast majority of automated revenue. Write down the top three flows by revenue — these are your Tier 1 rebuilds, and they need to be live in Klaviyo before you cut over.

While you're in Mailchimp, look at your list. Specifically, look at your engagement distribution. What percentage of your list hasn't opened an email in 90 or more days? If you have a significant chunk of unengaged contacts, clean your list before migrating. Importing a dirty list into a new sending domain doesn't just waste money on Klaviyo's contact pricing — it accelerates reputation damage during warmup, which is the highest-risk window of the entire migration.

Set up your Klaviyo account with your sending subdomain (typically mail.yourbrand.com or send.yourbrand.com) and complete your authentication setup (SPF, DKIM, DMARC) before you import a single contact. Authentication is not optional — Google and Yahoo require it for bulk senders, and skipping it guarantees deliverability problems during your warmup window.

How should you sequence rebuilding your Klaviyo flows?

Klaviyo Flows are automated email sequences that trigger based on subscriber actions or properties — such as joining a list, abandoning a cart, or making a purchase. Rebuild flows in revenue-priority order, not build complexity order. Your Tier 1 flows — welcome series, cart abandonment, and post-purchase sequence — must be live in Klaviyo before you cut over. Everything else can follow in the first two weeks post-migration. Rebuilding in the wrong order is the single most common cause of revenue gaps during migration.

Here is the framework we use with every DTC migration:

Tier 1: Rebuild before cutover (required)

• Welcome flow: Typically 30–50% of total flow revenue according to Blossom's benchmark data. Every day it's dark costs real money.
• Cart abandonment flow: 5–12% conversion rate according to Blossom's benchmark data, and it fires continuously. A 7-day gap here is measurable in your Shopify revenue report.
• Post-purchase sequence: Drives repeat purchase rate and review velocity. Not rebuilding this before cutover leaves your newest customers in a relationship vacuum.

Tier 2: Rebuild within the first week post-cutover

• Browse abandonment flow: Lower urgency than cart, but high volume. Get it live within days of cutover.
• Winback flow: Lapsed customers aren't going anywhere. A few extra days here doesn't create a measurable gap.
• VIP / loyalty flow: Important for retention, but not a revenue emergency if it's down for a week.

Tier 3: Rebuild within 30 days

• Sunset flow: List hygiene is critical, but it's not urgent on day one.
• Back-in-stock and review request flows: Valuable but not daily revenue drivers.
• Replenishment flow: Unless your replenishment cycle is weekly, you have time.

For each Tier 1 flow, use Klaviyo's flow builder to recreate the logic. Our guide on how to set up your Klaviyo flows covers the mechanics in full. For the migration specifically, your goal with Tier 1 flows is functional parity — don't try to optimize them during the rebuild. Get them live, get them converting, then optimize after the migration is stable.

The welcome flow and cart abandonment together account for the majority of automated email revenue for most DTC brands, based on Blossom's benchmark data across client programs. If these two flows aren't live in Klaviyo before you cut over, you will feel the gap in your weekly revenue report.

Running this migration yourself? We audit retention programs every week — and migration is one of the fastest ways to accidentally crater a program that was working. Get a free lifecycle audit before you cut over: we'll map your current flow revenue and show you exactly what needs to be live in Klaviyo on day one.

Will your open rates drop when you switch to Klaviyo?

Yes — temporarily, if you don't warm up your sending domain. Your Mailchimp sender reputation does not transfer to Klaviyo. Even if you're bringing 50,000 engaged subscribers, your Klaviyo sends start from a new domain with no established reputation. A structured warmup over 2–3 weeks prevents a deliverability drop that looks like an audience problem but is actually an infrastructure problem.

Email deliverability is the measure of how reliably your emails reach the inbox rather than the spam folder. Sender reputation is the score mailbox providers assign to your sending domain and IP based on engagement signals — opens, clicks, spam complaints, and bounce rates. IP warmup is the process of gradually increasing sending volume from a new IP address or domain so that mailbox providers can establish a reputation baseline before you send at full scale. When you switch ESPs, your new Klaviyo sending domain starts with no reputation history, regardless of how strong your Mailchimp reputation was.

The good news: you're not starting from zero in the way a brand-new sender would be. You have a list of real subscribers who genuinely engaged with your emails. The warmup process is about re-establishing that engagement signal on a new domain — not building it from scratch.

Here's the warmup sequence we use for DTC migrations, calibrated by list size:

1. Week 1 — Start with your highest-engagement segment only. Contacts who opened or clicked within the last 30 days. Cap sends at numbers that depend on your setup — numbers that depend on your setup of your total list. Send your best-performing content — your most recent campaigns or your freshest welcome email. You need strong engagement signals on these first sends.
2. Week 2 — Expand to 60-day engagers. Include contacts who opened or clicked within the last 60 days. Increase daily volume by performance that shifts with your audience over your Week 1 ceiling. Continue monitoring bounce rate (keep it below figures that differ across accounts) and spam complaints (keep them below performance that shifts with your audience).
3. Week 3 — Expand to 90-day engagers. You're now sending to the majority of your active list. Ramp volume another outcomes tied to your specific list. If engagement metrics are holding, you're on track for full sends by the end of Week 3.
4. Week 4 and beyond — Full sends. You can now send to your full sendable list. Keep suppressing unengaged contacts (no opens or clicks in 90+ days) from campaigns during this period.

Monitor Google Postmaster Tools throughout. Your domain reputation score will start climbing through the warmup period — you want to see it move from "low" toward "medium" or "high" before you open full sends. For a deeper dive into the full warmup methodology, see our guide on Google Postmaster Tools domain reputation tracking and our internal guide on domain warmup strategy.

One migration-specific note: because you're bringing an existing list rather than building one from scratch, the warmup window is typically shorter than for a brand-new sender. Two to three weeks is realistic for most DTC brands with reasonably healthy lists.

Should you run Mailchimp and Klaviyo simultaneously during migration?

For lists over 10,000 contacts or brands with three or more active revenue-generating flows, yes — running both platforms simultaneously during the transition is worth the added complexity. For smaller lists or simpler programs, a clean cutover with good preparation is simpler and equally safe. The key is preventing double-sends, which requires a clear suppression strategy.

Here's the decision framework:

Run in parallel if:

• List size: 10,000+ contacts (the deliverability risk of a cold start is higher)
• Flow complexity: Three or more active flows generating revenue (more to lose if any go dark)
• Revenue sensitivity: Email is results that vary by program+ of your total revenue (higher stakes for the transition window)

Do a clean cutover if:

• List size: Under 10,000 contacts
• Simple program: One or two flows, occasional campaigns
• Fast rebuild: You can get Tier 1 flows live in Klaviyo within a few days

If you run in parallel, the structure is: Klaviyo handles all new subscribers from day one (they enter your Klaviyo welcome flow immediately). Mailchimp continues running active flows and campaigns for your existing list during the warmup and flow rebuild period. Once your Klaviyo warmup is complete and Tier 1 flows are live and tested, you cut over entirely — stop all Mailchimp sends, move existing subscribers to Klaviyo-only.

Suppression list is a list of contacts excluded from sending — in this context, you use it to prevent any subscriber from receiving the same message from both platforms. The mechanism is straightforward: as contacts move to Klaviyo-only sends, add them to a Mailchimp suppression list so they stop receiving Mailchimp sends. During the overlap window, new subscribers should only be in Klaviyo. Existing subscribers should only be receiving sends from one platform on any given day.

The specific trigger for killing Mailchimp entirely: your Klaviyo domain reputation is "high" in Postmaster Tools, your Tier 1 flows are live and have been running for at least 7 days without issues, and your warmup volume has reached your full sendable list size. When all three conditions are met, stop Mailchimp sends completely.

How do you validate that your Mailchimp segments migrate correctly to Klaviyo?

You can't assume your Mailchimp segments transfer intact — because Mailchimp and Klaviyo use fundamentally different segmentation logic. Mailchimp segments are primarily tag-based and list-based. Klaviyo segments are property-based and event-based. A CSV import moves your contact data, not the behavioral logic behind your segments. Validation is a required step, not an optional one.

Shopify is an ecommerce platform whose native integration with Klaviyo enables automatic syncing of purchase events, customer data, and product activity to subscriber profiles. Custom properties in Klaviyo are profile-level data fields that store information about a contact — purchase history, quiz results, tags imported from Mailchimp, and other attributes. They're the Klaviyo equivalent of Mailchimp tags, but they work differently: Klaviyo can build segments on combinations of properties AND behavioral events (email opens, purchases, site visits), while Mailchimp segments are typically static or tag-based.

The most common segment fidelity failure we see: a brand imports their Mailchimp "engaged subscribers" tag as a Klaviyo custom property, builds a segment on that property, and sends campaigns to it — not realizing that the tag was applied months ago and the segment now includes contacts who have since become completely inactive. In Mailchimp, engagement groups update based on activity. In Klaviyo, an imported tag is static until you rebuild the segment logic on Klaviyo event data.

Here's how to validate your key segments after import:

1. Identify your three most important segments. Typically: engaged subscribers, active buyers, and cart abandoners or browse abandoners.
2. Compare contact counts between Mailchimp and Klaviyo. A large discrepancy usually indicates a tracking or import issue. A small discrepancy (numbers that depend on your setup) is normal due to timing differences.
3. Check Klaviyo profile data for a sample of contacts. Pull 20–30 profiles from your imported list and verify that their property data looks correct — purchase history, tags, custom fields.
4. Rebuild behavioral segments from Klaviyo event data. Don't rely on imported tags for your key segments. Build your "engaged subscribers" segment in Klaviyo using Klaviyo's own data: opened email in last 30 days, clicked email in last 30 days, placed order in last 90 days. These signals come from Klaviyo tracking, not Mailchimp tags.
5. Verify Shopify event history is syncing. Klaviyo's Shopify integration pulls historical purchase data for imported contacts. Check that purchase events are appearing on profiles for contacts you know have ordered before.

The translation you need to know: Mailchimp tags become Klaviyo custom properties on import. Mailchimp engagement groups (active, lapsed, etc.) have no direct equivalent — you need to rebuild these using Klaviyo's engagement event data. For a full walkthrough of how Klaviyo's segmentation system works, see our guide on email segmentation for ecommerce. For additional context on Klaviyo's native segmentation documentation, see Klaviyo's official guide to building segments.

How long does a Klaviyo migration take?

The technical setup — account creation, list import, Shopify connection, authentication — takes 2–4 hours. The strategic migration — warmup, flow rebuild, segment validation, parallel-send management, and cutover — takes 3–4 weeks for a brand with a typical DTC program. Plan for 30 days from start to fully operational.

Here's the realistic timeline breakdown:

• Day 1–2: Account setup, subdomain configuration, authentication records, list export/import, Shopify connection
• Day 3–5: Tier 1 flow rebuild (welcome, cart abandonment, post-purchase) in Klaviyo — aim to have these live before starting warmup sends
• Week 2: Warmup sends begin; Tier 2 flow rebuild (browse abandonment, winback); segment validation
• Week 3: Warmup continues at higher volume; Tier 3 flows; full segment audit complete
• Week 4: Full sends live; parallel-send window closes; Mailchimp cutover; monitoring period begins

In our experience, the fastest clean migrations — typically brands with a simple program, one or two flows, and a small list — can complete in roughly two weeks. The slowest we've seen take closer to three months, usually because the brand started the technical migration without planning the strategic layer and spent weeks troubleshooting deliverability issues that a proper warmup would have prevented.

The two factors that most affect migration timeline: list size (larger lists require longer warmup) and flow complexity (more flows to rebuild means more pre-cutover work). Both are knowable before you start — use your pre-migration audit to set a realistic timeline before you touch a single DNS record.

What do you monitor after the migration is complete?

In the first 30 days post-migration, monitor Google Postmaster Tools daily, your Klaviyo flow performance against pre-migration Mailchimp benchmarks, and your deliverability metrics (bounce rate, spam complaints, unsubscribe rate). The first two weeks after cutover are when most migration problems surface — catching them early prevents long-term reputation damage.

The metrics that matter most in the post-migration window:

• Domain reputation in Postmaster Tools: Should be "medium" or "high" within 2–3 weeks post-cutover. If it's still "low" or "bad" after three weeks of full sends, you have a deliverability problem that needs diagnosis.
• Flow conversion rates vs. pre-migration benchmarks: Your welcome flow and cart abandonment should be converting at rates comparable to what you saw in Mailchimp within the first few weeks. A significant drop (more than performance that shifts with your audience below pre-migration levels) usually indicates a deliverability issue, a flow logic problem, or a segment mismatch.
• Spam complaint rate: Keep this below figures that differ across accounts. Above outcomes tied to your specific list is a deliverability emergency. If complaints spike after migration, it's often because imported contacts don't remember subscribing — a strong welcome email re-establishing the relationship helps here.
• Bounce rate per send: Should be under results that vary by program. High bounces after migration usually mean the imported list contained invalid addresses that Mailchimp was suppressing automatically.

After 30 days, your migration is effectively complete and you're in normal operations. At that point, shift your monitoring to standard retention KPIs: flow revenue as a percentage of total email revenue, inbox placement after migration, and engagement rate trends across your key segments. For a full framework on what to track weekly, see our guide on email marketing KPIs for ecommerce.

Key takeaways

• The technical migration takes an afternoon. The strategic migration — warmup, flow rebuild sequencing, segment validation — takes 3–4 weeks done correctly.
• Rebuild flows in revenue-priority order: welcome, cart abandonment, and post-purchase must be live in Klaviyo before you cut over.
• Your Mailchimp sender reputation doesn't transfer. Start warmup with your highest-engagement segment and ramp over 2–3 weeks.
• For lists over 10,000 contacts, running both platforms simultaneously during the transition protects revenue and reduces deliverability risk.
• Mailchimp tags and Klaviyo properties are not equivalent. Rebuild key segments from Klaviyo behavioral event data — don't rely on imported static tags.

Want us to run this migration for your brand? Book a free strategy call — we'll map your current flow revenue, identify your highest-risk gaps, and give you a 30-day migration plan you can run yourself or hand off to us.

FAQ: Migrating to Klaviyo from Mailchimp

How do I migrate from Mailchimp to Klaviyo without losing data?

Export your Mailchimp list as a CSV (including merge fields and tags), then import it into Klaviyo via the List Import feature. Connect your Shopify store during account setup — Klaviyo will pull historical purchase data for imported contacts automatically. The data itself transfers cleanly; what doesn't transfer is the behavioral logic behind your Mailchimp segments, which you'll need to rebuild using Klaviyo's event-based segmentation tools.

Will my open rates drop when I switch to Klaviyo?

They may drop temporarily if you skip the domain warmup. Your Klaviyo sending domain starts with no reputation history regardless of your Mailchimp standing. A 2–3 week warmup — starting with your most engaged contacts and ramping volume gradually — prevents the deliverability dip that looks like an audience problem but is actually an infrastructure problem. In our experience working with DTC brands through this process, open rates tend to stabilize at or above pre-migration levels within 3–4 weeks when the warmup is executed correctly.

Do I need to rebuild my automations from scratch in Klaviyo?

Yes — Klaviyo's flow builder is a different system from Mailchimp's automation builder, so there's no direct import of automation logic. The good news is Klaviyo's flows are significantly more powerful, with conditional splits, predictive analytics, and Shopify event triggers that Mailchimp doesn't match. Prioritize rebuilding your highest-revenue flows (welcome, cart abandonment, post-purchase) before you cut over to Klaviyo, and rebuild the rest in the first week post-migration.

Can I run Mailchimp and Klaviyo at the same time during migration?

Yes, and for lists over 10,000 contacts we recommend it. Use Klaviyo for all new subscribers from day one, and keep Mailchimp running for existing subscribers during the warmup and flow rebuild period. Use suppression lists to prevent any contact from receiving sends from both platforms on the same day. Once your Klaviyo warmup is complete and Tier 1 flows are live, cut over entirely and stop Mailchimp sends.

How do I warm up my sending domain after migrating to Klaviyo?

Start by sending only to your most engaged contacts — those who opened or clicked in the last 30 days. In Week 2, expand to 60-day engagers. In Week 3, expand to 90-day engagers. Monitor Google Postmaster Tools throughout; you want your domain reputation score moving toward "medium" or "high" before you open full sends. The full warmup methodology is covered in our domain warmup strategy guide.

Get tactics like this in your inbox every week. Subscribe to our newsletter →