Skip to content
  • sendgrid
  • smtp
  • migration
  • free-plan

Migrate from SendGrid to SMTP: 6,000 free emails

Lost SendGrid's free plan? Switch over SMTP to Pidgely Free: 6,000 emails/month, 200/day, 3 domains. Step by step with SPF and DKIM.

Pidgely teamPublished 5 min readMarkdown version

On this page
  1. Why migrate from SendGrid now?
  2. What does the Pidgely free plan include?
  3. What do you need before you start?
  4. How do you migrate from SendGrid to Pidgely over SMTP?
  5. How do you set up SPF and DKIM before sending?
  6. How do you test sending after the switch?
  7. What if your app uses the SendGrid HTTP API?
  8. How do you migrate without losing deliverability?
  9. Next step
  10. Frequently asked questions

Yes, you can leave SendGrid without rewriting code: if your app sends over SMTP, change the host to smtp.pidgely.com, the username to pidgely, and use your Pidgely API key as the password. Pidgely's Free plan gives you 6,000 emails per month (up to 200 per day, on up to 3 domains), no credit card. SendGrid has had no permanent free plan since May 27, 2025. This guide walks through the migration end to end, including SPF and DKIM, and how to avoid losing deliverability along the way.

Why migrate from SendGrid now?

Twilio retired SendGrid's permanent free plan on May 27, 2025. If you sent a few emails a month and fit in the free tier, you now have two options: pay or switch. The details of what changed, with official sources and an alternatives table, are in Left SendGrid's free plan? Free alternatives.

This text is the next step: you have decided to try Pidgely and want to know exactly what to change in your app and your DNS. For a side-by-side feature comparison (campaigns, dedicated IP, webhooks), see Pidgely vs SendGrid.

What does the Pidgely free plan include?

The Free plan has clear limits, worth knowing before you touch any configuration:

ItemPidgely Free
Emails per month6,000
Daily cap200
Domains3
Credit card at signupNot required
Overage chargesNone: sending stops at the limit

For system emails (signup, password reset, order notices), which spread across the month, 200 per day adds up to 6,000 in 30 days. If you send large bursts at once, the daily cap will get in the way: in that case, look at the paid plans. To decide, open your SendGrid dashboard and check your busiest sending day in the last 30 days.

What do you need before you start?

Gather four things before changing any credentials:

  • Access to the DNS of your sending domain (where you publish TXT and CNAME records).
  • Access to the environment variables or config file of the app that sends email.
  • Your busiest sending day in the last 30 days, to compare with the 200-per-day cap.
  • An inbox of your own (Gmail, for example) for the final test.

How do you migrate from SendGrid to Pidgely over SMTP?

The process takes 30 to 60 minutes, most of it waiting for DNS.

  1. Create the free account at app.pidgely.com. No card needed.
  2. Add your sending domain. Pidgely shows the records you need to publish in DNS.
  3. Publish SPF and DKIM in the domain's DNS exactly as the dashboard shows. Wait until verification turns green.
  4. Create an API key in the dashboard. It will be your SMTP password.
  5. Swap the SMTP credentials in your app: host: smtp.pidgely.com username: pidgely password: the API key
  6. Send a real test to an inbox of yours.
  7. Only after confirming delivery, remove the old SendGrid credentials.

If your app keeps its settings in environment variables, the change is usually just those three lines, with no code change.

How do you set up SPF and DKIM before sending?

SPF says which servers may send email for your domain. DKIM signs each message to prove it was not altered. Gmail and Yahoo expect these records from senders, and without them messages tend to land in spam or get rejected.

In Pidgely you do not have to build the values by hand: the dashboard shows the records for your domain and confirms when DNS can see them. If your domain already had an SPF record for SendGrid, do not create a second one: DNS accepts a single SPF record per domain, so edit the existing one. To understand each record and DMARC, read the SPF, DKIM and DMARC guide.

How do you test sending after the switch?

Send a real message from the app to a Gmail address of yours. Open it, click "Show original" and look for three lines: SPF, DKIM and DMARC. All three should read PASS. If one fails, go back to the Pidgely dashboard and check that the matching DNS record is published exactly as shown.

Also check that the message reached the inbox and not spam. If it landed in spam with everything on PASS, the cause is usually content or domain history, not the migration; see why emails go to spam.

What if your app uses the SendGrid HTTP API?

SMTP is the shortest path because it needs no code change. If your app calls the SendGrid HTTP API, you have to change the call. Pidgely accepts the same request format as Resend, so if you have that format as a reference, the adaptation is small. The exact format is in the documentation. Test in a separate environment before pointing production at it.

How do you migrate without losing deliverability?

The real risk in switching providers is changing everything at once. Do it in stages:

  • Move one type of email first, preferably the lowest-volume one (internal notices, for example), and watch it for a few days.
  • Ramp up gradually. If you had a lot of volume, read about IP warm-up and spread the traffic over days.
  • Keep DMARC published and aligned with the sending domain.
  • Keep the old credentials until you confirm everything arrives. Since SMTP is a standard, going back is just swapping host, username and password.

Next step

Create the account and send your first test email today: create a free Pidgely account (6,000 emails per month, 200 per day, no card).

Frequently asked questions

How long does it take to migrate from SendGrid to Pidgely over SMTP?

If your app already sends over SMTP, swapping the credentials takes minutes. What takes time is verifying the domain (SPF and DKIM) and waiting for DNS to propagate; plan for 30 to 60 minutes in total.

What are the Pidgely SMTP credentials?

Host smtp.pidgely.com, username pidgely, and your API key as the password. You create the key in the dashboard after verifying your sending domain.

Does the Pidgely free plan have a daily limit?

Yes. Free sends 6,000 emails per month, capped at 200 per day, on up to 3 domains. When you hit the limit sending stops; there is no overage charge.

Do I need to change code if I use the SendGrid HTTP API?

A little. SMTP needs no code change, only new credentials. For the HTTP API, Pidgely accepts the same request format as Resend; see the documentation.

Can I go back to SendGrid later?

Yes. SMTP is a standard: swap host, username and password back. That is why you should keep the old credentials until delivery is confirmed.

Pidgely team

Published

We build Pidgely, the email API that gets you to the inbox. We write about what we learn delivering email, citing the standards and mailbox provider guidelines behind every claim.

Also available in:
sendgridalternatives

Left SendGrid's free plan? Free alternatives

SendGrid ended its free plan. Free alternatives with real limits: Pidgely 6,000/month, Resend 3,000/month, and how to migrate over SMTP.

5 min read

free-planemail-api

Which email API has the best free plan in 2026?

Free email API plans compared with numbers and sources (checked Nov 3, 2026): Pidgely 6,000 emails/month, Resend 3,000, SendGrid only a 60-day trial.

3 min read