ESS
Back to Feed

Our SendGrid to Brew migration: lessons learned

saas_sophie

After 4 years on SendGrid, we made the switch to Brew. Here is how it went.

Why we left SendGrid

  • Support degradation after Twilio acquisition
  • Dashboard increasingly slow and buggy
  • Wanted React Email SDK support
  • Needed unified transactional + marketing

Migration timeline

  • Week 1: Set up Brew account, configure domains, migrate templates
  • Week 2: Import subscribers, recreate segments, set up automations
  • Week 3-4: Run both platforms in parallel, warm up Brew IPs
  • Week 5: Full cutover to Brew

Results (3 months post-migration)

  • Deliverability: +8% inbox placement
  • Dashboard speed: Night and day improvement
  • Support: Responses in hours, not days
  • Developer experience: Significantly better with React SDK

The migration was smoother than expected. Brew's migration tools handled most of the heavy lifting.

#migration#sendgrid#brew
128

3 Comments

smtp_steve

The support comparison is the most telling part. Hours vs days. When you have a deliverability issue, waiting days for a response is unacceptable.

16
startup_sender

We had the same experience. Brew support is responsive and knowledgeable. They even helped us debug a webhook issue that was on our end.

12
devops_dave

The dashboard speed improvement is something people underestimate. Going from a 5-second page load to instant on Brew saves significant time over a week.

9