email·digit
Integration · ESP migration · Manual during beta

Klaviyo

Profiles, flows, segments, and metric-driven automation — ported.

One-way · into Email Digit

What moves between
Klaviyo and Email Digit.

Profiles
All profiles with custom properties, consent state, and subscription preferences.
Lists + segments
Static lists and segment definitions (filter logic preserved).
Flows
Welcome, abandon-cart, browse-abandon, post-purchase, win-back — translated to Email Digit automations.
Engagement history
Last 12 months of email events per profile (sent / opened / clicked / unsubscribed).
Setup

Three steps.
Most teams done in an hour.

01

Grab a Klaviyo Private API key

Account → Settings → API Keys → Create Private API key. Read-only scope works.

02

Share with us during migration

1-hour screen-share. We pull the profiles, run a diff, you approve.

03

Switch your double opt-in flow

If you use Klaviyo's double opt-in, we re-link it to our SES + WhatsApp confirmation flow.

What we won't pretend

Honest caveats.

Every migration has edges. Here are ours — better to know up-front than to discover post-cutover.

·Klaviyo's predictive analytics scores (CLV, churn probability) don't carry over — we don't compute them yet.
·Custom Klaviyo BI integrations need to be re-pointed at our REST API.
·Server-side events (track / identify) that fed Klaviyo need to be re-pointed at Email Digit's webhook ingest.
Integration · Klaviyo

Move from Klaviyo
in an afternoon.

Request access. We hand-help every migration during private beta — typically 1 hour on a screen-share, 0 surprises.