Switching from MailPace? 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.
MailPace's send endpoint (POST https://app.mailpace.com/api/v1/send) uses lowercase field names run together (htmlbody, textbody, replyto), a MailPace-Server-Token header and comma-separated address strings. The token is per domain. It is also commonly used over SMTP, where the token is both username and password.
curl -X POST https://app.mailpace.com/api/v1/send \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "MailPace-Server-Token: $MAILPACE_API_TOKEN" \
-d '{
"from": "Acme <[email protected]>",
"to": "[email protected]",
"subject": "Welcome",
"htmlbody": "<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>"
}'MailPace fields and their Envello equivalents
| MailPace | Envello |
|---|---|
| MailPace-Server-Token header | Authorization: Bearer <API key> |
| from, to, subject | from, to, subject |
| htmlbody, textbody | html, text |
| cc, bcc (comma-separated string) | cc, bcc (string or array) |
| replyto | reply_to |
| attachments: [{ name, content, content_type, cid }] | attachments: [{ filename, content (base64), contentType }] |
| tags (array or single string) | tags: [{ name, value }]; for example "welcome" becomes { name: "type", value: "welcome" } (letters, digits, _ and - only) |
| inreplyto, references, list_unsubscribe | headers: In-Reply-To, References, List-Unsubscribe |
| X-MailPace-Tags header (SMTP) | tags in the REST body (the SMTP relay doesn't map headers to tags) |
| SMTP username and password (the domain's API token) | Any non-empty username (envello in the examples) and your Envello API key as the password |
One token per domain
A MailPace token belongs to one domain, and from must use that domain. If you hold one token per domain, collect them in your config, then verify each sending domain in Envello (SPF and DKIM) before you send from it.
Tags over SMTP
MailPace reads tags from an X-MailPace-Tags header when you send over SMTP. Envello's SMTP relay doesn't turn headers into tags, so use the REST API with the tags field if you rely on tags for filtering.
Attachments
MailPace attachments use name and content_type, and its docs list the allowed file types. Envello attachments use filename and contentType with base64 content, or a url that Envello fetches.
The migration, end to end
1. Add Envello DNS records alongside your existing MailPace 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 MailPace
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 MailPace 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 MailPace 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 MailPace 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 MailPace 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 →