Article
Emails Bouncing After Switching Email Providers? How to Fix It Before You Send
By Unlimited Verifier Team ·

Summary
Emails bounce after switching email providers mainly because the imported list is stale, old suppressions were never migrated, and the new platform has no sending history for your account. Verify the full list before the first send, suppress every invalid address, and ramp volume gradually to keep hard bounces under 1% per send.Emails bounce after switching email providers mostly because the imported list is stale, old suppressions never migrated, and the new platform has no sending history for you, so verify the full list and keep hard bounces under 1% per send.
This guide is for marketers, list owners, agencies and SaaS teams moving tens of thousands of addresses to a new platform. If your account is already under review, start with our high bounce rate account suspension guide, then return here for the migration steps.
Quick answer
- Most common root cause: a stale list. Addresses that closed between your last send and the cutover bounce on the new platform too.
- Fastest fix: verify the full list before the first send, then suppress every Invalid address.
- Silent killer: old suppressions. Re-mailing known hard bounces and unsubscribes is the quickest route to a warning.
- Safe ramp: start with your most engaged verified contacts, expand over roughly 2–4 weeks, and keep hard bounces under 1% per send.
Why do emails bounce after switching email providers?
A bounce happens when a receiving server rejects a message permanently (a 5xx reply) or defers it temporarily (a 4xx reply), as described in RFC 5321. A migration changes three things at once: the list, your sending identity (new domain, new IP or new authentication records), and the feedback loop that tells you what bounced. Any one can cause a spike. Together they compound.
The point most teams miss is that the old platform was quietly protecting them. Its bounce handling, suppression lists and sending history absorbed problems you never saw. The new platform starts with none of that context, so every hidden problem surfaces in your first few sends.
How much bounce is too much? Sources disagree. Many ESPs treat hard-bounce rates around 2% as a warning sign, and mailbox providers set their own undisclosed thresholds. Google's published guidance focuses on spam complaints (keep them under 0.1%, never above 0.3%), not bounces. For a migration, we recommend a stricter working target of under 1% hard bounces per send. On a 52,000-address send, 1% is 520 bounces and 2% is 1,040. That gap often separates a clean cutover from an account review. For the thresholds that trigger suspensions, see what bounce rate gets your ESP account suspended.
Bottom line: a migration bounce spike is almost always a process gap you can check before sending, not bad luck.
How do you tell which cause is behind your bounces?
Read the raw bounce text, not just the bounce count. The enhanced status code, defined in RFC 3463, usually tells you which family of problem you have.
- 5.1.1 (mailbox doesn't exist): a stale list or typos. See causes 1 and 7.
- 5.1.2 (domain doesn't exist): a lapsed domain or a typo domain. See causes 1 and 7.
- 5.7.x (policy or authentication rejection): check authentication first, then reputation. See cause 3.
- 4.x.x deferrals that later convert to bounces: usually volume ramping too fast. See cause 4.
- Bounces to addresses that were already suppressed on the old platform: the suppression file didn't migrate. See causes 2 and 6.
Then run a cohort test. Group your hard bounces by signup year. If they cluster in older signups, decay is the driver. If they're spread evenly, including recent signups, look at authentication or import formatting. Platforms format bounce logs differently, so confirm the code before acting on it.
Bottom line: the status code tells you the category, and the signup-year split tells you whether the list is the problem.
Which fix should you start with?
- Best first move for most migrations: verify the full list before the first send. Upload and verify a list in Unlimited Verifier, or compare options in our roundup of the best email verification tools.
- Best for day-one rejections: check authentication records and run a seed test.
- Best for bounces that arrive days later: segment catch-all and Risky addresses.
- Best for compliance-sensitive lists: migrate unsubscribes and complaints before any contact is set to subscribed.
- Best for cutover week: freeze campaigns on the old platform so two systems don't mail the same people.
- Best for dormant lists (no sends for 12+ months): verify and sunset before import.
| Cause | When it shows up | Bounce signal | Primary fix | Verification role |
|---|---|---|---|---|
| 1. Stale addresses | Sends 1–3 | Hard bounces, clustered in older signup cohorts | Verify full list; suppress Invalid | Core: Valid/Risky/Invalid sort |
| 2. Suppressions not migrated | Send 1 | Repeat bounces, complaints from past opt-outs | Merge and import suppressions first | Checks addresses, not history |
| 3. Authentication gaps | Send 1 | 5xx rejections, spam placement | SPF, DKIM and DMARC on new platform | None |
| 4. No warm-up | Days 1–14 | Deferrals that convert to bounces | Ramp volume in tiers | Informs the ramp, doesn't replace it |
| 5. Parallel platforms | Cutover week | Duplicate sends, doubled exposure | One system of record | None |
| 6. Bounce feedback not connected | Ongoing | Same bad address bounces every campaign | Confirm bounces update status | None |
| 7. Import errors | Send 1 | Immediate bounces on typo domains | Normalize, dedupe, reconcile counts | Domain and MX checks catch undeliverable domains |
| 8. Catch-all acceptance | Days 1–5 | Late bounce notices | Treat catch-alls as Risky | Detects catch-all domains |
How we compared (and limitations)
We ranked these causes on four criteria: how early the failure appears after cutover, whether it creates permanent bounces or reputation damage, whether it can be checked before the first send, and how much compliance exposure it carries.
This analysis is based on public documentation: RFC 5321, RFC 7208 (SPF), RFC 7489 (DMARC), Google's and Yahoo's sender guidance, and the FTC's CAN-SPAM guide. We have not run a controlled migration or measured verifier accuracy ourselves, so the ordering reflects how the mechanisms work rather than measured frequency across migrations. Timelines and bounce splits will vary with list age and source. Figures labeled "illustrative" are arithmetic examples, not data. Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's own stated figure, and this article does not independently verify it. No verifier can see consent, engagement or every spam trap. If you're choosing a verifier for this job, our guide to how to choose an email verifier covers the criteria.
Bottom line: the ranking explains where to look first, but your own bounce logs will show which causes apply to you.
1. Stale addresses from the old list
What happens. An address that was valid at your last send may now belong to a closed mailbox or a lapsed domain. Some vendors and marketers quote annual list decay of 20–30%, but no shared, measured figure exists, so measure your own. Run verification on the full export and compare the Invalid share across signup years. A migration makes decay visible: bounces you'd have absorbed slowly over a year land in your first three sends.
Warning signs. Hard bounces on the first sends, clustered by signup year or import source. If that matches, our explainer on why your bounce rate jumped after importing a list covers the other usual suspects.
Fix. Verify the full list before the first send. Route Valid to sending, Invalid to suppression and Risky to a separate segment.
Worked example (illustrative). Suppose a 60,000-address list verifies as 52,000 Valid, 5,000 Risky and 3,000 Invalid. Sending to all 60,000 puts 3,000 known-dead addresses in the first send: 3,000 ÷ 60,000 = 5% hard bounces, well above a 1% working target. Suppressing the Invalid group removes that known exposure. Your split will differ.
What the fix doesn't solve. Disengagement. A valid address that never opens still weighs on your engagement signals, so pair verification with a sunset policy from our email list maintenance best practices.
Bottom line: verification before import is the single highest-leverage step in a migration.
2. Suppressions that never migrated
What happens. Your old platform held a record of hard bounces, unsubscribes and spam complaints. If you export only active contacts and import them as subscribed, that record stays behind. The first campaign then re-mails people who bounced or opted out.
Compliance angle. Under the FTC's CAN-SPAM rules, opt-out requests must be honored within 10 business days. Re-importing someone who unsubscribed as "subscribed" is a compliance failure, not just a bounce problem. UK and EU rules on consent are stricter still, which is why our overview of email verification compliance and hygiene treats suppression as a legal control. See also the FTC's CAN-SPAM compliance guide.
Warning signs. Bounces to addresses you remember bouncing before, and complaints from people who had already unsubscribed.
Fix. Export three files from the old platform: hard bounces, unsubscribes and complaints. Confirm each export covers your full history, since some platforms limit what they export, and ask support if unsure. Merge the three into one suppression file and import it as suppressed before any active contact comes in. Our guide on how to avoid ESP suspension when importing old lists has platform-specific steps.
What the fix doesn't solve. Addresses that were never recorded as bounced or unsubscribed, such as contacts from an old purchased list. Verification can flag some of these, but it cannot establish consent.
Bottom line: merge suppressions before importing active contacts, not after the first send.
3. Authentication not set up on the new sending domain
What happens. SPF lists the servers allowed to send for your domain. DKIM signs messages. DMARC tells receivers what to do when checks fail and requires alignment with your From domain, as defined in RFC 7489. A new platform usually means new records. Google's sender guidelines set authentication requirements for bulk senders, generally those sending 5,000 or more messages a day to Gmail, and Yahoo's sender best practices set similar expectations. Rejections for failed authentication often carry 5.7.x enhanced codes, so the failure can look like bounces rather than spam placement.
The detail that breaks quietly: the SPF lookup limit. RFC 7208 caps SPF evaluation at 10 DNS-querying mechanisms. Each include that triggers a lookup counts toward that limit, and included records can nest further lookups. Teams that keep the old platform's include and add the new one can exceed the limit, and the SPF check then returns a permanent error. Remove the old include once cutover is complete, and validate the record before sending.
Warning signs. 5xx rejections that mention authentication, or a sudden drop into spam folders during the first sends.
Fix. Publish the new platform's SPF include and DKIM records, then send a seed test to a few Gmail, Outlook and Yahoo addresses you control. Open each message's original headers and confirm SPF, DKIM and DMARC all pass. Publish a DMARC record, starting at p=none while you monitor. DNS changes can take anywhere from minutes to a couple of days depending on TTLs, so make them before cutover. If you use a dedicated IP, confirm forward and reverse DNS for it.
What the fix doesn't solve. A bad list. Authenticated mail to dead addresses still bounces.
Bottom line: authentication prevents day-one rejections, and the SPF lookup limit is the detail that breaks it without warning.
4. A cold domain or IP with no warm-up
What happens. Mailbox providers judge new senders on limited history. Jumping from a few thousand monthly sends to tens of thousands in one day can look like abuse. Providers respond with temporary deferrals. Deferred messages retry, and when retries fail, or the addresses turn out to be dead, the deferrals become bounces.
Fix: ramp in tiers. Send first to your most engaged verified contacts, those who opened or clicked in the last 90 days. Expand over about 2–4 weeks. That range is a common planning practice rather than a published provider rule. Our guide on how to send to an old email list safely walks through the tiers in more detail.
Worked example (illustrative). Day 1: 5,000 engaged Valid contacts. At a 1% ceiling, that's at most 50 hard bounces. Days 3–5: 10,000 more. Week 2: 20,000 more. Week 3: the remaining Valid contacts. Check each tier's bounce rate before expanding.
What the fix doesn't solve. Poor list quality. A ramp limits the damage per step but doesn't remove dead addresses.
Bottom line: the ramp converts one large risk into a series of small, checkable ones.
5. Old and new platforms running at the same time
What happens. Cutovers rarely happen in a single moment. A campaign scheduled on the old platform, an automation on the new one and a welcome series from both can reach the same person within hours. Each platform sees only its own bounces, so a hard bounce on one doesn't suppress the address on the other. Duplicate sends multiply bounce exposure and complaint risk for every address they reach.
Warning signs. The same address appears in both platforms' send logs on the same day.
Fix. Name one system of record. Freeze new campaigns and automations on the old platform from a fixed cutover date. Export its send logs before you disable it, and carry its suppression data into the merged file from cause 2. Pause any scheduled automations that the new platform has duplicated.
What the fix doesn't solve. Bad addresses. One clean send to a dirty list still bounces.
Bottom line: two active platforms during cutover double the places a bad address can be mailed from.
6. Bounce feedback not connected on the new platform
What happens. A list only gets cleaner when bounces flow back and change address status. Some setups need bounce processing configured or a webhook connected. Without it, a hard bounce stays "subscribed" and goes out again in the next campaign. The old platform may have handled this automatically, so nobody configured it on the new one. If your sending service is Mailgun, our Mailgun high bounce rate warning fix covers its warning path.
Warning signs. The same address bounces in consecutive campaigns.
Fix. Run a controlled test: send to a known-invalid test address and confirm its status changes to suppressed. Then set rules. Hard bounces should be suppressed after one occurrence. For soft bounces, suppressing after repeated failures is a common working rule, typically around three consecutive, but confirm what your platform does by default.
What the fix doesn't solve. Bounces that happened before the connection. Re-verify those addresses rather than trusting old statuses.
Bottom line: a hard bounce that isn't written back to your list will bounce again.
7. Import errors: typos, formatting and duplicates
What happens. Old signup forms leave domain typos like gmial.com, yahoo.con or hotmial.com. Spreadsheet round-trips add trailing spaces, mixed case, duplicate rows and sometimes mangled characters from encoding. Duplicates cause double sends to the same person. Typo domains cause immediate hard bounces.
Warning signs. Bounces on the first batch with malformed domains, or a column mapping error that puts names in the email field.
Fix. Before upload, trim spaces, lowercase addresses, deduplicate, and save as a UTF-8 CSV with the email column formatted as text. Avoid repeatedly resaving the file in Excel, which can alter values such as long numbers. Then verify. Domain and MX checks are designed to catch domains that can't receive mail, so many typo domains should surface in the Invalid bucket. Afterward, reconcile: Valid + Risky + Invalid should equal your deduplicated row count. A gap means rows were lost or duplicated somewhere in the process.
What the fix doesn't solve. Typo-free but dead addresses, which need the verification in cause 1.
Bottom line: the reconciliation check is the cheapest insurance in the whole migration.
8. Catch-all and Risky addresses that bounce days later
What happens. Catch-all domains accept mail for any local part at SMTP time, so a standard check can't confirm that a specific mailbox exists. Some of those messages later produce bounce notices, sometimes days after the send, after you've already counted the address as delivered. That's why a migration can show a bounce tail that a first-day report misses.
Warning signs. Bounce notifications arriving one to three days after sends, concentrated in company domains.
Fix. Treat catch-all addresses as Risky, not Valid. Unlimited Verifier detects catch-all domains and sorts them into Risky. Send Risky addresses only to recent engagers, and use deep verification on that bucket. Pro includes 25,000 deep verifications a month, and Free includes 750. See catch-all email verification for how these domains are handled.
What the fix doesn't solve. Ambiguity. You can't confirm every catch-all mailbox. You can only decide how much risk to accept for each segment.
Bottom line: a catch-all address is a risk to manage, not a confirmed good address.
How do you move a list to a new provider without bounces?
Unlimited Verifier doesn't connect directly to ESPs or CRMs, so the workflow is export, verify, re-import, with the API as an option on Pro. Here is the sequence for a list of about 60,000 addresses.
- Export everything from the old platform. Pull active contacts with signup date and source, plus separate files for hard bounces, unsubscribes and complaints. If you don't have an account yet, sign up before you start.
- Build the suppression file first. Merge the three exports into one file. It is never imported as sendable.
- Clean the active file. Trim spaces, lowercase addresses, remove anything in the suppression file, and save as UTF-8 CSV.
- Check file sizes against plan limits. Free allows 25 lists a month of up to 150 emails each. A 60,000-address list needs 400 files (60,000 ÷ 150), which at 25 files a month takes 16 months. Pro allows unlimited lists of up to 25,000 emails each, so the same list is three files (25,000 + 25,000 + 10,000). Compare email verification pricing models before choosing a plan, and keep each upload under 10MB.
- Upload and verify each file. The email column is detected automatically. Each address comes back as Valid, Risky or Invalid.
- Deep-verify the Risky bucket only. A 5,000-address Risky bucket fits within Pro's 25,000 monthly deep-verification allowance but exceeds Free's 750, so a list with that much catch-all exposure points to Pro.
- Export and archive immediately. Export as CSV, Excel or JSON. Free results are kept for 24 hours and Pro results for 30 days, so save copies to your own storage.
- Reconcile counts. In the illustrative split, 52,000 Valid + 5,000 Risky + 3,000 Invalid = 60,000. Any other total needs investigating before import.
- Import with the right status. Valid goes in as subscribed, Risky gets a tag for segmentation, and Invalid plus the suppression file go into suppressions. Confirm the suppression count matches before the first send.
- Confirm authentication and bounce handling. Run the seed test from cause 3 and the controlled suppression test from cause 6.
- Ramp and monitor. Start with engaged Valid contacts. Watch the hard-bounce percentage for about 72 hours after each tier, since late bounces are common, and pause expansion above 1%.
- Automate signups on Pro. Use the email verification API for email verification API and automation, either checking single addresses at signup or sending batches of up to 10,000 emails per request, within the 100,000-email monthly API allowance. For the signup-time pattern, see real-time email validation. The Free plan has no API access, so use the free email checker for one-off spot checks.
Bottom line: the migration is an export, verify, reconcile and ramp sequence, and each step leaves a record you can check.
Which approach fits your migration?
| Your situation | Start with | Why |
|---|---|---|
| List untouched for 6+ months before the move | Cause 1: verify and suppress | Decay is the likeliest source of day-one bounces |
| Importing an unsubscribe or complaint export | Cause 2: merge suppressions | Protects against re-mailing opt-outs |
| New sending domain or new dedicated IP | Cause 3, then cause 4 | Authentication first, then ramp |
| Both platforms still active during cutover | Cause 5: freeze the old platform | Stops duplicate sends |
| Lists merged from forms, events or spreadsheets | Cause 7: normalize and reconcile | Typos and duplicates cause immediate bounces |
| Large B2B or company-domain share | Cause 8: treat catch-alls as Risky | Late bounces hide in catch-all domains |
| Already under review on a current ESP | Mailchimp, SendGrid or Brevo guidance | Platform-specific appeal and cleanup steps |
| SaaS team with signup-driven growth | Cause 1, then ongoing checks | See email verification for ecommerce and SaaS |
Bottom line: match the first fix to the symptom you see, then work through the list.
What mistakes make migration bounces worse?
- Importing everything as subscribed. This re-mails old bounces and unsubscribes.
- Ramping the full list on day one. One large send concentrates every problem into a single reputation event.
- Deleting every Risky address. Catch-all domains often include real readers. Segment them by engagement instead.
- Verifying once and assuming the list stays clean. Decay continues after the migration. If you're already seeing a spike, our guide to 5 steps to take after a bounce rate spike covers the next moves.
- Running both platforms through cutover. Duplicate sends are hard to unwind.
- Forgetting result retention. Free results expire after 24 hours, so export and archive first.
- Treating verification as consent. A deliverable address can still be one you have no permission to email.
- Underestimating post-spike damage. One bad send can affect later sends, which is why does one high-bounce campaign hurt deliverability for weeks is worth reading before you ramp.
Bottom line: most migration bounce problems come from skipped steps, not from the verification tool.
Verdict
Emails bounce after switching providers because the list, the suppressions and the sending identity all change at once. Verify the full list before the first send, merge every suppression before importing, and ramp volume while keeping hard bounces under 1%. Unlimited Verifier fits this workflow because standard verification is unlimited on every plan, its Valid/Risky/Invalid sort maps directly to send, suppress and segment decisions, and Pro's API covers ongoing signup checks. Plan around its limits: Free caps lists at 150 emails, there is no native ESP integration, and Free results expire after 24 hours.
For the broader process, see our email list maintenance best practices.
Bottom line: verify before you send, suppress before you import, and ramp before you scale.
Worked example: 52,000-address send
| Hard bounce rate | Bounces on 52,000 addresses | Status |
|---|---|---|
| 0.5% | 260 | Safe |
| 1% | 520 | Working target ceiling |
| 2% | 1,040 | Warning zone at many ESPs |
If 1,040 addresses bounce, the list was not verified and the account is at risk of review. Verifying first and suppressing Invalid results before sending typically keeps the rate under the 1% target.
Frequently asked questions
Why do emails bounce after switching email providers?
Emails usually bounce after a switch because the list is stale, old suppressions were not migrated, and the new platform has no sending history for your account. The old platform was absorbing problems you never saw, so they surface in the first sends on the new one.
What bounce rate is acceptable during an email migration?
Many ESPs treat hard-bounce rates around 2% as a warning sign. For a migration, a stricter working target is under 1% hard bounces per send, which keeps you well clear of typical review thresholds.
Should I verify my whole list before switching providers?
Yes. Verify the full list before the first send on the new platform and suppress every address marked invalid. This is the fastest way to prevent a bounce spike from closed or mistyped addresses.
Do I need to migrate suppression lists?
Yes. Re-mailing known hard bounces and unsubscribes is one of the quickest routes to a warning. Export suppressions from the old platform and import them before any campaign goes out.
How fast should I ramp volume on a new ESP?
Start with your most engaged verified contacts and expand over roughly 2 to 4 weeks. A fast ramp on a new platform with no sending history often triggers deferrals that later convert into bounces.
What does a 5.1.1 bounce mean?
A 5.1.1 enhanced status code means the mailbox does not exist. It usually points to a stale list or typos, so verify the addresses and suppress any that fail.
What does a 5.7.x bounce mean?
A 5.7.x code is a policy or authentication rejection. Check SPF, DKIM and DMARC for the new sending domain or IP first, then look at sender reputation.
Will switching providers hurt my sender reputation?
It can, if the switch brings a new domain, new IP or bad list hygiene. Keeping authentication records correct and sending to engaged, verified contacts first helps protect reputation during the move.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.