mailexodus
home/migrations/from Shopify Email
// migrate from

leave Shopify Email. keep the work.

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

agentUse mailexodus skill: Shopify Email → Sequenzy playbook
// try it

see what moves out of Shopify Email.

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

analyzing Shopify Email…
source modePartial automated adapter
source exports5
Mailchimp imports8
destination gapsautomations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from shopify-email --to mailchimp --dry-run
agentUse mailexodus skill: Shopify Email → Mailchimp playbook
running…open the Shopify Email migration guide →
// why teams leave

why teams leave Shopify Email.

  • →
    Shopify Email migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, segments, tags, custom fields.
  • →
    Shopify Email campaign HTML export is not reliably exposed through the Admin API
// transfer boundary

what mailexodus pulls from Shopify Email.

can migrate
  • +
    subscribers
  • +
    tags
  • +
    segments
  • +
    custom fields
  • +
    suppressions
needs review
  • ?
    segments
  • ?
    suppressions
cannot migrate
  • x
    lists
  • x
    campaigns
  • x
    templates
  • 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

Partial automated adapter

Customers with email marketing consent map to subscribers. Segments map to segments. Tags map to tags. Metafields map to custom attributes. Consent state maps to active or unsubscribed status

Shopify Email campaign HTML export is not reliably exposed through the Admin API

// the playbook

how an agent migrates Shopify Email → Sequenzy.

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

01 · authenticate

Create a Shopify Admin API custom app with read_customers and customer segment access. Paste SHOP.myshopify.com|ADMIN_API_ACCESS_TOKEN, or JSON with shop and accessToken

01subscribersmigrates
readPOST /admin/api/{version}/graphql.json query customers (Read subscribers from Shopify Email.)
mapCustomers with email marketing consent map to subscribers. Segments map to segments. Tags map to tags. Metafields map to custom attributes. Consent state maps to active or unsubscribed status 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
readPOST /admin/api/{version}/graphql.json query customers.tags (Read tags from Shopify Email.)
mapCustomers with email marketing consent map to subscribers. Segments map to segments. Tags map to tags. Metafields map to custom attributes. Consent state maps to active or unsubscribed status mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_tag (Write or stage tags in Sequenzy.)
03segmentsneeds review
readPOST /admin/api/{version}/graphql.json query segments (Read segments from Shopify Email.)
mapCustomers with email marketing consent map to subscribers. Segments map to segments. Tags map to tags. Metafields map to custom attributes. Consent state maps to active or unsubscribed status 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
readPOST /admin/api/{version}/graphql.json query customer.metafields (Read custom fields from Shopify Email.)
mapCustomers with email marketing consent map to subscribers. Segments map to segments. Tags map to tags. Metafields map to custom attributes. Consent state maps to active or unsubscribed status 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.)
05suppressionsneeds review
readPOST /admin/api/{version}/graphql.json query customer.emailMarketingConsent (Read suppressions from Shopify Email.)
mapCustomers with email marketing consent map to subscribers. Segments map to segments. Tags map to tags. Metafields map to custom attributes. Consent state maps to active or unsubscribed status mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePATCH update_subscriber.status (Write or stage suppressions in Sequenzy.)
stays behind
  • lists
  • campaigns
  • templates
  • automations
  • sender reputation and domain warmup
  • historical analytics, revenue attribution, and aggregate reporting
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: Create a Shopify Admin API custom app with read_customers and customer segment access. Paste SHOP.myshopify.com|ADMIN_API_ACCESS_TOKEN, or JSON with shop and accessToken

inspect

provider coverage

npx mailexodus@latest info shopify-email

guide

agent playbook

npx mailexodus@latest guide --from shopify-email --to sequenzy

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