Migration guide

Keep Mailtrap for testing. Send for half the price.

You do not have to leave Mailtrap’s sandbox to move your live sending. Swap the production credentials, bring the suppression list, and keep testing where you test today.

On Mailtrap$30/mo
On Bluey$14.95/mo

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

In short

Moving live sending from Mailtrap to Bluey is about a day of code changes and one to two weeks of staged cutover — and you can keep Mailtrap’s Email Testing sandbox if your team likes it. Export the suppression list from Suppressions in the sidebar or the /api/accounts/{account_id}/suppressions endpoint (10 requests per minute). Replace live.smtp.mailtrap.io or bulk.smtp.mailtrap.io and calls to send.api.mailtrap.io; leave sandbox credentials alone. Recreate stored templates first, because sends that reference a deleted template UUID fail. At 100,000 emails a month Mailtrap Basic is $30 and Business $85 with a dedicated IP; Bluey Email API Essentials is $14.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
SuppressionsTransfersSuppressions in the sidebar, or the suppressions API. Import into Bluey first.
Live SMTP credentialsRebuildReplace live.smtp.mailtrap.io and bulk.smtp.mailtrap.io (user “api”, token as password).
API callsRebuildReplace POST send.api.mailtrap.io/api/send with Bluey’s REST API.
TemplatesRebuildMailtrap templates are referenced by UUID. Recreate them before you delete anything.
WebhooksRebuildMailtrap batches events; re-point delivery, bounce, spam and unsubscribe handlers to Bluey.
Sandbox testingTransfersKeep it. Sandbox and live sending use different hosts and tokens.
LogsPartialRetention is 3–30 days by plan, and no log export is documented. Save what you need first.

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 the suppression listExport from the Suppressions page, or page through the API — it is rate-limited to 10 requests per 60 seconds, so a large list takes a while. Import it into Bluey before any send.
  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 webhooksMailtrap sends events in batches of up to 500 every 30 seconds. Check that your handlers cope with Bluey’s event format before the final switch.
  6. 6Week 3
    Remove Mailtrap's DNS records lastOnly once nothing has been sent through Mailtrap 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 Mailtrap

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

Replacing the sandbox credentials instead of the live onesMailtrap’s sandbox uses sandbox.api.mailtrap.io with its own tokens, and Mailtrap itself calls swapping SMTP credentials between them error-prone. Check which credentials you are replacing — the live ones are on live.smtp.mailtrap.io and send.api.mailtrap.io.
Deleting templates while code still calls themA send that references a deleted Mailtrap template UUID fails. Leave templates in place until no traffic goes through Mailtrap.
Forgetting the bulk streamIf you also send bulk mail through bulk.smtp.mailtrap.io, it is a second set of credentials to move.

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 keep using Mailtrap for testing?

Yes. The sandbox is separate from live sending, with its own host and tokens, so you can move production mail to Bluey and keep testing in Mailtrap.

How much will I save?

At 100,000 emails a month, Mailtrap Basic is $30 and Business is $85 with a dedicated IP (checked 19 November 2026). Bluey Email API Essentials is $14.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 Mailtrap handles the rest, and compare delivery and cost on your own data before you move the domain.