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

Switch from SMTP2GO to MigoSMTP

Move SMTP or API sending in stages, run both providers in parallel, and check your ports and support needs first.

A staged move between two SMTP and API services, with an honest list of where SMTP2GO is stronger

SMTP2GO 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 SMTP2GO so nothing is forgotten.
SMTP2GO
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 SMTP2GO 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

SMTP2GOMigoSMTPWhat to do
Verified senders and domainsDomain authenticationAdd the new records and verify them.
SMTP usersSMTP credentialsCreate one per application.
API keysScoped API keysCreate keys per service.
WebhooksWebhooks and eventsUpdate the endpoint and payload handling.
SuppressionsSuppression listImport before sending.
Ports 25, 80, 587, 2525, 8025, 465, 8465Ports 587 and 465Test from the sending server.

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 https://api.smtp2go.com/v3/email/send \
  -H "X-Smtp2go-Api-Key: SMTP2GO_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "sender": "hello@yourdomain.com",
        "to": ["user@example.com"],
        "subject": "Hello",
        "html_body": "<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 SMTP2GO to MigoSMTP?

To move from SMTP2GO to MigoSMTP, list your sender domains and verified senders, SMTP users, API keys and webhooks, then authenticate your domains with MigoSMTP while the SMTP2GO records stay in place. Create scoped keys or SMTP credentials, point webhooks at your handler, import suppressions, and move one stream at a time. If your application sends over SMTP, the change is often a new host, username and password.

SMTP2GO and MigoSMTP are the same kind of service: a sending platform with an SMTP relay and an API. That makes the move simpler than leaving a marketing suite, but it also means the decision comes down to specifics. SMTP2GO documents SMTP ports 25, 80, 587, 2525 and 8025, plus SSL on 465 and 8465, and says 2525 is open from most locations. MigoSMTP documents 587 with STARTTLS and 465 with implicit TLS. If your hosting provider blocks 587 and you rely on 2525, check that first.

SMTP2GO lists a free plan of 1,000 emails a month with a cap of 200 a day, and describes 24 hour support by helpdesk, chat and phone. It assigns a dedicated IP automatically at 100,000 emails a month and above. MigoSMTP also has a free plan of 1,000 emails a month, offers dedicated IPs as an add-on on its Growth and Scale plans, and includes them on Enterprise. These details are from smtp2go.com, read on 15 October 2026.

Use cases

Ways to move from SMTP2GO

Swap SMTP credentials first

If an application sends over SMTP, create MigoSMTP credentials, change the host, username and password in staging, and send a test. That is often the whole change for that application.

Check the port

If you send on 2525 because your host blocks 587, test 587 or 465 from the same server before you commit. A blocked port is the most common reason an SMTP move fails on day one.

Move API callers one at a time

SMTP2GO's API takes a sender, a recipient list, a subject and a body. The equivalent MigoSMTP call has the same shape, so changes are usually field renames.

Recreate sender verification

SMTP2GO asks you to verify senders or domains. Authenticate each sending domain in MigoSMTP and keep both sets of DNS records until the move is complete.

Re-point webhooks

Map the events your code uses, such as delivered, bounced and spam complaint, update the endpoint, and verify signatures in the new payload.

Import suppressions

Export bounced and unsubscribed addresses from SMTP2GO and import them before the first send so you never mail a known bad address.

How we help

Help with the move from SMTP2GO

DNS

Check both providers can send

Use the free SPF, DKIM and DMARC checker to confirm that your domain authorises SMTP2GO 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

Test from the real server

Run a send from the machine that will send in production, not from your laptop. Network rules differ and you want to find them early.

Authenticate both providers

Publish SPF and DKIM for MigoSMTP while keeping SMTP2GO's records so both can send during the overlap.

Keep the free plan idea in mind

Both providers have a free tier, so you can test MigoSMTP end to end without paying before you move real traffic.

Watch deferrals by domain

During the overlap, compare deferral and complaint rates by recipient domain between the two providers.

Plan for support

If you rely on SMTP2GO's phone support, decide what you will use instead, and ask us what each MigoSMTP plan includes.

Retire in order

Remove the old credentials first, wait a week, then remove old DNS records.

FAQs

SMTP2GO: frequently asked questions

Moving from SMTP2GO? Our team can review your senders and ports before you start.

How do I migrate from SMTP2GO to MigoSMTP?

Authenticate your domains with MigoSMTP alongside SMTP2GO, create credentials or API keys, update webhooks, import suppressions, and move one stream at a time. For SMTP senders the change is usually a new host, username and password.

Is MigoSMTP better than SMTP2GO?

Not in every way, and that is the honest answer. SMTP2GO documents more SMTP ports and describes 24 hour phone, chat and helpdesk support. MigoSMTP offers INR and EUR billing, GST invoices for India, UPI payment, and a different plan structure. Choose on what matters to you.

Which SMTP ports does MigoSMTP support?

Port 587 with STARTTLS and port 465 with implicit TLS. We advise against port 25 for submission because many hosts block it. SMTP2GO documents additional ports such as 2525 and 8025.

Do I get a dedicated IP?

Dedicated IPs are an add-on on Growth and Scale and are included on Enterprise. SMTP2GO says it assigns one automatically from 100,000 emails a month, and that a shared IP usually works better below that.

What about the free plan?

Both have one. MigoSMTP's free plan has 1,000 emails a month. SMTP2GO lists 1,000 a month with a 200 a day cap.

Can I run both at once?

Yes. Authenticate both and move a small share first.

When should I stay on SMTP2GO?

If you depend on a port MigoSMTP does not offer, or on phone support, staying is sensible. Test before you decide.

Where did you get the SMTP2GO numbers?

From SMTP2GO's public FAQ and pricing information, read on 15 October 2026. Check their live pages 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.