What happens when a company with 200 mailboxes and fifteen years of archived email decides to switch providers? Someone has to move every message, every folder, every calendar entry, and every contact without losing a single thread. That job falls to email migration services, and the market for them is more confusing than most buyers expect. Some tools charge per mailbox. Others charge per gigabyte. A few charge a flat fee and then quietly throttle your transfer until the project drags on for weeks.
This comparison breaks down how the major categories of migration services actually work, where the hidden costs hide, and which questions separate a smooth cutover from a month of support tickets.
What Email Migration Services Actually Do
At the core, a migration service copies mailboxes from one system to another. Most tools do this server-to-server using IMAP, the standard protocol for accessing mail stored on a server. The current specification, IMAP4rev2, was published as RFC 9051 in August 2021 and updated the long-standing RFC 3501 from 2003. Because both revisions are still widely deployed, the extensions a tool supports matter more than the version number on the box.
Beyond raw copying, a full migration usually covers:
- Mail, including nested folders and labels
- Calendar events and shared calendars
- Contacts and distribution lists
- Rules, signatures, and out-of-office settings (often only partially)
- Permissions and delegation rights (frequently manual)
The gap between “copies email” and “copies everything” is where budgets blow up. A tool that handles mail flawlessly but drops calendar recurrence exceptions will leave users grumbling for months.
The Four Main Types of Migration Providers

Buyers tend to lump very different services under one label. Sorting them first saves time.
| Type | Typical pricing model | Best for | Main trade-off |
|---|---|---|---|
| Built-in provider tools | Included with plan | Same-vendor moves, small teams | Limited source support |
| Self-serve migration software | Per mailbox or per GB | IT teams with in-house skills | You own the troubleshooting |
| Managed migration services | Fixed project fee or per mailbox | Companies without spare IT capacity | Less control, higher cost |
| Full-service IT consultancies | Day rates or scoped contracts | Complex hybrid environments | Slowest, priciest |
Google documents its own data migration service for importing mail from other providers into Workspace, and Microsoft publishes a full overview of Exchange Online migration methods covering cutover, staged, hybrid, and IMAP approaches. These native tools are genuinely useful, but they assume a clean, well-documented source environment. They also assume you have someone who knows which of the four Microsoft methods fits your mailbox count and coexistence needs.
Why Per-Mailbox Pricing Is Trickier Than It Looks
Per-mailbox pricing sounds fair until you count the mailboxes. A 500-seat company at $12 per mailbox pays $6,000. The same company with 40 shared mailboxes, 30 departed-employee archives, and a dozen resource accounts suddenly has 582 billable objects.
Watch for these pricing traps:
- Shared and resource mailboxes billed as full seats. Ask explicitly whether shared mailboxes count.
- Archive mailboxes priced separately. Many vendors treat online archives as an add-on.
- Re-runs charged again. If a delta pass fails, does the vendor bill twice?
- Minimum project fees. Small migrations often hit a floor price that makes per-mailbox math meaningless.
- Data overage tiers. Some tools include 10 GB per mailbox and charge per extra gigabyte, which punishes long-tenured staff.
If you are comparing vendors on cost, it helps to see how other software categories structure their billing, because the same tricks show up everywhere. A close look at email marketing tools pricing comparison you actually pay shows how seat counts, contact tiers, and send limits stack up in ways the headline price never reveals.
The Authentication Problem Nobody Warns You About
Here is the mistake that derails more migrations than any other: assuming a username and password will still work.
Modern mail providers have moved to OAuth 2.0, the authorization framework specified in RFC 6749, for third-party access. Microsoft began disabling basic authentication for Exchange Online across 2021 and 2022, and Google has required modern authentication for most client and migration scenarios. A migration tool that only supports password-based login may simply not connect to your source or destination tenant.
Before signing anything, confirm the tool supports:
- OAuth 2.0 for both source and target
- Multi-factor authentication on admin accounts
- App registration with granular scopes rather than full tenant access
- Token refresh across long-running migrations
This single check eliminates half the shortlist. It also explains why some quotes look cheap: the vendor has not yet built modern auth and is pricing for the customers who have not noticed.
Speed, Throttling, and the Timeline You Were Promised
Every vendor claims a migration speed. Almost none of those numbers survive contact with provider rate limits. Google and Microsoft both document API and IMAP throttling per tenant, and those limits vary by edition and by time of day. A tool advertising “10 GB per hour” is describing a best case that your provider may not permit.
Practical guidance from people who run these projects:
- Run a pilot with 10 to 20 real mailboxes before committing to a date. Measure actual throughput on your own tenant.
- Start the bulk pass early. Large historical mailboxes can take days regardless of vendor promises.
- Plan for a delta pass. A final sync of new mail between the bulk copy and the cutover is standard practice, and it needs its own window.
- Never schedule cutover on a Monday. Give yourself business days to fix what breaks.
Throttling also interacts with concurrency. More parallel connections do not always mean faster transfers; providers often penalize aggressive clients with temporary blocks that cost more time than they save.
Security, Compliance, and the Paperwork Buyers Forget
A migration vendor will handle every message your organization has ever sent. That is a serious data-processing relationship, and the paperwork matters.
Under the EU General Data Protection Regulation (Regulation (EU) 2016/679), a vendor processing personal data on your behalf generally requires a data-processing agreement under Article 28. If your mailboxes contain protected health information, the US HIPAA Security Rule at 45 CFR Part 164, Subpart C, adds safeguard requirements and typically a business associate agreement with the vendor.
For a broader security baseline, NIST Special Publication 800-45 Version 2 covers guidelines on electronic mail security, including authentication and transport considerations that are useful when writing migration requirements.
Questions worth putting in writing:
- Where is migration data stored during the transfer, and for how long afterward?
- Is data encrypted in transit and at rest?
- Who on the vendor side can access mailbox contents?
- What is the deletion timeline once the project closes?
- Will the vendor sign a DPA or BAA without negotiation?
A vendor that hesitates on the last point is telling you something.
Don’t Forget Email Authentication at Cutover
Migration is not finished when the last mailbox lands. If your sending domain or gateway changes, your SPF, DKIM, and DMARC records must be updated. DMARC is specified in RFC 7489, and a misconfigured record after cutover can send legitimate mail straight to spam or get it rejected outright.
Build these into the runbook:
- Publish updated SPF records including the new sending infrastructure.
- Rotate DKIM keys and publish the new selectors.
- Keep DMARC in monitor mode through the transition, then tighten the policy.
- Test with real external recipients in addition to internal accounts.
Teams that skip this step often blame the migration tool for deliverability problems that are actually DNS problems.
Where Adjacent Tools Fit Into the Budget
Migration rarely happens in isolation. Most projects also touch list hygiene, outreach, and client communication, and those line items compete for the same budget. If you are cleaning contact data before or after the move, a look at email verification tools pricing comparison you actually pay helps you see whether per-verification credits or flat plans make more sense at your volume. Teams that need to rebuild prospect lists from scratch after a domain change often weigh email finder tools pricing comparison you actually pay per, where per-result pricing can quietly outrun a subscription.
For very small organizations, the smarter play is sometimes to skip paid migration software entirely. Budget-friendly options exist, and a roundup of best low cost email marketing tools that still deliver shows how much capability now sits at the low end of the market. The same logic applies to verification: best low cost email verification tools actually works budget covers what cheap tools genuinely handle well and where they fall short.
A Practical Comparison Framework
When quotes land in your inbox, normalize them before comparing. Build a simple grid:
| Question | Why it matters |
|---|---|
| Total billable objects, including shared mailboxes | Reveals the real per-seat cost |
| Re-run and delta pass policy | Failed syncs are common; know who pays |
| OAuth 2.0 support on both ends | Non-negotiable in 2026 |
| Measured throughput on a pilot | Replaces marketing speed claims |
| Data residency and retention | Drives DPA and BAA requirements |
| Cutover support included? | Weekend coverage costs extra with some vendors |
| Post-migration verification report | Proves nothing was lost |
Score each vendor against the same grid. The cheapest quote frequently loses once re-runs and shared mailboxes are counted, and the fastest claim usually evaporates during the pilot.
Common Mistakes That Cost Real Money
Three patterns show up again and again.
First, migrating without an inventory. Nobody knows how many mailboxes exist until the bill arrives. Export a full list from the admin console before requesting quotes.
Second, skipping the pilot. A ten-mailbox test on a Tuesday afternoon costs almost nothing and surfaces authentication, throttling, and folder-mapping problems while they are still cheap to fix.
Third, treating cutover as the finish line. Post-migration verification, DNS updates, client reconfiguration, and user training all happen after the “go live” email. Budget time for them or the project will feel unfinished for weeks.
Conclusion
Email migration services range from free native tools to six-figure consultancy engagements, and the price difference rarely tracks the quality difference. What separates a good project from a painful one is preparation: an accurate mailbox inventory, verified OAuth support, a measured pilot, a written data-processing agreement, and a cutover plan that includes DNS and authentication updates. Compare vendors on total billable objects and re-run policy rather than headline rates, and insist on real throughput numbers from a pilot on your own tenant. Do that, and the migration becomes a scheduled IT project instead of an emergency.
Frequently Asked Questions
How long does an email migration usually take?
For a few hundred mailboxes, bulk transfer typically runs from several days to a couple of weeks, depending on mailbox sizes and provider throttling. Large historical archives and hybrid environments stretch longer. Always add a delta pass and a buffer of business days after cutover for verification and client fixes.
Is it cheaper to migrate email myself with built-in tools?
Often yes, if your source and target are well documented and you have IT staff who understand the provider’s native migration methods. Built-in tools are included with your plan, which makes them attractive for small teams. The trade-off is that troubleshooting, re-runs, and cutover support all land on your own people.
What is OAuth 2.0 and why does it matter for migration?
OAuth 2.0 is the authorization framework that lets a migration tool access mailboxes without storing user passwords. Major providers now require it instead of basic authentication for most third-party access. A tool that only supports password login may fail to connect entirely, so confirm OAuth support on both source and target before signing.
Do shared mailboxes count toward migration pricing?
It depends entirely on the vendor, and the answer can swing a quote by thousands. Some bill shared, resource, and archive mailboxes as full seats; others charge a reduced rate or include them. Get the answer in writing and count every object in your tenant before comparing totals.
What paperwork should a migration vendor sign?
If personal data is involved, expect a data-processing agreement, which GDPR Article 28 generally requires when a vendor processes data on your behalf. If mailboxes contain protected health information, a business associate agreement under the HIPAA Security Rule is typically needed too. Vendors who resist these agreements are a red flag.
Can I lose email during a migration?
Loss is rare with reputable tools, but it happens when folder mappings are wrong, delta passes are skipped, or verification is never performed. Insist on a post-migration report comparing message counts per folder between source and target, and keep the source system read-only but intact until the report is signed off.