Switching from Amazon SES? 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.
The SESv2 SendEmail API nests everything under Content (Simple, Raw or Template) and Destination, uses PascalCase names, and is signed with AWS credentials, which the SDK does for you. Envello takes one flat JSON body with a Bearer API key. Envello sends through SES underneath, so a move from direct SES calls changes the API surface, not the delivery infrastructure.
import { SESv2Client, SendEmailCommand } from "@aws-sdk/client-sesv2";
const ses = new SESv2Client({ region: "eu-west-1" });
await ses.send(
new SendEmailCommand({
FromEmailAddress: "Acme <[email protected]>",
Destination: { ToAddresses: ["[email protected]"] },
Content: {
Simple: {
Subject: { Data: "Welcome" },
Body: { Html: { Data: renderedHtml } },
},
},
}),
);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,
});await ses.send(
new SendEmailCommand({
FromEmailAddress: "Acme <[email protected]>",
Destination: { ToAddresses: ["[email protected]"] },
ReplyToAddresses: ["[email protected]"],
EmailTags: [{ Name: "category", Value: "invoice" }],
Content: {
Simple: {
Subject: { Data: "Your invoice" },
Body: { Html: { Data: renderedHtml } },
Attachments: [
{
FileName: "invoice.pdf",
ContentType: "application/pdf",
RawContent: pdfBytes,
},
],
},
},
}),
);await fetch("https://api.envello.dev/emails", {
method: "POST",
headers: {
Authorization: "Bearer " + process.env.ENVELLO_API_KEY,
"Content-Type": "application/json",
},
body: JSON.stringify({
from: "Acme <[email protected]>",
to: "[email protected]",
reply_to: "[email protected]",
subject: "Your invoice",
html: renderedHtml,
tags: [{ name: "category", value: "invoice" }],
attachments: [
{ filename: "invoice.pdf", contentType: "application/pdf", content: pdfBase64 },
],
}),
});Amazon SES fields and their Envello equivalents
| Amazon SES | Envello |
|---|---|
| AWS credentials, SigV4 signing (done by the SDK) | Authorization: Bearer <API key> |
| FromEmailAddress | from |
| Destination.ToAddresses / CcAddresses / BccAddresses | to / cc / bcc (string or array) |
| ReplyToAddresses (array) | reply_to (one address) |
| Content.Simple.Subject.Data | subject |
| Content.Simple.Body.Html.Data / Text.Data | html / text |
| Content.Simple.Headers: [{ Name, Value }] | headers: { name: value } |
| Content.Simple.Attachments: [{ FileName, ContentType, RawContent }] | attachments: [{ filename, contentType, content (base64) }] |
| Content.Raw.Data (MIME message) | No equivalent; pass the parts as from, to, subject, html, text and attachments |
| EmailTags: [{ Name, Value }] | tags: [{ name, value }] (letters, digits, _ and - only) |
| Content.Template: { TemplateName, TemplateData } | template_id plus variables for plain {{variable}} templates; otherwise render the HTML in your code and send it as html |
| ConfigurationSetName (event publishing) | Envello webhooks: delivered, bounced, complained, opened, clicked, HMAC-signed |
Calling SES directly vs a layer on top
Calling SES directly is a fair choice for low volume or if you already run on AWS tooling. When it stops being one is covered in /blog/migrate-aws-ses-direct-to-envello. Your domain's reputation with mailbox providers is tied to the domain, so it moves with you. The domain still needs SPF and DKIM records verified in Envello.
Raw MIME messages
If you build MIME yourself and send it as Content.Raw, you'll need to split it into fields. Most libraries that produce MIME also expose the parts (subject, html, text, attachments), so the change is mapping them to the Envello body instead of serialising them.
Notifications
SES reports bounces and complaints through SNS or event destinations you configure. In Envello you register a webhook URL instead and verify the HMAC signature on each event. The SNS subscriber code can be deleted once the new handler is live.
The migration, end to end
1. Add Envello DNS records alongside your existing Amazon SES 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 Amazon SES
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 Amazon SES suppression list and add each address with Envello's POST /suppressions so previously-suppressed recipients stay suppressed. Remove the old DNS records last.
For Amazon SES-specific API detail (field mapping, webhook payload differences, template equivalents), see the deep-dive guide.
Migration questions
Can I keep sending through Amazon SES 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 Amazon SES 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 Amazon SES 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 →