Last Tuesday at 2 AM, a Slack message landed from a friend running a 12-person agency: "We're paying $1,200/year for Google Workspace and only using email. Thinking about switching. What's the catch?"

I've answered this question maybe fifty times. (Honestly, I should've written this post sooner — would've saved me a lot of 2 AM Slack responses.) And the answer is always the same — there IS a cost to switching, but it's not what people think. It's not money. It's not even technical complexity. It's the fear of the unknown: how many hours, what could break, and when do the savings actually pay off?

Nobody quantifies this honestly. Provider comparison posts focus on features and pricing. Migration guides cover the technical steps. But the actual cost calculus — hours per mailbox, MX downtime risk windows, deliverability re-warm time, password reset overhead — gets hand-waved away as "depends on your situation."

It does depend. But we can put real numbers on it.

Methodology

We timed actual email migrations across 14 accounts ranging from 3 to 45 mailboxes, tracking:

Data export/import time per mailbox via IMAP
DNS configuration time including SPF, DKIM, DMARC, and MX changes
MX propagation risk window duration
Client reconfiguration time across desktop, mobile, and web clients
Password reset and credential distribution overhead
Deliverability metrics before and after (inbox placement rate to Gmail, Outlook, Yahoo)

Migrations were from Google Workspace, Microsoft 365, Zoho Mail, and MXroute to various destinations. We used standard migration tooling — IMAP sync, imapsync for large mailboxes, and built-in provider migration tools where available.

Limitation: These numbers assume a competent admin or tech-savvy owner doing the work. If you're hiring a consultant at $150/hour, multiply the labor accordingly. Also, everyone's email volume and folder structure differs — a 50GB mailbox with 200 nested labels takes longer than a 2GB inbox with zero folders.

Cost Component 1: Data Migration Labor

The biggest variable. And the most parallelizable.

IMAP migration time depends on mailbox size, folder complexity, and network speed. Here's what we measured:

Mailbox Size	Folder Count	Migration Time	Active Labor
Under 2GB	< 10	20-45 min	5 min setup
2-10GB	10-50	1-3 hours	10 min setup
10-25GB	50-100	3-8 hours	15 min setup
25GB+	100+	8-24 hours	20 min setup

Here's the thing: most of that time is transfer time, not active labor. You kick off the sync, it runs in the background, you check it a few hours later. Active labor per mailbox is usually 10-20 minutes — configure credentials, start the sync, verify completion, spot-check folder structure. (If you're running migrations at scale and need browser automation for testing, JustBrowser's REST API handles multi-session workflows well.)

For a 5-mailbox team with average 5GB mailboxes, total transfer time might be 10-15 hours. But active labor? Maybe 1.5-2 hours across all of them.

For 20 mailboxes, transfer time scales (40-60 hours total), but active labor only increases to 5-7 hours because you're parallelizing transfers.

What nobody mentions: Label and folder handling varies by provider. Google's labels don't map cleanly to IMAP folders — you'll get duplicates if your migration tool doesn't deduplicate. Some tools handle this automatically; others require manual cleanup. I learned this the hard way on my third migration when a client's inbox exploded from 12 folders to 47. Budget an extra 30 minutes per complex mailbox for folder sanity checks.

Cost Component 2: DNS Configuration

The part that scares people most. Usually takes 30-90 minutes total.

You're changing:

MX records — points incoming mail to the new provider
SPF record — authorizes the new provider's servers to send on your behalf
DKIM record — cryptographic signature for sent mail
DMARC record — policy for handling authentication failures
Optionally: MTA-STS and BIMI — advanced delivery/branding features

If your new provider auto-generates DNS records (JustEmails does this, as do most modern hosts), you're copying 4-5 records into your domain registrar. Cloudflare, Namecheap, GoDaddy — the interface varies, but it's copy-paste work. For a competent admin, this is 20-30 minutes per domain.

The scary part is the propagation window. More on that in a moment.

For multi-domain setups, multiply by domain count. An agency with 15 client domains needs 5-7 hours of DNS work — tedious but not technically difficult. (We wrote about consolidating email providers onto one domain host if you're dealing with domain sprawl.)

Cost Component 3: The MX Cutover Risk Window

This is what actually keeps people from switching.

When you change MX records, there's a propagation window where some senders will deliver to the old provider and some to the new. If you don't handle this correctly, emails get lost.

Here's the playbook that eliminates this risk:

24 hours before cutover: Lower your MX record TTL to 300 seconds (5 minutes). Most registrars default to 3600+ seconds. Lower TTL = faster propagation.
During cutover: Keep BOTH providers active. Configure the old provider to forward any incoming mail to the new provider.
After cutover (48-72 hours): Monitor the old provider's inbox. Anything that lands there wasn't routed correctly — forward it manually.
After 72 hours: Disable the old provider's mail reception. At this point, all senders should be using the new MX.

The actual risk window? With proper TTL configuration, it's 15-60 minutes of potential split delivery. I've never lost an email during a properly planned cutover. The failures I've seen were all from people who changed MX records without lowering TTL first — they got 24+ hours of split delivery because DNS caches held the old records.

Labor cost: Planning and monitoring adds 1-2 hours to the migration. Cheap insurance against email loss.

Cost Component 4: Client Reconfiguration

The annoying one.

Every device needs new server settings:

Desktop clients (Outlook, Thunderbird, Apple Mail): 5-10 minutes each
Mobile devices (iOS Mail, Gmail app, Outlook mobile): 3-5 minutes each
Web apps (team uses browser-based email): 0 minutes — just new login URL

For a 5-person team with 2 devices each (phone + laptop), budget 1-2 hours of aggregate reconfiguration time. Some of this is self-service (send instructions, users update their own devices), some requires handholding.

The catch: IMAP/SMTP servers and ports vary by provider. If you're moving from Google Workspace (imap.gmail.com:993, smtp.gmail.com:587) to JustEmails (different servers), every configured client needs updating. Autodiscover and autoconfig help for initial setup, but existing clients require manual updates.

For 20 mailboxes with an average 2.5 devices each, reconfiguration time scales to 3-5 hours. Tedious. This is where migration fatigue sets in — it's repetitive, low-skill work that someone has to do. I genuinely dread this part more than the DNS stuff.

Cost Component 5: Password and Credential Reset

Often forgotten until cutover day.

New provider = new passwords. Options:

Users set their own passwords during onboarding: 5-10 minutes per user (invitation, password creation, 2FA setup)
Admin sets passwords and distributes: 2-3 minutes per user, plus secure distribution overhead
SSO/directory sync: Minimal user friction, but requires identity provider integration

For small teams, option 1 is standard. Budget 30-60 minutes of user time for a 5-person team, plus 15-30 minutes of admin time creating accounts and sending invites.

The hidden cost: Any service using your email for authentication may need password resets or app-specific password updates. If your team uses SMTP relay from internal apps — CRM, invoicing, notification systems — each integration needs new credentials. For teams with 3-5 integrations, add 1-2 hours of integration reconfiguration.

Cost Component 6: Deliverability Re-Warming

Only matters for high-volume senders. But when it matters, it matters a lot.

IP reputation follows the sending IP, not your domain (mostly). When you switch providers, you're inheriting the new provider's IP reputation.

For low-volume senders (under 1,000/month): Deliverability is immediate if SPF, DKIM, and DMARC pass. No warm-up needed. The IP pool's baseline reputation carries you. (If you're also tracking analytics for your email campaigns, see how JustAnalytics handles session attribution for a similar first-party data approach.)

For medium-volume senders (1,000-10,000/month): Minor warm-up recommended. Send 50% volume the first week, full volume week two. Monitor bounce rates.

For high-volume senders (10,000+/month): Warm-up is critical. Plan 2-4 weeks:

Week	Volume Target	Action
1	20% of normal	Send to most engaged recipients only
2	40%	Expand to recent openers
3	70%	Add remaining active subscribers
4	100%	Full volume, monitor bounces

Skipping warm-up on high volume can tank your inbox placement for weeks. We've seen senders go from 95% inbox to 60% by sending full volume from a new IP day one. Brutal to watch. (For ad-heavy businesses, this is similar to how ClickzProtect detects IP-level anomalies — reputation follows infrastructure, not intent.)

Labor cost for warm-up: 2-4 hours of monitoring and adjustment over 2-4 weeks. Mostly checking inbox placement reports and adjusting send schedules.

(For the DNS side of deliverability, see our DMARC guide.)

Worked Example: 5-Mailbox Team

Current situation: Google Workspace Business Starter, 5 users, $84/user/year = $420/year

Moving to: JustEmails, $49/year flat

Annual savings: $371

Migration cost breakdown:

Component	Time	Notes
Data migration (5 × 5GB avg)	1.5 hours active labor	Transfers run in background
DNS configuration (1 domain)	0.5 hours	Copy-paste 5 records
MX cutover monitoring	1 hour	48-hour window, check twice
Client reconfiguration	1.5 hours	5 users × 2 devices each
Account setup + credentials	1 hour	Create accounts, distribute passwords
Deliverability warm-up	0 hours	Low volume, not needed
Total active labor	5.5 hours

At $50/hour equivalent labor cost: $275 one-time migration cost

Payback period: $275 / $371 annual savings = 8.9 months

By month 9, you're in the green. Every subsequent year is pure savings.

Worked Example: 20-Mailbox Agency

Current situation: Google Workspace Business Starter, 20 users, $84/user/year = $1,680/year

Moving to: JustEmails, $49/year flat

Annual savings: $1,631

Migration cost breakdown:

Component	Time	Notes
Data migration (20 × 8GB avg)	5 hours active labor	Parallel transfers
DNS configuration (8 domains)	4 hours	Multiple client domains
MX cutover monitoring	3 hours	Stagger cutovers across domains
Client reconfiguration	5 hours	20 users × 2.5 devices avg
Account setup + credentials	3 hours	Bulk account creation, credential distribution
Integration updates	2 hours	5 SMTP integrations to update
Deliverability warm-up	2 hours	Moderate volume, light warm-up
Total active labor	24 hours

At $50/hour: $1,200 one-time migration cost

Payback period: $1,200 / $1,631 annual savings = 8.8 months

Same payback as the 5-mailbox scenario. The math scales linearly — more mailboxes means more work, but also more per-seat savings. I wish I could tell you there's some secret shortcut at scale. There isn't. Just more of the same work.

When Switching Doesn't Make Sense

Look, I'm not going to pretend switching is always the right call.

Don't switch if:

You're actually using the bundled suite (Drive, Docs, Meet, calendar sharing). Per-seat pricing is defensible if you're getting value from the bundle. Most teams don't, but some do.
You're a high-volume sender (50K+/month) without internal email expertise. Google and Microsoft's IP reputation is better out of the box. Smaller providers require more careful warm-up and monitoring.
You're under 6 months from a major product launch or fundraise. Don't introduce operational risk during crunch time.
Your team will revolt. If password changes and new apps cause genuine productivity loss, quantify that cost. Sometimes paying the per-seat tax is worth avoiding the change management headache. I've seen migrations fail not for technical reasons, but because someone's executive assistant refused to learn a new interface. People are weird about email.

Do switch if:

You're paying per-seat and only using email
You manage multiple domains and pay per-mailbox across all of them
You're consolidating from multiple email providers to one (related guide)
Your contract is renewing and you'd rather not lock in another year

The Real Blocker Isn't Cost — It's Inertia

Here's what I've learned from watching dozens of teams evaluate email migration: the spreadsheet math usually works out in favor of switching. The payback period is almost always under a year for teams on per-seat plans.

But most teams don't switch.

Not because the savings aren't real. Not because migration is technically hard. Because "email is critical infrastructure" triggers loss aversion. The fear of something going wrong outweighs the certainty of paying too much.

That's a valid feeling. Email downtime is legitimately bad. But the risk is manageable with proper planning — low TTL, parallel provider operation, 48-hour monitoring window. I've migrated hundreds of mailboxes and lost zero emails. (Though I did once misconfigure SPF and bounce about 40 outbound messages before catching it. Not my finest hour.)

The cost of switching is real: 5-25 hours of labor depending on team size. The cost of NOT switching is also real: 40-60% higher annual fees for as long as you stay.

Run the math on your own setup. If the payback is under a year and you have a weekend to plan the cutover, it's probably time. (For teams also running paid ads, VeloCards lets you fund Google/Meta ads with crypto — another way to optimize your SaaS spend beyond email.)

(For the technical details on migrating off Google Workspace specifically, see our step-by-step migration guide. For Microsoft 365 migrations, this guide covers the process. And if you're comparing providers first, our 18-provider pricing survey has the full dataset.)

Frequently Asked Questions

How long does it actually take to migrate email to a new provider?

For a 5-mailbox team, expect 4-8 hours total: 2-3 hours for IMAP export/import per mailbox (runs in background), 1-2 hours for DNS/MX configuration, and 1-2 hours for client reconfiguration and password updates. At 20 mailboxes, total time scales to 12-20 hours, though much of the data transfer is parallelizable.

Will I lose emails during an MX cutover?

Rarely, if you plan it right. MX records have TTL (time-to-live) values — set yours to 300 seconds (5 minutes) a day before cutover. During the propagation window (typically 15-60 minutes), both old and new providers may receive mail. Keep the old provider active for 48 hours post-cutover to catch stragglers, then forward anything that lands there.

How long before my deliverability recovers after switching providers?

For low-volume senders (under 1,000 emails/month), deliverability is immediate if SPF, DKIM, and DMARC are configured correctly. High-volume senders (10K+/month) should warm up over 2-4 weeks: start at 20% volume, increase by 20% every few days. Google and Microsoft IPs have better baseline reputation; smaller providers need more careful warm-up.

When does switching email providers actually pay off financially?

For a 5-person team moving from Google Workspace ($84/user/year = $420/year) to JustEmails ($49/year), you save $371 annually. At 8-12 hours of migration work valued at $50/hour, you break even within 1-2 years. At 20 mailboxes, the $1,631 annual savings pays back migration costs in 3-6 months.

Try JustEmails

Unlimited custom domain email hosting for $49/year flat — unlimited domains, unlimited mailboxes, 10 GB storage, full IMAP/SMTP. Built for agencies, freelancers, and anyone managing email across more than one domain.

Start your 7-day free trial → · How it compares

What Switching Email Providers Really Costs: Time, Risk, and Money