A step-by-step plan for moving production email off Mailtrap — DNS records, credentials, 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
Both APIs are JSON — flatten the payload and swap the 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 Mailtrap account active — you'll run both in parallel for a few weeks, not cut over instantly. Mailtrap is often used for both testing and sending; this guide moves production sending, and your testing inboxes can keep catching dev and CI email. Note whether your traffic uses the transactional or the bulk stream.
Add your domain in Sendcorex, then publish the SPF, DKIM and DMARC records it gives you as new DNS entries. Leave the records Mailtrap gave you in place, and merge Sendcorex's SPF include into your existing SPF record rather than adding a second one.
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.
Mailtrap's send API is already JSON with a Bearer token, so the change is small: new URL, new key, and flatten the payload — from: { email } becomes a plain address string, and to: [{ email }] becomes a string too. If you send over SMTP, change the host from live.smtp.mailtrap.io to smtp.sendcorex.com and use your new API key as both username and password.
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. Leave staging and CI pointed at Mailtrap's testing inbox; only production traffic needs to move.
Once 100% of volume runs cleanly through Sendcorex for a few days, remove Mailtrap's sending records from your DNS and cancel the sending plan. Testing inboxes are separate, so you can keep using them for development.
await fetch('https://send.api.mailtrap.io/api/send', {
method: 'POST',
headers: {
'Authorization': 'Bearer MAILTRAP_API_TOKEN',
'Content-Type': 'application/json',
},
body: JSON.stringify({
from: { email: 'hello@yourdomain.com', name: 'Your App' },
to: [{ email: '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>',
}),
});SPF is a single record that includes both Sendcorex and Mailtrap for now
DKIM selector for Sendcorex shows as verified in the dashboard
Test send delivered to Gmail, Outlook, and Yahoo test inboxes without landing in spam
Only production uses Sendcorex credentials; staging and CI still point at Mailtrap's testing inbox
Webhook or event listener updated to receive delivery and 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.
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 Mailtrap?
Create your account, verify your domain, and start the parallel-sending window today.
No credit card required