Move your sending without losing reputation, history or sleep. Run both providers in parallel, then cut over in stages.
AI helps map your Mailgun domains, routes and webhooks; you approve each change
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 https://api.mailgun.net/v3/YOUR_DOMAIN/messages \ --user "api:MAILGUN_KEY" \ -F from="hello@yourdomain.com" \ -F to="user@example.com" \ -F subject="Hello" \ -F 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.
Mailgun organises sending by domain, so migrate the same way. Authenticate one domain, move its traffic, confirm results, then repeat. Subdomains for marketing and transactional mail can move separately.
If you use Mailgun routes to forward or parse incoming mail, list each match expression and action, then recreate it as an inbound rule. Test with real addresses before changing MX records.
Applications that send over SMTP often need just a new host, port and credentials. Change one service at a time and keep Mailgun credentials active until logs show no remaining use.
If you use IP pools, decide which streams get dedicated IPs. Start each on a warm-up schedule and keep low-volume mail on shared infrastructure until the dedicated IPs have a track record.
Reads exported domains, keys and webhook settings, then proposes MigoSMTP equivalents with confidence scores. Low-confidence items are listed separately, and a team member approves each mapping before it is created.
Takes Mailgun route match expressions and actions and drafts equivalent inbound rules. It shows what it changed and what it could not convert, and you approve or edit every rule.
Scans templates for variables and compares them with the data your code sends, listing missing or renamed fields. Corrections are suggestions only, applied after your review.
Answers questions about your plan in plain language, such as which domain to move next. It cites the relevant docs, and any step it recommends still needs your approval.
AI suggestions for your Mailgun migration are reviewed and approved by you before anything is applied. [Confirm which AI features are available at launch.]
Write down every sending domain, its region and what uses it. Forgotten subdomains with old scripts are the usual source of surprise failures after cutover.
Pull bounce, complaint and unsubscribe lists for each domain and import them before sending. This protects reputation and avoids mailing addresses that already rejected you.
Capture sample events from both providers and diff the fields. Update your handler to accept the new format, and verify signature checks with the new signing key.
Reduce TTLs on records you plan to change a day ahead. If you need to roll back, the change then takes effect in minutes rather than hours.
Leave old keys active until logs show zero traffic for several days. Then revoke them and delete the unused DNS records.
Inventory your domains, keys, routes and webhooks, authenticate each domain with MigoSMTP alongside Mailgun, recreate templates and routes, import suppressions, and shift traffic gradually. Retire Mailgun records and keys once volume is stable and logs show no remaining use. Test on a small share of traffic first and review the results with your team.
A single domain with SMTP sending can move in days. Several domains, inbound routes and dedicated IPs take longer because each needs testing and warm-up. Plan [n] weeks and migrate one domain at a time. Test on a small share of traffic first and review the results with your team.
Yes, but you recreate them. Export each route's match expression and action, then rebuild them as inbound rules in MigoSMTP. Test with a sample address before updating MX records. Check priority behaviour against [verify against provider docs]. Keep the old routes active until the new ones are confirmed working.
Reputation is tied to your domain and sending IPs, so you do not carry it over automatically. Authenticate the domain, start with a small share, and increase gradually. Dedicated IPs need a proper warm-up before full volume. Test on a small share of traffic first and review the results with your team.
Export them per domain and import them into MigoSMTP as suppressions before your first send. That prevents mailing addresses that previously bounced or complained. Confirm the export format against [verify against provider docs] before importing. Test on a small share of traffic first and review the results with your team.
For SMTP, usually just host, port and credentials. For the HTTP API, the endpoint, authentication and field names differ, so update the call or use an SDK. Test in staging and switch one service at a time. Test on a small share of traffic first and review the results with your team.
Yes. Both can authenticate your domain at once, so you can route part of your mail through MigoSMTP and leave the rest on Mailgun. Splitting by domain or application keeps comparisons simple. Test on a small share of traffic first and review the results with your team.
It handles the repetitive mapping. The assistant reads your exported domains, webhooks and templates, proposes MigoSMTP equivalents with confidence scores and flags routes it cannot translate. A person approves each change before it is applied. [Confirm which AI features are available at launch.]
Yes. Most teams send a small share through MigoSMTP first and increase gradually.
Moving from a shared pool to a dedicated IP needs warmup. Use the guide or the calculator.
Our team can review your plan for Mailgun and the cutover schedule.
Create an account, add your domain and send your first email.