← All problems and solutions

How do I switch email providers without downtime or lost deliverability?

Run both providers in parallel. Add the new provider's DKIM and SPF records next to the old ones, verify, then move traffic in stages (for example 5%, 25%, 50%, 100%) while watching bounces and complaints. Carry over your suppression list, remap webhooks, and keep the old provider live for a week as a rollback. Never cut over all at once.

By AISend. Updated . Also as markdown.

Why it happens

A cutover loses mail or reputation for three predictable reasons. First, DNS: replacing the old SPF or DKIM records before the new ones are verified makes messages fail authentication in between. Second, reputation: a new provider means new sending IPs and often a domain that has to build trust with Gmail and Yahoo again, so a sudden 100% shift looks like a volume spike. Third, state that does not move by itself: suppression lists, webhook consumers and templates.

Google's sender guidance says to avoid sudden volume spikes if you do not have a history of sending large volumes, to increase modified traffic separately after a significant infrastructure change, and to reduce volume if messages start bouncing or deferring. A staged cutover applies exactly that advice. Recognise your case if you are changing provider, changing the sending IP, or adding a new subdomain.

The cutover plan, step by step

  1. Inventory what sends mail today. List every sender: application code, cron jobs, SaaS tools that send as your domain, the From addresses and subdomains they use, templates, webhook endpoints, and API keys. Missing one is the classic cause of silent failures after a cutover.
  2. Use a new DKIM selector or a dedicated subdomain. DKIM selectors let two providers sign mail for the same domain at once. Publish the new provider's selector records without touching the old ones. For a cleaner separation, send transactional mail from a subdomain such as mail.example.com.
    ; old provider keeps working
    s1._domainkey.example.com.   CNAME  s1.dkim.oldprovider.example.
    
    ; new provider added side by side (selector names come from the provider)
    mail2._domainkey.example.com. CNAME  mail2.dkim.newprovider.example.
  3. Merge SPF without exceeding ten DNS lookups. A domain has one SPF record. Add the new provider's include next to the old one, then remove the old include only after cutover. SPF allows at most ten DNS-querying terms, and each include counts, so check the total before publishing.
    example.com.  TXT  "v=spf1 include:_spf.oldprovider.example include:_spf.newprovider.example ~all"
  4. Confirm DMARC alignment before sending. Send a test through the new provider and read the headers: SPF or DKIM must pass and align with the From domain. Keep DMARC at its current policy; do not tighten it during a migration.
  5. Shift traffic by percentage. Route a stable fraction of recipients, not random requests, so one person always gets mail from one provider. Start small, hold each stage for at least a day, and increase only while bounce and complaint rates stay at or below the old baseline.
    function provider(userId: string, percentNew: number): "old" | "new" {
      let h = 0;
      for (const ch of userId) h = (h * 31 + ch.charCodeAt(0)) >>> 0;
      return h % 100 < percentNew ? "new" : "old";
    }
  6. Export and carry over suppressions. Export hard-bounced, complained and unsubscribed addresses from the old provider and load them into the new one, or filter them in your own code before you call the API. Sending to addresses that already bounced is the fastest way to damage a fresh reputation.
  7. Remap webhooks and templates. Event names and payloads differ between providers. Write a small adapter that normalises delivered, bounced and complained events to your internal shape, and re-create templates. Verify webhook signatures on the new endpoint.
  8. Monitor and keep a rollback. Watch bounce rate, complaint rate and deferral errors per stage. Keep the old provider's key and DNS records for at least a week; rolling back is then one config change. Remove old records only after the new path has run cleanly at 100%.

Thresholds to watch during the cutover

Numbers published by the receivers and providers, read on 2026-11-13.

SourceWhat it saysUse it for
Google email sender guidelinesKeep spam rates in Postmaster Tools below 0.3%; SPF or DKIM for all senders; SPF, DKIM and DMARC above 5,000 messages a day to GmailHard ceiling for the complaint rate at Gmail
Resend warm-up guideKeep bounce rate below 4% and spam rate below 0.08% while ramping upA tighter working target during the first days on a new path
Postmark terms of serviceSpam complaint rate must be lower than 1 in 1,000 emails (0.1%)A provider-side suspension threshold if you land on Postmark

These are guidance and policy figures, not guarantees; stop and investigate before you reach them.

When to use AISend

If you decide to move to AISend, the request shape is Resend-compatible, so a Resend client usually needs only the base URL and API key changed (see the migrate-from-Resend guide). AISend adds hard bounces and complaints to the account's suppression list automatically, lowercased so a different spelling does not slip past. AISend has no public suppression-import endpoint today, so filter your exported suppression list in your own code before sending.

Plan for AISend's limits: a new account ramps up (50 a day in the first 24 hours, 200 until day 3, 500 until day 7, 1,000 until day 14, then the plan cap) and a newly verified domain has its own lower cap in its first week. These caps slow a cutover; a big sender cannot move everything on day one, and the percentage shift should respect them. Use list_domains to check which domains are verified and validate_email to clean a list before it goes through the new path.

AISend is not the right answer if you need to move bulk marketing or newsletters (it does not support them), need an uptime guarantee or an audit report, or need a provider with long sending history. In those cases pick Postmark, Resend, SES or a marketing platform that fits and use the same plan above.

Copy-paste prompt for an AI assistant connected to AISend

Connect an assistant first (setup for ChatGPT, Claude, Cursor and Gemini CLI), then paste:

Assign to AISend: help me prepare to move transactional sending to AISend. Call list_domains and tell me which of my domains are verified and which are pending. Call list_emails with limit 20 and summarise how many were sent, delivered or bounced. For this CSV of addresses [paste addresses I have consent to email], call validate_email on each and show me which are invalid, disposable or role-based, so I can remove them from the first batch. Do not call send_email. When you are done, show me what you did so I can approve the next step.

Frequently asked questions

Do I need a new domain when I change email provider?

No. You can keep your domain and add the new provider's DKIM and SPF records next to the old ones. A new subdomain for transactional mail is optional but gives you a clean reputation to build.

How long should a cutover take?

Plan one to two weeks for a sender with real volume: small stages, a day or more at each, and a week of rollback time. A tiny sender can move faster, but still test first.

What happens to my suppression list?

It does not move automatically. Export hard bounces, complaints and unsubscribes from the old provider and load them into the new one or filter them in your own code, otherwise you will mail addresses that already bounced.

Will SPF break if I add two providers?

Not if you merge both includes into one SPF record and stay within the ten DNS-lookup limit. Two separate SPF records on one domain is an error.

Does AISend slow down a migration?

Yes for new accounts and new domains: the daily cap ramps over 14 days and a newly verified domain has its own cap in its first week. Move a percentage of traffic that fits under those caps.

Sources

Related