> ## Documentation Index
> Fetch the complete documentation index at: https://docs.migma.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Email Service Providers

> Choose Migma sending or a connected delivery provider for campaign and API email.

Migma can send email through built-in sending or through a connected delivery provider. Choose the provider that should deliver the message, then review campaign state, logs, and results from Migma where supported.

<Info>
  Mailchimp, Klaviyo, HubSpot, Omnisend, and Brevo are export destinations. They are separate from direct delivery providers. See [Platform Integrations](/integrations/platform-integrations).
</Info>

<Note>
  Migma sending has the most complete Migma-side tracking. Third-party delivery providers can expose less detail inside Migma depending on the provider setup.
</Note>

## Supported sending providers

| Provider                                   | Best for                                                           | External account needed |
| ------------------------------------------ | ------------------------------------------------------------------ | ----------------------- |
| [Migma sending](/sending-domains/overview) | Fastest setup, managed or custom domains, Migma campaign workflows | No                      |
| [Amazon SES](/integrations/amazon-ses)     | Teams already using AWS email infrastructure                       | Yes                     |
| [Resend](/integrations/resend)             | Developer-led lifecycle and transactional email                    | Yes                     |
| [SendGrid](/integrations/sendgrid)         | Teams already using SendGrid delivery                              | Yes                     |
| [Mailgun](/integrations/mailgun)           | Teams already using Mailgun delivery                               | Yes                     |

## How provider choice works

The sending domain or sender still needs to be approved for the provider you choose. If no external provider is selected, Migma uses built-in sending.

```typescript theme={null}
await migma.sending.send({
  recipientType: 'email',
  recipientEmail: 'sarah@example.com',
  from: 'hello@yourdomain.com',
  fromName: 'Your Brand',
  subject: 'Welcome!',
  emailId: 'email_123',
  providerType: 'resend'
});
```

Supported `providerType` values:

| Value      | Provider      |
| ---------- | ------------- |
| `migma`    | Migma sending |
| `ses`      | Amazon SES    |
| `resend`   | Resend        |
| `sendgrid` | SendGrid      |
| `mailgun`  | Mailgun       |

## Setup checklist

<Steps>
  <Step title="Verify sender identity">
    Set up a managed Migma address, a custom sending domain, or a provider-approved sender.
  </Step>

  <Step title="Connect the provider">
    Add provider credentials in **Settings** under email providers.
  </Step>

  <Step title="Choose the provider">
    Select the provider for campaign or API sends.
  </Step>

  <Step title="Send a test">
    Check sender, reply-to, rendering, tracking, and unsubscribe behavior before launch.
  </Step>

  <Step title="Monitor results">
    Review logs, bounces, complaints, skipped recipients, and domain health after sending.
  </Step>
</Steps>

## Choosing a provider

| If you need                                                       | Use                             |
| ----------------------------------------------------------------- | ------------------------------- |
| No external ESP setup                                             | Migma sending                   |
| Existing AWS delivery setup                                       | Amazon SES                      |
| Developer-first provider workflow                                 | Resend                          |
| Existing SendGrid infrastructure                                  | SendGrid                        |
| Existing Mailgun infrastructure                                   | Mailgun                         |
| Mailchimp, Klaviyo, HubSpot, Omnisend, or Brevo campaign workflow | Export to that platform instead |

## Related pages

<CardGroup cols={2}>
  <Card title="Sending Domains" icon="globe" href="/sending-domains/overview">
    Set up managed or custom sending domains.
  </Card>

  <Card title="Send Campaign" icon="paper-plane" href="/campaigns/send-campaign">
    Send a campaign from Migma.
  </Card>

  <Card title="Email Logs" icon="list-bullet" href="/sending-domains/email-logs">
    Review individual email delivery status and tracking data.
  </Card>

  <Card title="Export Options" icon="download" href="/email-editor/export-options">
    Use export when another platform owns final sending.
  </Card>
</CardGroup>