Envello
Mailtrap alternative

Switching from Mailtrap? Move your transactional email to Envello

A step-by-step guide: DNS setup alongside your existing records, the sending-code swap, a dual-send cutover window, and verification with 90 days of searchable logs on Pro.

Mailtrap's send API (POST https://send.api.mailtrap.io/api/send) uses address objects ({ email, name }) and an API token sent as a Bearer token or an Api-Token header. Envello's body is flat and uses a Bearer key. The field names are close, so the work is reshaping addresses, tags and templates.

Before: Mailtrap Node SDK
import { MailtrapClient } from "mailtrap";

const mailtrap = new MailtrapClient({ token: process.env.MAILTRAP_API_KEY });

await mailtrap.send({
  from: { name: "Acme", email: "[email protected]" },
  to: [{ email: "[email protected]" }],
  subject: "Welcome",
  html: renderedHtml,
});
After: Envello Node SDK
import { Envello } from "envello";

const envello = new Envello(process.env.ENVELLO_API_KEY);

await envello.emails.send({
  from: "Acme <[email protected]>",
  to: "[email protected]",
  subject: "Welcome",
  html: renderedHtml,
});
Before: Mailtrap REST
curl -X POST https://send.api.mailtrap.io/api/send \
  -H "Authorization: Bearer $MAILTRAP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": { "email": "[email protected]", "name": "Acme" },
    "to": [{ "email": "[email protected]" }],
    "subject": "Welcome",
    "html": "<p>Welcome aboard</p>"
  }'
After: Envello REST
curl -X POST https://api.envello.dev/emails \
  -H "Authorization: Bearer $ENVELLO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Acme <[email protected]>",
    "to": "[email protected]",
    "subject": "Welcome",
    "html": "<p>Welcome aboard</p>"
  }'
Field mapping

Mailtrap fields and their Envello equivalents

MailtrapEnvello
Authorization: Bearer or Api-Token headerAuthorization: Bearer <API key>
from: { email, name }from: "Name <email>"
to, cc, bcc: [{ email, name }]to, cc, bcc (string or array of "Name <email>")
reply_to: { email, name }reply_to: "Name <email>"
subject, text, htmlsubject, text, html
headers (map of strings)headers (map of strings)
attachments: [{ content, filename, type }]attachments: [{ content (base64), filename, contentType }]
category (one string)tags: [{ name: "category", value: "..." }]
custom_variables (map of strings)tags: [{ name, value }] (letters, digits, _ and - only)
template_uuid + template_variablestemplate_id + variables for plain {{variable}} templates; otherwise render the HTML in your code and send it as html
Bulk stream host (bulk.api.mailtrap.io)Same endpoint, with stream: "broadcast"

Templates

Mailtrap templates take Handlebars variables. Envello's stored templates do {{variable}} substitution only, with flat string values and an Envello template id (a UUID). Recreate simple templates in Envello. For templates with conditionals or loops, render the HTML in your code and send it as html.

Transactional and bulk streams

Mailtrap sends transactional and bulk mail from two hosts. Envello uses one endpoint, and a message is transactional unless you set stream: "broadcast". A broadcast message goes to one recipient per message and gets an unsubscribe link added for you. Keep password resets and receipts on the default stream.

Categories and custom variables

Mailtrap's category is a single string and custom_variables is a map. Both become Envello tags, which are name and value pairs that accept only letters, digits, underscores and dashes. Rewrite any value with spaces or dots before you send.

Four steps

The migration, end to end

1. Add Envello DNS records alongside your existing Mailtrap records

Verify your sending domain in Envello and add the SPF include, DKIM CNAMEs, and the return-path CNAME Envello generates. Keep your existing records in place: both providers can authenticate the same domain at once, which is what makes a safe cutover possible. Only remove the old records after Envello has been the sole sender for a few days.

2. Swap the sending call

Point your outbound path at Envello's SDK. The request shape (from, to, subject, html, text, cc, bcc, reply_to, headers, attachments) mirrors the common transactional-API pattern, so the diff in most codebases is the import line, the client instantiation, and the API key environment variable. Templates rendered client-side (React Email, MJML, plain string) plug straight into the html field.

3. Dual-send during the cutover window

Route a small percentage of traffic to Envello first, or fork production sends so each message goes through both providers to non-critical recipients while you verify. Envello's log search shows every send, bounce, complaint, open, and click for 90 days on Pro (7 days on Free, up to 365 days on Scale) so you can confirm parity before flipping the rest of the traffic.

4. Cut over and retire Mailtrap

Once Envello has handled a full week of production traffic without regressions on your key deliverability metrics (bounce rate, complaint rate, delivered rate per domain), route 100% of sends through Envello. Export your Mailtrap suppression list and add each address with Envello's POST /suppressions so previously-suppressed recipients stay suppressed. Remove the old DNS records last.

Sending HTML from React components? See the React Email guide for how render() plugs straight into the html field.

FAQ

Migration questions

Can I keep sending through Mailtrap while I test Envello?+

Yes. Both providers authenticate the same domain via separate DKIM selectors and their own SPF include, so parallel sending is safe as long as each provider's records are in place. Keep the old records until Envello has been the sole production sender for a few days, then remove them.

What happens to my suppression list?+

Export it from Mailtrap and add each address with POST /suppressions (a full-access API key works, one address per request), or one by one in the dashboard. If you skip this step, addresses that Mailtrap had marked as bounced or complained can send successfully through Envello on day one and generate the same bounce or complaint again, which harms deliverability. Import first, cut over second.

Do I need to change my webhook consumer?+

Yes, at least the payload shape. Envello's webhooks send delivered, bounced, complained, opened, and clicked events with HMAC-signed payloads; the field names and signature header are documented at envello.dev/docs. If your current consumer branches on your existing provider's specific bounce-subtype taxonomy, decide upfront how each subtype maps to Envello's simpler event set before writing the new handler.

How long does the whole migration take?+

For a codebase with a single central sending path, most teams complete the code change in under an hour. Add DNS propagation (up to 48 hours, usually much less), a dual-send verification window (a few days), and one week of production monitoring before retiring the old provider. Plan for two to three weeks end-to-end, not one afternoon.

Free tool

Check your own GDPR/DPA gaps before you switch

8 questions covering data residency, retention, and subprocessor documentation, the same things a security questionnaire asks.

Run the free checklist →
Ready to migrate?

Start free and migrate at your own pace.