Prompt
How to migrate off of Resend
Latest observation
If you want to migrate off Resend, the safest approach is to treat it like any other email-provider cutover: inventory what you use, add a replacement in parallel, test deliverability, then switch traffic gradually.
1) Inventory how you use Resend
List every place Resend is involved:
- Transactional email
Password resets, verification emails, receipts, alerts, invites, etc. - Broadcast / marketing email
Newsletters, announcements, lifecycle campaigns - Event/webhook handling
Delivery events, bounces, complaints, opens/clicks if used - API usage
sendbatch send- templates
- attachments
- domains / DNS config
- suppression lists / unsubscribes
- Inbound dependencies
- If anything depends on Resend-specific message IDs or webhook payloads
2) Pick your replacement
Choose based on your use case:
- Transactional-focused: Postmark, Amazon SES, Mailgun, SendGrid
- Marketing-focused: Customer.io, Klaviyo, Mailchimp, Brevo, HubSpot
- All-in-one: SendGrid, Mailgun, Brevo, SES + your own app logic
Consider:
- deliverability reputation
- pricing at your volume
- template support
- webhook/event model
- suppression/unsubscribe handling
- ease of DNS setup
- SDK compatibility
- compliance and regions
3) Set up the new provider in parallel
Before removing Resend:
- Verify your sending domain
- Configure:
- SPF
- DKIM
- DMARC
- return-path / bounce handling if needed
- Recreate templates
- Migrate metadata you rely on:
- from-name/from-email
- reply-to
- headers
- tags
- custom variables
If you use Resend templates, copy them into the new system or move template rendering into your app.
4) Abstract your email sending code
If you haven’t already, route all sending through a small internal wrapper so the provider is swappable.
Example shape:
interface EmailProvider {
sendTransactional(input: {
to: string
subject: string
html: string
text?: string
}): Promise<{ id: string }>
}
Then implement:
ResendProviderNewProvider
This prevents vendor lock-in next time.
5) Migrate templates and assets
Move:
- HTML templates
- inline styles
- images and logo URLs
- unsubscribe links
- localization strings
Make sure:
- tracking links still work
- images are hosted somewhere stable
- templates render correctly across email clients
6) Handle bounces, complaints, and unsubscribes
This is one of the easiest places to break things.
If you rely on Resend events, map them to the new provider’s equivalent:
- delivered
- bounced
- deferred
- complained
- unsubscribed
Also migrate:
- suppression lists
- opted-out users
- bounce history if available
7) Test before cutover
Send test emails to:
- Gmail
- Outlook
- Apple Mail
- Yahoo
- internal company addresses
Check:
- inbox placement
- spam placement
- SPF/DKIM/DMARC alignment
- links and images
- unsubscribe flow
- reply-to behavior
Also run a small production canary:
- 1–5% of traffic to the new provider
- monitor bounce rate, complaint rate, and support tickets
8) Cut over gradually
A good migration sequence:
- Add new provider
- Send non-critical emails through it first
- Route a small percentage of transactional traffic
- Increase to 100%
- Keep Resend active briefly as fallback
- Remove Resend only after stability is proven
9) Update operational tooling
Don’t forget:
- environment variables / secrets
- CI/CD deployment config
- webhook endpoints
- dashboards and alerts
- runbooks
- infrastructure-as-code
- docs for support/team members
10) Decommission Resend safely
Once stable:
- disable Resend API keys
- remove webhooks
- delete DNS records only if no longer needed
- archive templates/config
- keep logs and event history if useful for compliance or debugging
If you want the quickest path
The quickest migration usually looks like:
- Choose SES/Postmark/Mailgun
- Duplicate your Resend templates
- Wrap email sending behind an internal service
- Test in staging
- Route 10% of email
- Move to 100%
- Shut off Resend after a week or two of clean metrics
If you’re using Resend only for transactional email
A common low-friction replacement is:
- Postmark for simplest transactional email
- Amazon SES for lowest cost at scale
- Mailgun for flexible developer tooling
If you’re using Resend for newsletters too
You may want two systems:
- one provider for transactional
- one marketing platform for campaigns
That often improves deliverability and keeps marketing lists separate from app-critical messages.
If you want, I can give you a provider-by-provider migration plan for:
- Resend → Postmark
- Resend → Amazon SES
- Resend → SendGrid
- or a code refactor plan for your specific stack (Node, Next.js, Python, etc.).