How to Warm Up After Switching Email Providers

Published November 4, 2026 · 9 min read

Warming up after switching email provider means sending to your most engaged contacts first, holding daily volume below a cap that grows slowly, and watching bounces, complaints and clicks before each increase. A new platform almost always means a new sending subdomain or a new IP, so mailbox providers have no history for that combination and treat your first sends with caution. The ramp is how you build that history without burning it.

This is the pillar article of the Warmup Scenarios cluster. Supporting pieces on new domains, dedicated IPs, re-warming after a pause and re-engaging inactive contacts will be linked here once published.

What actually changes when you switch platforms

Reputation is attached to the sending domain and the sending IP, not to your brand name. If you move to a new provider and set up mail.yourdomain.com on their infrastructure, Gmail, Outlook and the rest see a domain-IP pair they have never observed. Your old provider's reputation stays with the old provider.

If you keep the same sending domain and the same IP, the situation is different. You are not rebuilding reputation from zero; you are adapting to a new platform's sending patterns, a new bounce and complaint pipeline, and whatever list hygiene the migration left behind. Warmup is still worth doing, but shorter and mostly about verifying that suppression, authentication and segmentation survived the move.

One more thing that changes quietly: your old platform's engagement data may not travel with you. If opens and clicks were stored per campaign and you export only contacts, you lose the signal you need to pick the engaged segment. Export engagement fields or tags before you cancel the old account.

What you'll set up and what you need

Get these in place before the first send:

A sending subdomain, for example mail.yourdomain.com, separate from the domain you use for company email. Keeping them apart means a deliverability problem in bulk sending does not touch your day-to-day correspondence.
DKIM, SPF and DMARC records for that subdomain, added at your DNS host.
A suppression list exported from the old platform: hard bounces, complaints, unsubscribes, and anyone who asked to be removed.
An engaged segment: contacts who opened or clicked in the last 90 days. This is your day-one audience.
A first email that works as plain text: one purpose, one link, a monitored reply-to address.
A spreadsheet with columns for date, volume, segment, hard bounces, complaints, opens and clicks.

Mailerflow covers part of this setup: own-domain sending with guided DKIM, SPF and DMARC configuration and automatic verification, CSV import with duplicate and validity checks, and free migration help (contacts, suppression lists, templates, core automations) on eligible paid plans. Any platform with equivalent controls works the same way.

Step-by-step: warming up after switching email provider

1. Authenticate the new sending domain

Add the subdomain in the new platform and copy the DNS records it generates into your DNS host. Three records matter:

SPF: a TXT record on the subdomain that includes the new provider's sending host, for example v=spf1 include:spf.provider.example ~all. Keep it under the 10-lookup limit; remove includes for providers you no longer send through.
DKIM: a TXT record at the selector the provider gives you, for example mf2026._domainkey.mail.yourdomain.com, containing the public key.
DMARC: a TXT record at _dmarc.mail.yourdomain.com starting at v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. Start at p=none so you collect reports before enforcing anything.

Verify: run a DNS lookup on the DKIM selector and the SPF record to confirm they resolve. Then send a test to a seed address you control and read the Authentication-Results header: you want dkim=pass, spf=pass and dmarc=pass. Mailerflow verifies these records automatically after you add them, which saves the back-and-forth if a record is mistyped.

2. Import contacts and rebuild suppression

Import the engaged segment first, not the full list. In the import step, enable duplicate and validity checks, map your custom fields (signup date, last purchase, source), and apply tags such as source:old-platform and engagement:90d.

Then import the suppression list before any campaign goes out. Hard bounces, complaints and unsubscribes from the old platform must be excluded from the new one from the very first send.

Verify: compare the imported contact count against the source file row count, and open the first campaign's audience preview to confirm suppressed addresses are not in it.

3. Set the warm-up volume limits

This is the ramp for a new shared or dedicated IP. Treat the numbers as a starting shape, not a rule:

Day	Daily volume cap
1	200
2	500
3	1,000
4	2,000
5	4,000
6	8,000
7	15,000
8+	roughly double every 2–3 days while metrics hold

Your real ceiling is the lower of that cap and your engaged-audience size. If you have 3,000 engaged contacts, day four is 2,000 and day five is 3,000, not 4,000. Do not exceed the cap because you have more contacts waiting.

Verify: check the platform's send log shows the day's volume at or below the cap. Mailerflow includes warm-up limits and reputation monitoring, so the cap can be enforced in the platform rather than in your head.

4. Send to the most engaged segment first

Define the segment precisely: opened or clicked in the last 90 days, or signed up recently. Send the first three to five campaigns only to this group. These are the people most likely to open, click and reply, and those actions are what mailbox providers read as positive signals.

Keep the content simple: one clear purpose, mostly text, one link, no image-only emails, and a reply-to address someone actually monitors. Replies are a strong positive signal and a useful early-warning system.

Verify: after each send, compare open and click rates against the same segment's numbers in the old platform. A drop is a reason to slow down, not to push on.

5. Ramp volume and widen the audience

Each day, if hard bounces stay low and complaints are near zero, raise the volume and add the next engagement tier: opened 90–180 days ago, then clicked at any point, then the rest. Leave the least engaged contacts for last, or run a re-engagement send before adding them at all.

Verify: log daily volume, bounce rate, complaint rate, open rate and click rate in your spreadsheet. Day-over-day comparison is what tells you whether to increase, hold or pause.

6. Watch the metrics that decide the next step

Metric	Where to find it	What to do
Hard bounce rate	Campaign report, per send	Rising: pause the ramp, clean the list, resume at the previous day's volume
Complaint rate	Campaign report	Rising: stop, review the segment and the unsubscribe path before continuing
Open rate	Campaign report	Dropping versus the old platform for the same segment: slow down
Click rate and replies	Campaign report, reply-to inbox	Strongest positive signals; stable or rising means you can continue

Opens are approximate because of privacy features that pre-fetch or block tracking pixels, so weight clicks and replies more heavily when you decide whether to increase. Mailerflow's analytics cover delivery, bounces, complaints, clicks and approximate opens, per campaign and overall.

A worked example: 40,000 contacts, new subdomain

This is an illustrative example, not a customer story. A retailer moves 40,000 contacts to a new platform on mail.retailer.example. The engaged segment (opened or clicked in 90 days) is 9,000 contacts.

Day	Volume	Segment	Decision
1	200	Engaged 90d	Bounces flat, continue
2	500	Engaged 90d	Continue
3	1,000	Engaged 90d	Continue
4	2,000	Engaged 90d	Hard bounces tick up — hold
5	2,000	Engaged 90d	Suppression re-imported, bounces back to normal
6	4,000	Engaged 90d	Continue
7	8,000	Engaged 90d	Continue
8	9,000	Engaged 90d (rest)	Engaged segment fully mailed
9	12,000	+ opened 90–180d	Continue
10	18,000	+ opened 90–180d	Continue
11	25,000	+ clicked ever	Continue
12	30,000	+ clicked ever	Continue
13	35,000	Remaining	Continue
14	40,000	Remaining	Ramp complete

On day four the retailer saw hard bounces rise. They paused, re-imported the suppression list, checked where the new signups in that batch had come from, and resumed at day three's volume. After two weeks the engaged segment had been mailed in full and the ramp was moving into the less engaged tiers.

How to check it works

Run this checklist at the end of each week:

Authentication passes in a seed test: dkim=pass, spf=pass, dmarc=pass.
The suppression list is applied and suppressed addresses are absent from campaign audiences.
Daily volume stayed within the cap every day.
Bounce and complaint rates are flat or falling.
Open and click rates are within a normal range of the old platform for the same segment.
Inbox placement checked with a seed or panel test.
DMARC aggregate reports (rua) arriving and showing passes.

"Good" here is qualitative: stable or improving engagement, no spike in bounces or complaints, and mailbox providers accepting the volume you send. If any of those break, hold the ramp rather than pushing through.

Common mistakes and fixes

Importing the whole list on day one. Fix: import the engaged segment first and add tiers as the ramp progresses.
Skipping the suppression import. Fix: import hard bounces, complaints and unsubscribes before the first send, every time.
Sending one campaign to everyone at once. Fix: split by engagement tier and send tier by tier.
Using a brand-new domain instead of a subdomain of an established one. Fix: send from a subdomain of a domain with some history where possible.
Ignoring DMARC reports. Fix: read the rua reports weekly; they show who is sending as you and whether authentication is passing.
Treating opens as exact. Fix: weight clicks and replies when deciding to increase volume.
Pausing the ramp for too long. Fix: reputation cools when you stop; resume at the previous day's volume as soon as the issue is fixed.
Not monitoring replies to the first sends. Fix: watch the reply-to inbox daily during the first two weeks.

Where Mailerflow fits

Mailerflow handles several parts of this workflow: own-domain sending with guided DKIM, SPF and DMARC setup and automatic verification; automatic suppression of bounces and complaints, reputation monitoring and warm-up limits; CSV import with duplicate and validity checks, custom fields and tags; free migration help (contacts, suppression lists, templates, core automations) on eligible paid plans; and analytics for delivery, bounces, complaints, clicks and approximate opens. If you are comparing platforms, the same controls exist elsewhere — what matters is that your chosen platform lets you set a daily cap, exclude suppressed addresses and read bounce and complaint data per campaign.

FAQ

How long does warmup take?

For a new subdomain or IP, plan on two to four weeks to reach full volume, longer if your list is large or your engagement is uneven. The pace is set by your metrics, not the calendar: you increase while bounces and complaints stay low and engagement holds.

Do I need a new domain or can I reuse my old one?

Reuse your existing domain and send from a subdomain of it. A domain with some history is better than a brand-new one, and a subdomain keeps bulk sending separate from your company email.

Should I warm up if I keep the same domain and IP?

Yes, but shorter. You are not rebuilding reputation from zero; you are verifying that authentication, suppression and segmentation survived the migration and that the new platform's sending patterns do not cause problems.

A monthly cadence warms slowly because you get few data points. Keep the first few sends small and to your most engaged contacts, and expect the ramp to take a few months rather than weeks.

Can I skip warmup if my list is small?

If your entire list is a few hundred highly engaged contacts, the ramp is short by definition — you are already sending below the day-one cap. You still need authentication and suppression in place before the first send.

Next steps in this cluster

Once the supporting articles are published, this cluster will cover warming up a brand-new domain, warming up a dedicated IP, re-warming after a long sending pause, and re-engaging inactive contacts before a ramp. Read the one that matches your situation before you start sending.

Set up your sending domain in Mailerflow with guided DKIM, SPF and DMARC and automatic verification.