mailexodus
home/migrations/from Kit
// migrate from

leave Kit. keep the work.

mailexodus reads Kit over its API and normalizes subscribers, lists, tags, custom fields into one portable schema — so you move with a report, not a 40-item checklist.

agentUse mailexodus skill: Kit → Sequenzy playbook
// try it

see what moves out of Kit.

A live route check, computed from Kit's real API surface. Pick any destination to compare import support — nothing is written.

analyzing Kit…
source modeAutomated adapter
source exports6
Mailchimp imports8
destination gapsautomations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from kit --to mailchimp --dry-run
agentUse mailexodus skill: Kit → Mailchimp playbook
running…open the Kit migration guide →
// why teams leave

why teams leave Kit.

  • →
    Kit migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, tags, custom fields.
  • →
    List semantics are reconstructed from forms, tags, and exports
// transfer boundary

what mailexodus pulls from Kit.

can migrate
  • +
    subscribers
  • +
    lists
  • +
    tags
  • +
    custom fields
  • +
    campaigns
  • +
    automations
needs review
  • ?
    List semantics are reconstructed from forms, tags, and exports
cannot migrate
  • x
    segments
  • x
    suppressions
  • x
    templates
  • x
    sender reputation and domain warmup
  • x
    historical analytics, revenue attribution, and aggregate reporting
  • x
    contacts already mid-flight inside active automations
  • x
    A/B test results and provider-specific experiment history
  • x
    provider-native design blocks, product widgets, coupons, and private assets that are not exposed by API
source 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

List semantics are reconstructed from forms, tags, and exports

// the playbook

how an agent migrates Kit → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Kit, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.

01 · authenticate

In Kit, open Settings, Developer, API Keys, then copy your API key. Paste the API key here; do not use the API secret

01subscribersmigrates
readGET /v4/subscribers (Read subscribers from Kit.)
mapSubscribers 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 mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST add_subscriber (Write or stage subscribers in Sequenzy.) PATCH update_subscriber (Write or stage subscribers in Sequenzy.)
02listsmigrates
readGET /v4/forms (Read lists from Kit.)
mapSubscribers 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 mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_list (Write or stage lists in Sequenzy.) POST add_subscribers_to_list (Write or stage lists in Sequenzy.)
03tagsmigrates
readGET /v4/tags (Read tags from Kit.)
mapSubscribers 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 mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_tag (Write or stage tags in Sequenzy.)
04custom fieldsmigrates
readGET /v4/custom_fields (Read custom fields from Kit.)
mapSubscribers 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 mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePATCH update_subscriber.customAttributes (Write or stage custom fields in Sequenzy.)
05campaignsmigrates
readGET /v4/broadcasts (Read campaigns from Kit.)
mapSubscribers 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 mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
06automationsmigrates
readGET /v4/sequences (Read automations from Kit.)
mapSubscribers 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 mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_sequence (Write or stage automations in Sequenzy.) POST insert_sequence_step (Write or stage automations in Sequenzy.)
stays behind
  • segments
  • suppressions
  • templates
  • sender reputation and domain warmup
  • historical analytics, revenue attribution, and aggregate reporting
  • contacts already mid-flight inside active automations
guardrails
  • Sender reputation is earned at the destination — set up SPF/DKIM/DMARC and a warmup ramp; it does not transfer.
  • Keep the source platform active until authentication, warmup, and in-flight automations have finished.
  • Honor suppressions before the first send.
  • After writing, verify counts per object type against the source before switching live sends.
// run it

guide your agent, or follow it yourself.

Pull the full playbook from the skill prompt, CLI, or MCP server, then work the steps. Start by confirming credentials: In Kit, open Settings, Developer, API Keys, then copy your API key. Paste the API key here; do not use the API secret

inspect

provider coverage

npx mailexodus@latest info kit

guide

agent playbook

npx mailexodus@latest guide --from kit --to sequenzy

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