A step-by-step plan for moving transactional and marketing email off SendGrid — DNS records, API keys, 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
Same request shape — swap endpoint and key
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 SendGrid account active — you'll run both in parallel for a few weeks, not cut over instantly.
Add your domain in Sendcorex, then publish the SPF, DKIM, and DMARC records it gives you as new DNS entries — don't remove SendGrid's records yet. Domains can hold multiple valid DKIM selectors at once, which is what makes running both providers safe.
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.
If you're calling SendGrid's REST API directly, point the same POST body at Sendcorex's endpoint and swap the Authorization header. If you're on SMTP, change the host to smtp.sendcorex.com and use your new API key as both username and password. No SDK required either way.
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.
Once 100% of volume runs cleanly through Sendcorex for a few days, remove SendGrid's SPF include and DKIM records, and cancel the SendGrid subscription.
sgMail.setApiKey('SENDGRID_API_KEY');
await sgMail.send({
to: 'customer@example.com',
from: 'hello@yourdomain.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>',
}),
});SPF record includes Sendcorex alongside SendGrid, not replacing it 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 or event listener updated to receive delivery/bounce events from Sendcorex
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.
The steps are the same for any provider: verify your sending domain and publish the new SPF include and DKIM keys, export your SendGrid suppressions (bounces, blocks, spam reports, unsubscribes) and import them, swap the API call or SMTP credentials, then shift traffic gradually for 1–2 weeks while the new IPs warm up. Only remove SendGrid from SPF after the last email goes out through it.
Moving from a different provider?
Ready to move off SendGrid?
Create your account, verify your domain, and start the parallel-sending window today.
No credit card required