What’s the difference between full migration and split delivery?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

When you're switching ESPs, you've got two different end-states to choose from. Not just two migration styles, but two different ways of running email long-term. Understanding the distinction before you start will save you a lot of rework.

Full migration means you're moving everything to one new ESP and eventually switching off the old one. You might run both in parallel for a few weeks during the transition period, but the goal is a clean cut. One vendor, one dashboard, one place to look when something breaks.

Split delivery is a permanent setup where different types of email live on different platforms. Your transactional email (receipts, password resets, shipping notifications) goes through one provider, and your marketing campaigns go through another. The split isn't a stepping stone. It's the destination.

A common pairing: Postmark for transactional and Klaviyo for marketing. Or Twilio SendGrid for triggered sends and Mailchimp for newsletters. The exact combination depends on your priorities.

And the main reason to go split delivery is stream separation. If a marketing campaign triggers a spike in spam complaints, that reputational hit stays contained to your marketing stream. Your password reset emails keep flowing without interruption. That separation genuinely matters when you're sending both types at volume.

Full migration wins on simplicity. One contract, one set of integrations, all your subscriber data in one place. For smaller senders or teams without dedicated deliverability resources, managing two platforms adds overhead that rarely pays off.

Here's a rough guide for choosing:

  • If transactional email is critical to your product and you send serious marketing volume, split delivery is worth the complexity.
  • If you're a smaller sender, just getting started, or want one clean system, full migration is the right call.
  • Some teams start with a full migration and later carve out a separate transactional stream once they hit the volume where it matters. That's a perfectly reasonable path. (Just make sure you plan for it before you pick your first new ESP.)

Not sure which setup fits your situation? Our SOS hotline is free and we'll talk through the specifics with you, no pitch involved.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Get a recommendation for your setup

I'm planning an ESP migration and need to decide between full migration and split delivery. My setup is: describe your current ESPs and email types, my sending volume is roughly marketing volume marketing emails and transactional volume transactional emails per month, and my biggest concern is deliverability / simplicity / cost / team capacity. Which approach fits my situation, and what are the main risks I should plan for?

Edit the yellow boxes, then send to the AI of your choice.