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

# Migration Center

> Plan a migration from a developer email provider to MailChannels sender-risk infrastructure for platforms with many senders.

Use these guides to move sending workflows from another developer email provider to MailChannels Email API. The send call matters, but the larger migration decision is how you will govern many downstream senders without putting shared reputation at risk.

Each guide focuses on the operational differences that usually matter during a migration:

* Outbound send payload shape
* Sender identity and domain authorization
* Tenant isolation and sub-account mapping
* Policy, limits, and containment paths
* Template handling
* Webhook and event delivery
* Suppression and unsubscribe semantics
* Marketing-list or campaign replacement
* Inbound-mail feature gaps

## Migration inventory

Before you write code, inventory the sending features you use today:

| Current feature                                   | MailChannels planning question                                                                                |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| API keys, subusers, projects, servers, or tenants | Which boundaries need separate MailChannels sub-accounts, credentials, limits, suppressions, or webhooks?     |
| Sending domains                                   | Which domains need Domain Lockdown, SPF, DKIM, and DMARC records before production traffic moves?             |
| Batch or bulk sends                               | Should the workflow use `/send-async`, webhooks, and per-sender limits to keep risk scoped?                   |
| Tags or metadata                                  | Which sender, tenant, campaign, agent, or application IDs should you preserve for monitoring and remediation? |
| Suppressions and bounces                          | Which bounced or complained recipients should be migrated into your own suppression workflow?                 |
| Webhooks                                          | Which event handlers need new MailChannels event mappings so delivery outcomes become operational signals?    |

## Provider guides

<CardGroup cols={2}>
  <Card title="SendGrid" icon="send" href="/email-api/migration-center/migrate-from-sendgrid">
    Migrate SendGrid sending while replacing subuser, template, suppression, and marketing assumptions.
  </Card>

  <Card title="Mailgun" icon="send" href="/email-api/migration-center/migrate-from-mailgun">
    Migrate Mailgun domain-scoped sending into account, sub-account, and domain authorization boundaries.
  </Card>

  <Card title="Mailjet" icon="send" href="/email-api/migration-center/migrate-from-mailjet">
    Migrate Mailjet sending while moving campaigns and audience governance outside MailChannels.
  </Card>

  <Card title="Brevo" icon="send" href="/email-api/migration-center/migrate-from-brevo">
    Migrate Brevo senders, templates, blocklists, and campaigns into explicit sender controls.
  </Card>

  <Card title="Postmark" icon="send" href="/email-api/migration-center/migrate-from-postmark">
    Migrate Postmark servers and streams into MailChannels account, sub-account, or metadata boundaries.
  </Card>

  <Card title="Amazon SES" icon="send" href="/email-api/migration-center/migrate-from-amazon-ses">
    Migrate SES identities, configuration sets, events, and regional assumptions into MailChannels controls.
  </Card>

  <Card title="Resend" icon="send" href="/email-api/migration-center/migrate-from-resend">
    Migrate Resend sends, domains, templates, audiences, and broadcasts into a governed delivery layer.
  </Card>
</CardGroup>

## Common MailChannels concepts

| MailChannels concept    | Migration meaning                                                                                  |
| ----------------------- | -------------------------------------------------------------------------------------------------- |
| `/send`                 | Runtime API for governed transactional and personalized messages.                                  |
| `/send-async`           | Runtime API for larger or queued sends that need webhook-based outcome tracking.                   |
| `personalizations`      | Recipient-specific addressing and merge data.                                                      |
| `dynamic_template_data` | Runtime data available to Mustache-rendered message content.                                       |
| `transactional`         | Send classification that affects suppression behavior.                                             |
| `tracking_settings`     | Per-message click, open, and unsubscribe tracking controls.                                        |
| DKIM                    | Domain authentication that requires DNS publication.                                               |
| Domain Lockdown         | MailChannels control that authorizes which account can send for a protected domain.                |
| Sub-accounts            | Tenant isolation boundaries for credentials, limits, suppressions, webhooks, and suspension paths. |
| Webhooks                | HTTPS event delivery that lets you monitor outcomes and remediate risky senders.                   |
| Suppression list        | MailChannels recipient block list with transactional and non-transactional suppression types.      |

## Recommended migration sequence

1. Inventory current sending domains, downstream sender identities, templates, webhooks, suppressions, and any marketing or inbound workflows.
2. Decide whether source-side tenants, servers, subusers, agents, or configuration groups should map to one MailChannels account or to separate MailChannels sub-accounts.
3. Rebuild application send code against MailChannels payloads and authentication.
4. Move provider-managed templates into application code or another template store.
5. Create MailChannels DKIM and Domain Lockdown records and plan DNS publication.
6. Recreate webhook consumers so delivery outcomes feed monitoring, suppression, and remediation workflows.
7. Import or recreate suppressions with explicit transactional versus non-transactional policy.
8. Replace campaign, audience, broadcast, cold outreach, or inbound-mail workflows outside the MailChannels Email API when the source platform provided those features.
9. Run parallel test sends, validate authentication, verify webhooks, and then schedule production cutover.