when Shopify Email is the right move.
Shopify Email is a strong fit for teams that want shopify email teams moving commerce customers, customer segments, tags, metafields, and email marketing consent state. 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 Shopify Email objects.
// inboundwhat Shopify Email receives.
- +subscribers
- +tags
- +segments
- +custom fields
- +suppressions
- ?destination mappings still need final operator review
- xlists
- xcampaigns
- xtemplates
- xautomations
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 Dry-run the report first, then approve writes when the counts and destination gaps look right.
plan the move to Shopify Email.
- Authenticate your sending domain in Shopify Email (SPF, DKIM, DMARC) and plan a warmup window — sender reputation is earned here, it does not transfer.
- Bring consent and suppression state across first, so unsubscribes and bounces are honored from the first send in Shopify Email.
- QA migrated templates and segments inside Shopify Email, and send seed tests before any live campaign.
- Keep your current platform active until in-flight automations finish and Shopify Email is warmed and trusted.
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.
destination coverage
npx mailexodus@latest info shopify-email
agent playbook
Ask mailexodus for a migration_playbook with to=shopify-email
Use mailexodus skill: your source → Shopify Email playbook