Switching email platforms is mostly an export and an import. The bounce spike that sometimes follows is a different problem.
It usually shows up on the first big send from the new account, and it surprises people for the same reason every time. The list looked fine on the old platform. Bounce rates were low and engagement was steady. Then the same contacts, mailed from a new account, come back with a wave of hard bounces.
The short answer: the list was never as clean as it looked. Your old platform was quietly holding back addresses it already knew were bad, and that protection doesn’t come with the CSV. To move without a spike, bring your suppression data across with your contacts, verify the list before you import it, send to your most engaged contacts first, and widen the audience only while the numbers stay steady.
Key takeaways
- A standard export often leaves your old platform’s suppression list behind. Export it separately.
- Verify before import, so bad addresses never touch your new sending reputation.
- Import unsubscribes, complaints and hard bounces as suppressed, never as active contacts.
- Start with recently engaged contacts and scale on results, not on a calendar.
Why do bounces jump after switching email platforms?
Three things tend to happen at once.
Suppressions get left behind. Every platform keeps a list of addresses it refuses to mail: hard bounces, spam complaints, unsubscribes and, on some platforms, contacts it has cleaned for inactivity. Many exports include only active subscribers by default, or put suppressed records in a separate file. If that file doesn’t make the trip, the new platform treats every one of those addresses as a fresh contact.
Old records come back. A migration is when forgotten lists get merged in: an event spreadsheet, an old CRM segment, contacts from a tool the team stopped using years ago. Nobody has mailed those records recently, so nobody knows how many of them still exist.
The new sender has no history. Mailbox providers weigh a sender’s past behavior when deciding what to accept, which is a big part of how email deliverability works. A new account, new sending infrastructure or a new domain setup gives them fewer positive signals to go on. A bounce rate the old account could absorb can do more damage on the new one.
Sending platforms enforce this as well. Amazon SES, the infrastructure behind many email tools, places accounts under review at a 5% bounce rate and may pause sending at 10%. Your new provider will have its own limits, and one bad first campaign can reach them before you have settled in.
What should you export from your old platform?
More than the active list. Take the export while the old account is still paid and fully accessible, because some platforms restrict exports or delete data once a subscription lapses.
| Data | Why it matters | What to do with it |
|---|---|---|
| Active subscribers | The core of your new list | Verify, then import |
| Unsubscribes | Mailing them again is a compliance problem and a complaint risk | Import as suppressed |
| Hard bounces | These addresses have already failed | Import as suppressed |
| Spam complaints | The strongest negative signal you have | Import as suppressed |
| Cleaned or inactive records | Often left out of exports by default | Review before deciding |
| Engagement dates (last open, click, purchase) | You need them to plan the first sends | Keep as custom fields |
| Signup source and date | Tells you where the risk sits | Keep as a field or tag |
| Recent campaign reports | Your baseline for bounces, complaints and clicks | Save a copy before you leave |
Unsubscribed contacts deserve a specific note. Keeping them in the new platform as suppressed records is what stops a later form sync or CSV upload from quietly re-adding someone who opted out. Check how the new platform bills for them, since some platforms count unsubscribed contacts toward your plan and others don’t.
Why should you verify before the import instead of after the first send?
Because the first send is the most expensive place to learn that an address is dead. Every hard bounce on the new account counts against a reputation that is only just forming.
Running the active list through an email verification service before import gives you four groups to work with:
- Deliverable: import as active.
- Undeliverable: don’t import as active. Add these to your suppression list.
- Risky: look at the reason before deciding. A catch-all domain, a full mailbox and a disposable address are three different problems.
- Unknown: hold them back and check again before they join a send.
Some addresses need a decision of their own even when they verify. Shared inboxes such as info@ or sales@ behave differently from personal ones, and it’s worth deciding how to handle role-based addresses before they land in your main segment.
Two practical points. First, you only need to verify contacts you intend to mail. Unsubscribes, complaints and past hard bounces stay suppressed whatever a verifier says about them. Second, verify close to the import date. If the migration project runs for several weeks, a list verified at the start will have aged by the time it is imported. Addresses decay continuously, which is why list cleaning works better as a routine than a one-off.
How should you set up the new platform before the first send?
Authenticate the sending domain. Set up SPF, DKIM and DMARC before any real campaign goes out. Google requires all three from senders who send more than 5,000 messages a day to Gmail accounts. Yahoo applies similar rules, and Outlook.com began enforcing them for high-volume senders in 2025. Even below those volumes, authentication is the cheapest deliverability work you will ever do.
Confirm one-click unsubscribe. Google and Yahoo both expect bulk marketing mail to support one-click unsubscribe, and Yahoo asks senders to honor unsubscribe requests within two days. Most platforms add the headers automatically, but check a test message to be sure.
Keep what recipients recognize. Use the same from name, from address and sending domain your subscribers already know. If you also move to a new sending domain, you are changing two things at once, and the domain needs a gradual warm-up of its own.
Send a test first. Mail a draft campaign to your own addresses at Gmail, Outlook and Yahoo. Confirm that SPF, DKIM and DMARC pass in the message headers and that the email lands where you expect.
Who should get the first emails from the new platform?
Not everyone. Sort the list by the engagement dates you exported and start at the top.
| Stage | Who gets the email | Move on when |
|---|---|---|
| 1 | Opened or clicked in the last 30 days | Bounces and complaints match your old platform’s baseline |
| 2 | Engaged in the last 90 days | The same holds, and no single mailbox provider is lagging |
| 3 | Engaged in the last 6 to 12 months | Metrics stay steady across two or three sends |
| 4 | Older or never engaged | Only through a re-engagement campaign, or not at all |
How large each stage should be depends on your volume, so there is no universal number. What mailbox providers notice is a sudden jump, so avoid moving from a few thousand messages to your full list in a single step.
Be careful with the last stage. Amazon’s own guidance is that if you must send to addresses you haven’t mailed lately, you should do it only with a small portion of your overall sending. A migration is a good moment to accept that some old contacts are not coming with you.
What should you watch during the first two weeks?
Compare every send against the baseline you saved from the old platform.
- Hard bounce rate per send. This is the number that tells you whether verification and suppression worked.
- Soft bounces by domain. A cluster at one provider usually means throttling, not bad addresses.
- Spam complaint rate. Google Postmaster Tools shows your rate at Gmail. Google asks senders to stay below 0.3% and recommends staying below 0.1%.
- Clicks by mailbox provider. A sudden drop at one provider, while the others hold, points to filtering there. Lean on clicks rather than opens, since privacy features inflate open data.
- Unsubscribes. A jump often means people don’t recognize the email. Check the from name and the first lines of the message.
What should you do if bounces spike anyway?
- Pause the next stage. Don’t push the rest of the list through while you investigate.
- Read the bounce reasons. “Mailbox does not exist” points to a list problem. “Blocked” or “policy” responses point to reputation or authentication. They need different fixes.
- Find the source. Use the signup source field you kept. If the bounces cluster in one old import, that segment is the problem, not the whole list.
- Suppress and re-verify that segment only. There is no need to hold back contacts who are behaving normally.
- Resume with your engaged stage. Never retry addresses that hard bounced.
What does a bounce-safe migration checklist look like?
- Export active contacts, unsubscribes, bounces, complaints and engagement fields before closing the old account.
- Save recent campaign reports as your baseline.
- Verify the active list close to the import date.
- Import unsubscribes, complaints and hard bounces as suppressed.
- Set up SPF, DKIM, DMARC and one-click unsubscribe, then send a test.
- Send to your most engaged contacts first and scale on results.
- Watch bounces, complaints and provider-level clicks for the first two weeks.
FAQ
Do I need to verify a list that looked clean on my old platform?
Usually, yes. A low bounce rate on the old platform often meant it was filtering out known bad addresses before each send. Your export may not carry that protection, and addresses keep going stale while the migration is underway.
Should I import unsubscribed contacts into my new platform?
Yes, but as suppressed or unsubscribed records, never as active contacts. The record is what prevents them from being re-added by a later import or form sync.
How long should the ramp-up take?
There is no fixed timeline. A small, highly engaged list may move over in a few sends, while a large list with older segments takes longer. Move to the next stage when bounces, complaints and provider-level engagement stay steady.
Can I change my sending domain during the migration?
You can, but it doubles the number of things that can go wrong at once. If possible, move platforms on your existing, authenticated domain first, then change domains later with a warm-up of its own.
About the author
Tu Nguyen is a Marketing Specialist at Mailsoftly, an email marketing and automation platform based in San Ramon, California. Tu writes about email list management, deliverability and practical email marketing for small teams.
