A SendGrid alternative with a free plan that does not expire.

What each one ships.

Moving from SendGrid.

1. 01

   Add your domain and publish the DKIM and SPF records Samva generates next to the old provider's. Both can send while you switch.

2. 02

   Swap the send call.

   const sgMail = require("@sendgrid/mail");
   sgMail.setApiKey(process.env.SENDGRID_API_KEY);
   
   const msg = {
     to: "ada@example.com",
     from: "test@example.com",
     subject: "Your receipt",
     html: "<p>Thanks for your order.</p>",
   };
   
   sgMail
     .send(msg)
     .then((response) => console.log(response[0].statusCode))
     .catch((error) => console.error(error));
   

   await samva.messages.send({
     from: { email: "orders@example.com" },
     to: [{ email: "ada@example.com" }],
     channel: "email",
     email: {
       subject: "Your receipt",
       html: "<p>Thanks for your order.</p>",
     },
   });

3. 03

   Map webhooks. Samva sends signed events for sent, delivered, bounced, complained, failed, and received, with received going to the endpoint your domain's receiving route names. Opens and clicks arrive as message.opened and message.clicked, and unsubscribes as contact.unsubscribed.

   SendGrid event	Samva event
   delivered	message.delivered
   bounce	message.bounced
   spamreport	message.complained
   dropped	message.failed
   Inbound Parse webhook	message.received
   open	message.opened
   click	message.clicked
   unsubscribe	contact.unsubscribed

4. 04

   Recreate templates as versioned templates, or send your existing HTML inline while you move.

5. 05

   Keep the old provider's suppression list in your app and filter against it. Samva cannot import it.

6. 06

   Turn on receiving if you want replies back.

What does not move: templates, the suppression list, and message history.

The full walkthrough: Migrate SendGrid Inbound Parse without losing replies.