Most small business Google Workspace migrations run two to four weeks from kickoff to cutover, and the timeline is driven by data volume, not headcount. The team keeps working the entire time because the copy runs in the background and the cutover happens over a weekend with zero downtime. A 10-person office with typical mailboxes lands near the short end; years of large Drive libraries or PST archives push toward the long end.

Timeline is the second question every owner asks, right after cost. The answers online range from "one day" to "three months," and both can be true for different companies. This article explains what actually sets the clock, what a normal week-by-week looks like, and which parts you control.

What actually determines the timeline?

Four inputs set the calendar, and headcount is the least important of them:

  • Total data volume. The copy phase scales with gigabytes, not people. Email moves quickly; large file libraries are what take days.
  • Mailbox and archive sizes. A 4 GB mailbox and a 40 GB mailbox with a decade of PST archives are different projects wearing the same name.
  • The source platform. Microsoft 365, legacy Exchange, IMAP hosts, and file platforms each throttle bulk transfers differently, and that throttling is the ceiling on copy speed no matter what tooling is used.
  • Decision speed. Folder structure, naming standards, and who owns what are business decisions. When they are made in week one, the technical work never waits on them.

The week-by-week of a typical migration

The full step-by-step process lives in the migration process guide; this is the calendar view of the same work.

  • Week 1: planning and setup. Environment audit, Google Workspace tenant setup, DNS records staged, users and groups created, folder structure decided, and the migration plan mapped user by user.
  • Weeks 2 to 3: background data copy. Email, calendars, contacts, and files copy over while the team keeps working in the old system. Nobody notices this phase, which is the point.
  • Final week: verification and the weekend cutover. Every transfer is verified against the source, DNS switches over the weekend, and a delta pass copies anything that changed during the migration window. Monday opens in Google Workspace.
The zero-downtime rule. A longer timeline does not mean more disruption. The calendar length is background copy time; the team's working disruption is the same either way: none during the week, one weekend for the switch.

What stretches a migration past four weeks?

  • PST archives and local data. Mail that lives in files on laptops has to be gathered before it can be moved, and gathering is the slow part.
  • Very large file libraries. Multi-terabyte Drive, SharePoint, or file-server estates extend the copy phase; Google also caps how much data each account can take in per day, so very large moves are paced deliberately.
  • Source-side throttling. Hosts slow down bulk exports to protect themselves. This is normal and planned for, but it is a hard ceiling.
  • Compliance and legal holds. Data under retention rules needs its handling agreed before it moves, which adds planning time, not risk.

What you control

Three client-side moves shorten almost every migration: archive or delete what nobody needs before the copy starts, have registrar and admin credentials ready in week one, and make the structural decisions early. The migration service page covers what NeuGenity handles versus what it needs from you, and the pricing is the same regardless of timeline: $750 base plus $125 per mailbox, data transfer included.