Switching from SparkPost? 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.
SparkPost sends through one endpoint, POST /api/v1/transmissions, with a recipients array and a content object, and takes the raw API key in the Authorization header. Envello's body is flat (from, to, subject, html at the top level) and uses a Bearer key. SparkPost runs a separate EU region (api.eu.sparkpost.com), so data location alone isn't a reason to switch. The send call is a reshape; substitution_data and stored templates are the parts that need a decision.
const SparkPost = require("sparkpost");
const client = new SparkPost(process.env.SPARKPOST_API_KEY, {
origin: "https://api.eu.sparkpost.com:443",
});
await client.transmissions.send({
content: {
from: { name: "Acme", email: "[email protected]" },
subject: "Welcome",
html: renderedHtml,
},
recipients: [{ address: { email: "[email protected]" } }],
});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,
});curl -X POST https://api.eu.sparkpost.com/api/v1/transmissions \
-H "Authorization: $SPARKPOST_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"options": { "transactional": true },
"recipients": [{ "address": { "email": "[email protected]" } }],
"content": {
"from": { "name": "Acme", "email": "[email protected]" },
"subject": "Welcome",
"html": "<p>Welcome aboard</p>"
}
}'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>"
}'SparkPost fields and their Envello equivalents
| SparkPost | Envello |
|---|---|
| Authorization: <API key> (no scheme) | Authorization: Bearer <API key> |
| content.from (string or { name, email }) | from: "Name <email>" |
| recipients: [{ address: { email, name } }] | to (string or array of "Name <email>") |
| CC and BCC (extra recipients in the transmission) | cc, bcc as separate fields |
| content.subject, content.html, content.text | subject, html, text |
| content.reply_to | reply_to |
| content.headers | headers (map) |
| content.attachments: [{ name, type, data }] | attachments: [{ filename, contentType, content (base64) }] |
| options.start_time | send_at (ISO 8601 with an offset) |
| campaign_id, metadata, recipient tags | tags: [{ name, value }]; for example campaign_id "welcome" becomes { name: "campaign", value: "welcome" } (letters, digits, _ and - only) |
| content.template_id + substitution_data | template_id + variables for plain {{variable}} templates; otherwise render the HTML in your code and send it as html |
| Idempotency-Key header | Idempotency-Key header (idempotencyKey option in the Node SDK) |
| content.email_rfc822 (raw MIME) | No equivalent; pass the parts as fields |
One transmission, many recipients
A SparkPost transmission can carry many recipients, each with its own substitution_data, and the template language fills in each copy. Envello sends one email per item. Render each recipient's email in your code and post up to 100 to POST /emails/batch, which returns a result per item.
Templates
SparkPost's template language supports conditionals and loops. Envello's stored templates do {{variable}} substitution only, with flat string values. Recreate simple templates in Envello and send them with template_id and variables; render anything with logic in your own code (React Email, MJML, any engine) and send it as html.
Webhooks
SparkPost batches events into arrays of msys objects. Envello posts one HMAC-signed event per request (delivered, bounced, complained, opened, clicked), so the handler drops its batch loop and verifies the Envello-Signature header on each request.
The migration, end to end
1. Add Envello DNS records alongside your existing SparkPost 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 SparkPost
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 SparkPost 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.
Migration questions
Can I keep sending through SparkPost 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 SparkPost 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 SparkPost 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.
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 →