mailexodus
home/migrations/from SendGrid
// migrate from

leave SendGrid. keep the work.

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

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

see what moves out of SendGrid.

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

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

why teams leave SendGrid.

  • →
    SendGrid migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, segments, custom fields.
  • →
    Legacy and current Marketing Campaigns accounts may expose different endpoints. Marketing automation workflow import/export is not exposed as a current API reference surface
// transfer boundary

what mailexodus pulls from SendGrid.

can migrate
  • +
    subscribers
  • +
    lists
  • +
    segments
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
  • +
    templates
needs review
  • ?
    Legacy and current Marketing Campaigns accounts may expose different endpoints. Marketing automation workflow import/export is not exposed as a current API reference surface
cannot migrate
  • x
    tags
  • 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. Lists and segments map to matching destination resources. Custom fields map to attributes. Campaigns and templates map to content items

Legacy and current Marketing Campaigns accounts may expose different endpoints. Marketing automation workflow import/export is not exposed as a current API reference surface

// the playbook

how an agent migrates SendGrid → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from SendGrid, 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 SendGrid, open Settings, API Keys, then create or copy a restricted API key with read access to Marketing Campaigns contacts, lists, designs, single sends, templates, suppressions, and user profile details

01subscribersmigrates
readGET /v3/marketing/contacts (Read subscribers from SendGrid.)
mapContacts map to subscribers. Lists and segments map to matching destination resources. Custom fields map to attributes. 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.)
02listsmigrates
readGET /v3/marketing/lists (Read lists from SendGrid.)
mapContacts map to subscribers. Lists and segments map to matching destination resources. Custom fields map to attributes. Campaigns and templates 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.)
03segmentsmigrates
readGET /v3/marketing/segments (Read segments from SendGrid.)
mapContacts map to subscribers. Lists and segments map to matching destination resources. Custom fields map to attributes. 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 /v3/marketing/field_definitions (Read custom fields from SendGrid.)
mapContacts map to subscribers. Lists and segments map to matching destination resources. Custom fields map to attributes. 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.)
05suppressionsmigrates
readGET /v3/suppression/unsubscribes (Read suppressions from SendGrid.) GET /v3/suppression/bounces (Read suppressions from SendGrid.) GET /v3/suppression/spam_reports (Read suppressions from SendGrid.)
mapContacts map to subscribers. Lists and segments map to matching destination resources. Custom fields map to attributes. 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.status (Write or stage suppressions in Sequenzy.)
06campaignsmigrates
readGET /v3/marketing/singlesends (Read campaigns from SendGrid.)
mapContacts map to subscribers. Lists and segments map to matching destination resources. Custom fields map to attributes. 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.)
07templatesmigrates
readGET /v3/designs (Read templates from SendGrid.) GET /v3/templates (Read templates from SendGrid.)
mapContacts map to subscribers. Lists and segments map to matching destination resources. Custom fields map to attributes. 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
  • tags
  • automations
  • sender reputation and domain warmup
  • historical analytics, revenue attribution, and aggregate reporting
  • contacts already mid-flight inside active automations
  • A/B test results and provider-specific experiment history
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 SendGrid, open Settings, API Keys, then create or copy a restricted API key with read access to Marketing Campaigns contacts, lists, designs, single sends, templates, suppressions, and user profile details

inspect

provider coverage

npx mailexodus@latest info sendgrid

guide

agent playbook

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

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