New guide: how to warm up a dedicated IP without hurting your reputation. Read now →
Log in
MigoSMTP
Migration guide

Switch from Resend to MigoSMTP

Move your sending in stages, keep your email components as they are, and compare plans at your own volume.

A staged move between two developer-friendly sending services, with an honest price comparison

Resend audit
Authenticated domains
API keys and scopes
Templates
Event webhook
Suppression lists
Nothing missed
Plan first
Inventory what you useList the domains, API keys, templates, webhooks and suppressions on Resend so nothing is forgotten.
RESEND
MIGOSMTP
Domains
Domains
API keys
API keys
Templates
Templates
Webhooks
Webhooks
Cutover
1-to-1
Guided
Map each item acrossDomains, keys, templates and webhooks have direct equivalents. You recreate, not redesign.
Recreate, not redesign
Template
Template + variables
Event webhook
Signed webhook
Suppression list
Suppression import
Sender identity
Verified domain
Review and apply · nothing changes until you approve
Reads your setup
You approve
You map your templates and webhooksList your Resend templates and event settings, then recreate each one in MigoSMTP. Review every mapping before you switch traffic.
Event webhook
Signed events
/events
200 OK
Analytics
200 OK
CRM
200 OK
Mapped events
Signed
Re-point the event webhookEvent names map across and payloads are signed, so your consumers need minimal change.
Add records
TYPE
NAME
VALUE
CNAME
mig._domainkey
dkim.migosmtp.com
TXT
@
v=spf1 include:old-provider.example ~all
TXT
_dmarc
v=DMARC1; p=none
Both providers authorised
Side by side
No downtime
Authenticate your domainPublish DKIM and SPF for MigoSMTP alongside the old records so both can send during the move.
Share moved
Fully moved
D1
D3
D5
D7
D10
D14
D21
Staged cutover
Monitored
Shift traffic graduallyMove a little more volume each day, so reputation carries across with no sudden jump.
Audit
Map
Rebuild
Events
Authenticate
Warm
The plan

A migration in five steps

1

Audit

List your domains, keys, templates, webhooks and suppressions.

2

Authenticate

Add MigoSMTP DNS records alongside the old ones.

3

Rebuild

Recreate templates and webhooks, import suppressions.

4

Cut over

Shift traffic in stages and watch delivery.

5

Retire

Remove old records and keys once stable.

Concepts

How your setup maps across

ResendMigoSMTPWhat to do
DomainsDomain authenticationAdd the new records and verify them.
API keysScoped API keysCreate one key per application.
Stored templatesTemplatesRecreate content and variables.
WebhooksWebhooks and eventsUpdate the endpoint and payload handling.
SuppressionsSuppression listImport before sending.
Official SDK callsHTTP call or SMTPReplace behind a flag.

Terminology reflects the provider's documentation at the time of writing. Verify against current docs before publishing.

How a message travels

From your app to the inbox, with checks at every hop

Your appSends by SMTP or API with your key.
IntakeAuthenticates, validates and rate-checks the request.
Queue and routingPrioritises mail and picks the right IP pool.
Signing and deliverySigns with DKIM and delivers with provider-aware pacing.
Inbox and eventsDelivery, bounce and engagement events flow back to you.
Code changes

Update your send call

Before
curl -X POST https://api.resend.com/emails \
  -H "Authorization: Bearer RESEND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "from": "Your App <hello@yourdomain.com>",
        "to": ["user@example.com"],
        "subject": "Hello",
        "html": "<p>Hi there</p>" }'
After
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.

Overview

How do I move from Resend to MigoSMTP?

To move from Resend to MigoSMTP, list your domains, API keys, templates and webhooks, then authenticate your domains with MigoSMTP while Resend's DNS records stay in place. Create scoped keys, change the endpoint and key in your code, recreate any templates, import suppressions, and move one service at a time. Retire the Resend keys once volume has held steady for a few weeks.

Resend and MigoSMTP are the same kind of service: a sending platform with an API and an SMTP relay, aimed at product email. Resend is built around a simple developer experience, and its request format is close to ours, so the code change is usually small. The decision should come down to price, billing, support and the specific features you use.

On price, we are not the cheaper option at every volume. As listed on resend.com on 15 October 2026, Resend offers a free plan of 3,000 emails a month with a 100 a day limit, Pro at $20 for 50,000 and $35 for 100,000, and Scale from $90 for 100,000. MigoSMTP lists $10 for 10,000 and $75 for 100,000. At 100,000 emails a month Resend Pro lists lower than our Growth plan. The reasons to move are billing in INR or EUR with proper invoices, plan structure or support fit, not price alone.

Use cases

Ways to move from Resend

Swap the endpoint and the key

Resend's send call is a JSON POST with a Bearer key and from, to, subject and html fields. The MigoSMTP call has the same shape, so you mostly change the URL and the key, and check how recipients are passed.

Check SDK usage

If you use an official Resend SDK, find every call site first. Replace them with a plain HTTP call or our SMTP relay, and keep the change behind a flag so you can switch back.

Look at your email components

If your templates are code, such as React components rendered to HTML, they can keep working: render to HTML as before and send that HTML through MigoSMTP.

Recreate stored templates

If you use templates stored in Resend, rebuild them in MigoSMTP with the same variables and test with real sample data.

Re-point webhooks

Map the delivery, bounce and complaint events your code reads, update the endpoint, and verify signatures in the new payload.

Import suppressions

Export bounced and complained addresses from Resend and import them before the first send.

How we help

Help with the move from Resend

DNS

Check both providers can send

Use the free SPF, DKIM and DMARC checker to confirm that your domain authorises Resend and MigoSMTP at the same time before you move any traffic.

Warmup

Plan the warmup

If you move to a dedicated IP, the IP warmup calculator gives you a day-by-day volume ramp so reputation builds steadily.

Bounces

Read bounce codes during the overlap

While both providers run, the bounce code lookup turns raw SMTP responses into plain explanations and a suggested fix.

Review

Review the cutover order

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.

Best practices

Migration best practices

Compare on your own volume

Add up your real monthly volume and the features you use, then compare totals on both live pricing pages. Do not compare list prices at a volume you do not send.

Authenticate both providers

Publish SPF and DKIM for MigoSMTP while keeping Resend's records, so both can send for your domain during the overlap.

Check log retention

Resend lists 30 days of data retention on its Free, Pro and Scale plans. Decide how long you need logs and ask us what applies to your MigoSMTP plan.

Move the lowest-risk service first

Pick an internal tool or a low-volume notification, compare bounces and complaints for a week, then continue.

Do not move on a launch day

Choose a quiet week so you have time to fix anything you find.

Retire in order

Remove Resend keys first, wait a week, then remove old DNS records.

FAQs

Resend: frequently asked questions

Moving from Resend? Our team can review your keys and call sites before you start.

How do I migrate from Resend to MigoSMTP?

Authenticate your domains with MigoSMTP alongside Resend, create scoped keys, change the endpoint and key in your code, recreate templates, update webhooks, import suppressions, and move one service at a time. Retire Resend keys once the new setup has run cleanly for a few weeks.

Is MigoSMTP cheaper than Resend?

Not at every volume. As listed on 15 October 2026, Resend Pro is $35 a month for 100,000 emails and Scale starts at $90, while MigoSMTP Growth is $75. At 10,000 emails MigoSMTP Starter is $10 and Resend's Free plan covers up to 3,000. Compare at your own volume.

Why would I move at all?

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.

Do I have to rewrite my email templates?

If your templates are code that renders to HTML, no. Keep rendering as you do now and send the HTML through MigoSMTP. Only templates stored inside Resend need rebuilding.

Does MigoSMTP support SMTP as well as an API?

Yes. Use the SMTP relay on port 587 with STARTTLS or port 465 with implicit TLS, or the REST API.

Do I need to warm up?

If you move to a dedicated IP, yes. Raise volume in steps using the warmup calculator.

Where did you get the Resend numbers?

From Resend's public pricing page, read on 15 October 2026. Check the live page before you decide.

Next step

Ready to plan your move?

Tell us about your domains, volume and setup and we will help you plan a safe, staged cutover.

Start your migrationTalk to our migration team

Start sending in minutes.

Create an account, add your domain and send your first email.