Migrating from Klaviyo to Turtini Email Campaigns

Moving your email program off Klaviyo and into Turtini Email Campaigns takes about an hour for a typical SMB list and gives you DKIM-aligned sending on your own domain (no shared IP) plus Wally-assisted composition.

What we import:
• Subscribers — mapped to Turtini Contacts. Tags carry over as Contact tags. Email + name + phone + custom properties up to 25 fields.
• Lists — mapped to Turtini Distribution Lists. Subscriber-to-list memberships preserved.
• Segments — mapped to Turtini Email Segments. Klaviyo's segment definitions translate where Turtini has equivalent operators (most do — "opened email in last 30 days", "tagged X", "purchased in 90 days", etc.).
• Suppression / unsubscribes — full unsubscribe and bounce list, preserved with original opt-out timestamps. CAN-SPAM / GDPR compliance carries forward.
• Templates — Klaviyo's HTML templates import as Turtini email templates. Your branded layouts come over visually intact.
• Flows — mapped to Turtini Customer Journeys (welcome series, abandoned cart, post-purchase, etc.). Trigger logic translates where supported.
• Send history — last 90 days of campaign metadata (subject, send date, recipient count, opens, clicks). Older history stays in Klaviyo for reference.

What we don't import:
• Klaviyo's deep e-commerce events (Shopify/BigCommerce/etc. webhook data) — connect your storefront to Turtini directly via the Email Campaigns → Triggers tab to rebuild equivalent automations.
• Predictive analytics scores — Turtini doesn't have an exact equivalent.
• Drafts — only sent campaigns and active flows import.

Step by step:
1. Klaviyo → Account → Settings → Export Data → request a full account export. Klaviyo emails a .zip when ready (usually 30-60 minutes).
2. In Turtini, /setup/migrate → find Klaviyo → click "Connect & import".
3. Upload the .zip.
4. Pick "How much history" — last 90 days (default) or up to 2 years.
5. Pick "Send-domain mode" — if you already had Klaviyo sending from a custom domain, we walk you through verifying the same domain in Turtini (DKIM + SPF records). If you sent from Klaviyo's shared domain, you'll set up a custom sending domain after import.
6. Click "Run import". Progress shows in /setup/migrate/imports.

After the import:
• Email Campaigns → Subscribers — verify counts. Total should match your Klaviyo list size at export time, minus any duplicates we collapsed.
• Email Campaigns → Sending Domain — finish DKIM verification if you brought your own domain. The Cloudflare integration (if connected) auto-provisions DNS records; otherwise the Sending Domain panel shows the records to add manually.
• Email Campaigns → Journeys — open each imported flow and verify the trigger and steps look right. Flows import in "paused" mode by default — you turn each on once you've reviewed it.
• Send a test campaign to yourself before turning the firehose back on.

Cutover plan:
Don't cut over the same day as the import. Plan a week:
• Day 1: import.
• Day 2-3: verify subscribers, segments, journeys. Send test campaigns. Fix any template issues.
• Day 4: turn on Turtini and pause Klaviyo flows (don't delete — leave them paused as a fallback).
• Day 7: confirm Turtini is sending healthily (look at Email Campaigns → Analytics for delivery / open / click rates). Cancel Klaviyo at the next renewal.

Common issues:
• "Unsubscribe list incomplete" — verify Klaviyo export included the suppression list. If not, request a separate "Suppression Export" from Klaviyo support and upload it from Email Campaigns → Subscribers → Import → Suppressions.
• "Open rates dropped after migration" — this is normal for the first ~7 days as ISPs adjust to new sending IPs. Stays low if your DKIM is misconfigured — verify in Sending Domain.
• "Some segments don't translate" — Klaviyo segments using their predictive analytics or e-commerce-specific events skip on import. Rebuild them as Turtini Segments using the events we DO have.

Cost comparison reminder:
Turtini Email Campaigns charges Resend's actual sending cost + 15% — you see exact line-item cost-of-send per campaign. Klaviyo's per-recipient pricing typically lands at 4-10x the variable cost; for most SMBs the savings cover several other Turtini modules.