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.
Before changing anything, list what Amazon SES does for you today: sending domains, API and SMTP keys, templates, webhooks, suppression lists and any integration that sends through it. A complete inventory prevents the surprises behind most failed migrations, such as a forgotten webhook or a script still using an old key.
Add MigoSMTP DNS records alongside the old ones.
Add MigoSMTP's SPF, DKIM and DMARC records alongside your existing Amazon SES records instead of replacing them. Both providers can then send for your domain at the same time, so you can verify the new setup without interrupting live mail.
Recreate templates and webhooks, import suppressions.
Recreate your templates and webhooks in MigoSMTP and import the suppression lists you exported from Amazon SES, so people who bounced or unsubscribed are not emailed again on day one. Where Amazon SES concepts differ from ours, the mapping table further down shows what to use.
Shift traffic in stages and watch delivery.
Move traffic in stages, a low-risk stream first and then the rest, while watching delivery, bounces and complaints. Keep Amazon SES configured as a fallback until the new path has proved itself.
Remove old records and keys once stable.
Once delivery has been stable for a while, remove the old DNS records, revoke the old keys and close or downgrade the Amazon SES account. Tidying up removes stale credentials and avoids paying for two providers.
Terminology reflects the provider's documentation at the time of writing. Verify against current docs before publishing.
aws sesv2 send-email \ --from-email-address [email protected] \ --destination [email protected] \ --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": "[email protected]",
"to": "[email protected]",
"subject": "Hello",
"html": "<p>Hi there</p>"
}'Illustrative requests. See the API reference for the complete field list.
To migrate from Amazon SES to MigoSMTP, list your verified identities, configuration sets, event destinations and account-level suppressions, then authenticate your domains with MigoSMTP while the SES records stay in place. Create new SMTP or API credentials, replace SNS and queue consumers with webhooks, and import suppressions. Shift traffic in stages, compare delivery, and remove the SES identities and IAM credentials only after sending has been quiet on SES for a period you choose.
Teams often leave SES because they want fewer AWS moving parts around email, such as IAM policies, SNS topics and queues, or they want more routing and support options. Most of the setup carries over: verified identities become domain authentication, configuration sets map to workspaces and streams, and the suppression list imports. Details like sandbox status, sending quotas and regional behaviour should be confirmed with the provider's current documentation for your account. Keep notes on every difference so the team agrees on what changes.
The AI migration assistant reads the SES configuration you export, including identities, configuration sets and event destinations, and proposes how each maps to MigoSMTP with a confidence score. Where an SNS topic feeds custom code, it highlights the consumer you will need to update. A person approves each proposed change before anything is applied, and approvals are logged. The assistant never sends mail or edits DNS by itself, and you control timing, scope and rollback.
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.
Swap notification topics and handlers for webhooks that send the same events straight to your application.
Use managed domain checks, warmup guidance and monitoring instead of building them yourself.
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.
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 with your cloud and compliance teams before moving. Document where logs and recipient data are stored after the move.
Map your notification topics and handlers to webhook endpoints before you move volume.
Moving from Amazon SES? Our team can review your event pipeline before you start.
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 several 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 our team 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 the provider's current documentation 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.
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.
Tell us about your domains, volume and setup and we will help you plan a safe, staged cutover.
The DPDP Rules were published in November 2025 and phase in over 18 months. We explain the notice, consent, security, breach and retention duties in plain terms, the reported penalty ceilings and a plan for email programmes.
Password-based SMTP in Exchange Online is being retired after two postponements. We set out the reported timeline, what fails and when, the five migration routes and why system mail belongs on its own sending path.
As passkeys replace passwords, sign-in mail should shrink while recovery and security alerts matter more. We review the 2026 FIDO data and work through each message type and three scenarios to 2030.
Apple accounts for 62.26% of tracked opens, and AI assistants now read mail for people. We look at why the open rate fails, what the data says and which signals to measure instead.
Fluent, targeted phishing is now cheap. We review the figures and their weaknesses, explain what authentication can and cannot stop and set out what legitimate senders should do next.
BIMI shows a verified logo beside authenticated email, but its entry ticket is enforced DMARC. We set out Gmail's requirements, VMC against CMC, the unverified vendor claims and three scenarios to 2028.
A new class of sender is arriving: software agents with their own inboxes. We review the 2026 funding and product signals, the deliverability and security risks and three scenarios to 2030.
Two independent 2026 studies show DMARC records are common while enforcement lags. We compare their numbers, explain why domains stall at p=none and set out a 90-day plan to move to reject.
Create an account, add your domain and send your first email.