mailexodus
home/migrations/from Omnisend
// migrate from

leave Omnisend. keep the work.

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

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

see what moves out of Omnisend.

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

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

why teams leave Omnisend.

  • →
    Omnisend migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, tags, custom fields, segments.
  • →
    Automation import is not part of current native coverage
// transfer boundary

what mailexodus pulls from Omnisend.

can migrate
  • +
    subscribers
  • +
    tags
  • +
    segments
  • +
    custom fields
  • +
    campaigns
  • +
    templates
needs review
  • ?
    Automation import is not part of current native coverage
cannot migrate
  • x
    lists
  • x
    suppressions
  • x
    automations
  • 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

Contacts map to subscribers. Tags and custom properties map directly. Segments map to segments. Campaigns and templates map to content items

Automation import is not part of current native coverage

// the playbook

how an agent migrates Omnisend → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Omnisend, 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 Omnisend, open Store settings, API keys, then create or copy an API key with read access to contacts, segments, campaigns, and templates

01subscribersmigrates
readGET /v5/contacts (Read subscribers from Omnisend.)
mapContacts map to subscribers. Tags and custom properties map directly. Segments map to segments. Campaigns and templates 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.)
02tagsmigrates
readGET /v5/contacts (Read tags from Omnisend.)
mapContacts map to subscribers. Tags and custom properties map directly. Segments map to segments. Campaigns and templates 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.)
03segmentsmigrates
readGET /v3/segments (Read segments from Omnisend.)
mapContacts map to subscribers. Tags and custom properties map directly. Segments map to segments. Campaigns and templates map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
04custom fieldsmigrates
readGET /v5/contacts (Read custom fields from Omnisend.)
mapContacts map to subscribers. Tags and custom properties map directly. Segments map to segments. Campaigns and templates 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 /v3/campaigns (Read campaigns from Omnisend.)
mapContacts map to subscribers. Tags and custom properties map directly. Segments map to segments. Campaigns and templates 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.)
06templatesmigrates
readGET /v3/templates (Read templates from Omnisend.)
mapContacts map to subscribers. Tags and custom properties map directly. Segments map to segments. Campaigns and templates map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_template (Write or stage templates in Sequenzy.)
stays behind
  • lists
  • suppressions
  • automations
  • 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 Omnisend, open Store settings, API keys, then create or copy an API key with read access to contacts, segments, campaigns, and templates

inspect

provider coverage

npx mailexodus@latest info omnisend

guide

agent playbook

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

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