How to Switch Cold Email Platforms: Migration Guide

Most people overthink the deliverability side of switching tools and underthink the operational side. That's backwards. Your sender reputation isn't stored in your current platform. It lives with your sending domains, your mailboxes, and the engagement history those mailboxes have built up at Gmail and Outlook. Move to a new tool and that history comes with you, untouched.

So what actually goes wrong during a migration? Dropped warmup. Authentication that quietly breaks when a record gets overwritten. The same prospect getting two opening emails because both tools were live at once. A suppression list that didn't make the trip, so you email someone who unsubscribed last month. None of those are reputation problems on day one. All of them become reputation problems by week two if you rush.

This guide walks the act of switching: what to inventory, how to move mailboxes between cold email tools, how to migrate cold email campaigns and sequences when there's no export button, and how to run a phased cutover that never leaves your numbers exposed. It doesn't pick a destination tool for you. If you're still comparing options, our roundup of the best cold email software is the place to do that first.

Key Takeaways

• Reputation is portable. It's tied to your domains and mailboxes, not your software, so switching tools doesn't reset it as long as you don't drop volume to zero or spike it.
• The riskiest parts of a migration are warmup continuity, authentication records, and your suppression list, not the move itself.
• Plain-password SMTP is dead at both Google and Microsoft. You'll reconnect every mailbox with OAuth or an app password tied to 2-Step Verification.
• Run both platforms in parallel. Drain old sequences on the incumbent, start new ones on the new tool, and ramp gradually rather than flipping everything overnight.

Does switching cold email platforms hurt your deliverability?

No, not by itself. Switching tools doesn't touch the two things providers actually score: your domain's reputation and your mailbox's engagement history. Google calculates domain reputation from how recipients treat your mail, and that signal sits at the domain level in Postmaster Tools, completely independent of which software pushed the send. Change the tool, keep the domain, and the reputation carries over.

The damage, when it happens, comes from how you switch, not whether you switch. Four mistakes do most of it:

• You pause warmup during the move. Reputation decays when a mailbox goes quiet. A gap of a week or two while you "get set up" can undo weeks of warming.
• You break authentication. Overwrite a DKIM record, point SPF at the wrong place, or leave a tracking domain dangling, and messages start failing alignment or showing broken links.
• You run both tools hot at once. Two live platforms on the same mailbox means duplicate sends, double follow-ups, and prospects who now see you as careless at best.
• You dump full volume into the new tool on day one. Even on a warmed domain, a sudden spike reads as a behavior change. Google explicitly warns against sudden volume jumps and tells senders to increase volume slowly.

Every one of those is preventable with sequencing and a checklist. That's really all a clean migration is.

Step 1: Build a migration inventory before you touch anything

Start by writing down everything the old platform is doing for you. Most botched migrations trace back to an asset nobody documented: a suppression list that lived only inside the tool, a DKIM selector nobody recorded, three contacts mid-sequence who got skipped. You can't move what you haven't catalogued.

Here's the inventory I work from:

That last row is the one people skip, and it's the one that tells you later whether the switch helped or hurt. Pull 30 days of per-mailbox numbers before you move anything. If you're not sure which numbers are worth tracking, our guide to the cold email metrics that matter covers the short list. Without a baseline, every post-migration wobble looks like a disaster, and you can't tell a normal settling period from a real problem.

Step 2: How to move mailboxes between cold email tools

Moving a mailbox is really just re-authorizing it somewhere new. The mailbox itself never moves. You're granting a new application permission to send through the same Google Workspace or Microsoft 365 account. The catch in 2026 is that the easy old method, a username and a plain password, no longer works at either provider.

Google Workspace and Gmail

Google finished removing "less secure app" access across Workspace on May 1, 2025, after killing it for personal Gmail back in 2022. There's no admin toggle to bring it back. That leaves two ways to connect a Gmail mailbox to a new platform:

• OAuth ("Sign in with Google"). The cleanest option. You click through Google's consent screen, the tool gets a scoped, revocable token, and there's no password to store. Use this whenever the new tool offers it.
• An app password. A 16-digit code you generate in your Google Account. It only works on accounts that have 2-Step Verification turned on, so you'll enable 2SV first if it isn't already.

If the new platform connects by raw SMTP, Gmail's settings are smtp.gmail.com on port 587 with STARTTLS, or port 465 with SSL, authenticated by OAuth or that app password. For reply syncing it'll also pull IMAP at imap.gmail.com on port 993.

Microsoft 365 and Outlook

Microsoft has been retiring Basic authentication across Exchange Online for years, and it's removing it for SMTP AUTH client submission too, pushing every sender toward OAuth (modern auth). There's a second gotcha specific to Microsoft: SMTP AUTH has been disabled by default for tenants created after January 2020, and it's a per-mailbox setting. If your new tool needs authenticated SMTP, an admin has to confirm the "Authenticated SMTP" box is checked for each mailbox under Users in the Microsoft 365 admin center.

Microsoft's submission settings are smtp.office365.com on port 587 with STARTTLS, and the protocol supports OAuth in addition to basic auth. Connect with modern auth where you can, since basic auth is on its way out regardless.

Here's the quick-reference version:

One non-negotiable rule for this step: do not stop warmup while you reconnect. Warmup engagement is what keeps a mailbox's reputation warm, and it should keep flowing through the entire transition. If your old tool ran warmup, get the new tool's warmup live on each mailbox before you disconnect the old one, so there's no silent gap. The mechanics of a healthy warmup cadence haven't changed, and our complete warmup guide is the reference if you need to confirm the ramp.

Step 3: Migrate sequences, lists, and your suppression data

Here's the honest part nobody likes: there's no clean way to export sequences to a new platform. Cold email tools don't share a common format for multi-step campaigns. Step copy, delays, branching logic, and A/B variants are all stored differently, so "migrate cold email campaigns" really means "rebuild the sequences and move the data they act on." Plan for the rebuild rather than hunting for an import button that doesn't exist.

Tackle this in three layers, easiest to hardest in terms of consequences if you get it wrong.

1. Sequence content (rebuild, low risk). Copy your step copy, subject lines, delays, and conditions into a plain document, then recreate them in the new tool. This is tedious but forgiving: a typo in a delay is easy to catch. Treat the move as a chance to prune. Most accounts carry a few sequences that never performed, and there's no reason to port dead weight. If you're reworking the follow-up structure while you're in there, our follow-up sequence framework is a good template to rebuild against.

2. Lead lists and live state (medium risk). Export your contacts with their custom fields, and crucially, note which sequence and which step each active lead sits on. This is how you avoid the two classic migration failures: re-sending step one to someone who already got steps one through three, or stranding a prospect who never gets their next touch. For anyone mid-sequence, the safe move is to let them finish on the old tool and only start fresh prospects on the new one. More on that in the cutover step.

3. Suppression and bounce data (high risk, do not skip). Your unsubscribe list, hard bounces, and do-not-contact entries are the one export you cannot afford to lose. Emailing someone who opted out is a compliance problem and a fast way to earn spam complaints, which is exactly the signal that drags a domain down. Export the full suppression list and import it into the new platform before you send a single message. If your old tool buried this list, dig it out anyway. This is the data that protects both your reputation and your legal footing.

Step 4: Sort out DNS and authentication

Most of your DNS doesn't change when you switch tools, and knowing what stays put saves you from "fixing" records that were never broken. If you keep sending through the same mailbox provider, your core authentication is fine as-is. Here's what moves and what doesn't.

• SPF: Usually unchanged. SPF authorizes the servers that send for your domain, and if you're still sending through Google Workspace or Microsoft 365, those include: entries are the same regardless of which tool triggers the send. SPF only changes if you switch to a tool's own sending relay, which most mailbox-based cold email setups don't.
• DKIM: Unchanged for the same reason. The mailbox provider signs the mail, so your existing DKIM selectors stay valid. Don't delete them.
• DMARC: Unchanged. Your policy is about your domain, not your tooling. Leave it where it is.
• Custom tracking domain (CNAME): This is the one that often does need attention. If your old platform served open and click tracking through a branded CNAME, that record points at the old tool's infrastructure. The new tool will give you a new tracking host to point a CNAME at. Update it, or your tracked links break and your click data goes dark.

So the practical rule is: verify, don't rebuild. Confirm SPF, DKIM, and DMARC still pass after the move, and repoint only the tracking CNAME. If a check fails or you inherited a setup you don't fully trust, our SPF, DKIM, and DMARC guide walks the full validation. The goal here is to confirm nothing broke in transit, not to redo authentication you already had working.

Step 5: Run a phased cutover, not a hard switch

The single best decision you can make is to refuse to flip everything at once. Run both platforms in parallel for a stretch, drain the old one, and ramp the new one gradually. A hard cutover is how you get duplicate sends, a volume spike, and a panicked rollback. A phased one barely registers to Gmail and Outlook.

The pattern that works:

1. Connect and warm the new tool first, with the old one still live. Get every mailbox reconnected and warmup running on the new platform while the incumbent keeps handling active campaigns. No prospect is touched by the new tool yet.
2. Stop starting new sequences on the old tool. From here, all fresh prospects begin on the new platform. Anyone already mid-sequence keeps finishing on the old one so they don't get reset or double-touched.
3. Ramp the new tool's volume gradually. Don't move a mailbox from zero to its full daily number overnight. Google's guidance is explicit: start with a low volume to engaged users and increase it slowly, avoiding sudden spikes. Treat the new tool like a soft restart of volume, even though the domain is already warm.
4. Let the old sequences drain, then disconnect. Once the last mid-sequence prospect on the incumbent has finished their final step, you can disconnect those mailboxes from the old tool and cancel it. Nobody's left stranded.

How long should the parallel period run? Long enough for your longest active sequence to finish, usually two to four weeks. If you spread volume across many mailboxes, this is also the moment to confirm your distribution is sane on the new tool. Our inbox rotation guide covers how to share load so no single mailbox carries a dangerous spike during the ramp.

Step 6: Validate before you call it done

Don't trust the migration until you've measured it. The new tool's dashboard showing "sent" tells you nothing about where mail landed. Run an actual validation pass before you scale volume back up, and compare it against the baseline you captured in Step 1.

Work through this check:

• Inbox placement test. Send to a seed set across Gmail, Outlook, and Yahoo and confirm you're landing in the primary inbox, not spam or Promotions. This is the truest signal that the move was clean.
• Authentication pass. Send yourself a message and check the headers show SPF, DKIM, and DMARC all passing under the new setup.
• Tracking and links. Confirm tracked links resolve under your repointed CNAME and that click and open data is actually recording.
• Reply capture. Send a test, reply to it, and verify the response lands in the new tool's inbox view. A migration that drops replies is silently losing you deals.
• Unsubscribe flow. Trigger an unsubscribe and confirm it writes back to your suppression list. If opt-outs aren't being recorded, stop and fix it before sending more.
• Reputation watch. Keep an eye on Postmaster Tools for the first couple of weeks. Hold your spam rate below 0.10%, and never let it approach the 0.30% line Google treats as a hard problem.

For a structured version of this pass, our deliverability audit checklist is the full 10-step diagnostic, and our guide to domain health monitoring covers what to watch on an ongoing basis once the dust settles. If every check passes and your numbers hold near your baseline, the switch worked. If placement drops, you've caught it early, while volume is still low and recoverable.

A realistic migration timeline

Migrations feel urgent, but the calendar is mostly dictated by your longest sequence and your warmup ramp, not by how fast you can click. Here's a sane shape for a multi-mailbox switch.

The parallel run is the part you can't compress, because it's gated by real prospects finishing real sequences. Trying to shortcut it is how you end up double-sending. If you're not migrating but building from scratch, the timeline and the steps are different, and our guide to cold email infrastructure covers the greenfield path instead.

Common questions about switching cold email platforms

Will I lose my warmup if I switch tools?

Not if you keep warmup running through the move. Warmup builds reputation at the domain and mailbox level, and that reputation stays with the mailbox no matter which tool sends. What you can lose is the momentum: if warmup stops while you set up the new platform, the mailbox goes quiet and reputation starts to slide. So get the new tool's warmup live on each mailbox before you disconnect the old one, and there's no real gap.

Can I export my sequences directly to a new platform?

Usually not. Cold email tools don't share a standard format for multi-step sequences, so there's rarely a one-click way to export sequences to a new platform and import them whole. Plan to rebuild them: copy the step content, delays, and branching into a document, then recreate them in the new tool. The upside is you get to prune sequences that never performed instead of carrying them over.

Do I need to change my SPF, DKIM, and DMARC when switching?

Generally no. If you keep sending through the same mailbox provider, SPF, DKIM, and DMARC all stay the same, because they describe your domain and its provider, not your tooling. The one record that often does change is a custom tracking domain CNAME, which points at your old tool's tracking host and needs repointing to the new one. Verify all four after the move rather than rebuilding anything.

How long should I run both platforms in parallel?

Long enough for your longest active sequence to finish, which is typically two to four weeks. During that window, start all new prospects on the new tool and let anyone already mid-sequence complete their steps on the old one. Once the last in-flight sequence drains, you can disconnect the old mailboxes and cancel the subscription.

Will switching reset my domain reputation?

No. Domain reputation is computed by the receiving providers from how recipients engage with your mail, and it's tied to your domain, not your software. Google reports it at the domain level in Postmaster Tools. Switching tools doesn't reset it. The only way a switch hurts reputation is indirectly: a warmup gap, a volume spike, or broken authentication, all of which the phased approach above prevents.

The bottom line

Switching cold email platforms is low-risk when you treat it as an operational migration and high-risk when you treat it as a single flip of a switch. Your reputation is portable. Your sequences are not, so you rebuild them. Your suppression list is non-negotiable, so you export it first. And your warmup has to keep running the whole way through.

Do it in order: inventory everything, reconnect mailboxes by OAuth, rebuild sequences and move the data, verify DNS instead of redoing it, then run both tools in parallel while you ramp the new one gradually and validate placement before you scale. Move through those steps with a little patience and the providers will barely notice you changed anything. That's the goal. A migration nobody on the receiving end can detect.

MailBeast was built to make this kind of move boring: OAuth mailbox connection, warmup that runs alongside your campaigns, and deliverability monitoring so you can see the switch worked instead of hoping it did.

Sources

• Google, Email sender guidelines
• Google, How 2-Step Verification works with legacy apps
• Google, Sign in with app passwords
• Google, IMAP, POP, and SMTP
• Microsoft, Deprecation of Basic authentication in Exchange Online
• Microsoft, Enable or disable SMTP AUTH in Exchange Online