It is the first question every prospective client asks, and most providers answer it with "it depends" and a request for a meeting. It does depend, but the ranges are not a mystery, and you deserve to know them before anyone gets you on a call. This article lays out typical market pricing for Exchange migrations, what pushes a project toward the top or bottom of the range, and how to read a quote so you are comparing like with like.
Everything here describes common market ranges for small and mid-sized business projects, not a price list. Your quote will reflect your actual environment, which is exactly what a discovery phase is for.
The short answer: a per-mailbox range
Most professionally run migrations for SMBs price out, all-in, somewhere in the low to mid hundreds of dollars per mailbox. A simple, clean environment lands near the bottom of that range; a complex one with public folders, compliance requirements, and years of accumulated oddities lands near the top or above it. Very small projects carry a practical minimum, because the fixed work (tenant setup, DNS, cutover planning, testing) exists whether you have 8 mailboxes or 80.
| Project profile | Typical all-in market range | What it usually looks like |
|---|---|---|
| Small and simple | Low hundreds per mailbox, with a project minimum | Under ~25 mailboxes, one domain, no public folders, standard Outlook and mobile devices |
| Mid-size, some complexity | Low to mid hundreds per mailbox | 25 to 150 mailboxes, shared mailboxes and calendars, a few mail-connected apps and devices |
| Complex or legacy-heavy | Mid hundreds per mailbox and up | Exchange 2010/2013 sources, large public folder trees, journaling or retention requirements, multiple domains or sites |
| Tenant-to-tenant or unusual | Scoped individually | Mergers, divestitures, hosted-provider shutdowns, half-finished prior migrations |
Note what the range excludes: your ongoing Microsoft 365 licensing. Those subscription costs are covered separately in our Exchange Online vs on-premises cost comparison; the migration fee is a one-time project cost on top of them.
What actually drives the price
Two environments with the same mailbox count can differ by 2x in effort. These are the factors that move the number, roughly in order of impact.
Source system age and health
Exchange 2016 and 2019 support modern migration tooling and hybrid coexistence, so mail can move in the background with a clean cutover at the end. Exchange 2010 and 2013 are old enough that the smooth paths are partly or fully closed, which means more manual staging, more fallback planning, and more engineer hours. A server that is unhealthy (failing disks, corrupt databases, expired certificates) adds stabilization work before migration can even start.
Public folders and shared data
Plain mailboxes move predictably. Public folder trees, especially large or permission-heavy ones, are consistently the most labor-intensive part of legacy Exchange projects. Shared mailboxes, delegated calendars, and distribution lists all need mapping and testing so that access works identically on day one.
Mail-connected devices and applications
Every scanner that emails PDFs, every application that sends alerts through SMTP, every CRM that reads a mailbox: each one must be found, re-pointed, and tested. Missing one is how "the migration went fine" turns into "invoices stopped going out and nobody noticed for a week." Discovery time spent here is the cheapest insurance in the whole project.
Data volume and throttling
Total data size matters less than people expect, but it sets the calendar. Microsoft throttles ingestion, so tens of terabytes of mail cannot be crammed into a weekend. Larger datasets mean longer pre-staging windows, which means more sync monitoring, not necessarily proportionally more cost.
Compliance and retention requirements
Litigation holds, journaling, and regulated retention need to survive the move intact. Getting this right requires planning and verification, and it typically also affects which licenses you need on the destination side.
User count and device mix
Each user brings an Outlook profile and usually a phone. Some providers quote low and then bill hourly for "device reconfiguration"; a real all-in quote includes cutover support for users and devices, because that is where the help tickets happen.
What a serious quote includes
When you compare quotes, make sure each covers the same scope. A complete fixed-price migration should include:
- Discovery: an inventory of mailboxes, public folders, shared resources, domains, and mail-connected apps and devices, with a written plan and dated cutover.
- Tenant setup: Microsoft 365 configuration, identity sync where applicable, DNS and mail-flow preparation, and a security baseline.
- Pre-staged data copy: a full trial sync of mail, calendars, and contacts while your current system keeps running untouched.
- Cutover: final delta sync, MX flip, device and Outlook reconfiguration, and live support on the first business day after.
- Verification and fallback: item-count checks, mail-flow tests in both directions, and a rollback plan you hopefully never use.
- Decommissioning: retiring the old server properly instead of leaving it exposed on the internet.
If a quote is dramatically cheaper than the others, one of these pieces is usually missing, most often discovery, device support, or decommissioning. The gap does not disappear; it moves onto your team or into a change order.
The cost of doing it yourself
DIY is not free; it is paid in your team's hours and your organization's risk. A first-time Exchange-to-cloud migration typically consumes multiple weeks of a capable admin's attention across planning, syncing, cutover, and cleanup, and the first attempt hits problems a specialist has already solved dozens of times: throttled syncs, autodiscover misbehavior, that one 80 GB mailbox, the app nobody documented. Price those hours honestly and add the exposure of an extended outage, and in-house work is frequently the more expensive option even before anything goes wrong. We go deeper on that decision in DIY vs Migration Partner: When to Bring in a Specialist.
How to keep your migration near the bottom of the range
- Clean up first: delete or archive dead mailboxes, and let shared mailboxes be shared mailboxes (they are free in Microsoft 365 within limits) instead of licensed users.
- Decide what history you truly need: migrating everything is fine, but exporting ancient departed-user mail to archives can shrink the project.
- Consolidate domains and distribution lists before the move rather than after.
- Pick the right destination plan up front so licensing is not reworked mid-project; if you are weighing staying on-premises against moving, read Exchange Server SE vs Exchange Online first.
- Get discovery done properly. Surprises found before the quote change the price; surprises found during cutover change the weekend.
One more structural note: a migration is a one-time cost, and the savings it unlocks recur. For most organizations coming off self-hosted Exchange, the project pays for itself within the first year or two of not running a server, and the security exposure of an end-of-life mail server goes to zero on cutover day.
Get a real number instead of a range
Tell us what you are running and how many mailboxes, and we will come back with a dated plan and a fixed quote, free.
Plan My Migration