Migrating from Mailgun to MailSend
This guide outlines how to migrate your contacts, templates, domains, credentials, and webhooks from Mailgun to MailSend smoothly.
Quick Answer
Migrating from Mailgun to MailSend involves exporting list databases and suppressions, updating DNS verification keys (SPF, DKIM, DMARC), and replacing API endpoints or REST API credentials. Most teams complete cutovers in under 2 hours.
1. What to Export
Export subscriber mailing lists and suppressions. Retrieve custom template HTML layouts using Mailgun's template dashboard tools.
2. API & API Credentials
Change API settings in your backend server configurations to target MailSend's relay ports. For API integrations, update payload parameters to match MailSend REST endpoints.
3. Verification & Testing
Verify API credentials and API handshake authentication. Execute test dispatches to check that webhooks deliver logs back to your systems.
Cutover Checklist
- 1Verify custom domain settings in MailSend settings
- 2Configure SPF, DKIM, and DMARC DNS settings
- 3Export subscriber records and suppression logs from legacy provider
- 4Import contacts CSV database using visual mapper
- 5Replace legacy API keys and API host settings in application server configs
- 6Verify webhook event routes are active and tested
- 7Monitor live delivery metrics in analytics panels