A step-by-step plan for moving transactional email off Resend — the SDK swap, DNS records, and the parallel-sending window that keeps your sender reputation intact.
No credit card required · Migration usually takes 1–2 weeks end to end
Code changes
Minutes
Field names line up — swap the SDK call for one REST request
DNS propagation
24–48h
SPF, DKIM and DMARC records need time to settle
Full migration
1–2 wks
Includes the parallel-sending warm-up window
Typical timeline for a mid-size sender. Larger lists or dedicated IP warm-up can take longer.
Sign up free and generate an API key from the dashboard. Keep your Resend account active — you'll run both in parallel for a few weeks, not cut over instantly. Before you start, list every place that sends through Resend: app servers, background jobs, and any React Email templates.
Add your domain in Sendcorex, then publish the SPF, DKIM and DMARC records it gives you as new DNS entries. Leave Resend's records exactly as they are — Resend authenticates with its own DKIM key and bounce-handling records, and separate DKIM selectors are what let both providers verify on one domain at the same time.
Give it 24–48 hours. Check verification status in the Sendcorex dashboard before sending anything — sending through unverified DNS is what causes the deliverability problems people blame on migrations.
Remove the resend package and replace resend.emails.send() with a plain fetch POST — the from, to, subject and html fields keep the same names. If you send over SMTP, change the host from smtp.resend.com to smtp.sendcorex.com and use your new API key as both username and password. If you pass a react: component, render it to an HTML string first with React Email's render helper and send that as html.
Start with 10–20% of sends routed through Sendcorex, watch delivery and bounce rates in real time, then increase over 1–2 weeks. This lets Sendcorex's IPs warm up against mailbox providers instead of arriving as an unknown sender all at once. A percentage flag around your send function is the simplest way to split traffic.
Once 100% of volume runs cleanly through Sendcorex for a few days, remove Resend's DKIM and bounce-handling DNS records and cancel the subscription. Export anything you keep in Resend first, such as contacts stored in Audiences.
import { Resend } from 'resend';
const resend = new Resend('re_YOUR_API_KEY');
await resend.emails.send({
from: 'hello@yourdomain.com',
to: 'customer@example.com',
subject: 'Welcome!',
html: '<h1>You are in.</h1>',
});const response = await fetch('https://mail.sendcorex.com/v3.0/send', {
method: 'POST',
headers: {
'Authorization': 'YOUR_API_KEY',
'Content-Type': 'application/json',
},
body: JSON.stringify({
to: 'customer@example.com',
from: 'hello@yourdomain.com',
senderName: 'Your Company',
subject: 'Welcome!',
body: '<h1>You are in.</h1>',
}),
});Sendcorex's SPF and DKIM records are published alongside Resend's, not replacing them yet
DKIM selector for Sendcorex shows as verified in the dashboard
Test send delivered to Gmail, Outlook, and Yahoo test inboxes without landing in spam
Webhook handlers for Resend's email.delivered and email.bounced events mapped to the events Sendcorex sends
Any react: templates render to an HTML string before sending
Bounce and complaint rate monitored daily during the ramp-up window
Common questions
Steps and timelines reflect typical migrations as of 2026 and may vary based on list size, DNS provider, and existing authentication setup.
Not if you run a parallel sending window instead of an instant cutover. Sender reputation lives on the sending domain and IP, so warming up Sendcorex's IPs for 1–2 weeks while gradually shifting volume avoids a deliverability dip.
Moving from a different provider?
Ready to move off Resend?
Create your account, verify your domain, and start the parallel-sending window today.
No credit card required