BitTitan vs CodeTwo: Honest Comparison

You are choosing between two of the most established names in Microsoft 365 migration, and the marketing pages aren't helping you decide. BitTitan MigrationWiz and CodeTwo are both mature, both well-supported, and both used by thousands of MSPs. They are not, however, the same product. They diverge sharply on licensing model, source coverage, throttling behaviour, and what happens after the cutover. This breakdown is for the engineer who has to actually pick one before the weekend.

What each product actually is#

BitTitan MigrationWiz is a SaaS migration platform. You buy per-user licenses, configure source and destination endpoints in a web console, queue batches, and let BitTitan's cloud workers do the data movement. The product line also includes DeploymentPro (for Outlook profile reconfiguration) and HealthCheck for Active Directory. BitTitan was acquired by Idera in 2021 and rebranded fully into the Idera portfolio in 2024.

CodeTwo is a Polish ISV that built its name on Exchange signature management and later expanded into migration. Their migration product, CodeTwo Office 365 Migration (and the related CodeTwo Exchange Migration), is also licensed per source mailbox, but their flat per-mailbox license is non-expiring within the contract window. CodeTwo also sells signature management, backup, and admin tooling, which is relevant if you want one vendor across multiple use cases.

Both companies will sell to MSPs. Both have partner programs. Neither is a desktop tool.

Source and destination coverage#

This is where the gap between the two products is widest.

BitTitan supported sources#

BitTitan covers a long list of sources because MigrationWiz started life as a generic mailbox mover before Microsoft 365 dominated everything. The current source list includes Microsoft 365, Exchange (2010 and later), Google Workspace, Gmail (consumer), IMAP, Lotus Notes/Domino, GroupWise, Zimbra, Kerio, IceWarp, Rackspace, Intermedia, AOL, Yahoo (via IMAP), and PST files. Destinations are narrower and largely focused on Microsoft 365, Exchange, and Google Workspace.

CodeTwo supported sources#

CodeTwo's migration products are more focused. They migrate from Exchange (2007 and later) and Office 365 / Microsoft 365 tenants to Microsoft 365. IMAP migration is supported but feels secondary — features like throttling controls, granular folder mapping, and incremental sync are less developed for IMAP than for Exchange sources. If your source is anything other than Exchange or another Microsoft 365 tenant, BitTitan is the more natural fit.

Licensing models#

Both vendors charge per source mailbox, but the way the license is consumed differs in ways that matter for project budgeting.

BitTitan MigrationWiz uses a credit/license model. You buy a UMB (User Migration Bundle) license per user. The license is consumed once that user is moved. Licenses do not expire within a reasonable timeframe (typically 12 months from purchase) but they also do not refund. If you over-purchase, you eat the difference on the next project — assuming you have a next project.

CodeTwo sells perpetual licenses for the migration product itself, and the per-mailbox component is bundled into the support contract. In practice this means CodeTwo is often cheaper for a single defined project, especially if you're migrating fewer than 500 mailboxes and don't have a pipeline of similar work.

If you are an MSP migrating clients constantly, BitTitan's pooled-license model is more flexible. If you are an internal IT team doing one large migration this quarter, CodeTwo's pricing usually lands lower.

Throttling and performance#

Both products run into the same Microsoft 365 throttling ceilings — neither vendor can magic them away. Where they differ is how they react.

BitTitan handles throttling automatically. When MigrationWiz hits the 429 TooManyRequests or the EWS ErrorServerBusy response, it backs off and retries on a randomised schedule. You can also set explicit concurrency caps per endpoint, which is useful if you've been warned by your destination tenant or if you're sharing connection allowance with a backup tool.

CodeTwo also implements backoff, but the throttling controls in the UI are slightly less granular. You can set the maximum number of mailboxes processed in parallel, but tuning the per-mailbox concurrency is more limited. For most projects this isn't a problem; for large enterprise cutovers where every hour matters, BitTitan's tuning surface is wider.

Expect 90–120 minutes per mailbox of average size (10–25 GB) on either product, assuming healthy throttling headroom on the destination tenant. Multiple mailboxes run in parallel, so a 200-user project commonly completes in a long weekend either way.

What happens after the data moves#

The post-cutover story is where CodeTwo quietly pulls ahead for some scenarios.

Outlook profile reconfiguration#

BitTitan ships DeploymentPro, an agent that runs on user workstations and reconfigures Outlook profiles automatically after the mailbox is moved. This is genuinely useful when you have 500 users and don't want to touch each laptop. DeploymentPro is an extra license SKU, not bundled with the migration license.

CodeTwo does not have a directly equivalent agent. You handle profile cutover via Autodiscover, manual reconfiguration, or your RMM. For small to medium projects this is fine; for large enterprise rollouts, BitTitan's tooling saves real time.

Signature management#

CodeTwo wins here without much argument. CodeTwo Email Signatures is one of the most widely deployed signature management platforms for Microsoft 365. If your post-migration scope includes "and roll out a new email signature standard", buying CodeTwo for the migration and keeping the signature product afterward is a clean story.

BitTitan does not offer signature management.

Hybrid coexistence#

CodeTwo's heritage in Exchange tooling means their hybrid coexistence story (free/busy, mail flow during migration) is more mature for Exchange-to-Microsoft 365 staged migrations.

At-a-glance comparison#

Honest weaknesses#

Neither product is perfect, and pretending otherwise wastes your time.

BitTitan weaknesses. The web console feels dated. Errors in batches sometimes surface as generic messages that require a support ticket to decode. Pricing is opaque until you're in a quoting conversation. Since the Idera acquisition, support response times have varied — some MSPs report no change, others report longer queues. The license-once-consumed model creates real waste if a migration changes scope.

CodeTwo weaknesses. Source coverage outside Microsoft and Exchange is thin. The product assumes you are migrating to Microsoft 365 — if your destination is anything else, look elsewhere. Larger projects can hit performance ceilings that aren't always obvious from the UI. Documentation is generally good but assumes Exchange admin literacy.

Which one to pick#

The decision usually collapses to two questions.

1. What is your source?

• Exchange on-prem or another Microsoft 365 tenant only: either works, lean CodeTwo for cost
• Google Workspace, IMAP, Lotus Notes, GroupWise, Zimbra, or PST archives: BitTitan
• Mixed sources in a single project: BitTitan

2. What do you need after the cutover?

• Outlook profile reconfiguration at scale: BitTitan (DeploymentPro)
• Email signature standardisation: CodeTwo
• Nothing — just data moved: either

For MSPs running migrations as a recurring service line, BitTitan's pooled licensing and broader source coverage usually wins. For internal IT teams doing a one-off Exchange-to-Microsoft 365 cutover, CodeTwo's bundled licensing and lower per-project cost usually wins.

For more context on how these two sit alongside the rest of the market, see our best email migration tools 2026 roundup and the dedicated best Office 365 migration tools guide. If you're already comparing other names in the same bracket, the SkyKick vs Cloudiway breakdown covers the other major MSP-leaning pair.

When neither fits#

There's a third scenario worth naming. Both BitTitan and CodeTwo are built for Exchange-class migrations: hundreds of mailboxes, multiple wave plans, MX cutovers, coexistence. If your actual job is "move 8 IMAP mailboxes from a hosting provider to Fastmail this weekend", both tools are wildly over-specified and over-priced.

That's the gap Mailbox Taxi was built for. It's a desktop IMAP migration tool you run locally on Windows, Mac, or Linux. Credentials never leave your machine. There's no per-mailbox license burn, no SaaS console, no cloud workers handling your client's mail. For small-to-medium IMAP-to-IMAP cutovers across providers like Gmail, Outlook, Yahoo, iCloud, Zoho, Fastmail, ProtonMail Bridge, and custom IMAP servers, it's usually the right shape of tool.

If your project is heavyweight Microsoft 365 work, pick between BitTitan and CodeTwo using the rules above. If it's anything closer to a clean IMAP move, look at Mailbox Taxi vs BitTitan or Mailbox Taxi vs CodeTwo instead.