Migrating from Legacy cloud email setup to MailSend
This guide outlines how to migrate your contacts, templates, domains, credentials, and webhooks from Legacy cloud email setup to MailSend smoothly.
Quick Answer
Migrating from Legacy cloud email setup 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
Retrieve verified domain records and suppression lists. Export HTML templates stored in your codebase or cloud storage.
2. API & API Credentials
Replace legacy sending credentials in application settings with MailSend API variables. This removes the need to manage delivery infrastructure directly.
3. Verification & Testing
Verify domain SPF and DKIM records in DNS. Send a test email to confirm delivery status, monitoring reputation stats in your dashboard.
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