Move your sending without losing reputation, history or sleep. Run both providers in parallel, then cut over in stages.
AI turns your SES identities and SNS events into a mapping you can review
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.
aws sesv2 send-email \
--from-email-address hello@yourdomain.com \
--destination ToAddresses=user@example.com \
--content 'Simple={Subject={Data=Hello},Body={Html={Data="<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.
If delivery, bounce and complaint events flow through SNS to queues or Lambda functions, repoint that logic at MigoSMTP webhooks. Run both paths briefly to confirm your database updates match.
Applications using SES SMTP credentials need a new host, port and MigoSMTP credentials. Change one service at a time, since IAM-derived SES credentials and MigoSMTP credentials are managed separately.
Each configuration set usually represents a use case such as receipts or newsletters. Create a matching workspace or stream for each so reporting and suppression handling stay separated.
A new sending account starts with its own limits, so confirm your starting quotas before moving volume. Keep SES active for any mail class you have not yet verified on MigoSMTP.
Reads exported identities, configuration sets and event destinations, and proposes MigoSMTP equivalents with confidence scores. Ambiguous items are flagged, and a team member approves each mapping before it is created.
Scans your code repository exports for SNS and SQS message handlers and lists the ones that need webhook changes. It drafts updates for you to review; nothing is changed automatically.
Tracks bounce, deferral and complaint rates against your SES baseline while traffic shifts, and alerts on drift. You decide whether to continue, hold or roll back each stage.
The MigoSMTP API is documented in a form tools and agents can read, so your own scripts or assistants can draft requests. Every sending or configuration change still needs your approval.
AI suggestions for your SES migration are reviewed and approved by you before anything is applied. [Confirm which AI features are available at launch.]
Download the account-level suppression list, and any list-level entries, before you send anything. Importing it prevents repeat mail to addresses that already bounced or complained.
Find every service holding SES SMTP credentials or access keys. Replace them one by one, then disable the old credentials once logs show no activity.
Authenticate the same domains and from addresses you use today. A mismatch between the From domain and the authenticated domain is a frequent cause of failed tests.
Leave SES identities and credentials active during the transition. If a stream misbehaves on MigoSMTP, you can route it back quickly and investigate calmly.
If your mail must stay in a given region, confirm available regions [Confirm data residency options] before moving. Document where logs and recipient data are stored after the move.
Export your identities, configuration sets and suppression list, authenticate your domains with MigoSMTP, create new credentials, replace SNS event handlers with webhooks, and move traffic in stages. Disable SES identities and IAM credentials only after sending there has stopped. Test on a small share of traffic first and review the results with your team.
Simple SMTP-only setups can move in days. Setups with several configuration sets, SNS topics and Lambda handlers take longer because the event pipeline must be rebuilt and tested. Plan [n] weeks including a staged ramp. Test on a small share of traffic first and review the results with your team.
MigoSMTP has its own account onboarding, separate from your SES sandbox status. Confirm your starting limits with [Confirm onboarding and sending limits] before moving volume, and keep SES active for anything you have not verified yet. Test on a small share of traffic first and review the results with your team.
MigoSMTP webhooks deliver delivery, bounce, complaint and other events directly to your HTTPS endpoint, so you may not need SNS topics or queues. Update your consumer for the new payload, and run both paths briefly to compare. Test on a small share of traffic first and review the results with your team.
Reputation follows your domain and IPs, so it does not transfer automatically. Authenticate your domain, start with a small share of mail, and increase gradually. If you use dedicated IPs on SES, plan a warm-up for new ones. Test on a small share of traffic first and review the results with your team.
Yes. Export the account-level suppression list and import it into MigoSMTP before the first send. Check the export format and any list-level entries against [verify against provider docs] so nothing is missed. Test on a small share of traffic first and review the results with your team.
Yes. Both can authenticate your domain at once, so split traffic by application, configuration set or recipient domain. Keep SES credentials active until logs confirm nothing is still using them. Compare bounce and complaint rates between the two before each increase.
AI drafts the mapping; people decide. It reads exported identities, configuration sets and event destinations, proposes MigoSMTP equivalents with confidence scores, and flags SNS consumers needing changes. A person approves every 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 Amazon SES and the cutover schedule.
Create an account, add your domain and send your first email.