Planning Guide · Microsoft 365 Migrations
How long does a Microsoft 365 migration take? A 100-user migration can often be completed as a project within a few weeks, while an organization with 5,000 users will typically need several months. But the number of accounts is only one part of the equation: 500 users with straightforward Exchange and OneDrive environments may be migrated faster than 100 users with several terabytes of SharePoint data, hundreds of Teams, Intune, Power BI, and dependent applications.
It is also important to distinguish between the time required to copy the data, the cutover window, and the total project duration. A company may cut over 500 users during a single weekend after spending several weeks on assessment, preparation, pre-staging, pilots, and validation.
In this guide, we provide planning ranges for 100, 500, 1,000, and 5,000 users, explain which factors genuinely affect a Microsoft 365 migration timeline, and use performance data published by Microsoft to distinguish a serious project estimate from a sales figure with no context.
Want to know how long your Microsoft 365 migration would take?
To estimate a project correctly, we need more than the number of users. We review mailboxes, OneDrive, SharePoint, Teams, domains, devices, applications, data volumes, coexistence requirements, and your target completion date.
With that inventory, we can define a phased migration timeline, a pilot, and realistic migration waves instead of promising a date based solely on the number of licenses.
How long does a Microsoft 365 migration take?
As a planning reference, a standard Microsoft 365 migration typically takes around 2–4 weeks for 100 users, 4–8 weeks for 500 users, 6–10 weeks for 1,000 users, and approximately 12–20 weeks for 5,000 users. These ranges refer to the complete project — assessment, preparation, pilot, migration, cutover, and stabilization — rather than only the time required to copy data.
The actual timeline depends far more on the volume and type of information than on the number of accounts. Exchange can move many mailboxes in parallel; SharePoint and OneDrive are affected by file count, metadata, and throttling; Teams adds dependencies involving SharePoint and conversations; and Intune may require device re-enrollment. A simple migration may be considerably faster, while an environment with multiple domains, Power BI, Power Platform, Purview, or coexistence requirements may need several additional months.
Quick summary: how long it takes to migrate 100, 500, 1,000, and 5,000 users
Standard project with Exchange, OneDrive, and Microsoft 365 collaboration without unusual dependencies.
Typically includes a pilot, pre-staging or content preparation, and multiple user migration waves.
A phased approach is recommended, with sufficient room for issues, coexistence, and validation.
Enterprise migration program delivered in waves. Complex environments may significantly exceed this range.
Important: these are planning ranges for a standard Microsoft 365 migration scenario. They are not Microsoft SLAs and do not replace a proper assessment of your environment.
| Users | Simple migration | Standard migration | Complex migration | Typical change model |
|---|---|---|---|---|
| 100 | 1–2 weeks | 2–4 weeks | 4–8 weeks | Single cutover or a few waves |
| 500 | 2–4 weeks | 4–8 weeks | 8–12 weeks | Multiple waves |
| 1,000 | 3–6 weeks | 6–10 weeks | 10–16 weeks | Phased migration |
| 5,000 | 6–10 weeks | 12–20 weeks | 20–32+ weeks | Wave-based migration program |
What we mean by a “standard” migration: Exchange Online, OneDrive, SharePoint/Teams within a reasonable scope, identity already prepared, one or a small number of domains, a previous pilot, and no large-scale rebuild of Intune, Power BI, Power Platform, or applications.
What does “how long does a Microsoft 365 migration take?” actually mean?
There are three different timelines: the total project duration, the data transfer time, and the cutover window. Confusing them is one of the main reasons why very different estimates can be found for the same number of users.
1. Project duration
From initial discovery until the new environment has been validated: assessment, design, preparation, pilot, migrations, cutover, and hypercare.
2. Data copy time
The hours or days during which Exchange, OneDrive, SharePoint, or another migration tool is actively moving information.
3. Cutover window
The period during which final changes are performed: domain, identity, email, access, or user reconnection.
A migration may last six weeks as a project while having a cutover window of only a few hours.
This is possible because much of the work takes place beforehand: data is pre-staged where the technology allows it, users are provisioned, permissions are mapped, testing is completed, and communications are prepared.
Why is the number of users not enough to calculate the migration timeline?
Because Microsoft 365 migrations move data and objects, not just people. Two organizations with 500 users may differ tenfold in data volume, number of files, SharePoint sites, Teams, or devices, despite having exactly the same number of employees.
The main factors are:
- Exchange volume: average and maximum mailbox size.
- OneDrive: GB per user and number of files.
- SharePoint: sites, libraries, lists, versions, and metadata.
- Teams: teams, channels, conversations, and applications.
- Intune: the actual number of endpoints and the enrollment method.
- Identity: cloud-only users, hybrid users, groups, and applications.
- Domains: one or multiple domains and their dependencies.
- Compliance: holds, retention, Purview, and Customer Key.
- Coexistence: whether source and target must operate together for weeks or months.
- Business availability: 24×7 organizations have fewer maintenance windows.
Example: 100 users with 100 GB of OneDrive data each represent 10 TB. Another 500 users with only 5 GB each represent 2.5 TB. The organization with fewer employees therefore has four times more personal data to move.
And that still does not account for the number of files. One terabyte made up of large video files will usually process much faster than one terabyte consisting of millions of small files.
How long does a 100-user Microsoft 365 migration take?
A standard 100-user Microsoft 365 migration can typically be planned within approximately 2–4 weeks. A straightforward email-and-files scope may take only 1–2 weeks, while an environment with complex Teams, Intune, applications, or compliance requirements may need 4–8 weeks.
Typical timeline
| Phase | Typical duration |
|---|---|
| Assessment and inventory | 2–4 business days |
| Target environment and identity preparation | 2–5 days |
| Pilot | 2–4 days |
| Pre-stage / initial migration | Several days, usually in parallel with other tasks |
| Cutover | One window or a few waves |
| Validation / hypercare | 2–5 days |
Can all 100 users be migrated together?
In many scenarios, yes. Microsoft describes the Single-Event Migration model as suitable for small to medium-sized organizations and relatively straightforward organizational changes.
However, even with only 100 users, we recommend running a pilot first with several representative users.
The entire production user population should not be the first real migration batch of the project.
100 users does not automatically mean a “small” migration. If the organization has a multi-terabyte SharePoint environment, business applications, Intune, or dozens of shared mailboxes, the project may be more complex than that of a much larger company.
How long does a 500-user Microsoft 365 migration take?
For 500 users, a reasonable planning range is 4–8 weeks for a standard Microsoft 365 migration. The project may finish sooner when the scope is straightforward, or extend to 8–12 weeks when it includes extensive collaboration, applications, devices, or coexistence requirements.
Why are migration waves usually recommended at this scale?
Once an organization reaches several hundred users, operational risk begins to matter as much as raw migration speed.
Dividing the project into waves makes it possible to:
- validate each batch before continuing;
- avoid concentrating every issue on the same Monday morning;
- separate departments or locations;
- manage permissions and dependencies more effectively;
- adjust the pace based on what is learned from each wave.
Can 500 users be cut over in one weekend?
Yes, it can be technically viable in a well-prepared environment. Microsoft even provides a planning example where an observed throughput of 100 mailboxes per hour, after accounting for one hour of queuing, would allow 500 mailboxes to be processed during a six-hour window.
However, that example is intended to explain Exchange capacity calculations; it does not mean that every 500-user organization can migrate all of Microsoft 365 in six hours.
SharePoint, OneDrive, Teams, domain changes, devices, and end-user support remain separate workloads and activities.
For 500 users, we always distinguish between “data prepared beforehand” and “actions that must happen during cutover.” The fewer critical operations that depend on the final window, the lower the risk.
How long does a 1,000-user Microsoft 365 migration take?
A 1,000-user Microsoft 365 migration will typically require approximately 6–10 weeks in a standard scenario. A straightforward project may take around 3–6 weeks, while an enterprise migration involving multiple workloads may require 10–16 weeks.
At 1,000 users, the migration should generally be governed as a wave-based program, even if certain workloads can technically be moved much faster.
What actually takes up those weeks?
- full assessment;
- identity mapping;
- inventory of groups and shared mailboxes;
- pilot testing with representative users;
- pre-staging where supported by the chosen migration method;
- SharePoint and Teams;
- multiple cutover waves;
- exception management;
- post-migration validation and support.
Why not migrate all 1,000 users at once?
It may be technically possible in a very simple environment, but it rarely provides a benefit proportional to the additional risk.
Microsoft presents phased migrations as the appropriate model for large organizations or complex environments.
At 1,000 users, the bottleneck often stops being purely technical data transfer. Communications, service desk availability, business coordination, and exception resolution may determine the largest reasonable wave size.
How long does a 5,000-user Microsoft 365 migration take?
For 5,000 users, a standard Microsoft 365 migration timeline will usually fall somewhere between approximately 12 and 20 weeks. A relatively straightforward scope may be completed in around 6–10 weeks, while a complex enterprise consolidation may require 20–32 weeks or more.
At this scale, it is no longer useful to think in terms of “migration day.” This becomes a transition program involving multiple waves that may coexist for several months.
Why aren’t 5,000 users simply five times as much work as 1,000?
Because many processes can run in parallel.
While one batch is migrating:
- another can be under validation;
- the next one can be pre-staging;
- multiple SharePoint sites can be migrated in parallel;
- future users can be prepared;
- security and application workstreams can run simultaneously.
This is why a 5,000-person organization does not necessarily take exactly five times longer than a 1,000-person organization.
But Microsoft also imposes operational limits
Native cross-tenant OneDrive migration allows up to 4,000 OneDrive accounts to be scheduled for migration in advance at any given time. SharePoint likewise supports a maximum of up to 4,000 pending migrations in the queue.
This does not mean that 4,000 accounts are being processed simultaneously; it is a queue limit. However, it illustrates why a 5,000-user environment must be planned as a migration project at scale.
What commonly extends a 5,000-user migration timeline?
- multiple countries or time zones;
- 24×7 operations;
- Multi-Geo;
- multiple domains;
- thousands of Teams;
- tens or hundreds of terabytes;
- Intune and device migration;
- Power BI;
- Power Platform;
- SSO applications;
- compliance and retention requirements;
- extended coexistence requirements.
With 5,000 users, trying to save two weeks by removing the pilot, validation, or migration-wave contingency usually increases risk far more than it reduces the timeline.
Related official source: Microsoft Learn — Cross-tenant OneDrive migration.
How long does an Exchange Online migration take?
Exchange can usually migrate many mailboxes in parallel, so the timeline should not be calculated by multiplying “days per mailbox × number of users.” Microsoft publishes observed duration percentiles by mailbox size, providing a much more realistic planning reference.
Microsoft-published cross-tenant mailbox migration times
| Mailbox size | P50 | P90 | How to interpret it |
|---|---|---|---|
| 0–10 GB | 1 day | 1 day | Most observed mailbox moves fall within this range. |
| 10–50 GB | 1 day | 2 days | 90% of the analyzed sample had completed within approximately 2 days. |
| 50–100 GB | 2 days | 5 days | Large mailboxes require more planning margin. |
| 100–200 GB | 3 days | 6 days | Individual mailbox size becomes a significant factor. |
P50 and P90 are not guarantees. They are percentiles derived from migrations observed by Microsoft.
A P90 of two days also does not mean that 500 mailboxes of 30 GB each will take 1,000 days. Mailboxes are processed concurrently within the limits of the Microsoft service and the source infrastructure.
The number of items also matters
Microsoft provides a particularly useful example: a 4 GB mailbox containing 400 items with large attachments will migrate faster than another 4 GB mailbox containing 100,000 smaller items.
The reason is that every individual object requires additional processing.
Queuing also consumes time
A migration request can be created correctly and remain temporarily in a Queued state while waiting for Mailbox Replication Service resources.
Microsoft recommends including queue time in migration planning and running tests before the final production window.
Do not plan Exchange migration time based only on GB. Mailbox size, item count, actual concurrency, source platform, queue time, and observed pilot performance should all be measured.
Official source: Microsoft Learn — Microsoft 365 and Office 365 email migration performance and best practices.
How much time does Microsoft Teams add to a migration?
Teams may add very little time or several additional weeks because “migrating Teams” is not a single operation. Chats, meetings, Teams structure, channels, SharePoint, files, Planner, tabs, and applications all need to be considered separately.
Microsoft 365 Migration Orchestrator currently coordinates:
- Exchange Online;
- OneDrive;
- Teams chats;
- Teams meetings.
However, Microsoft excludes shared data such as the following from that same scope:
- Teams;
- channels;
- SharePoint sites.
Therefore, a company asking to “migrate 1,000 users with Teams” could be describing two radically different projects:
Simple scenario
A small number of Teams, limited history, controlled file volumes, and no special applications.
Complex scenario
Hundreds of Teams, private and shared channels, historical conversations, Planner, Lists, OneNote, tabs, apps, and guest users.
When estimating a Teams migration timeline, we do not use only the “number of Teams users.” The useful inventory includes the number of Teams, channels, associated SharePoint sites, data volume, conversations, and dependencies.
Official source: Microsoft Learn — Migration Orchestrator overview.
How does Intune affect a Microsoft 365 migration timeline?
Intune can add several weeks to a migration timeline because the important number is not the number of users, but the number of devices. Policies can be rebuilt or partially automated, but endpoints may require re-enrollment in the target tenant.
An organization with 1,000 users could have:
- 800 laptops;
- 1,000 laptops;
- 1,600 laptops and mobile devices;
- more than 2,000 managed devices.
These are very different projects even though the employee count is exactly the same.
What needs to be planned?
- Configuration Profiles;
- Compliance Policies;
- Endpoint Security;
- applications;
- Autopilot;
- Entra Join;
- BitLocker;
- certificates;
- Wi-Fi and VPN;
- Company Portal;
- re-enrollment;
- end-user support.
If Intune is in scope, we would not use the 100/500/1,000/5,000-user table without also adding the number of managed devices.
Can Power BI, Power Platform, Planner, and security extend a Microsoft 365 migration timeline?
Yes, and they can do so completely independently of the number of users. A 300-person company with a business-critical Power BI environment may require more work than a 2,000-user organization that barely uses those workloads.
Power BI
Workspaces, gateways, semantic models, dataflows, connections, credentials, and Power BI Apps require analysis and, in different scenarios, reconstruction.
Power Platform
Power Apps, Power Automate, and Dataverse have their own migration procedures and post-migration tasks.
Planner
Plans may require recreation or automation. The relevant metric is the number and complexity of plans, not the number of licensed users.
Conditional Access, Purview, and Defender
These configurations do not automatically move together with Exchange or OneDrive. They must be recreated or adapted in the target environment.
Enterprise Applications
SSO, service principals, certificates, secrets, consent, and applications may require an independent workstream.
Does the migration timeline change depending on the source environment?
Yes. A tenant-to-tenant migration, a migration from Exchange on-premises, Google Workspace, or a generic IMAP server uses different mechanisms and can have very different migration speeds.
Microsoft publishes observed mailbox migration duration percentiles for different source environments.
Example for a 10–50 GB mailbox
| Source | P50 | P90 |
|---|---|---|
| Microsoft 365 tenant-to-tenant | 1 day | 2 days |
| Exchange on-premises | 2 days | 6 days |
| Specialized Gmail onboarding / Google Workspace | 1 day | 8 days |
| Generic IMAP | 1 day | 2 days |
These figures show why simply saying “500 users will take five weeks” without knowing the source environment is far too simplistic.
And again, these are observed per-mailbox durations, not the total duration of the organization’s migration project.
Official source: Microsoft Learn — Exchange migration duration estimates.
What is throttling, and why can it delay a Microsoft 365 migration?
Throttling is the mechanism Microsoft uses to temporarily limit certain workloads in order to protect Microsoft 365 availability and performance. It is normal during migrations and does not necessarily mean that something is wrong.
Exchange documents several forms of throttling:
- user throttling;
- migration-service throttling;
- resource health-based throttling.
SharePoint and OneDrive also regulate migration workloads to protect the service.
Does more concurrency always mean a faster migration?
No. Launching too many jobs at the same time can have the opposite effect.
Microsoft recommends, for example, not having more than 5,000 migration jobs or requests in the SharePoint Migration API queue at one time.
The objective is to find the optimal level of parallelism, not to launch every possible migration job at once.
Why is a pilot important when estimating migration time?
Because it reveals the real throughput of the environment:
- queue time;
- Exchange migration speed;
- OneDrive behavior;
- errors;
- throttling;
- source performance;
- impact on users.
After the pilot, a theoretical estimate can be replaced with a projection based on the customer’s actual data.
Official sources: Exchange migration performance · SharePoint and OneDrive migration performance.
How many users should be migrated in each wave?
There is no universal migration wave size. It should be calculated according to complexity, support capacity, the available cutover window, and the performance measured during the pilot.
As a project principle, each wave should be small enough to:
- complete critical actions within the available window;
- validate users before beginning the next phase;
- absorb incidents without overwhelming support;
- keep departments and dependencies together when necessary;
- leave room for exceptional users and edge cases.
Practical example
For an organization with 1,000 users, it may be reasonable to begin with:
- a small pilot;
- a controlled first production wave;
- several larger waves after validating performance;
- a specific wave for special or exceptional cases.
This is generally more reliable than defining four exact batches of 250 people on day one without knowing the actual migration throughput.
Can a Microsoft 365 migration be completed over a weekend?
The cutover can be completed over a weekend; the full migration project usually cannot. The key is to move as much work as possible outside the final cutover window.
Before Friday, the following should already be prepared:
- target tenant;
- users and groups;
- licenses;
- identity mapping;
- migration tools;
- supported pre-staging;
- pilot;
- domain and DNS;
- communications;
- runbook;
- rollback criteria;
- support team.
100 users
A single weekend cutover is common when the scope is reasonable.
500 users
It may also be viable in a single window when the migration has been properly pre-staged and the organization accepts that level of concentration.
1,000 users
It can technically be achieved in specific scenarios, but we would normally assess whether several migration waves would reduce risk.
5,000 users
A single cutover window for the entire organization is generally much less attractive than a phased transition, especially when several workloads and time zones are involved.
What are the phases of a Microsoft 365 migration, and how long does each one take?
The total timeline is divided across assessment, preparation, pilot, data movement, cutover, and stabilization. Many of these phases can overlap.
| Phase | Objective | Typical duration |
|---|---|---|
| 1. Discovery / Assessment | Inventory data, users, workloads, and risks. | Days to several weeks depending on scale. |
| 2. Design | Target architecture, coexistence, domains, security, and migration waves. | Several days to several weeks. |
| 3. Preparation | Users, groups, licenses, permissions, applications, and migration tools. | Several days to several weeks. |
| 4. Pilot | Measure throughput and validate the real user experience. | Usually several days. |
| 5. Bulk / Pre-stage | Move as much content as possible before the final change. | Can run for days or weeks in parallel. |
| 6. Waves / Cutover | Move users into production. | One or multiple windows. |
| 7. Hypercare | Resolve issues and validate acceptance. | Several days per phase or at the end. |
In an organization with 5,000 users, for example, the assessment of the final department may still be wrapping up while the first users are already being migrated.
Not every phase has to wait until the previous phase is 100% complete.
How can you speed up a Microsoft 365 migration without increasing risk?
The most effective way to accelerate a Microsoft 365 migration is not to blindly increase concurrency, but to remove unnecessary work and prepare the source and target environments properly.
- Inventory before migrating. Do not move unused data and objects.
- Remove obsolete content. Less data means less transfer and fewer errors.
- Identify problematic files in advance.
- Prepare identities correctly. This helps prevent broken permissions and post-migration remediation.
- Run a pilot. This provides actual throughput data.
- Use controlled parallelism. Microsoft recommends parallelizing different site collections where possible.
- Use off-peak hours. This is particularly relevant for SharePoint and OneDrive.
- Pre-stage data where the technology supports it.
- Separate exceptional cases. One problematic mailbox should not block 500 users.
- Automate validation. Counts, errors, permissions, and logs can be checked programmatically.
One of the best ways to reduce a migration from 16 weeks to 12 may be to remove content that should not be migrated at all, rather than attempting to force 30% more jobs against Microsoft 365.
What factors usually delay a Microsoft 365 migration?
Delays usually arise from exceptions that were not discovered during assessment, rather than because Microsoft 365 consistently “copies data slowly.”
- very large mailboxes;
- millions of small items;
- SharePoint sites with excessive item counts;
- incompatible file paths;
- holds;
- Customer Key;
- users without proper mapping;
- complex permissions;
- Teams with numerous dependencies;
- Power BI environments that were not inventoried;
- applications that depend on the old tenant;
- an unprepared domain cutover;
- Intune devices that were not inventoried;
- throttling;
- network or source-platform issues;
- lack of available business windows;
- pending customer decisions;
- insufficient support resources during migration waves.
The earlier these elements are identified, the less impact they will have on the final completion date.
What information is required to calculate how long a Microsoft 365 migration will take?
To build a reliable Microsoft 365 migration timeline, we need an inventory by workload together with actual data volumes. Saying “we have 1,000 users” is enough only for an initial planning range.
Exchange and identity
- Total users
- User mailboxes
- Shared mailboxes
- Archive mailboxes
- Average and maximum mailbox size
- Holds
- Groups
- Domains
- On-premises AD
OneDrive and SharePoint
- OneDrive accounts
- Total TB
- Number of files
- SharePoint sites
- SharePoint TB
- Items per site
- Versions
- Permissions
Teams and applications
- Number of Teams
- Channels
- Chats
- Planner
- Power BI
- Power Platform
- Enterprise Applications
- App Registrations
Users and operations
- Intune devices
- Countries and time zones
- 24×7 operations
- Required coexistence
- Cutover window
- Support capacity
- Target completion date
Once this information has been collected, a pilot can be run and the initial planning range can be replaced with a far more accurate timeline.
Do you already have the figures for your environment?
Send us your users, mailboxes, OneDrive accounts, SharePoint sites, Teams, groups, devices, and target date. We can review the scope and propose a realistic phased Microsoft 365 migration timeline.
What are the most common mistakes when estimating a Microsoft 365 migration timeline?
The main mistake is converting the number of users directly into days without understanding the underlying data and workloads. From there, many unreliable migration estimates follow.
- Calculating based only on users.
- Failing to distinguish project duration, data copy time, and cutover.
- Multiplying one mailbox’s migration time by every user.
- Ignoring parallel processing.
- Assuming Internet bandwidth determines the entire migration speed.
- Failing to count files and items.
- Ignoring throttling.
- Estimating Teams solely by user count.
- Forgetting Intune.
- Failing to include Power BI or Power Platform.
- Skipping the pilot.
- Leaving no contingency for exceptions.
- Using the same size for every migration wave.
- Confusing technical throughput with service desk capacity.
- Promising a fixed completion date before completing the inventory.
Microsoft native tools or specialized migration platforms: which option is faster?
There is no universal answer. The fastest approach depends on the workload being migrated, the native capabilities available, and whether the project requires pre-staging, delta passes, coexistence, or advanced reporting.
Microsoft currently provides powerful native capabilities for:
- Cross-Tenant Mailbox Migration;
- Microsoft 365 Migration Orchestrator;
- Cross-Tenant OneDrive Migration;
- Cross-Tenant SharePoint Migration;
- Cross-Tenant Identity Mapping.
Specialized migration platforms can provide:
- pre-staging;
- delta passes for supported workloads;
- coexistence;
- matching;
- reporting;
- automation;
- integrated handling of multiple workloads.
The fastest migration tool is not necessarily the one that achieves the highest raw throughput. It is the one that allows the overall project to be completed with less rework and lower risk while meeting the organization’s requirements.
If you want to compare approaches, see our guide to Microsoft 365 tenant-to-tenant migration tools and scripts.
How does MSAdvance plan a Microsoft 365 migration timeline?
We first provide a planning range and then turn it into a real project timeline through assessment and pilot testing. We do not set the final schedule based only on the number of users.
Our process is based on:
- inventorying users and workloads;
- measuring data volumes and item counts;
- identifying exceptions;
- defining the target architecture;
- selecting the migration tools;
- creating a pilot batch;
- measuring real throughput;
- calculating migration wave sizes;
- coordinating the schedule with the business;
- reserving contingency for incidents and hypercare.
This makes it possible to answer not only “how many weeks will the migration take?” but also more useful questions such as:
- when will each department move?
- how long will both tenants coexist?
- what will happen during the cutover weekend?
- what will users need to do?
- what happens if a migration batch does not finish?
- when can the source tenant be decommissioned?
Frequently asked questions about Microsoft 365 migration timelines
Direct answers to the most common questions organizations ask when planning a Microsoft 365 migration timeline.
How long does a Microsoft 365 migration take?
It depends on the number of users, data volume, and workloads. As a project-planning reference, a standard migration may take around 2–4 weeks for 100 users, 4–8 weeks for 500 users, 6–10 weeks for 1,000 users, and 12–20 weeks for 5,000 users. A very simple scope may be faster, while an environment involving Teams, Intune, Power BI, Power Platform, multiple locations, or compliance requirements may take considerably longer.
How long does it take to migrate 100 users to Microsoft 365?
A standard 100-user Microsoft 365 migration can usually be planned within approximately 2–4 weeks. A straightforward email-and-files migration may be completed sooner, while complex Teams, SharePoint, Intune, applications, and compliance requirements may extend the timeline.
How long does it take to migrate 500 users to Microsoft 365?
As a planning reference, a standard 500-user migration will usually fall within approximately 4–8 weeks. Data can be copied in the background during part of that period, while the final cutover may be concentrated into one or several windows. The total duration is especially affected by OneDrive, SharePoint, Teams, mailbox size, and coexistence requirements.
How long does it take to migrate 1,000 users to Microsoft 365?
A reasonable range for a standard 1,000-user Microsoft 365 migration is approximately 6–10 weeks. At this scale, a phased approach with a pilot, multiple migration waves, validation, and support is usually recommended. A straightforward environment may take less time, while a consolidation involving many workloads may require 10–16 weeks or more.
How long does it take to migrate 5,000 users to Microsoft 365?
A standard 5,000-user migration will commonly be planned over approximately 12–20 weeks. Relatively straightforward environments may be faster, while multinational or 24×7 organizations with Teams, Intune, Power BI, applications, and tens of terabytes of data may require 20–32 weeks or more.
Can a Microsoft 365 migration be completed over a weekend?
The cutover can be completed over a weekend when the environment is properly prepared and much of the content has already been migrated or preprocessed. The complete project will normally begin weeks earlier with assessment, identity preparation, pilot testing, pre-staging, DNS preparation, communications, and testing. “Migrating over a weekend” generally refers to the final change window, not the entire project.
Can 500 users be migrated over a weekend?
Yes, it can be technically viable when the scope is properly prepared. Exchange can process multiple mailboxes in parallel, and Microsoft even provides examples involving hundreds of mailboxes within a several-hour window. However, SharePoint, OneDrive, Teams, domain changes, and end-user support must all be prepared beforehand. In other environments, several migration waves may be safer.
Can 1,000 users be migrated at once?
It is technically possible in certain scenarios, but it is not always advisable. Microsoft identifies phased migration as a suitable model for large organizations and complex environments. Dividing users into waves reduces the impact of incidents and makes support, dependencies, and validation easier to control.
Which takes longer to migrate: Exchange or OneDrive?
This cannot be answered based on the workload name alone. A small mailbox may migrate very quickly, while a OneDrive account containing hundreds of gigabytes and many files may take significantly longer. The reverse may also be true. Exchange is strongly affected by mailbox size and item count, while OneDrive is affected by volume, file count, permissions, and throttling.
How long does it take to migrate an Exchange Online mailbox?
For cross-tenant migrations, Microsoft publishes a P50 of approximately one day for mailboxes up to 50 GB and a P90 of two days for mailboxes between 10 and 50 GB. For mailboxes between 50 and 100 GB, Microsoft publishes approximately 2 days at P50 and 5 days at P90. These are observed performance figures, not guarantees.
How long does it take to migrate 1 TB to SharePoint?
It depends heavily on the type of content. For the SharePoint Migration API, Microsoft publishes maximum reference values ranging from around 250 GB/day for content with large numbers of small items and complex metadata, to 1 TB/day for medium content and 10 TB/day for large files. These are indicative maximum values, not an SLA.
Why can one terabyte take much longer to migrate than another?
Because every individual file or object requires processing. One terabyte consisting of large files can be transferred efficiently, while the same volume distributed across millions of small files, lists, versions, and metadata creates many more operations and may migrate considerably more slowly.
Does Microsoft limit Microsoft 365 migration speed?
Yes. Microsoft 365 uses throttling to protect the service and maintain availability for all customers. Exchange and SharePoint apply different throttling mechanisms. Throttling is normal and does not necessarily indicate a problem with the migration tool.
Can Microsoft remove throttling to speed up a migration?
For SharePoint, Microsoft explicitly states that throttling rules cannot be disabled or suspended simply by opening a support ticket. The correct strategy is to design parallelism properly, use off-peak migration windows, and avoid overloading migration queues.
Are Microsoft 365 migrations faster at night?
For SharePoint and OneDrive, Microsoft documents that background applications may receive tighter throttling during weekday daytime hours and that greater capacity is available during evenings and weekends in the tenant’s region. For this reason, large migration projects commonly make use of these off-peak windows.
Does Teams significantly increase Microsoft 365 migration time?
It can increase the timeline substantially if the organization uses many Teams, channels, conversations, Planner plans, SharePoint sites, and applications. Teams is not a single data workload. Microsoft Migration Orchestrator currently covers chats and meetings within its scope, but Teams, channels, and shared SharePoint content require additional handling.
Does Intune increase the duration of a Microsoft 365 migration?
Yes, especially when there are many managed devices. Policies can be partially rebuilt or automated, but endpoints may require re-enrollment in the target tenant. A serious migration estimate therefore needs the number of devices in addition to the number of users.
What is migration pre-staging?
Pre-staging means moving a large portion of the data before the final migration window. Users continue working in the source environment, and additional synchronization passes are performed later where the technology supports them. This reduces the volume remaining during cutover. Not all native migration methods support delta passes; native cross-tenant OneDrive migration, for example, is one-and-done.
What is a migration wave?
A migration wave is a group of users that moves to the new environment during the same migration window. Waves make it possible to divide a large organization into manageable groups, validate results, and avoid concentrating every incident at the same time.
How long should two Microsoft 365 tenants coexist during a migration?
It depends on the migration strategy. A small organization may require coexistence for only a few days, while a migration involving thousands of users may keep both environments operational for weeks or months. Mail routing, free/busy availability, collaboration, and identity must be prepared for this coexistence period.
How can I know exactly how long my Microsoft 365 migration will take?
First, inventory users, mailboxes, Exchange sizes, OneDrive, SharePoint, Teams, groups, devices, applications, domains, and coexistence requirements. Then run a pilot to measure actual throughput and errors. With that information, a much more accurate migration timeline can be created than by using the number of users alone.
Which Microsoft 365 migration tool is the fastest?
There is no universally fastest migration tool. Microsoft’s native capabilities can be excellent for specific workloads, while specialized tools may provide pre-staging, delta passes, coexistence, or automation. The best option depends on the source environment, scope, and project requirements.
Can MSAdvance estimate the migration timeline before the project starts?
Yes. Based on the environment inventory, we can establish an initial range and design a phased migration plan. After the pilot, the timeline is adjusted using real throughput, queue times, errors, and observed environment behavior. This allows the target date to be based on actual project data rather than a generic per-user estimate.
Official Microsoft sources on Microsoft 365 migration performance and planning
Microsoft recommends testing the environment and measuring actual performance before finalizing a migration timeline. These are some of the official sources used in preparing this guide.
- Plan a Microsoft 365 tenant-to-tenant migration — planning, dependencies, coexistence, and factors that affect the migration timeline.
- Microsoft 365 and Office 365 email migration performance and best practices — mailbox migration duration percentiles, throttling, and performance factors.
- SharePoint and OneDrive migration performance — performance by content type and throttling recommendations.
- SharePoint Migration API — architecture, queues, and best-effort operation without a performance SLA.
- Microsoft 365 Migration Orchestrator — single-event and phased migration models, supported workloads, and dependencies.
- Cross-Tenant OneDrive Migration — queue limits, features, and restrictions.
- Cross-Tenant SharePoint Migration — scheduling, limits, and recommendations for large migration batches.
Related MSAdvance guides
Conclusion: how long does a Microsoft 365 migration really take?
As an initial planning reference, a standard Microsoft 365 migration may take approximately 2–4 weeks for 100 users, 4–8 weeks for 500 users, 6–10 weeks for 1,000 users, and 12–20 weeks for 5,000 users.
However, these figures are only useful when you understand what they represent: the total duration of the migration project, not the time required to copy each mailbox or the number of hours in the final cutover window.
Microsoft 365 allows many migration operations to run in parallel. At the same time, Exchange, OneDrive, SharePoint, and Teams each have their own mechanisms, queues, and limits. Data volume, item count, collaboration complexity, Intune, applications, and business constraints can completely change the migration timeline.
That is why the most useful piece of information is not “we have 1,000 users.” It is:
“We have 1,000 users, 850 mailboxes averaging 28 GB, 700 OneDrive accounts containing 12 TB, 160 SharePoint sites, 220 Teams, 1,400 Intune-managed devices, two domains, and we need to finish before a specific date.”
With that information, a realistic Microsoft 365 migration timeline can be built.
MSAdvance analyzes the environment, runs a pilot, and designs the migration waves so that the project duration is based on real capacity rather than a generic rule based on user count.
Want to know how long your Microsoft 365 migration would take?
Send us the number of users, mailboxes, OneDrive accounts, SharePoint sites, Teams, devices, and your target date. We will review the scope and propose a phased migration timeline for your environment.
