Home › Blog › Cold Email Provider Migration Checklist: Zero Lost Replies
Cold Email Provider Migration Checklist: Move Inboxes Between Google, Microsoft, or SMTP with Zero Lost Replies
Moving mailboxes between providers is a different animal from switching sequencers: this time the mailboxes themselves change, and the domains' DNS moves with them. The prize for doing it right is keeping every domain's hard-earned reputation. Here is the checklist that preserves DNS, conversations, forwarding, and baselines through the cut.
Quick Answer: Domain by Domain, DNS in One Window, Half-Warmup After
Provision new mailboxes first, IMAP-copy the conversations, then per domain in one change window: MX + SPF + new DKIM (leave old DKIM up during overlap), with sending paused 24-48h around the cut. Verify auth on real sends, resume at one-third volume ramping over two weeks, and keep old accounts readable for 30 days. Reputation rides the domain: clean DNS work carries it across intact.
The Checklist
BEFORE
□ zone snapshot per domain (DNS Checker export)
□ new mailboxes provisioned + tested
□ IMAP copy of conversations started
□ sequencer paused on affected domains
□ analytics baseline exported (compare after)
CUT (per domain, one window)
□ MX → new provider
□ SPF: swap include, still one record, ≤10 lookups
□ DKIM: add new keys; KEEP old records 30 days
□ provider CNAMEs; DMARC untouched, reports on
□ verify with Deliverability Checker + real send
→ Header Analyzer: spf=pass dkim=pass aligned
AFTER
□ reconnect mailboxes to sequencer
□ wk1 ~35% volume, wk2 ~65%, wk3 full
□ watch: bounce codes, seed matrix, DMARC reports
□ old accounts read-only 30 days, then close
□ update fleet inventory + monitoring targets- •Batch the fleet in waves (say 20% of domains per week): if anything surprises you, it surprises a slice, and the untouched majority keeps sending. Your rotation pools map naturally onto this, migrate the resting batch first.
- •DMARC reports are your migration telemetry: they show authentication results from real receivers during the cut, which catches a botched SPF or missing DKIM within hours (DMARC setup).
- •Verify with tools, then with mail: the Deliverability Checker confirms records, but the finish line is a real send whose headers read spf=pass and dkim=pass with the new signatures, checked in the Header Analyzer.
- •If Cloudflare runs your DNS, the whole cut is a scripted template swap per the bulk pipeline, which is the difference between a weekend and an afternoon at fleet scale.
Frequently Asked Questions
How do I migrate cold email inboxes to a new provider without losing replies?
Domain by domain, not all at once: (1) provision the new mailboxes on the new provider first, (2) IMAP-copy existing conversations across so thread history survives, (3) update DNS per domain, MX to the new provider, new SPF include, new DKIM keys, in one change window, (4) pause sending on that domain for 24-48h around the MX change while propagation settles, (5) verify auth passes on real sends from the new provider before resuming volume, (6) keep old accounts alive read-only for 30 days as the catch-all for anything mid-flight. Reputation is attached to the domain, so a clean DNS cut preserves it.
Does domain reputation survive a mailbox provider change?
Mostly yes: domain reputation, your DMARC history, and blocklist status travel with the domain, not the provider. What changes is the sending infrastructure behind it, new outbound IPs, new DKIM signatures, which receivers notice as a shift. That is why you resume at reduced volume for the first week and watch bounce codes and seed placement: filters re-learn the new fingerprint quickly when authentication is clean and volume is polite. What does NOT survive is skipped steps: a missed SPF update means a hard authentication failure on every send.
How do I move the actual emails between providers?
IMAP migration: both Google and Microsoft ship migration tools (Google's data migration service, Microsoft's IMAP migration in the 365 admin), and third-party movers handle bulk fleets. For cold email inboxes the priority is reply threads, past conversations with prospects, so a rep answering from the new mailbox has history. Calendars and contacts rarely matter for sending fleets. Budget real time: IMAP moves are slow per-mailbox, run them in parallel and start days before the DNS cut.
What DNS changes exactly, and what must not change?
Changes: MX records (new provider's hosts), SPF (swap the old include for the new one, keep it single-record and under 10 lookups), DKIM (new keys/selectors from the new provider; leave the old DKIM records up during the overlap so in-flight mail still verifies), and any provider-specific CNAMEs. Must not change: the domain itself, your DMARC record's policy (keep reporting on through the migration, the reports are your verification), and the web redirect. Snapshot the zone before touching anything.
When should I re-warm after a provider migration?
Treat it as a half-warmup, not a fresh start: the domain is known, the infrastructure is new. Week one at roughly a third of normal volume with warmup activity enabled on the new provider, week two at two-thirds while watching seed placement and bounce codes, full volume from week three if everything reads clean. Jumping straight to full volume on day one through brand-new IPs is the one reliable way to make a routine migration look like a reputation incident.
Get FREE .com Domains
Prewarmed Inboxes So You Can Send Cold Emails Today
Get Prewarmed & Fresh InboxesPrewarmed & Fresh Inboxes
Google, Microsoft 365 and Azure inboxes with free prewarmed domains and DNS configured before you log in. Prewarmed inboxes send the day they land; every order is delivered within 48 to 72 hours.
Get Prewarmed & Fresh Inboxes