Migrate
Move your email to Mail.Land
Plan the move so that your sending continues while you switch. These guides cover what moves, in what order, and how to test before you switch traffic.
Migration guides
- Migrate from SendGridField-by-field mapping of the Mail Send API, SMTP settings, suppression import and webhook events.
- Migrate from MailgunField-by-field mapping of the messages API, SMTP settings, per-domain suppression export and webhook events.
- Migrate from PostmarkField mapping of the Email API, message streams as keys, suppression import and webhook events.
- Migrate from Amazon SESFrom SendEmail, IAM and event publishing to one API key, signed webhooks and imported suppressions.
- Mail.Land vs SendGridA sourced comparison, including where SendGrid is the stronger choice.
What moves
The same six things move whichever provider you are leaving.
Sending domains
Add each domain in Mail.Land and publish the DNS records we show you. A domain keeps a single SPF record: add Mail.Land's include to the one you have. You can verify while your current provider is still sending.
API keys and SMTP credentials
Create Mail.Land keys for each application. Limit each one to the API or SMTP, to selected domains and to known IP addresses.
Send calls and SMTP settings
Point SMTP at smtp.mail.land on port 587, or change your API call to the Mail.Land send endpoint.
Templates
Recreate your templates in Mail.Land and send a test of each one before you switch.
Suppression lists
Import bounces, spam complaints and unsubscribes before your first send, so that people who opted out stay suppressed from day one.
Webhooks
Add your endpoint in Mail.Land and verify our HMAC-SHA256 signature. Event names differ between providers, so map them in your handler.
A safe order of work
- Create your account and verify your sending domain.
- Import your suppression lists.
- Create API keys and test with a sandbox key set to log only, which accepts requests without delivering them.
- Send real test messages to addresses you control.
- Move a small share of your traffic first, watch delivery and bounces, then move the rest.
- While both providers run, copy new unsubscribes, complaints and bounces from your old provider to Mail.Land, and do a final sync before you switch the last traffic.
- Keep your old provider active until the last scheduled or retried messages have gone.
Want help with your migration?
Tell us which provider you use, your monthly volume and how you send (API, SMTP or both). We will help you plan the move.
Start with a free account
Verify a domain and send your first test before you move any traffic.