Skip to main content
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:

​
Provider guides

SendGrid

Migrate SendGrid sending while replacing subuser, template, suppression, and marketing assumptions.

Mailgun

Migrate Mailgun domain-scoped sending into account, sub-account, and domain authorization boundaries.

Mailjet

Migrate Mailjet sending while moving campaigns and audience governance outside MailChannels.

Brevo

Migrate Brevo senders, templates, blocklists, and campaigns into explicit sender controls.

Postmark

Migrate Postmark servers and streams into MailChannels account, sub-account, or metadata boundaries.

Amazon SES

Migrate SES identities, configuration sets, events, and regional assumptions into MailChannels controls.

Resend

Migrate Resend sends, domains, templates, audiences, and broadcasts into a governed delivery layer.

​
Common MailChannels concepts

  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.