A key just for the migration
Account → Extras → API keys.
Delete afterNotix reads your Mailchimp 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 Mailchimp account keeps sending the whole time.
Mailchimp sends one-to-one email through its separate transactional product, so that is the code this reads. Your audiences and campaigns migrate with the Migration Center below.
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",
bcc: "ops@acme.com",
subject: "Your order is on its way",
html: "<p>Your parcel left our warehouse today.</p>",
});
The converter reads the code as text in your browser. It does not run it, store it or send it anywhere.
Paste a Mailchimp key made just for the migration in the Migration Center. It shows you what it found before it writes anything.
Templates come across from SendGrid only. From anywhere else, rebuild them in the editor or start from the 54 starter templates.
Account → Extras → API keys.
Delete afterHeld 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.
Mailchimp cannot tell us what a key may do. Delete the key at Mailchimp when we are done.
At most 1 hourPaste an API key, or upload your contacts and unsubscribes as CSV. Nothing is written until you have seen what we found.
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.
Contacts land in contact books you choose, with your custom fields mapped. Anyone suppressed arrives unsubscribed.
Publish our records alongside your old provider's. Both keep sending; DNS has room for both.
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.
The console uses the same words throughout: Emails, Broadcasts, Automations, Templates, Audience, Metrics, Logs, Webhooks and API keys.
| In Mailchimp | In Notix | Good to know |
|---|---|---|
| Audience | Audience | Each audience becomes a contact book. |
| Tags and segments | Audience > Segments | Same idea, same place. |
| Groups (interests) | Audience > Topics | Same idea, same place. |
| Campaigns | Broadcasts | Same idea, same place. |
| Customer Journeys | Automations | Email, delay, wait for event, if / else, update contact and add to segment steps. |
| Email templates | Templates | Same idea, same place. |
| Reports | Metrics | Same idea, same place. |
| Domains | Domains | Same idea, same place. |
| API keys | API keys | Same idea, same place. |
| Audience webhooks | Webhooks | Same idea, same place. |
| Transactional (Mandrill) outbound activity | Emails | Same idea, same place. |
The same email, as you send it today and as you send it with Notix.
| Language | Mailchimp | Notix |
|---|---|---|
| Node.js and TypeScript | @mailchimp/mailchimp_transactional | notix-js |
| Python | mailchimp-transactional | notix-sdk |
| PHP and Laravel | mailchimp/transactional | usenotix/notix-php |
| Go, Ruby, Java, .NET and the rest | Their libraries, or the Transactional API | REST API (JSON over HTTPS) |
const mailchimp = require("@mailchimp/mailchimp_transactional")(process.env.MANDRILL_API_KEY);
await mailchimp.messages.send({
message: {
from_email: "orders@acme.com",
from_name: "Acme",
subject: "Your order is on its way",
html: "<p>Your parcel left our warehouse today.</p>",
to: [
{ email: "amara@example.com", type: "to" },
{ email: "ops@acme.com", type: "bcc" },
],
tags: ["shipping"],
},
});
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",
bcc: "ops@acme.com",
subject: "Your order is on its way",
html: "<p>Your parcel left our warehouse today.</p>",
});
| Setting | Mailchimp | Notix |
|---|---|---|
| Host | smtp.mandrillapp.com | smtp.usenotix.dev |
| Ports | 587 or 25 (STARTTLS), 465 (TLS) | 465 (TLS) or 587 (STARTTLS) |
| Username | Any value, often your account name | notix |
| Password | A Transactional API key | An API key |
The SMTP settings are for Mailchimp Transactional. Marketing campaigns migrate as broadcasts, not over SMTP.
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.
| Mailchimp | Notix | Good to know |
|---|---|---|
send | email.sent | |
deferral | email.delivery_delayed | |
hard_bounce, soft_bounce | email.bounced | The bounce type is in the payload. |
reject | email.rejected | |
open | email.opened | |
click | email.clicked | |
spam | email.complained | |
unsub (or unsubscribe on an audience) | contact.unsubscribed | |
subscribe (audience) | contact.subscribed | |
cleaned (audience) | No direct match | Cleaned addresses arrive as hard bounces in your suppression list instead. |
The importer enforces the order. Someone who opted out at Mailchimp cannot get mail from Notix.
Give each app the key it needs: full access, or sending only.
Every delivery carries an HMAC signature and a timestamp, so your handler can refuse anything forged or replayed.
API request logs are kept 30 days. Keys, codes, email bodies and attachments are hidden before a log is saved.
If bounces or complaints climb past safe levels, the domain pauses before it damages your reputation. How it works.
The first broadcast to imported contacts is reviewed by us before it goes out.
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.
Send sign-in codes by SMS or email, with a risk check first, and verify them in one call. One-time codes.
Claude, ChatGPT or Cursor can work with Notix, and live keys ask you first above a limit you set. Connect your AI.
Top up a wallet in naira, shillings or dollars, and Pro renews from it. Pricing.
Receive mail on your own domain and forward it on, with an optional forwarded-message header. Inbound email.
Campaigns to a list, segment or topic, and email sequences that run themselves, behind the same key.
A domain may only have one SPF record, so you add Notix to the line you already have rather than replacing it. Keep include:servers.mcsv.net while Mailchimp is still sending, add include:_spf.usenotix.dev beside it, and remove Mailchimp's once you have switched off.
We haven't recorded Mailchimp's list prices for the plan this page is about, so there is no comparison here rather than a figure for a different product of theirs. Notix pricing is on one page, and a migration call can work your own numbers through with you.
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.