mailexodus
home/migrations/to SendGrid
// migrate to

move to SendGrid without rebuilding by hand.

mailexodus normalizes your current platform into one portable schema, then checks what SendGrid can actually import. You get a route report before your agent writes anything.

agentUse mailexodus skill: your source → SendGrid playbook
// try it

bring your data into SendGrid.

Pick the platform you're leaving and generate a route playbook. The report shows what maps cleanly into SendGrid's model and what needs review — before you approve writes.

analyzing Klaviyo…
source modeAutomated adapter
source exports8
SendGrid imports7
destination gapstags, automations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to sendgrid --dry-run
agentUse mailexodus skill: Klaviyo → SendGrid playbook
running…open the Klaviyo migration guide →
// fit

when SendGrid is the right move.

SendGrid is a strong fit for teams that want sendgrid teams separating transactional templates and suppressions from lifecycle email operations. 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 SendGrid objects.

// inbound

what SendGrid receives.

can import
  • +
    subscribers
  • +
    lists
  • +
    segments
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
  • +
    templates
needs review
  • ?
    destination mappings still need final operator review
not exposed for import
  • x
    tags
  • x
    automations
destination 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 Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to SendGrid.

  1. Authenticate your sending domain in SendGrid (SPF, DKIM, DMARC) and plan a warmup window — sender reputation is earned here, it does not transfer.
  2. Bring consent and suppression state across first, so unsubscribes and bounces are honored from the first send in SendGrid.
  3. QA migrated templates and segments inside SendGrid, and send seed tests before any live campaign.
  4. Keep your current platform active until in-flight automations finish and SendGrid is warmed and trusted.
// migrate it

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.

inspect

destination coverage

npx mailexodus@latest info sendgrid

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=sendgrid

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