Migration guide

Bring the suppression list. Get more than 3 days of logs.

Elastic Email’s own guide says the suppression list must be exported separately from contacts. Do that first, and the rest of the move is a credentials change.

On Elastic Email$19–49/mo
On Bluey$9.95/mo

Transactional API, 50,000 emails/month · Typical migration: About a day of code, 1–2 weeks of cutover

In short

Moving the Elastic Email API to Bluey is about a day of code changes and one to two weeks of staged cutover. Export suppressions first — Elastic Email says they must be exported separately from contacts — using the Suppressions list or the /v4/suppressions endpoints for bounces, complaints and unsubscribes. Replace smtp.elasticemail.com or calls to /v4/emails/transactional, recreate stored templates and re-point webhooks. Export events with /v4/events/export before you leave: logs are kept 3 days on Free and Starter and 7 on Pro. At 50,000 emails a month Elastic Email is $19 on Starter or $49 on Pro; Bluey Email API Essentials is $9.95.

What transfers, and what you rebuild

Stated up front, because finding out mid-migration is how a two-day job becomes a two-week one.

WhatStatusDetail
SuppressionsTransfersExported separately from contacts: /v4/suppressions/bounces, /complaints and /unsubscribes. Import into Bluey first.
SMTP credentialsRebuildReplace smtp.elasticemail.com (port 2525 by default).
API callsRebuildReplace /v4/emails/transactional and the X-ElasticEmail-ApiKey header with Bluey’s REST API.
TemplatesRebuildElastic Email stores templates server-side. Recreate the ones you use, or render in your app.
WebhooksRebuildRe-point sent, opened, clicked, unsubscribed, abuse-report and error events.
Event historyPartialExport with /v4/events/export before you leave. Logs last 3–7 days by plan.
Marketing contactsPartialIf you also use Elastic Email’s marketing product, export those contacts too; Bluey runs marketing and API on one account.

The migration plan, in order

  1. 1Day 1 — before any send
    Authenticate your sending domainPublish SPF, DKIM and, if you use one, DMARC records for the domain you will send from. Gmail and Yahoo have required authentication and one-click unsubscribe from bulk senders since February 2024, and an unauthenticated first send from a new platform is the fastest route to the spam folder. This is a DNS change and takes about fifteen minutes; allow up to a few hours for propagation.
  2. 2Day 1
    Export suppressions and recent eventsPull bounces, complaints and unsubscribes from the suppressions endpoints, and start an events export for anything you need to keep. With 3 to 7 days of logs, waiting until after the cutover means losing them.
  3. 3Day 2
    Put the provider behind a switch in your codeWrap the send call so the provider is chosen by configuration, not hard-coded. That lets you route a small share of traffic to Bluey, compare, and roll back in seconds if anything looks wrong — without a deploy.
  4. 4Week 1–2
    Shift traffic in stagesSend 5–10% of transactional mail through Bluey for a few days, watch delivery and bounce rates in the activity log, then move to half and finally all of it. Keep the old provider live until a full week passes with nothing routed to it.
  5. 5Week 2
    Re-point webhooksPoint your bounce and complaint handlers at Bluey’s event webhooks and test each one before the final switch.
  6. 6Week 3
    Remove Elastic Email's DNS records lastOnly once nothing has been sent through Elastic Email for a week, delete its DKIM, return-path and tracking records. Removing them earlier breaks authentication on any message still in flight or retried from a queue.

Mistakes people make leaving Elastic Email

Each of these is recoverable, and each is much cheaper to avoid than to fix.

Leaving the suppression list behindExporting subscribers without also exporting unsubscribes, bounces and complaints is the single most common migration error. The result is that people who opted out of Elastic Email receive your first Bluey campaign — which is a compliance breach in most markets and a fast way to breach Gmail's 0.3% complaint threshold on your very first send. Export suppressions and import them before anything else.
Running out of log history mid-migrationElastic Email keeps 3 days of logs on Free and Starter and 7 on Pro. If you need delivery evidence, export events on day one, not at the end.
Using the wrong SMTP credentialElastic Email’s older guides use the API key as the SMTP password, and newer ones use dedicated SMTP credentials. Check which your app uses so you replace the right thing.

Migration FAQ

What does the Bluey Email API include?

SMTP and a REST API, SPF and DKIM domain authentication, suppression management, analytics and inbound parse. Essentials has 2 event webhooks, 5 API keys and 3 days of searchable activity; Pro adds 5 webhooks, unlimited API keys, subusers and 7 days of activity. A dedicated IP is an add-on on both.

Can I move Elastic Email marketing and API together?

Yes. Bluey runs marketing campaigns and the Email API on one account, so export both your marketing contacts and your API suppressions and bring them across together.

How much will I save?

At 50,000 emails a month, Elastic Email is $19 on Starter or $49 on Pro, with a private IP as a $40–50 add-on (checked 19 November 2026). Bluey Email API Essentials is $9.95; a dedicated IP is an add-on.

Free · 7 days

Run both in parallel. Then decide.

Seven days of full access, no credit card. Import a segment, send from Bluey while Elastic Email handles the rest, and compare delivery and cost on your own data before you move the domain.