Move your sending in stages, run both providers in parallel, and compare plans at your own volume.
A staged move between two SMTP and API services, with an honest price note
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://api.elasticemail.com/v4/emails/transactional \
-H "X-ElasticEmail-ApiKey: ELASTIC_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "Recipients": { "To": ["user@example.com"] },
"Content": { "From": "hello@yourdomain.com", "Subject": "Hello",
"Body": [{ "ContentType": "HTML", "Content": "<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 from Elastic Email to MigoSMTP, list your sending domains, API keys, SMTP credentials, templates and webhooks, then authenticate your domains with MigoSMTP while Elastic Email's DNS records stay in place. Create scoped keys, change the host or endpoint, recreate templates, import suppressions, and shift one stream at a time. Retire the old keys once volume is stable.
Elastic Email and MigoSMTP both offer an SMTP relay and an API, and Elastic Email also includes marketing tools such as contacts and campaigns. If you only use it for sending application mail, the move is mostly a change of credentials and endpoint. If your team builds campaigns in it, that part does not move with this guide.
On price, Elastic Email lists a free plan of up to 3,000 emails a month, Starter at $19 a month and Pro at $49, each starting from a 50,000 email tier, with higher tiers on a slider (as listed on 15 October 2026). MigoSMTP lists $10 for 10,000 and $75 for 100,000, and we do not list a 50,000 tier. At some volumes Elastic Email will cost less than we do, so compare at your own volume. Elastic Email's page also lists inbound email processing, webhooks and sub-accounts on Pro, so check which of those you use.
If an application sends over SMTP, create MigoSMTP credentials, change the host, port, username and password in staging, and send a test.
Elastic Email has more than one API version. Find which one your code uses before you map fields, because the request shape differs between them.
Recipients, a from address, a subject and a body are the same ideas in both. Change the endpoint, the key header and the field names, and test each call type you use.
Rebuild stored templates in MigoSMTP with the same variables and test with real sample data.
Map the delivery, bounce and complaint events your code reads, update the endpoint, and verify signatures in the new payload.
Export bounced, complained and unsubscribed addresses from Elastic Email and import them before the first send.
Use the free SPF, DKIM and DMARC checker to confirm that your domain authorises Elastic Email 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 each application, plugin and tool that sends through Elastic Email. WordPress and CMS plugins are the usual forgotten ones.
Publish SPF and DKIM for MigoSMTP while keeping Elastic Email's records, so both can send during the overlap.
Add up your real monthly volume and the features you use, then compare totals on both live pricing pages.
Begin with mail people expect and open. Strong early engagement helps a new sending source build trust.
A rising complaint rate at one mailbox provider is the earliest warning sign.
Remove old keys first, wait a week, then remove old DNS records.
Moving from Elastic Email? Our team can review your credentials and templates before you start.
Authenticate your domains with MigoSMTP alongside Elastic Email, create scoped keys, change the host or endpoint in your code, recreate templates, update webhooks, import suppressions, and move one stream at a time. Retire the old keys once the new setup has run cleanly for a few weeks.
Not necessarily. As listed on 15 October 2026, Elastic Email Starter is $19 a month and Pro is $49, each from a 50,000 email tier. MigoSMTP lists $10 for 10,000 and $75 for 100,000. Compare at your own volume.
Moving sending does not touch them. Keep them in Elastic Email until you decide otherwise.
Its page lists inbound email processing, webhooks and sub-accounts on Pro. Check which you use and compare with MigoSMTP's plan features.
Common reasons are INR or EUR billing with proper invoices, a plan structure that fits your volume, or wanting sending and support from one team. If none apply to you, staying is a fair choice.
If you move to a dedicated IP, yes. Raise volume in steps using the warmup calculator.
Yes. Use the SMTP relay on port 587 with STARTTLS or port 465 with implicit TLS, or the REST API.
From Elastic Email'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.