Move your sending without losing reputation, history or sleep. Run both providers in parallel, then cut over in stages.
An AI assistant maps your SendGrid templates and webhooks for you to 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.
curl https://api.sendgrid.com/v3/mail/send \
-H "Authorization: Bearer SENDGRID_KEY" \
-H "Content-Type: application/json" \
-d '{ "personalizations": [{ "to": [{ "email": "user@example.com" }] }],
"from": { "email": "hello@yourdomain.com" },
"subject": "Hello",
"content": [{ "type": "text/html", "value": "<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.
Start with receipts, password resets and alerts sent through the v3 mail send API. Volume is predictable, so you can compare delivery against SendGrid before moving anything else.
Keep SendGrid live while a small percentage of mail goes through MigoSMTP. Split by application, template or recipient domain, and widen the share once bounce and complaint rates match.
If you use subusers per customer or brand, create one MigoSMTP workspace for each. Reputation, keys and suppression data stay separated the way they are today.
Point your delivery, bounce, open and click handlers at MigoSMTP webhooks. Run a mapping layer briefly so downstream systems that expect the old event names keep working.
Reads each dynamic template, converts handlebars variables and conditional blocks, and shows a side-by-side preview. You review the output and approve each template before it is saved.
Compares your SendGrid event webhook settings with MigoSMTP events and proposes a field-by-field mapping with confidence scores. Nothing is applied until a team member signs off on it.
During staged cutover it watches bounce, deferral and complaint trends against your baseline and raises an alert if they drift. You decide whether to pause, hold or continue the ramp.
If you move to dedicated IPs, it drafts a ramp from your volume history and adjusts the plan as results arrive. You approve each step before the sending schedule changes.
AI suggestions for your SendGrid migration are reviewed and approved by you before anything is applied. [Confirm which AI features are available at launch.]
Download bounces, spam reports, unsubscribes and group suppressions first. Importing them before the first send protects recipients who already opted out and keeps complaint rates low.
Add MigoSMTP DKIM and return-path records beside the SendGrid ones. Both can authenticate your domain at the same time, so you can roll back quickly.
Send each converted template with production-like variables, including empty and missing values. Differences in how conditionals are evaluated are the most common source of broken emails.
Cut over transactional mail, then marketing mail, as separate steps. Different volumes and engagement patterns mean each stream deserves its own check before the next begins.
Once all services use MigoSMTP keys, revoke the SendGrid API keys. Do this last, after logs show no remaining traffic using them.
Audit your SendGrid setup, add MigoSMTP domain authentication records alongside the existing ones, recreate templates and webhooks, import suppressions, then shift traffic in stages. Retire SendGrid only after volume is stable. Most teams run both providers in parallel during the transition.
It depends on how many templates, webhooks and sending applications you have. A single application with a few templates can move in days; a multi-subuser setup takes longer. Plan [n] weeks for staged cutover and warm-up if you add dedicated IPs.
You rebuild them in MigoSMTP, but you do not start from nothing. Export the template HTML and variables, and the converter proposes a matching version for you to review. Check handlebars helpers and conditionals in preview before approving. Test on a small share of traffic first and review the results with your team.
Reputation belongs to your domain and sending IPs, so it does not transfer automatically. Authenticate your domain, send a small share first, and increase gradually. On shared infrastructure you start with the pool's reputation; dedicated IPs need warm-up. Test on a small share of traffic first and review the results with your team.
Export it and import it into MigoSMTP before your first send, so bounced and unsubscribed addresses are not mailed again. Include unsubscribe group data if you use groups. Check the export format against [verify against provider docs]. Test on a small share of traffic first and review the results with your team.
If you send over SMTP, usually only the host, port and credentials change. If you use the v3 mail send API, the request body differs, so update the call or use an SDK. Test in a staging environment first. Test on a small share of traffic first and review the results with your team.
Yes. Both can authenticate the same domain at once, so you can route a percentage of mail through MigoSMTP and keep SendGrid for the rest. Split by application or template to make comparison easy. Keep SendGrid credentials active until logs show no remaining use.
AI does the tedious mapping, not the decisions. It reads your exported configuration, proposes template, webhook and subuser mappings with confidence scores, and flags gaps. Nothing is applied until a person on your team approves each change. [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 SendGrid and the cutover schedule.
Create an account, add your domain and send your first email.