Migrate from Resend

Migrate off Resend without stopping sending.

Notix reads your Resend account with an API key you paste, brings your contacts, unsubscribes and bounces over, and deletes its copy of the key within the hour. Your Resend account keeps sending the whole time.

Start the migration Book a free migration call

API key, held at most 1 hour

Code converter

Paste your Resend code, get the Notix version

Load an example or paste your own send call: Node.js, Python, PHP or cURL. Anything that does not have a Notix equivalent is listed under the result.

Your Resend codeNode.js, detected

Notix, Node.js (notix-js)

import { Notix } from "notix-js";

const notix = new Notix(process.env.NOTIX_API_KEY);

const { data, error } = await notix.emails.send({
  from: "Acme <orders@acme.com>",
  to: "amara@example.com",
  replyTo: "support@acme.com",
  subject: "Your order is on its way",
  html: "<p>Your parcel left our warehouse today.</p>",
});

Tags and categories were not converted: a Notix send has no tags field. Use your own header if you need to label mail.

The converter reads the code as text in your browser. It does not run it, store it or send it anywhere.

Or change nothing yet: the compat API

Notix accepts Resend's send request as it is and answers in the same shape. Swap the URL, send your Notix API key as the bearer token, and your existing code keeps working while you migrate.

Up to 100 messages in one request, and the Idempotency-Key header works
Replies and errors come back in Resend's own shape
Paused while an import is waiting for its review, so nothing slips out early

It is there to get you migrated, not to build on. New code should use /v1/emails. Of the providers on this site, only Resend and SendGrid have a compat API.

The only line that changes

- https://api.resend.com/emails
+ https://app.staging.usenotix.dev/api/compat/resend/emails

A Resend-shaped send, through Notix

curl -X POST https://app.staging.usenotix.dev/api/compat/resend/emails \
  -H "Authorization: Bearer $NOTIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Acme <orders@acme.com>",
    "to": ["amara@example.com"],
    "subject": "Your order is on its way",
    "html": "<p>On its way.</p>"
  }'

Migration Center

Move your audience in one sitting

Paste a Resend key made just for the migration in the Migration Center. It shows you what it found before it writes anything.

What comes across, in this order

Unsubscribes, bounces and complaints, first, as suppressions
Contacts, with your custom fields mapped
Each contact's unsubscribed flag, as a real suppression
Segments as contact books, or as Notix segments when they sit inside a bigger one
Topics, with each person's choice
Templates, as Notix templates
Broadcasts: drafts as drafts, sent ones as history
Webhooks, switched off with a new secret

Templates come across from SendGrid only. From anywhere else, rebuild them in the editor or start from the 54 starter templates.

A key just for the migration

API Keys → Create API Key.

Delete after

What happens to the key

Held sealed for at most an hour, and deleted when the import starts or ends. Never written to our database, never logged, never used to send.

Resend cannot tell us what a key may do. Delete the key at Resend when we are done.

At most 1 hour

Four weeks

How the migration goes

Day one
Connect or upload
Paste an API key, or upload your contacts and unsubscribes as CSV. Nothing is written until you have seen what we found.
During the import
Unsubscribes first
Every unsubscribe, bounce and complaint is written before the first contact, so nobody who opted out at your old provider can be emailed from Notix.
During the import
Your lists and fields
Contacts land in contact books you choose, with your custom fields mapped. Anyone suppressed arrives unsubscribed.
Before you send
Add Notix to your domain
Publish our records alongside your old provider's. Both keep sending; DNS has room for both.
Weeks one to four
Move volume gradually
A four-week plan, 15% to 100%, so mailbox providers see a sender that grows steadily. Switch the old provider off at the end, not the start.

Where things live

Resend's pages, and where to find them in Notix

The console uses the same words throughout: Emails, Broadcasts, Automations, Templates, Audience, Metrics, Logs, Webhooks and API keys.

Resend's names as their dashboard shows them; Notix names as the console shows them.
In Resend	In Notix	Good to know
Emails	Emails	Same idea, same place.
Logs	Logs	API requests, kept 30 days.
Metrics	Metrics	Same idea, same place.
Audiences and contacts	Audience	Audiences become contact books.
Segments	Audience > Segments	Same idea, same place.
Topics	Audience > Topics	Same idea, same place.
Broadcasts	Broadcasts	Same idea, same place.
Templates	Templates	The Migration Center copies them, with Resend's tags changed to Notix ones.
Domains	Domains	Same idea, same place.
API Keys	API keys	Same idea, same place.
Webhooks	Webhooks	Same idea, same place.
Receiving	Emails > Receiving	Same idea, same place.

SDKs and the API

Send through the API, side by side

The same email, as you send it today and as you send it with Notix.

Notix has official SDKs for Node.js, Python and PHP. Every other language uses the same JSON API.
Language	Resend	Notix
Node.js and TypeScript	`resend`	`notix-js`
Python	`resend`	`notix-sdk`
PHP and Laravel	`resend/resend-php`	`usenotix/notix-php`
Go, Ruby, Java, .NET and the rest	`Their libraries, or the REST API`	`REST API (JSON over HTTPS)`

Resend today

import { Resend } from "resend";

const resend = new Resend(process.env.RESEND_API_KEY);

await resend.emails.send({
  from: "Acme <orders@acme.com>",
  to: ["amara@example.com"],
  subject: "Your order is on its way",
  html: "<p>Your parcel left our warehouse today.</p>",
  reply_to: "support@acme.com",
  tags: [{ name: "category", value: "shipping" }],
});

Notix, with notix-js

import { Notix } from "notix-js";

const notix = new Notix(process.env.NOTIX_API_KEY);

const { data, error } = await notix.emails.send({
  from: "Acme <orders@acme.com>",
  to: "amara@example.com",
  replyTo: "support@acme.com",
  subject: "Your order is on its way",
  html: "<p>Your parcel left our warehouse today.</p>",
});

SMTP

SMTP settings, side by side

Resend's settings as their docs describe them; check your own account for the exact values.
Setting	Resend	Notix
Host	`smtp.resend.com`	`smtp.usenotix.dev`
Ports	`465 or 2465 (TLS), 587, 2587 or 25 (STARTTLS)`	`465 (TLS) or 587 (STARTTLS)`
Username	`resend`	`notix`
Password	`Your Resend API key`	`An API key`

The ports match, so most configs only need the host, the username and the key changed.

Webhooks

Your events, by their new names

Every Notix webhook is signed with X-Notix-Signature and retried up to six times. Point a new endpoint at Notix and match the names below.

Resend's event names as their docs list them; Notix names as they arrive in the X-Notix-Event header.
Resend	Notix	Good to know
`email.sent`	`email.sent`
`email.delivered`	`email.delivered`
`email.delivery_delayed`	`email.delivery_delayed`
`email.bounced`	`email.bounced`
`email.complained`	`email.complained`
`email.opened`	`email.opened`
`email.clicked`	`email.clicked`
`email.failed`	`email.failed`
`email.received`	`email.received`
`contact.created`	`contact.created`
`contact.updated`	`contact.updated`
`contact.deleted`	`contact.deleted`

For 30 days after a migration, a Notix webhook can also send Resend-shaped bodies, so the handler you have keeps working while you update it. They are signed the Notix way.

Security and safety

What protects your mail and your data

Suppressions before contacts

The importer enforces the order. Someone who opted out at Resend cannot get mail from Notix.

Keys with limits

Give each app the key it needs: full access, or sending only.

Signed webhooks

Every delivery carries an HMAC signature and a timestamp, so your handler can refuse anything forged or replayed.

Logs without secrets

API request logs are kept 30 days. Keys, codes, email bodies and attachments are hidden before a log is saved.

A domain that protects itself

If bounces or complaints climb past safe levels, the domain pauses before it damages your reputation. How it works.

A second pair of eyes

The first broadcast to imported contacts is reviewed by us before it goes out.

Idempotency

Retries never send twice

Send an Idempotency-Key header, up to 256 characters, with any send or batch. Notix keeps the result for 24 hours: a retry with the same key and body gets the first answer back, marked Idempotent-Replayed: true, and the same key with a different body is refused with a 409.

In notix-js it is one option: emails.send(payload, { idempotencyKey }). See it in action.

Also in your account

What else comes with Notix

SMS and one-time codes

Send sign-in codes by SMS or email, with a risk check first, and verify them in one call. One-time codes.

Connect your AI

Claude, ChatGPT or Cursor can work with Notix, and live keys ask you first above a limit you set. Connect your AI.

Pay in NGN, KES or USD

Top up a wallet in naira, shillings or dollars, and Pro renews from it. Pricing.

Inbound and forwarding

Receive mail on your own domain and forward it on, with an optional forwarded-message header. Inbound email.

Broadcasts and automations

Campaigns to a list, segment or topic, and email sequences that run themselves, behind the same key.

DNS

Your SPF record keeps both

A domain may only have one SPF record, so you add Notix to the line you already have rather than replacing it. Keep include:amazonses.com while Resend is still sending, add include:_spf.usenotix.dev beside it, and remove Resend's once you have switched off.

Pricing

What it costs

What you would pay on Notix

Migrating from

Emails a month

Provider	Plan	A month
Resend	Pro	$20
Notix	Pro	$15

You would save about $60 a year.

Resend list price, approximate, checked 12 Sep 2026: their pricing page. Prices change; check before you decide.

FAQ

Questions, answered

Do I have to rewrite my sending code?

Not on day one. Point your Resend send call at the Notix compat endpoint and it keeps working with your Notix key while you migrate. Then use the converter on this page to switch each call to the Notix SDK at your own pace.

Will my Resend unsubscribes come across?

Yes, and first. The import writes every unsubscribe, bounce and complaint before the first contact, so a person who opted out there cannot be emailed from Notix, even if the rest of the import stops halfway.

What happens to my Resend API key?

It is held sealed for at most an hour, and deleted when the import starts or ends. Notix never writes it to its database, never logs it and never sends email with it. Notix only reads with the key. Make a separate Resend key just for the migration and delete it when the migration is done.

Can I keep sending from Resend while I migrate?

Yes. Notix's DNS records sit beside Resend's, and the migration takes four weeks, from 15% of your volume to all of it. Switch Resend off at the end, not the start.

Is there someone who can help?

Yes. Book a free migration call from the contact page and we will look at your setup with you. The first broadcast to imported contacts is also reviewed by us before it goes out.

Start migrating off Resend.

Convert your code, bring your audience across with unsubscribes first, and move your volume over four weeks. We are happy to do it with you.