Microsoft 365 Migration Estimator
Tell it where your mail, files and devices live today. It picks the fixed-price services that fit, prices them at the figures printed on their own pages, and turns the list into a project you can review, add to, or send to an engineer.
01 Where mail lives today
The source platform picks the mail service.
Gmail, Calendar and Contacts; Drive optional
02 Mailboxes
User mailboxes to move. Shared mailboxes and archives are separate services.
03 File data to move
04 Devices to set up
Users whose Windows devices we enrol (Intune / Autopilot). Leave at 0 to skip.
05 Teams and DNS
06 Target date
2 services fit your answers
Google Workspace source: mail, calendars and contacts.
Printed price: Free (Microsoft Sponsored)
MX and Autodiscover changes are inside the mail line; this adds SPF, DKIM and DMARC on the new tenant, per domain.
Printed price: $450 per domain + $950 tenant fee · 1 domain × $450 + $950 tenant fee
Assumes one email domain.
The project page prices from the same catalog and can be saved or sent. Nothing is ordered; an engineer confirms every project before anything is billed.
Seven answers, a curated service map, and arithmetic you can check.
The source platform picks the mail line. Google Workspace gets the cutover that moves mail, calendars and contacts (with My Drive when Drive is in scope); your own Exchange gets the cutover up to 150 mailboxes and the hybrid path above; tenant-to-tenant, GoDaddy and IMAP each have their own service.
File data adds its own lines. Google shared drives go to SharePoint; a file server splits into departmental shares (SharePoint) and home folders (OneDrive); SharePoint from another tenant splits into sites and OneDrive.
Devices, Teams and DNS are add-ons. Device set-up is the Intune foundation plus Autopilot, or the device re-join service on a tenant move. Teams content only exists on a Microsoft 365 source. The DNS line is SPF, DKIM and DMARC on the new tenant; the MX change itself is inside every mail service.
The maths is quantity × unit fee, plus the tenant fee. Mailboxes count per-mailbox lines; one user per mailbox counts per-user lines; the devices you enter count per-device lines; per-project lines are their printed price. The arithmetic only runs when a page prints those exact numbers; otherwise the printed price is shown as it is.
Firmness travels with the price. A fixed price is firm. A price a page prints as “from” or as an estimate is indicative and shown as “from”. A quoted service has no number here; it is scoped on a call.
The total adds firm and “from” lines only and says how many lines it leaves out. Durations are printed per service and are not added up: most lines overlap.
Counts move the number. Bands move the plan.
Mailbox count
Per-mailbox lines scale one for one; the tenant fee does not. On your own Exchange the count also decides cutover versus hybrid at 150 mailboxes.
Mailbox size
Average size does not change a printed price. It changes how long the pre-stage sync runs before the cutover, which sets the cutover window.
File volume
File lines are priced per user, per server, per site or per project. Volume beyond the scope a page prints is quoted in writing before work begins.
Counts we do not ask for
Sites, teams and domains are counted on the call. A line priced per site or per team shows its printed price and stays outside the total; the DNS line assumes one email domain.
What every estimate excludes
- Microsoft 365 licenses and any Microsoft charge
- Data volume beyond the scope printed on a service page
- Shared mailboxes, archives and public folders (separate services)
- User training and decommissioning of the source platform
Questions people ask before they press “Add to project”.
Is this a quote?
No. It is the list of services that fit your answers, each at the price printed on its own page, and the arithmetic those pages describe: quantity × unit fee plus the tenant fee where there is one. A written quote follows once an engineer has confirmed the counts and the scope with you; you pay after you approve delivery.
Why does my Exchange migration show as hybrid?
Microsoft's cutover path stops at roughly 150 mailboxes on your own Exchange Server. Above that the estimator switches to the hybrid service, which synchronises identities first and moves mailboxes in batches. Both lines carry the price printed on their pages.
Some mail lines print as Microsoft-sponsored. What does that mean?
The estimator repeats the price exactly as the service page prints it. The conditions of the sponsored offer, who qualifies and what is inside its scope, are stated on that page and confirmed with you before the engagement begins; nothing here changes them. Lines like that sit outside the total because there is no number to add.
Are licenses and Microsoft charges included?
No. Every figure is a service fee. Microsoft 365 licenses, Exchange Online or SharePoint storage beyond plan limits, third-party migration tooling that a page names as excluded, and data volume beyond the scope printed on a service page are all outside the estimate.
What happens after I add the lines to a project?
They land on your project at /subscriptions/build alongside any subscriptions you have chosen, each labelled firm, indicative or scoped on a call. You can change quantities, remove lines, save the project or send it to us. Nothing is ordered; an engineer reviews every project before anything is confirmed.
Want an engineer to check the inputs?
Thirty minutes on a call confirms the counts, the sequence and anything the estimator leaves outside the total. The quote that follows is written, fixed, and paid after you approve delivery.
Sizing the subscriptions too? Build-a-Plan Wizard →