Migration Guide (Twilio & SendGrid to NotifySetu)
Step-by-step guide to migrate legacy single-provider codebases to NotifySetu without downtime.
# Migration Guide: Twilio & SendGrid -> NotifySetu
Migrating to NotifySetu takes less than 30 minutes and lets you keep your existing Twilio and SendGrid accounts while adding automatic backup providers like AWS SES or Plivo.
Step 1: Vault Existing Keys
Navigate to **Console -> Provider Connections** and add your Twilio Account SID/Auth Token and SendGrid API Key.
Step 2: Replace Provider SDK Calls
Replace separate SendGrid and Twilio SDK imports with a single NotifySetu client instance:
- const sgMail = require('@sendgrid/mail');
- const twilio = require('twilio');
+ const { NotifySetu } = require('@notifysetu/sdk');
+ const notifysetu = new NotifySetu({ apiKey: process.env.NOTIFYSETU_KEY });Step 3: Enable Smart Fallback
Add a secondary provider in your routing policy so that if SendGrid experiences downtime, emails automatically failover to AWS SES.