Envello
Elastic Email alternative

Switching from Elastic Email? 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.

Elastic Email's v4 API sends through POST https://api.elasticemail.com/v4/emails/transactional with the key in an X-ElasticEmail-ApiKey header. The body splits into Recipients and Content, uses PascalCase names, and carries HTML and plain text as an array of body parts. Envello's body is flat (from, to, subject, html at the top level) and uses a Bearer key. The send call is a reshape; merge fields and stored templates are the parts that need a decision.

Before: Elastic Email Node SDK
const ElasticEmail = require("@elasticemail/elasticemail-client");
const { promisify } = require("util");

const client = ElasticEmail.ApiClient.instance;
client.authentications["apikey"].apiKey = process.env.ELASTICEMAIL_API_KEY;

const emails = new ElasticEmail.EmailsApi();
const send = promisify(emails.emailsTransactionalPost.bind(emails));

await send({
  Recipients: { To: ["[email protected]"] },
  Content: {
    From: "Acme <[email protected]>",
    Subject: "Welcome",
    Body: [{ ContentType: "HTML", Content: 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: Elastic Email REST
curl -X POST https://api.elasticemail.com/v4/emails/transactional \
  -H "X-ElasticEmail-ApiKey: $ELASTICEMAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "Recipients": { "To": ["[email protected]"] },
    "Content": {
      "From": "Acme <[email protected]>",
      "Subject": "Welcome",
      "Body": [{ "ContentType": "HTML", "Content": "<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

Elastic Email fields and their Envello equivalents

Elastic EmailEnvello
X-ElasticEmail-ApiKey: <API key>Authorization: Bearer <API key>
Content.From ("Name <email>")from: "Name <email>" (same format)
Recipients.To, Recipients.CC, Recipients.BCC (string arrays)to, cc, bcc
Content.Subjectsubject
Content.Body: [{ ContentType: "HTML" | "PlainText", Content }]html, text
Content.ReplyToreply_to
Content.Headersheaders (map)
Content.Attachments: [{ BinaryContent, Name, ContentType }]attachments: [{ filename, contentType, content (base64) }]
Content.AttachFiles (names of uploaded files)attachments: [{ url }] pointing at a file you host
Content.TemplateName + Content.Mergetemplate_id + variables for plain {{variable}} templates; otherwise render the HTML in your code and send it as html
Options.TimeOffset (minutes)send_at (ISO 8601 with an offset)
Options.ChannelNametags: [{ name, value }]; for example channel "welcome" becomes { name: "channel", value: "welcome" } (letters, digits, _ and - only)
Idempotency-Key headerIdempotency-Key header (idempotencyKey option in the Node SDK)
Content.EnvelopeFrom, Options.PoolNameNo equivalent field; drop them

Merge fields

Elastic Email merge fields use single braces in the body, like {firstname}. Envello's stored templates use double braces, {{firstname}}, with flat string values. Change the placeholders when you recreate a template in Envello, or render the email in your own code and send it as html.

Async style

The Elastic Email Node SDK takes Node-style callbacks, so most codebases wrap it with util.promisify. Envello's SDK returns promises, so the wrapper goes away with the swap.

Webhooks

Elastic Email signs webhooks with X-ElasticEmail-Timestamp and X-ElasticEmail-Signature: v1=<hex>, an HMAC-SHA256 over the timestamp, method, path and raw body. Envello sends Envello-Signature: t=<unix seconds>,v1=<hex>, an HMAC-SHA256 over the timestamp, a dot and the raw body. Both want the raw body, so the verifier changes only in the header parsing and the signed string.

Four steps

The migration, end to end

1. Add Envello DNS records alongside your existing Elastic Email 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 Elastic Email

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 Elastic Email 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 Elastic Email 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 Elastic Email 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 Elastic Email 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?

Create your account and migrate at your own pace.