Move production sending in stages, keep Mailtrap's testing inboxes if you use them, and compare plans at your own volume.
A staged move for production sending, with a clear note on what Mailtrap's testing product covers
List your domains, keys, templates, webhooks and suppressions.
Add MigoSMTP DNS records alongside the old ones.
Recreate templates and webhooks, import suppressions.
Shift traffic in stages and watch delivery.
Remove old records and keys once stable.
Terminology reflects the provider's documentation at the time of writing. Verify against current docs before publishing.
curl -X POST https://send.api.mailtrap.io/api/send \
-H "Authorization: Bearer MAILTRAP_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "from": { "email": "hello@yourdomain.com", "name": "Your App" },
"to": [{ "email": "user@example.com" }],
"subject": "Hello",
"html": "<p>Hi there</p>" }'curl https://api.migosmtp.com/v1/send \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "hello@yourdomain.com",
"to": "user@example.com",
"subject": "Hello",
"html": "<p>Hi there</p>"
}'Illustrative requests. See the API reference for the complete field list.
To move production sending from Mailtrap to MigoSMTP, list your sending domains, API tokens, templates and webhooks, then authenticate your domains with MigoSMTP while the Mailtrap records stay in place. Create scoped keys, recreate templates, point webhooks at your handler, import suppressions, and shift one stream at a time. Retire Mailtrap tokens once volume has held steady.
Mailtrap sells two things that people often mix up. Email Sending delivers real mail, and Email Testing gives developers sandbox inboxes to inspect messages without sending them to customers. This page is about moving Email Sending. MigoSMTP is not a replacement for Mailtrap's sandbox inboxes, so if you use Mailtrap for testing, you may want to keep it for staging and move only production.
On price, Mailtrap lists a free sending plan of 4,000 emails a month with a 150 a day cap, Basic at $15 for 10,000, $20 for 50,000 and $30 for 100,000, and Business at $85 for 100,000 with a dedicated IP, SSO and sub-accounts (as listed on mailtrap.io on 15 October 2026). MigoSMTP lists $10 for 10,000 and $75 for 100,000. At 100,000 emails a month Mailtrap's Basic plan costs less than ours, so the reason to move is features, billing or support fit, not price.
If your team uses Mailtrap's sandbox for staging, keep it. Move only the production sending, and point your staging environment at the sandbox as before.
Each application that sends through a Mailtrap token should get its own MigoSMTP key. Move the lowest-risk application first.
Mailtrap's sending API takes a Bearer token and a JSON body with from, to, subject and a text or html part. The MigoSMTP call has the same shape, so changes are mostly the URL, the key and a few field names.
Rebuild each template in MigoSMTP with the same variables and test with real sample data before it goes live.
Map the delivery and bounce events your code reads, update the endpoint, and verify signatures in the new payload.
Export bounced and unsubscribed addresses from Mailtrap and import them before the first send.
Use the free SPF, DKIM and DMARC checker to confirm that your domain authorises Mailtrap and MigoSMTP at the same time before you move any traffic.
If you move to a dedicated IP, the IP warmup calculator gives you a day-by-day volume ramp so reputation builds steadily.
While both providers run, the bounce code lookup turns raw SMTP responses into plain explanations and a suggested fix.
Send our team your list of streams and rough volumes and ask for a review of the order in which to move them. This is offered on request.
The checker, calculator and lookup are free tools on this site. The cutover review is a conversation with our team, and you decide every change in your own account.
Write down whether you are replacing sending, testing, or both. They are separate decisions with different alternatives.
Publish SPF and DKIM for MigoSMTP while keeping Mailtrap's records so both can send during the overlap.
Pricing differs by tier. Add up your real monthly volume and the features you use, then compare the totals.
Mailtrap lists log retention from 3 days on Free to 30 days on Enterprise. Decide how long you need logs and ask us what applies to your MigoSMTP plan.
Choose a quiet week so you have time to fix anything you find.
Remove old tokens first, wait a week, then remove old DNS records.
Moving from Mailtrap? Our team can review your tokens and templates before you start.
Authenticate your domains with MigoSMTP alongside Mailtrap, create scoped keys, recreate templates, update webhooks, import suppressions, and move one stream at a time. Retire Mailtrap tokens once the new setup has run cleanly for a few weeks.
No. Mailtrap's sandbox inboxes for inspecting test email are a different product. Keep it for staging if you use it. This page covers moving production sending.
Not at every volume. As listed on 15 October 2026, Mailtrap Basic is $30 a month for 100,000 emails and Business is $85, while MigoSMTP Growth is $75. At 10,000 emails Mailtrap Basic is $15 and MigoSMTP Starter is $10. Compare at your own volume.
Its Business plan lists a dedicated IP with automatic warmup, SSO, sub-accounts, 15 days of logs and 24/7 live chat. Check which of those you use and compare with MigoSMTP's plan features before you decide.
Common reasons are INR or EUR billing with proper invoices, a plan structure that fits your volume, or wanting your sending and support under one provider. If none apply to you, staying is a fair choice.
Yes. Authenticate both and send a small share through MigoSMTP first.
If you move to a dedicated IP, yes. Raise volume in steps using the warmup calculator.
From Mailtrap's public pricing page, read on 15 October 2026. Check the live page before you decide.
Tell us about your domains, volume and setup and we will help you plan a safe, staged cutover.
Create an account, add your domain and send your first email.