Migration guide

Stop running the mail server. Keep your list and your history.

Sendy’s list exports already include each subscriber’s status, and its suppression list exports as CSV. This is a clean migration, and afterwards there is no server, SES account or bounce pipeline left to look after.

Typical migration: 1–2 days of work, over about a week

In short

Moving from Sendy to Bluey takes a day or two. Export each list as CSV — since version 3.0.6 the export includes Unsubscribed, Bounced, Marked as spam and Unconfirmed statuses — and export Sendy’s suppression list and blocked domains, which have exported as CSV since 4.0.8. Also check your Amazon SES account-level suppression list, which Sendy does not see. Autoresponders and templates have no export, so rebuild them. After the move, Bluey Grow covers 100,000 emails a month for $45 with sending infrastructure, bounce and complaint handling, automation and reporting included — the parts you were building and maintaining yourself around Sendy.

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
SubscribersTransfersExport each list as CSV. Statuses come with it.
Unsubscribed, bounced, spamTransfersIncluded in the list export as statuses. Import them into Bluey as suppressions, first.
Suppression list and blocked domainsTransfersExportable as CSV since Sendy 4.0.8.
SES account suppression listPartialHeld by AWS, not Sendy. Read it with aws sesv2 list-suppressed-destinations.
TemplatesRebuildSendy has duplication but no template export. Copy the HTML you need.
AutorespondersRebuildNo export. Rebuild in Bluey, where the common flows are templated.
Subscribe forms and API callsRebuildReplace the Sendy form HTML and any calls to its /subscribe endpoint.

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 lists, suppressions and the SES listExport every list, then the suppression list and blocked domains. Then pull your SES account-level suppression list with the AWS CLI. It holds hard bounces only and does not receive Gmail complaints, but it can contain addresses Sendy never recorded.
  3. 3Day 1
    Import suppressions before contactsCombine Sendy’s suppressions, the bounced and spam statuses from the list exports, and the SES list into one suppression import for Bluey. Then import subscribers, leaving Unconfirmed out.
  4. 4Day 2
    Rebuild autoresponders and swap formsRebuild your autoresponders in Bluey, then replace the Sendy subscribe form on your site. If your app calls Sendy’s /subscribe API, point it at Bluey’s API instead.
  5. 5Week 1–2
    Run Bluey and Sendy in parallelSplit the audience rather than duplicating it: send to one segment from Bluey and leave the rest on Sendy. You get a like-for-like comparison of delivery, engagement and cost on your own data, and nobody receives the same campaign twice. Do not run both against the same contacts — that is the one way to make a careful migration look sloppy to your readers.
  6. 6Week 2 — gradually
    Ramp volume rather than switching itStart with your most engaged segment — people who opened or clicked in the last 30 days — and increase volume over several days. Receiving servers judge a new sending pattern partly on engagement, so leading with your best contacts builds reputation, while leading with your whole list including two-year-dormant addresses damages it. If you were on a dedicated IP, treat the new one as cold and warm it deliberately.
  7. 7Week 3
    Wind down SES and the serverOnce Bluey has run a full cycle, stop sending through SES and retire the server. Keep your exported SES suppression list: AWS deletes the account-level list 90 days after sending is paused.

Mistakes people make leaving Sendy

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

Exporting from Sendy but not from SESSES keeps its own suppression list per account and region, separate from Sendy’s. Skip it and addresses that hard-bounced at the SES level can come back on your first Bluey send.
Shutting down SES before the last bounces arriveBounces and complaints for your final Sendy campaigns can arrive days later through SNS. Keep SES and the bounce webhook running until a week passes with nothing sent, then export the suppression lists one last time.
Importing the whole list, including the dead partA migration is the best opportunity you will get to drop contacts who have not engaged in a year or more. Bringing them across because storage is free is a mistake: they do not open, some addresses have gone stale and now hard-bounce, and a few have become spam traps. They will not cost you money on send-based billing, but they will cost you deliverability on the send that matters most — your first.

Migration FAQ

What does Sendy really cost to run?

More than the SES bill. Add the licence, a server, and the time spent on updates, SNS and IAM setup for bounces, SES sandbox and suspension risk, and building automation by hand. Bluey Grow is $45 a month for 100,000 emails with all of that included.

Do Sendy exports include unsubscribes and bounces?

Yes. Since version 3.0.6, list exports include Unsubscribed, Bounced, Marked as spam and Unconfirmed statuses, and the suppression list has exported as CSV since 4.0.8.

Do I need to do anything in AWS?

Export the SES account-level suppression list before you stop sending, because AWS deletes it 90 days after sending is paused.

Free · 7 days

Run both in parallel. Then decide.

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