Moving from Sendy to Listmonk

Sendy got slow once your list got big, or you're tired of patching PHP. We've run Sendy for customers since 2019, so we know where everything lives in its database. We'll move it over for you.

Start your Listmonk

What we move

  • Subscribers, with their custom fields
  • Lists. Each Sendy brand can become its own set of lists, or its own Listmonk if you'd rather keep them apart.
  • Unsubscribes, bounces and spam complaints, so they stay blocked. This is the part people get wrong when they do it themselves with a CSV export, and it's the part that hurts your sending reputation.
  • Your SES setup. Same AWS account, same verified domains. We point Listmonk at it and set up bounce handling.

What doesn't come across

Better to hear this now than after the move.

  • Autoresponders. Listmonk doesn't have them. If your Sendy autoresponders matter to you, tell us before you move and we'll talk through options honestly, including staying on Sendy.
  • Past campaign reports. Opens and clicks from old Sendy campaigns stay in your Sendy export, not in Listmonk.
  • Templates come across as HTML. Most work as they are; some need small fixes for Listmonk's template tags, which we do.

How it goes

  1. You start a Listmonk with us and pick "Sendy" when we ask where you're coming from.
  2. We ask for a database export from your Sendy (or, if you're on Sendybay, we already have it).
  3. We import it into your new Listmonk and send you a list of what moved, with counts per list, so you can check nothing's missing.
  4. You send a test campaign. When you're happy, you switch your signup forms over.

Keep Sendy running until you've sent your first real campaign from Listmonk. Then turn it off.

Should you move at all?

If Sendy works for you and isn't slow, stay. If you've got a big list and sends take hours, or you want a modern API and a cleaner editor, Listmonk is worth it. And if you're not sure, ask us. We host both.

Ask us first