Mailbox Taxi vs SkyKick — desktop tool vs MSP cloud service

SkyKick has been the default email-migration choice for many Microsoft partners for years, with automation that goes well beyond moving mail — DNS cutover, Outlook profile creation, post-migration cleanup. Mailbox Taxi is a desktop-first IMAP tool that does one thing well: move mail directly between source and destination on hardware you control. The right answer depends on whether your business model rewards automation depth or flat license costs.

TL;DR — when to pick which#

Side-by-side comparison#

Where Mailbox Taxi wins#

Flat license cost regardless of volume#

SkyKick's economics get better with partner tier and volume, but they are still per-mailbox at the bottom. Mailbox Taxi's planned per-engineer license means the marginal cost of moving an extra mailbox is zero. For an MSP that runs migrations as part of monthly managed-services work, that flips the unit economics in your favour.

Data stays on your machine#

Every byte of mail content Mailbox Taxi moves goes directly between source and destination IMAP servers. No SkyKick cloud, no relay. For projects where a DPO has flagged "mail content cannot transit any third-party processor," this is the easier answer. SkyKick's architecture is fine for most commercial work but is harder to justify under tighter data-residency rules.

Provider variety#

SkyKick is optimised for M365-bound projects. Mailbox Taxi treats any IMAP host as a first-class source: cPanel hosts, GoDaddy IMAP, Bluehost, IONOS, custom self-hosted Dovecot, and the long tail. If your migrations are not all M365-to-M365, Mailbox Taxi's matrix is broader on that axis. Our best tools for MSPs round-up covers when this breadth actually matters in practice.

No partner enrolment required#

To get SkyKick's best pricing you typically need to be in the Microsoft CSP program. That is a multi-week onboarding and ongoing reporting commitment. Mailbox Taxi is just software you buy and run — there is no programme to enrol in.

Where SkyKick wins#

SkyKick has a real engineering investment behind it and is more complete than Mailbox Taxi in several genuinely important ways.

Workflow automation#

SkyKick does not just move mail. It handles DNS cutover, Outlook client profile re-creation, MX record changes, autodiscover updates, and licence assignment. For an MSP doing five 25-mailbox migrations a month, the post-cutover automation is what saves engineering hours. Mailbox Taxi does the mail-move step well but leaves the surrounding workflow to you.

Calendar and contacts#

Mailbox Taxi is an IMAP mail tool. SkyKick covers calendar and contacts as part of a standard project. If your scope is "migrate mailboxes," Mailbox Taxi is fine. If your scope is "make Outlook work on Monday morning with all the meetings and contact lists intact," SkyKick covers more of that.

Microsoft partner integration#

If you already run your M365 tenants through SkyKick's partner portal, the migration tool slots into the same dashboard, the same billing, the same support relationship. That ecosystem fit is real and is worth a non-trivial amount of engineering time per project.

SMB-tuned automation#

SkyKick has spent years tuning their automation for the 10–100 mailbox SMB shape. The defaults work. Mailbox Taxi requires the engineer to understand each provider's quirks before they configure the job. For an MSP whose junior engineers do the heavy lifting, SkyKick's "click through the wizard" model is lower risk.

Pricing comparison#

SkyKick

• Office 365 Migration Suite: typically $10–$20 per mailbox depending on partner tier and bundle.
• Email-only and full-suite (mail + DNS + Outlook automation) tiers.
• Discounts at higher volume and within Microsoft CSP partner tiers.
• Subscription model for the partner portal, separate from per-mailbox migration license.

Mailbox Taxi

• One-time desktop license, pricing not yet announced.
• Per-engineer or per-machine, not per-mailbox.
• No subscription required to keep using a migrated mailbox.
• Join the waitlist to be notified when pricing goes live.

Where the math flips: for an MSP migrating fewer than ~75 mailboxes a year, SkyKick's per-seat model is usually cheaper because you avoid an upfront tool license. Above that volume, the flat-cost desktop tool starts to win. The break-even moves with whatever Mailbox Taxi prices the license at, so revisit the math when pricing is announced.

Decision framework — which fits which reader#

The Microsoft CSP-tier MSP#

You are already in the Microsoft partner ecosystem. You bill your customers per seat per month. Your engineers expect the migration tool to slot into the SkyKick portal they already use for tenant provisioning. SkyKick is the easier choice; switching tools would create more friction than it would save in license cost.

The lean MSP outside the partner programme#

You run a small shop. You are not in CSP because the reporting overhead does not pay back. You move 5–30 mailboxes a month across mixed providers. Mailbox Taxi is the better fit because there is no partner enrolment, no per-mailbox cost, and the IMAP coverage matches the messy mix of small-business sources you actually see.

The internal IT lead at a 200-person company#

You are migrating once. Your tenant is M365 already. You want a Microsoft partner to run the project end to end. The partner will use SkyKick because it is what they have invested in. You are not really making a tool choice; you are picking a partner who happens to use SkyKick.

The compliance-led migration#

Healthcare, legal or financial services. Your DPO has said mail body content cannot transit a third-party cloud. Mailbox Taxi is the easier sell because the data never leaves the path between source and destination IMAP servers.

Migration mechanics: what each tool actually does#

Auth flows#

Both support OAuth 2.0 for Gmail and Microsoft endpoints. SkyKick runs OAuth through its own cloud app — you grant SkyKick's app permission on the source tenant. Mailbox Taxi runs OAuth locally, so the token sits on the engineer's machine. Same security primitive, different trust placement.

Throttling and connection limits#

SkyKick's cloud hits Microsoft endpoints from SkyKick IP ranges, and shares a throttle budget with other SkyKick projects in the same region. Mailbox Taxi runs from your IP, so the throttle budget is yours. The practical implication: a Friday-night migration on Mailbox Taxi is not competing with somebody else's Monday-morning queue.

Error handling#

Both tools log the messy 5% — Folder UTF-7 conversion error, Message too large for destination, OAuth2 token expired, Too many simultaneous connections. SkyKick wraps the retry loop inside its automation, so the engineer sees fewer error messages by default. Mailbox Taxi shows them in raw form and expects the engineer to interpret them. For a senior engineer that is faster; for a junior it is harder. See our Office 365 migration guide for what these errors actually mean.

Post-migration#

This is where the tools diverge most. SkyKick rewrites Outlook profiles, updates DNS, validates the cutover and reassigns licences. Mailbox Taxi finishes when the mail is moved; you handle the surrounding workflow with your own scripts or a separate tool.

Hybrid use is plausible#

It is genuinely common to use both. SkyKick for the M365-bound SMB jobs where DNS and Outlook profile automation pays for itself. Mailbox Taxi for the IMAP long-tail — the acquired business with three Fastmail mailboxes, the contractor on Zoho — where the SkyKick per-seat cost is hard to justify. We talk about this split in our wider best email migration tools 2026 review.

FAQ#