Google Workspace Migration Plan: 12-Week Template With Cutover Steps

8 min read · 2026-10-25

A Google Workspace migration plan sets out how you will move users, email, calendars, contacts and files from your current system (often Microsoft Exchange, Microsoft 365, an IMAP host or file servers) into Google Workspace, in what order, and how you will switch mail delivery without losing messages. Google's own deployment guide for large organizations uses three 30-day phases: Core IT, early adopters, and go-live for the whole organization.

The template below follows that model and adds the work around it: discovery before you start and adoption after go-live. It covers 12 weeks in six phases, each with a milestone you can check. You also get a filled-in example for a 400-person company, a cutover checklist, roles, metrics and the traps that cause lost mail and angry users.

The roadmap at a glance

Goal: Every user works in Google Workspace with their mail, calendar, contacts and files moved, mail flows through Gmail, and the old system is read-only or shut down. Duration: 12 weeks

1. Discovery and plan (Weeks 1-2)

   Know what you are moving and agree on how.

   • Count users, shared mailboxes, groups, distribution lists, resources such as meeting rooms, and total data volume per mailbox and file share.
   • List integrations that send or read mail, such as scanners, CRM, ticketing and marketing tools.
   • Decide what moves and how far back, such as all mail or the last five years, and what gets archived instead.
   • Pick the migration tools for each data type and test them on two or three accounts.
   • Agree on the cutover date, freeze windows and communication plan with the sponsor.

   Milestone: A signed-off migration plan with scope, tools, wave lists and a target go-live date.

2. Admin setup and Core IT (Weeks 2-4)

   Prepare the tenant and move the IT team first.

   • Verify your domain in the Google Admin console and set up organizational units that match your departments or policies.
   • Provision users, either by CSV upload or by syncing from Active Directory with Google Cloud Directory Sync.
   • Set up single sign-on if you use an identity provider, plus 2-Step Verification and mobile device rules.
   • Configure Gmail settings, mail routing for coexistence and Drive sharing rules.
   • Move the IT team's mail, calendars and files and have them use Workspace daily.

   Milestone: IT team working fully in Google Workspace, with security settings approved by the security lead.

3. Early adopters (Weeks 4-6)

   Test the method and support model on a small group of real users.

   • Pick about 5 percent of users across departments, including a few heavy calendar and shared drive users.
   • Migrate their mail, calendars, contacts and files, and set up their phones.
   • Run short training on Gmail labels, Calendar sharing and Drive shared drives.
   • Collect issues in a tracker and fix the migration settings before the main waves.
   • Train help desk staff on the top questions and write short how-to articles.

   Milestone: Early adopters signed off, with known issues fixed and a help desk FAQ published.

4. Bulk data migration (Weeks 6-10)

   Copy historic data for everyone before cutover, so go-live only needs a final sync.

   • Create accounts for all remaining users without changing mail delivery yet.
   • Migrate historic mail, calendars and contacts in waves of departments, oldest data first.
   • Move file shares or OneDrive and SharePoint content into shared drives and My Drive, keeping folder ownership clear.
   • Recreate groups, shared mailboxes as Groups or delegated accounts, and meeting rooms as calendar resources.
   • Check item counts per mailbox and per folder against the source after each wave.

   Milestone: Historic data copied for all users, with item counts checked and exceptions logged.

5. Go-live cutover (Weeks 10-11)

   Switch mail delivery and move everyone over in one planned window.

   • Lower the TTL on your MX records a few days ahead so the change spreads faster.
   • Run a final sync of mail and files after hours.
   • Change MX records at your DNS host to point to Google, and update SPF, DKIM and DMARC records.
   • Re-point apps and devices that send mail, such as scanners and CRM, to the new mail settings.
   • Staff a floor walker and help desk war room for the first days.

   Milestone: Mail flows only through Gmail, test messages arrive from outside and inside, and every user has signed in.

6. Adoption and decommission (Weeks 11-12)

   Help people work well in the new tools and close the old system.

   • Run follow-up training on shared drives, Meet and shared calendars by department.
   • Track sign-ins and support tickets and reach out to teams that are struggling.
   • Set the old mail system to read-only for a defined period, then archive or delete as your retention policy says.
   • Cancel old licenses and document the new admin setup.

   Milestone: Old system read-only or shut down, licenses cancelled, and ticket volume back to normal.

Common mistakes to avoid

• Switching MX records before historic data is copied leaves users with empty inboxes, so migrate history first and run only a final sync at cutover.
• Forgetting apps that send mail breaks invoices and alerts, so list every integration in discovery and test each one before go-live.
• Leaving Drive sharing settings at defaults leads to oversharing, so set sharing rules with security before early adopters start.
• Moving file shares user by user creates orphaned files, so move shared content into shared drives owned by teams.
• Training everyone in one big session leaves questions unanswered, so train by department and publish short how-to articles.
• Shutting down the old system on go-live day removes your safety net, so keep it read-only for a set period first.

Frequently asked questions

How long does a Google Workspace migration take?

Google's deployment guide for large organizations uses a 90-day plan in three 30-day phases. Small companies can move faster, sometimes in a few weeks. Data volume, the number of integrations and your change windows set the real timeline.

Can we migrate email to Google Workspace without downtime?

Yes, if you copy historic mail before cutover and switch MX records during a quiet window. Users may see a short delay while DNS changes spread. Keeping the old system read-only for a while gives you a fallback.

What data can be migrated to Google Workspace?

Mail, calendars, contacts and files can all be moved with the right tools. Some items need extra work, such as shared mailboxes, room bookings, file permissions and app integrations. Test each data type on a few accounts before the main waves.

Should we migrate all old email?

Not always. Many companies move a set number of years and archive the rest. Agree the cut-off with legal and records owners, based on your retention policy.

What are early adopters in a Google Workspace rollout?

They are a small group of real users, often around 5 percent, who move before everyone else. They test the migration, training and support model. Their feedback fixes problems before the whole company moves.

Generate this roadmap with AI