Article

How to Migrate Your Email List Without Losing Deliverability

Moving to a new ESP resets your sender reputation to zero. A phased migration over 5 weeks prevents spam rate spikes. Full checklist for practitioners.

Switching email platforms feels simple until you send your first campaign from the new provider and watch open rates fall by half. The cause is predictable: your new sending IP has zero reputation with Gmail, Yahoo, and Outlook. Their spam filters don't know you yet. A single-day migration of a 3,000-person list from MailChimp to MailerLite, where you flip the switch and send to everyone at once, triggers exactly the spam rate spike that damages sender reputation for months. The correct approach takes five weeks and protects the deliverability you've built.

This guide covers the pre-migration checklist, the phased sending schedule, and what to do with cold subscribers who will hurt your metrics on any platform.

The Core Risk of Platform Migration

Every email service provider sends from its own IP addresses. Your old ESP has months or years of sending history on those IPs, which builds sender reputation with inbox providers. Your new ESP's IPs are unknown. Sending a large volume immediately from an unknown IP is one of the clearest spam signals to Gmail's filters.

The consequence: email goes to spam, spam rate climbs, domain reputation drops. Once domain reputation drops to "Low" or "Bad" in Google Postmaster Tools, recovery takes 8-12 weeks of low-volume, high-engagement sending. It's easier to prevent than fix.

Source: mailflowauthority.com/email-deliverability/esp-migration-playbook; mailtrap.io/blog/esp-migration

Pre-Migration Checklist (Week 1)

Complete all of this before sending a single email from the new platform.

1. Set up authentication on the new ESP first

Configure SPF, DKIM, and DMARC for your domain on the new platform before sending anything. If you're running both ESPs simultaneously (old and new sending at the same time during transition), your SPF record must include both:

`v=spf1 include:old-esp-spf include:new-esp-spf -all`

DKIM configuration is done through your ESP's domain settings panel. DMARC at `p=none` with a reporting address lets you monitor without disrupting delivery. Verify all three are passing using MXToolbox (free) before your first send.

2. Export everything from your old ESP

Export: your full contact list with all tags and segments, campaign history, engagement statistics (opens, clicks by subscriber), historical bounce rates, and your unsubscribe list. Most ESPs allow export to CSV from the contacts or audience section.

3. Export and import suppression lists first

Before uploading your main list to the new platform, import suppressed contacts: everyone who has unsubscribed, hard-bounced, or filed a spam complaint. This step is critical and commonly skipped. Re-mailing suppressed contacts on a new platform violates both CAN-SPAM and GDPR, and immediately triggers spam complaints that damage your new ESP reputation before your list is even fully migrated.

4. Segment your list by engagement

Sort your current list into three groups based on email open history:
- Hot: opened any email in the last 30 days
- Warm: last opened 31-90 days ago
- Cold: no open in 90 or more days

You will migrate these segments in sequence, not all at once. Most ESPs allow you to create segments based on last open date.

Phased Migration Schedule (Weeks 2-5)

Send to the new ESP in stages while keeping the old ESP active for your full list during the transition.

Week

Audience on New ESP

Notes

Week 2

Hot segment only (10-20% of list)

Validate authentication and deliverability first

Week 3

Hot + Warm, 30-40% of list

Expand if Week 2 bounce rate stayed below 2%

Week 4

60-80% of list

Continue monitoring metrics daily

Week 5

100% of list on new ESP

Retire old ESP sends after this

During Weeks 2-4, continue sending your regular campaigns to the full list on your old ESP. This avoids double-sending to subscribers who are in both segments. In Week 5, you consolidate entirely on the new ESP and stop sending from the old one.

Monitor after each send: spam complaint rate (should stay below 0.1%), bounce rate (below 2%), and open rate relative to your baseline. A sudden spike in any negative metric means pause and investigate before expanding.

Sources: mailerlite.com/blog/esp-migration; mailtrap.io/blog/esp-migration

What to Do With Cold Subscribers

Do not migrate cold subscribers (90-plus days of no opens) directly to your new ESP. They are the most likely to trigger spam complaints, which damages your reputation on a platform where you're starting from zero.

Run a re-engagement campaign on your old ESP first. Two or three emails over two weeks asking: "Are you still interested in [topic]? Click to confirm you want to stay subscribed." Anyone who opens or clicks is warm enough to migrate. Anyone who ignores all three is suppressed and removed from the migration list.

This reduces your migrated list size. It also protects you. A 1,500-subscriber list where 45% open consistently outperforms a 3,000-subscriber list where 20% open on every deliverability metric that matters.

Post-Migration Monitoring (Weeks 6-8)

For two weeks after completing the migration, monitor these metrics daily:

- Bounce rate: keep below 2%. Above 2% indicates list quality issues or authentication problems.
- Spam complaint rate: keep below 0.1%. A spike here requires immediate action: remove the most recent segment added and investigate what triggered complaints.
- Open rate: compare to your baseline on the old platform. Some drop is normal during the warming period. A drop of more than 20 percentage points signals a deliverability problem.

Set up Google Postmaster Tools (postmaster.google.com, free) with your domain verified. It shows your domain reputation as High, Medium, Low, or Bad, and tracks spam rate from Gmail users specifically.

Cancel your old ESP subscription only after two full weeks of clean metrics on the new platform. Remove the old ESP's entries from your SPF record at the same time.

Platform-Specific Notes

For practitioners migrating away from MailChimp: MailChimp's free plan dropped to 500 contacts in 2022 and most ESPs now offer more at the same price. Kit's free tier supports 10,000 subscribers. MailerLite's free plan was 500 active subscribers before the June 2026 reduction to 250 (verify current limits at mailerlite.com/pricing). At 1,000+ subscribers, Moosend Pro at $16/month or Kit Creator at $9/month are both more capable than MailChimp's equivalent tiers.

For the comparison of specific platforms, see MailChimp vs ConvertKit and ConvertKit vs Beehiiv vs Substack to evaluate which destination platform is right before starting the migration.

Common Mistakes

- Migrating the full list in a single day. Even a well-segmented list sent all at once from a new IP overwhelms the ISPs' ability to classify your sending as legitimate.
- Skipping suppression list import. The first spam complaint from a previously unsubscribed contact sets a negative tone for your new ESP account.
- Cancelling the old ESP before verifying new ESP deliverability. If something goes wrong during migration, having the old platform as fallback sends prevents revenue disruption.
- Not removing cold subscribers first. Migrating 1,000 cold subscribers who haven't opened in a year poisons the new ESP account's warming period.

Frequently Asked Questions

How long does it take to build sender reputation on a new ESP?

Typically 4-8 weeks of consistent, clean sending before inbox placement stabilizes at the level of your old platform. The phased migration schedule is designed to match this warming period: by the time you're sending to 100% of the list in Week 5, you've already established 3 weeks of sending history on the new IP. The 2-week monitoring period after full migration confirms stability before you retire the old platform.

Can I migrate to a new ESP and change my sending domain at the same time?

No. Changing both the sending IP and the sending domain simultaneously doubles the reputation uncertainty. Migrate to the new ESP using your existing sending domain first. Once migration is complete and metrics are stable (4-8 weeks), you can consider a domain change as a separate project with its own warming period.

What if my old ESP doesn't export tags or segments?

Recreate segmentation on the new platform using engagement data from the export. Most exports include last open date and click data at the subscriber level, which is enough to rebuild Hot/Warm/Cold segments. Tags that are product-based (which reading type a client purchased) may need to be rebuilt from your order history rather than the ESP export.

Is migration worth it if I'm getting good open rates on my current platform?

If your current ESP is working and you're not hitting a cost or feature ceiling, there's no reason to migrate. Migration is the right choice when: the platform raised prices significantly (MailerLite's June 2026 changes affect practitioners on the old free plan), your list outgrew the free tier, or you need features your current platform doesn't offer. Good deliverability metrics are worth protecting; only migrate when there's a clear reason.