How Long Does a
Microsoft 365 Migration Take?
Real migration timelines by company size and migration type, and what actually drives how long your project will take.
Timeline is one of the first questions every business asks when considering a Microsoft 365 migration. The honest answer is that it depends — on the size of your organisation, the type of migration, your data volumes, and the complexity of your existing environment. This guide gives you real, practical timelines based on migration type and company size so you can plan accurately.
The short answer
Most Microsoft 365 migrations for small businesses take between one and four weeks from start to finish. Enterprise migrations with complex environments can take several months. The actual cutover — the moment when users switch to the new environment — is typically scheduled for a few hours outside business hours, regardless of organisation size.
Timeline by company size
| Company size | Typical total timeline |
|---|---|
| Under 25 users | 3–7 days |
| 25–100 users | 1–3 weeks |
| 100–500 users | 3–6 weeks |
| 500+ users | 2–6 months |
These are total project timelines from initial assessment to post-migration sign-off. The cutover itself is a fraction of this time — the majority is planning, preparation, and pre-staging.
Timeline by migration type
IMAP email migration: 3–10 days for small businesses. IMAP migrations are typically the fastest because they involve email only — no SharePoint, Teams, or OneDrive to move.
GoDaddy defederation: 1–3 weeks. Involves tenant provisioning, data migration, and DNS transition — more steps than a simple email migration but a well-defined process.
Google Workspace to Microsoft 365: 2–4 weeks. Multiple workloads (Gmail, Drive, Calendar, Contacts) migrating to different Microsoft 365 destinations requires careful sequencing.
Exchange Online migration (on-premise to cloud): 2–6 weeks depending on mailbox count and whether a hybrid deployment is required. See our comparison of Exchange hybrid vs cutover migration for how this choice affects your timeline.
Tenant-to-tenant migration: 4–12 weeks. The most complex migration type — identity mapping, cross-tenant routing, and moving data between entirely separate Microsoft environments.
Cloud storage migration (Dropbox, Box, Google Drive to OneDrive): 1–3 weeks depending on data volume and permission complexity.
What affects your migration timeline?
Data volume. The more email history and files need to move, the longer pre-staging takes. A user with 50GB of email takes significantly longer than one with 5GB.
Number of mailboxes. Migrations are typically batched — not all users move simultaneously. Larger organisations take longer simply because there are more batches to process.
Source environment complexity. On-premise Exchange environments with custom configurations, public folders, or complex mail flow rules require more discovery and planning time before migration can begin.
Third-party integrations. Applications connected to your Microsoft 365 environment — CRM systems, accounting software, document management tools — need to be identified and reconnected after migration.
SharePoint and Teams. Moving SharePoint sites and Teams channels adds significant complexity compared to email-only migrations.
Decision-making speed. Migrations involving multiple stakeholders who need to approve plans, cutover windows, and sign-off documents take longer than those with a single decision-maker.
The phases of a migration and how long each takes
Understanding what happens in each phase helps set realistic expectations.
| Phase | What happens | Typical duration |
|---|---|---|
| Discovery | Audit of source environment, data volumes, integrations | 2–5 days |
| Planning | Migration plan, batch schedule, cutover timing, rollback plan | 1–3 days |
| Pilot | Small group migrated to validate the approach | 1–2 days |
| Pre-staging | All data synced to destination before cutover | 1–5 days |
| Cutover | DNS changes, final sync, users switch over | 1–4 hours |
| Hypercare | Post-migration support, integrity checks | 7 days |
How to reduce your migration timeline
The fastest migrations are the ones that start with the most complete preparation. Businesses that can quickly provide a full list of mailboxes, identify their third-party integrations, and make timely decisions on cutover windows consistently complete migrations faster than those where information is gathered slowly.
The other key factor is pre-staging. A migration service that pre-syncs your data before cutover day dramatically reduces the live window — meaning less risk, less pressure, and a shorter overall disruption period. Our Microsoft 365 migration service is built around exactly this approach, and our migration checklist walks through the preparation steps in detail.
Frequently asked questions
Related articles
Need help with
your migration?
Request a free consultation.
No commitment required · Response within one business day · sales@cloudynex.co