What doesn't transfer from Klaviyo to Omnisend?

The migration gap map

Omnisend's migration guide separates contact import from the work of rebuilding flows, forms and templates. Treat the import status as a starting signal, then inspect each area below in a test account or controlled pilot.

1. Reconcile consent, not just profile totals

Omnisend's Klaviyo import documentation maps subscribed, never-subscribed and unsubscribed profiles to different states. Consent details only transfer as a record when Klaviyo contains the required timestamp and supporting source, method or form information; SMS consent needs its own timestamp. A completed import therefore does not prove that every subscriber has a usable audit trail.

Before the first send, compare counts by email and SMS status, sample consent records with their source, and check suppression separately. Klaviyo explains that consent and suppression are distinct: a subscribed profile can still be suppressed. Keep a do-not-send list for cases that need manual review.

2. Rebuild segment rules that do not translate

The Omnisend import tool attempts to move segments whose conditions it supports. Unsupported conditions can fail, and membership is recalculated against the data in Omnisend. Export each important segment's rule and current count, then compare the resulting membership—not only the segment name. Pay particular attention to predictive or Klaviyo-specific conditions, custom properties and segments that control offers or flow entry.

3. Test flows with real events and inboxes

Omnisend says Klaviyo workflows cannot be transferred directly. Inventory each live flow's entry event, filters, delay, split, exit rule and email content before rebuilding it. Test a welcome signup, an abandoned cart and a post-purchase journey with controlled test identities where those flows exist. Verify the right person enters, waits the intended interval, receives the message, and exits or suppresses correctly.

Omnisend's Trigger Preview Tool can help check whether recent events satisfy trigger conditions. It is in beta and its green check is not proof that a message arrived. Confirm delivery in a test inbox and inspect the actual message and links.

4. Recheck every template and signup path

HTML templates can be imported, but Omnisend's template guidance calls for replacing old personalization and unsubscribe elements, then checking the rendered email. Recreate signup forms or confirm whether Omnisend's Kickstart support will help. Test both the visible form and the resulting contact status before collecting new subscribers through it.

5. Archive the history you need

Omnisend says reports and past campaign statistics do not transfer. Save the campaign and flow evidence needed for financial review, benchmarking or future decisions while Klaviyo access remains available. Klaviyo provides a campaign analytics CSV export; check which other historical records your team depends on.

The cutover checklist

1. Record baseline counts for subscribed, non-subscribed and suppressed contacts by channel.
2. Import, compare status counts and inspect a sample of consent evidence.
3. Rebuild critical segments and compare both rules and membership.
4. Recreate essential automations and forms; run test journeys through to the inbox.
5. Authenticate the sending domain and run a controlled first send to eligible contacts.
6. Export historical reports, document unresolved gaps, then decide when Klaviyo can be switched off.

The import sync is manual rather than real-time. If both platforms run in parallel, repeat the sync and reconciliation before cutover. Omnisend itself recommends keeping Klaviyo active until migration work has been checked. For domain authentication and list preparation, use our safe switching guide.

Where independent help could add value

Omnisend's Kickstart program offers free migration support for qualifying stores with more than 250 contacts. Check its current eligibility and scope first. An independent assessment is useful only if it gives you a clearer inventory, proof of what worked, and a list of unresolved risks beyond the vendor's setup help.

Sources checked 2026-09-28: Omnisend migration overview, import details, trigger preview, template import, Klaviyo suppression and analytics export. Product behavior and eligibility can change; confirm in your accounts before acting.