Reference
Migration Guide
Migrating to PostMTA is straightforward. This guide covers SendGrid, Mailgun, Amazon SES, and Postmark.
Migration Overview
- Create your PostMTA account and add sending domains
- Verify DNS records (DKIM, SPF, DMARC)
- Migrate contact lists and suppression data
- Update your code to use the PostMTA API
- Run a parallel send test period
- Switch DNS and decommission the old provider
From SendGrid
| SendGrid | PostMTA |
|---|---|
POST /v3/mail/send | POST /v1/messages/send |
personalizations[].substitutions | template_data or to[].substitutions |
| IP Pools via UI | ip_pool field in send payload |
Migrating Suppressions
curl -X POST https://api.postmta.com/v1/suppressions/upload -H "Authorization: Bearer pmta_live_xxxx" -F "file=@sendgrid_suppressions.csv" -F "reason=bounced"From Mailgun
| Mailgun | PostMTA |
|---|---|
POST /v3/{domain}/messages | POST /v1/messages/send |
| Route-based forwarding | Webhook event system |
| Mailgun mailing lists | Campaigns with list segmentation |
From Amazon SES
| Amazon SES | PostMTA |
|---|---|
| SES SendEmail API | PostMTA /v1/messages/send |
| Configuration Sets | IP Pools plus webhooks |
| No built-in templates | Native template engine |
| No webhook delivery | Full event webhooks |
Parallel Send Testing
Before fully switching, run both providers in parallel to verify deliverability parity.
Migration Support
Enterprise customers receive complimentary migration support. Contact sales to get started.