Blog · · 6 min read
Switching email providers without losing mail: a checklist
By Y Naga Vamsi, creator of Mailtruss.
On this page
Moving to a new email provider is mostly a code change, but the failures happen in the parts that are not code: DNS, lists of blocked addresses, and the places that quietly send email. This checklist is the order that keeps mail flowing.
1. Find everything that sends
Search your code and your tools for every sender: the app, background jobs, your auth provider, your billing tool, your CMS, your support desk. Anything that sends as your domain needs to move or keep working. The ones people forget are the SMTP settings in third-party tools.
2. Set up DNS before you send anything
- Verify your sending domain with the new provider. Its DKIM records are separate from the old one's, so both can coexist.
- Do not add a second SPF record. A name may have only one. Merge the new provider into the existing record, then check the result, and the ten-lookup limit, with the domain checker.
- Check that DMARC is at least in monitoring mode, so you get reports showing which services send as you during the move.
3. Test without real mail
Send a few messages that reach no real mailbox, and read the delivery record. Check that the from address, the reply-to and the links are right, and that your webhook endpoint accepts the new provider's events. Webhook signatures differ between providers, so verification code has to change.
4. Switch in steps
- Move low-risk mail first, such as internal notifications.
- Move one message type at a time, with a way to switch back.
- Ramp up volume over days if you send a lot, instead of moving everything at once. Reputation attaches to your domain and to the sending addresses, and a sudden jump in volume from a new source looks like a new sender to receivers.
5. Carry over your suppression list
The old provider knows which addresses bounced or complained. A fresh account does not, so the first send to those addresses bounces again and costs reputation. Export the list and import it before you move volume.
6. Keep the old one for a while
Leave the old provider running for a few days after the last send, to read its history and catch anything that still points at it. Look at the new provider's bounce and complaint rates before you cancel. Then remove the old provider from SPF, and delete its DKIM records.
Guides for specific services
Mailtruss has step-by-step migration guides that show the send call before and after for Resend, SendGrid, Postmark and Mailgun. The same order applies to any provider.
Keep reading
- 6 min readSPF's ten-lookup limit, and how to stay under itWhy an SPF record that looks fine can fail: RFC 7208 allows ten DNS lookups. What counts, what does not, how to count yours, and the safe ways to get under the limit.
- 6 min readHow to read an email bounce: what 550 5.1.1 and 5.7.1 meanA bounce carries two codes and a sentence. Here is how to read them: the reply code, the enhanced status code, the digits that say retry or not, and the codes you will see most.