mailexodus
home/migrations/to Kit
// migrate to

move to Kit without rebuilding by hand.

mailexodus normalizes your current platform into one portable schema, then checks what Kit can actually import. You get a route report before your agent writes anything.

agentUse mailexodus skill: your source → Kit playbook
// try it

bring your data into Kit.

Pick the platform you're leaving and generate a route playbook. The report shows what maps cleanly into Kit's model and what needs review — before you approve writes.

analyzing Klaviyo…
source modeAutomated adapter
source exports8
Kit imports5
destination gapslists, segments, suppressions, templates
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to kit --dry-run
agentUse mailexodus skill: Klaviyo → Kit playbook
running…open the Klaviyo migration guide →
// fit

when Kit is the right move.

Kit is a strong fit for teams that want kit teams with subscriber data, campaigns, and automation branches that need a migration report before rebuild. The migration risk is rarely the CSV — it is the automation graph: triggers, delays, branches, template references, and consent state. mailexodus puts a portable schema in the middle so those objects are inspected before they become Kit objects.

// inbound

what Kit receives.

can import
  • +
    subscribers
  • +
    tags
  • +
    custom fields
  • +
    campaigns
  • +
    automations
needs review
  • ?
    automations
not exposed for import
  • x
    lists
  • x
    segments
  • x
    suppressions
  • x
    templates
destination adapter

Automated adapter

Subscribers map to subscribers. Forms and landing pages can become lists when used as acquisition buckets. Tags and fields map directly. Broadcasts and sequence emails map to content items

Kit can receive subscribers, tags, custom fields, broadcasts, and sequences. Forms are readable as acquisition buckets but are not treated as a clean list-create destination surface. Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to Kit.

  1. Authenticate your sending domain in Kit (SPF, DKIM, DMARC) and plan a warmup window — sender reputation is earned here, it does not transfer.
  2. Bring consent and suppression state across first, so unsubscribes and bounces are honored from the first send in Kit.
  3. QA migrated templates and segments inside Kit, and send seed tests before any live campaign.
  4. Keep your current platform active until in-flight automations finish and Kit is warmed and trusted.
// migrate it

start with the route playbook.

The agent prompt returns a route report with source exports, destination imports, skipped objects, and manual-review tasks. When it looks right, wire credentials and approve writes from a controlled machine.

inspect

destination coverage

npx mailexodus@latest info kit

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=kit

agentUse mailexodus skill: your source → Kit playbook
compare Kit alternatives →browse every migration page →