Email Deliverability Drop After ESP Migration: Diagnosis Checklist from 200+ Audits

An email deliverability drop after ESP migration follows a predictable pattern. Volume goes out on day one, open rates crater by day three, and by week two someone is asking whether the whole migration was a mistake. It rarely is. The problem is almost always a missed step, not a bad decision. This checklist exists so you can find that step before the damage compounds.

It is built for CRM managers, email marketing leads, and CMOs who have recently switched platforms (or are about to) and need a structured way to isolate what went wrong. Bookmark it. You will likely need it more than once.

The Diagnosis Checklist: Fixing Email Deliverability Drop After ESP Migration

1. Verify DNS authentication records transferred correctly. SPF, DKIM, and DMARC records tied to your old ESP will not automatically apply to the new one. A single misconfigured DKIM selector can push your entire volume to spam. Run a full DMARC, DKIM, and SPF audit within 24 hours of switching.
2. Check whether you migrated to new IPs without a warm-up plan. New sending IPs have no reputation. Mailbox providers treat unknown IPs with suspicion. If you pushed full volume on cold IPs, throttle immediately and follow a structured IP warming schedule before scaling back up.
3. Confirm your sending domain reputation survived the switch. IP reputation matters, but domain reputation now carries more weight at Gmail and Microsoft. Use Google Postmaster Tools and Microsoft SNDS to check domain-level signals. If your domain shows “Low” or “Bad” reputation, the migration exposed a pre-existing list hygiene issue.
4. Audit your suppression lists for completeness. Bounces, complaints, and unsubscribes from your old platform must transfer to the new one. Missing even a fraction of these means you are re-mailing people who already opted out or hard-bounced. According to Validity’s 2024 State of Email report, complaint rates above 0.1% trigger filtering at most major mailbox providers. One missed suppression file can push you past that threshold in a single send.
5. Compare inbox placement rate, not just delivery rate. Your new ESP may report 98% delivery, but that counts spam folder placement as “delivered.” Inbox placement rate is the metric that reflects actual visibility. Use seed testing tools to measure where messages actually land.
6. Review your sending cadence against historical patterns. Mailbox providers build expectations based on your sending history. A migration that changes send times, frequency, or volume patterns trips anomaly detection. Match your pre-migration cadence as closely as possible for the first 30 days.
7. Validate tracking domains and link wrapping. New ESPs replace your click-tracking links with their own domains. If those domains are shared with senders who have poor reputations, your links inherit that toxicity. Check whether your tracking infrastructure is shared or dedicated, and run your links through blocklist checkers like Spamhaus DBL.
8. Test rendering and content across the new platform. Template migration introduces subtle changes: broken personalization tokens, missing alt text, or shifted image-to-text ratios. These content-level shifts can trigger spam filters that your old templates had already “trained” past. Send test campaigns to multiple mailbox providers before resuming production sends.
9. Segment your reactivation by engagement recency. Data Innovation, a Barcelona-based Boutique ESP and CRM consultancy whose Sendability platform orchestrates over 10 billion emails monthly across more than 10 countries, has documented that sending to subscribers inactive for 90+ days during the first two weeks post-migration is the single most common accelerant of reputation collapse. Start with your 30-day actives only, then expand gradually.
10. Monitor feedback loops and postmaster dashboards daily for 30 days. According to a Litmus deliverability study, senders who monitor complaint data within the first 48 hours of a sending change resolve placement issues 3x faster than those who wait for open rate declines to surface. Set calendar reminders. Daily checks are non-negotiable during this window.

One honest caveat

This checklist catches the mechanical failures. What it cannot diagnose quickly is a reputation problem that pre-dated the migration but was masked by your old ESP’s shared infrastructure. Sometimes the migration reveals that your list quality was worse than you thought. If you complete every item here and placement still does not recover within 30 days, the root cause is likely deeper. A full ESP migration playbook can help you distinguish between migration-induced damage and legacy debt.

When to Use This Checklist

• Within the first 72 hours after switching ESPs, before volume-related damage sets in.
• When open rates drop more than 15% in the first week post-migration.
• Before a planned migration, as a pre-flight checklist to prevent the drop entirely.
• During a quarterly deliverability review if you migrated within the past 6 months and still see inconsistent placement.

Every day you delay diagnosing an email deliverability drop after ESP migration, mailbox providers build a stronger negative profile of your new sending setup. Reputation is easier to protect than to rebuild.

If your inbox placement has fallen more than 20 points since migration and the items above have not resolved it, we have documented the recovery process across hundreds of similar audits. The data tends to point somewhere specific.