Migrating from Resend to MailSend
This guide outlines how to migrate your contacts, templates, domains, credentials, and webhooks from Resend to MailSend smoothly.
Quick Answer
Migrating from Resend 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 your contact lists and suppressions from the Resend dashboard. Since Resend is primarily API-based, download any React Email components or HTML templates stored in your local codebase repository.
2. API & API Credentials
Retrieve a new MailSend REST API key and update the API base URL in your configuration files to `https://api.mailsend.dev/v1/emails`. Retrieve new API keys from the MailSend credentials panel if routing via API.
3. Verification & Testing
Send a test payload using MailSend's API key. Check that webhook events trigger correctly on your server endpoints.
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