Mailbox Taxi vs MultCloud: Desktop vs Web Mail Migration

MultCloud is a tempting first pick when someone says "migrate my Gmail to Outlook." It's a browser tab, a couple of OAuth prompts, and a green button. No installer, no firewall whitelist, no IT ticket. The trade-off is that your mail flows through someone else's servers, the migration runs on shared infrastructure, and the bulk and MSP features stop short of what a real cutover needs. This comparison sets MultCloud against Mailbox Taxi, the desktop-first alternative, so you can pick the right shape of tool for the job in front of you.

TL;DR#

What each tool actually is#

MultCloud is a web application that lets you connect multiple cloud accounts — Drive, Dropbox, OneDrive, Box, plus a long list of mail providers — and transfer data between them. The mail feature treats mailboxes like buckets: connect Gmail on one side, Outlook on the other, click Transfer. Everything happens on MultCloud's servers; you can close the browser and the job keeps running. It's a clever, lightweight model with a clean UI.

Mailbox Taxi is a desktop app for Windows, macOS and Linux. It connects to IMAP servers directly from your machine using OAuth2 or app passwords. No mail touches a third party in transit — the bytes go source-IMAP → your laptop → destination-IMAP. You get bulk CSV mailbox imports, per-folder progress, retry logic, and a workflow built for IT pros running cutovers, not for a consumer moving their personal Gmail.

If you're still deciding between the two shapes of tool generally, the cloud vs desktop migration tools breakdown lays out the trade-offs.

Feature comparison#

Where MultCloud wins#

It's worth being honest about where MultCloud is genuinely the right pick.

Zero install friction. You're on a locked-down corporate laptop that won't let you install anything. Or you're helping a friend's parent move from AOL to Gmail and you don't want to walk them through a desktop installer. MultCloud opens in a browser tab and you're authenticating accounts within thirty seconds. Mailbox Taxi requires a download and an install.

Truly unattended runs. Once the MultCloud job is queued, you can close the lid of your laptop, go to sleep, and check back in the morning. The transfer continues on their infrastructure. Mailbox Taxi runs on your machine, so the laptop has to stay awake (or you need a dedicated migration host).

Multi-cloud file transfer in the same pane. If the project is "move everything from Google Workspace to Microsoft 365 — mail, Drive, calendars, the lot," MultCloud's broader scope is appealing. You get Drive-to-OneDrive in the same UI that handles Gmail-to-Outlook. Mailbox Taxi is mail-only by design.

Pricing is up front. MultCloud publishes its monthly and annual tiers openly. You know exactly what a year of transfers will cost. Mailbox Taxi is in waitlist phase and has not yet published pricing, which is fair information to factor in.

Where Mailbox Taxi wins#

Mail never leaves your environment. This is the headline. For any client in legal, financial services, healthcare, or any regulated industry, the idea of streaming a partner's entire inbox through a third-party SaaS in Singapore (or wherever the load balancer lands) is a non-starter. Mailbox Taxi keeps mail on your local machine in transit. The conversation with your compliance officer is much shorter.

Real bulk operations. MultCloud's bulk mail handling is limited — you set up transfer tasks one mailbox at a time. For an MSP cutting over a 60-person company on a weekend, that's a deal-breaker. Mailbox Taxi takes a CSV of source and destination accounts, fires off concurrent migrations, and reports per-mailbox status. You configure 60 mailboxes in five minutes, not 60.

Better throttle handling. Microsoft 365 throttles bulk IMAP pulls. Gmail kills sessions that breach Too many simultaneous connections. MultCloud, sharing infrastructure across all of its customers, frequently hits those throttle ceilings and has to slow your job down further. Mailbox Taxi runs from your IP, with your concurrency settings, and backs off intelligently when it sees the warning signs.

Resumable from the right place. Both tools resume from disconnects. Mailbox Taxi tracks last-confirmed UID per folder, so a resume picks up at the exact message. MultCloud resume granularity is coarser; long jobs can re-copy a chunk of mail on resume.

Field-engineer workflow. Mailbox Taxi has logs you can grep, a CSV report you can email to a client, and config files that fit into the rest of your migration runbook. MultCloud is great for one-shot consumer moves; it's not what you reach for when you have a runbook in Notion and a Slack channel of stakeholders.

For more on tools at this end of the market, the email migration tools shortlist gives the broader landscape, and Mailbox Taxi vs BitTitan covers the heavier enterprise option.

Pricing reality check#

MultCloud sells monthly and annual plans tied to total data transferred. For a single user moving a few gigabytes of mail and a Drive folder, the free tier may even cover it. For a 200-mailbox MSP project with 20GB average inboxes, you're going to need the largest tier and probably stacking annual plans.

Mailbox Taxi has not announced pricing — it is in waitlist phase. Sign up for the waitlist to get early access and pricing when it launches. The architectural positioning is desktop-first with per-mailbox economics, which is usually friendlier than per-GB pricing for production migrations.

The deeper picture lives in the complete email migration guide, which walks through how to size and budget a real cutover.

Decision framework#

Pick MultCloud when:

• You're a single user moving your own mailbox once.
• You have no ability or appetite to install software.
• You also need to move Drive / OneDrive / Dropbox data in the same job.
• The total volume is small (under a few GB) and the source and destination are well-supported by their connector list.
• Streaming mail through a third-party server is acceptable under your privacy and compliance rules.

Pick Mailbox Taxi when:

• You're an MSP, IT admin, or sysadmin running migrations as a job.
• Mail must not transit a third-party SaaS.
• You're moving more than a handful of mailboxes — bulk CSV import is the win.
• You need OAuth2 with proper token refresh during long-running jobs.
• You want detailed per-folder logs, retry logic, and resumability tuned for production windows.
• You run a mix of Windows, macOS and Linux hosts and want one app that runs everywhere.

For the cloud-orchestrator alternative, also weigh Mailbox Taxi vs Cloudiway.

Common errors and how each handles them#

A few real ones to expect during a Gmail-to-Microsoft-365 cutover:

• OAuth2 token expired mid-transfer. Mailbox Taxi refreshes silently and continues from the last UID. MultCloud usually re-prompts in the UI, which is awkward if you've already closed the tab.
• Too many simultaneous connections from Gmail. Mailbox Taxi backs off and lowers concurrency automatically. MultCloud's shared infrastructure may hold your job in a queue for hours.
• STARTTLS handshake failed against a custom IMAP server. Mailbox Taxi exposes the cipher and TLS-version negotiation in its logs. MultCloud surfaces a generic error and asks you to contact support.
• Folder UTF-7 conversion error. Mailbox Taxi rewrites legacy IMAP folder names; MultCloud's behaviour varies by provider connector.

A worked example#

Scenario: a 35-person creative agency moving from Google Workspace to Microsoft 365, with an average mailbox of 18GB and a Friday-night cutover window of 8 hours.

With MultCloud you would create 35 transfer tasks, each authenticating Gmail and 365, and let them run on MultCloud's servers. You'd hit Too many simultaneous connections from Google early because they share connection pools across customers, and the queue would back up. By Monday some mailboxes finish and some need manual restart.

With Mailbox Taxi you would import a CSV of 35 source/destination pairs, set concurrency to 4 (a safe number for Google's per-source throttle), and run from a single beefy migration host. By Saturday morning all 35 are complete with per-folder logs you can hand to the client. Mail never touched a third-party server.

That difference — predictability and data path — is the core of the choice.

What to test on your pilot#

Take one of your real mailboxes and run it through both tools end-to-end before deciding:

1. Time to complete a 10GB mailbox.
2. Folder hierarchy fidelity, including nested labels in Gmail.
3. Read/unread state preservation.
4. Calendar and contacts behaviour, if either is in scope.
5. Behaviour when you intentionally drop the connection mid-transfer.
6. Where the data physically lives during the job — your machine or theirs.

You'll know within an hour which one fits your project.

FAQ#