Short answer
Most Google Workspace to Microsoft 365 migrations for small and mid-sized organizations take about 3 to 10 weeks from discovery to cutover. Mail and calendar are usually the quick part. Drive and shared drive content, identity setup, device changes and user training drive the schedule. A firm timeline should be set only after discovery has measured data volume and complexity.
Key facts
- Typical range: about 3 to 10 weeks for SMB and mid-market organizations, longer for very large data sets.
- Mail moves in a pre-stage and delta pattern, so the MX cutover itself is a short window.
- Google Drive and shared drives usually take longer to plan and move than Gmail.
- Identity, device sign-in and Outlook or Teams onboarding often set the real pace, not data copy speed.
- A schedule is reliable only after discovery has sized mailboxes, Drive data and sharing.
Typical timeline by organization size
Elapsed time depends more on complexity than on headcount, but size is a useful starting point. The ranges below assume a planned project with a pilot group, one or more migration waves and a short cutover window.
| Organization size | Typical elapsed time | What usually drives it |
|---|---|---|
| Under 50 users | 2 to 4 weeks | DNS access, licensing, user training |
| 50 to 250 users | 4 to 7 weeks | Drive volume, shared drives, device sign-in |
| 250 to 1,000 users | 6 to 10 weeks | Wave planning, shared drive mapping, change management |
| 1,000+ users or several domains | 10+ weeks | Multiple domains, large archives, integrations, phased business units |
The phases and what each one takes
A Google Workspace move follows the same pattern as most Microsoft 365 migrations. The phases overlap, and the copy work runs in the background while users keep working in Google.
- Discovery, about 1 to 2 weeks: inventory users, groups, aliases, shared mailboxes, calendars, rooms, Drive and shared drive data, third-party apps using Google sign-in, and DNS ownership.
- Tenant and identity preparation, about 1 to 2 weeks: verify domains, create users, assign licenses, plan sign-in and MFA, and set up Teams and SharePoint structure.
- Pilot, about 1 week: move a small group of IT and business users to test mail, calendar, Drive mapping and the user guide.
- Pre-stage copy, 1 to 4 weeks: Gmail, Calendar and Contacts move with Exchange Online migration batches, and Drive content moves with Migration Manager or a third-party tool.
- Cutover, usually a weekend: switch MX and Autodiscover, run final delta syncs, and get users signed in to Outlook, Teams and OneDrive.
- Hypercare, 1 to 2 weeks: fix profile issues, missing items and mobile setup, then retire Google licenses on a planned date.
What makes a Google migration take longer
The biggest variable is Drive. A firm with a few gigabytes per user in My Drive is very different from one with years of project folders in shared drives, heavy external sharing and Google-native Docs, Sheets and Slides that must be converted to Office formats.
Other common drivers are large Gmail archives, many aliases and Google Groups that need to become distribution lists or Microsoft 365 Groups, room and resource calendars, and apps that use Sign in with Google. Each of those adds planning and testing time.
Change management also matters. Users who have lived in Gmail and Google Docs need help with Outlook, OneDrive sync and Teams. Training and floor support often set the pace of later waves.
What can shorten the schedule
Clean source data shortens everything. Removing departed users, archiving old shared drives and agreeing on a cutoff date for very old mail reduces copy time and testing.
- Decide early how Drive maps to OneDrive, SharePoint sites and Teams, so the copy job runs once.
- Get DNS registrar access in week one, since MX and verification changes cannot wait on a ticket.
- Pre-stage mail and Drive data weeks before cutover so the final delta is small.
- Publish a one-page user guide and run short training sessions before each wave.
Why the timeline is set after discovery
Copy speed in Microsoft and Google services is subject to throttling, so a schedule built on data size alone can be wrong. Discovery measures the real volume, counts shared drives and external shares, and identifies blockers such as legacy apps or unmanaged devices.
Only then can a partner commit to wave dates, a cutover weekend and a license retirement date with confidence. A quote that names a fixed date before anyone has looked at the tenant is a guess.
How Accred Consulting approaches it
Accred Consulting starts every Google Workspace move with a discovery phase that sizes Gmail, Calendar, Drive and shared drive data and maps out identity and DNS. The Proposal then sets a clear scope, a fixed price and a timeline with named waves and a cutover weekend. US-based specialists run delivery with structured check-ins, pre-stage mail and Drive, and stay on for hypercare. In one engagement, an approximately 180-person firm moved mail, calendar and Drive in 5 weeks, with Drive mapped into Teams and SharePoint rather than dumped into OneDrive. Handover includes documentation and knowledge transfer.
Track record: 400+ client projects, 2,000+ migration workstreams and 150,000+ users migrated by a US-based team. Company facts · Case studies
Related questions
Want this scoped for your environment?
Book a free consultation. After discovery you get a written plan with scope, a fixed price and a timeline.
Book a free consultation