Leaving Google Workspace: the order of operations that keeps mail flowing

A few years ago moving a company off Google meant buying a migration product and hoping. That has changed. Microsoft now provides an automated batch migration inside the Exchange admin center, and its own documentation recommends it over the manual route because it completes several of the setup tasks in your Google admin console for you. It moves mail, calendars and contacts, and it lets you do so in stages while both environments stay active.

So the tooling is no longer the hard part. Sequencing is.

The order we use

Inventory first. Before anyone opens an admin console, write down what exists. Mailboxes are the easy part. The surprises are in the aliases, the groups that forward to outside addresses, the shared calendars that run a meeting room, and the old account that owns a folder of files half the company depends on. If it is not on the list, it will not be on the plan.

Prepare the destination. Buy the licences, create the accounts, and set up the two routing subdomains the migration needs so that mail can pass between the systems while people are split across them. Microsoft's automated method configures four of the required steps on the Google side. You still have to complete the prerequisites properly, and the documentation is blunt that the migration will not succeed otherwise.

Run a pilot. Five people, one week. Pick people who will complain. You are looking for the things no checklist predicts: the phone that will not sync, the shared mailbox somebody uses for supplier invoices, the calendar invitation that arrives twice.

Move in batches. Each batch is driven by a simple list of addresses. Go department by department, and do finance on a day that is not month end.

Cut over last. Only when every mailbox is across do you change the records that tell the world where your mail lives. Do it on a weekend, early, with someone watching. Until that moment new mail keeps landing in Google and is copied over, so nobody misses anything.

Then wait. Leave Google running for a short overlap. Something will turn up that somebody needs.

What the mail tool does not move

The batch migration covers mail, calendars and contacts. Files are a separate piece of work with its own tools and its own decisions, mostly about who should own what in the new place. Treat it as a second project that shares a timeline with the first. Trying to do both in the same weekend is how people end up restoring from backup.

The step everyone forgets

Your domain sends mail from more places than the mail system. The website contact form. The invoicing tool. The copier. Each of these needs to be allowed by your domain's mail records, and those records are exactly what changes at cutover. Find them all before the weekend, not on the Monday after, when the complaint is that customers have stopped replying.

How long it takes

The copying itself runs from several hours to a couple of days depending on how much data there is. The calendar time around it is longer. For an organization of fifty we would normally plan four to six weeks from inventory to closing the old account, and most of that is the pilot and the overlap, which are the two parts people are tempted to skip.

Where X-Axis fits

We plan and run these moves for organizations in the United States and Canada. The estimator gives a price range for your size, and the Microsoft 365 page shows what is included.