Free vs Paid Email Migration Tools: When Each One Wins

You are pricing a migration and the spreadsheet has two columns: $0 and "depends on the vendor call." Free tools work. Paid tools work. They are not the same product and they do not fit the same project. This breakdown is the honest read from someone who has shipped both, so you can pick before the kickoff, not after the first failed wave.

What "free" actually covers#

Three categories sit under the free umbrella and they behave differently.

Native cloud paths. The Google Data Migration Service (DMS) inside admin.google.com and the migration wizards inside the Microsoft 365 Exchange Admin Center are included with the destination platform license. There is no per-mailbox cost. You pay engineering time and accept the limits of the wizard.

Open-source CLIs. imapsync (GPL source), the Thunderbird ImportExportTools NG extension, getmail, offlineimap, mbsync (isync). Free to download, compile, and run. You pay nothing in license. You pay engineering time and the cost of running them on your own infrastructure.

Free tiers of commercial tools. Many paid vendors expose a 5-mailbox or 25-mailbox free tier. Useful for testing, not viable for the project itself.

These behave very differently from each other. A native cloud path is a managed service you run from a web console. An open-source CLI is a binary you orchestrate yourself. A free tier is a marketing on-ramp. Lumping them all together as "free" is the mistake teams make on the first vendor call.

What "paid" actually covers#

Two patterns:

Per-mailbox SaaS. BitTitan MigrationWiz, CloudM Migrate, SkyKick, Quest On Demand, Avepoint Fly. You pay $8 to $20 per mailbox depending on volume and bundled workloads. The vendor runs the orchestration, you watch a dashboard, support is included to varying degrees.

One-time licensed software. A smaller category: tools you buy a perpetual or annual license for and run yourself. Older Exchange migration tools, some niche source-specific products. Less common in 2026.

Most "paid" conversations are about per-mailbox SaaS. The per-seat price funds a real team building real product, including the orchestration and the reporting that free tools either lack or hide behind manual work.

Feature matrix#

When free is enough#

Three cases where free is the right answer.

Small, technical, one-off#

A 40-mailbox cutover, an engineer who already knows their way around IMAP, a weekend window, and no compliance team waiting at the other end. Spend nothing on tooling, spend the weekend, ship the migration. The native path or imapsync both work. The shortlist of free migration tools covers the candidates and where each one fits.

Pilots before a paid commitment#

Even when the project will end up on a paid tool, you can use a free path for the pilot. Move five mailboxes through DMS or the EAC wizard, see what survives, see what breaks. The findings inform which paid tool you actually need, or whether you need one at all.

Personal and prosumer moves#

A consultant moving their own mail off Fastmail onto Workspace, a family moving off a hosted IMAP onto iCloud, a one-person LLC switching providers. Paying $15 to move 3 mailboxes is silly. A free CLI or a free trial of a paid tool gets the job done.

When paid pays off#

Five cases where the paid line is the right answer, even on a tight budget.

Compliance and audit#

If an auditor will read a report at the end, paid tools earn their fee on day one. Per-user CSV exports with skipped-item categorisation, retention markers, and timestamp accuracy are not optional in regulated industries. Free tools produce log files. Paid tools produce auditor-grade artefacts.

Scale beyond ~300 mailboxes#

The orchestration burden grows non-linearly with mailbox count. Twenty mailboxes is a shell script. Two hundred is a real piece of software you would rather not write. Above 300 mailboxes the paid SaaS pays for itself in saved engineering days. The migration cost-per-mailbox guide covers the math.

Cross-tenant and M&A#

When two tenants merge under a deadline, the orchestration is the project. Paid tools have wave scheduling, identity mapping, mail-flow coexistence, and rollback baked in. Free tools have none of that. M&A almost always justifies a paid tool.

Calendars and contacts from heterogeneous sources#

Native paths handle calendars cleanly only between similar systems (Workspace to Workspace, Exchange to Exchange Online). Open-source IMAP tools do not handle calendars at all. If your project includes calendars from a non-Microsoft, non-Google source, paid tooling is what closes the gap.

Per-user SLA tracking#

If leadership wants weekly status by user and by department, the dashboard that ships with paid SaaS is what you show on the call. Building the same view on top of free tooling is a sprint of engineering work, not a Friday afternoon.

The shortlist of 2026 email migration tools maps each paid vendor to a project shape so you can match before the demo call.

Cost breakdown#

Treat the cost as a sum, not a line:

Total cost = License + Engineering hours × Rate + Risk premium

For a 100-mailbox project:

• Free path: License $0. Engineering 40 hours at $150 = $6,000. Risk premium of 10 percent on a $50,000 project = $5,000. Total: $11,000.
• Paid path: License 100 × $12 = $1,200. Engineering 15 hours at $150 = $2,250. Risk premium of 3 percent = $1,500. Total: $4,950.

For a 30-mailbox project the same calculation:

• Free path: License $0. Engineering 12 hours at $150 = $1,800. Risk premium = $500. Total: $2,300.
• Paid path: License 30 × $12 = $360. Engineering 6 hours at $150 = $900. Risk premium = $200. Total: $1,460.

The paid path still wins on the spreadsheet at 30 mailboxes, but the gap is small enough that a competent engineer who genuinely likes the CLI can justify free.

The numbers are illustrative. Plug your own hourly rate and your own confidence in the engineer. Do not skip the risk premium. A botched migration costs more than the tool you should have bought.

Performance reality#

Free and paid tools end up bound by the same destination limits:

• Microsoft 365 EWS, Graph, and IMAP throttles per user and per tenant.
• Google Workspace per-user API quotas.
• Source IMAP per-account append rate.
• Bandwidth between source and destination data centres.

Within those ceilings, paid tools tune themselves more aggressively across multiple connections. Free tools achieve the same ceiling if you orchestrate carefully. The difference is who writes the orchestration: you, or the vendor.

For raw throughput on a single mailbox, expect 1 to 3 GB per hour from either approach. For elapsed wall-clock time on 500 mailboxes, expect paid tools to finish about 20 to 40 percent faster on a typical project, simply because their concurrency logic is mature.

Support and recovery#

Free tools have community support. Stack Overflow, GitHub issues, Reddit, the imapsync forum. Mean time to resolution depends on the time of day, the obscurity of the failure, and your willingness to read source code. For a one-off project it is fine. For a project with a Monday deadline it is a gamble.

Paid tools have ticketed support with SLAs. 24x7 for enterprise tiers, business hours for lower tiers. The agents have seen most failure modes. They will tell you whether the OAuth2 token expired storm is your tenant policy, the migration app's consent, or their service.

Whichever path you pick, log the migration. Verbose logs are the single best investment of project time. They are how you debug, and they are how you justify what happened to whoever asks afterward.

A decision tree#

Walk through this in order:

1. Are you migrating fewer than 50 mailboxes with no compliance audit? Free wins.
2. Is engineering time effectively zero (someone is doing it on weekends as part of their normal job)? Free is at least viable.
3. Will an auditor read a report at the end? Paid.
4. Is the project above 300 mailboxes? Paid.
5. Does the source include calendars from a non-Microsoft, non-Google system? Paid.
6. Is there a cutover window that cannot slip? Paid for the safety net.
7. Are you mid-range and unsure? Pilot with free, decide based on what hurt.

Where Mailbox Taxi fits#

Mailbox Taxi is a desktop-first option that sits between the two camps. It runs locally on Windows, macOS, and Linux, talks IMAP to all major providers with OAuth2 built in, and gives a per-mailbox view without a SaaS console or per-seat licensing. For teams that find free CLIs too DIY and SaaS tools too heavy, it is a middle path. The product is in waitlist phase.

The head-to-head against imapsync covers how it differs from the most common free CLI. If your migration involves Workspace specifically, the Google Data Migration vs third-party breakdown covers the equivalent decision on that platform.

A practical playbook#

If you are choosing today and the project is mid-sized (100 to 500 mailboxes):

1. Pilot small with free. Five mailboxes through the native path or imapsync. Document what survived, what broke, how long it took.
2. Demo two paid tools. Run them through the same five mailboxes if possible. Compare reports, not feature lists.
3. Cost the engineering honestly. Include the cutover weekend at premium rates.
4. Decide on a hybrid. Many shops end up using free for the bulk and paid for the executive wave or the audit-critical batch.
5. Lock the cutover plan before you pick the tool. The tool serves the plan, not the other way round.

Common failure modes (both sides)#

These show up regardless of which path you pick:

• OAuth consent missed in the source tenant. Produces 401 storms.
• Too many simultaneous connections from over-aggressive concurrency. Back off and retry.
• Folder UTF-7 conversion error on legacy IMAP sources with non-ASCII folder names.
• Source bandwidth saturated. Migration is bottlenecked on the source pipe, not the tool. Check before blaming the software.
• Time-zone drift in internal dates. Verify with one mailbox before running the full batch.

FAQ#