# Moving from Google Workspace: the DNS cut-over checklist

> The exact order of operations for moving a domain's email off Google Workspace without losing a single message, plus what Koltrix does not import yet.

- Published: 2026-09-29
- Author: Koltrix Team
- Category: Guides
- Source: https://koltrix.com/blog/moving-from-google-workspace

This is the guide G3 in our launch plan asks for: what to do, in what order, to move a domain's email onto Koltrix. It assumes you own the DNS for the domain and have a Workspace account you are leaving.

**Read this first:** Koltrix does not import your existing mailbox in v1. There is no IMAP importer yet; it is planned for the release after launch. Until then, keep the old mailbox alive and read-only for as long as you need the archive, and export it from Google Takeout before you cancel.

## How long does a move off Google Workspace take?

The DNS change itself takes minutes once the old records have expired; the work around it takes longer. Plan one afternoon of preparation, one quiet morning for the cut-over, and a week of watching afterwards. Most of the risk is not in the switch but in the systems you forgot were sending or receiving as your domain, which is why the checklist starts with an inventory. If the domain carries a lot of history, the [sender inventory guide](/blog/email-migration-sender-inventory) goes through how to build that list.

## Before you touch DNS

1. **Export the old mail.** Google Takeout produces an MBOX per mailbox. Do this while the account is still paid for.
2. **Write down every system that sends as your domain.** Your invoicing tool, your CRM, your helpdesk, your newsletter. If you have DMARC reports, read them — the list is longer than you think.
3. **Lower your MX TTL to 300 seconds** at least a day beforehand. This is the single step that turns a bad cut-over from an eight-hour problem into a five-minute one.
4. **Add the domain in Koltrix** and publish SPF, DKIM and DMARC. These are safe to publish while Workspace is still live, as long as your SPF record includes both.
5. **Create the addresses** you need, including the shared ones, and confirm a test send arrives in an inbox.

## The cut-over

1. Pick a quiet morning. Not a Friday.
2. **Replace the MX records** with ours. Remove Google's — leaving both in place splits your mail across two systems, which is worse than either.
3. Watch for the first inbound message. With a 300-second TTL this is usually within a few minutes.
4. **Send a test from an outside address** to each address you created, and reply to one of them.
5. **Tighten SPF.** Once nothing sends through Workspace, remove its `include:` and move DMARC from `p=none` towards `p=quarantine`.

## What does Google's MX record look like, and what replaces it?

Google Workspace domains point at either a single record, `smtp.google.com`, or the older set of five records starting with `aspmx.l.google.com`. Which one you have depends on when the domain was set up. Either way, the cut-over replaces all of them with the MX records Koltrix shows for your domain. [MX records](/blog/mx-records-explained) are tried in order of priority, so a mixed set sends part of your mail to each system until the old ones are gone.

| Record | Before | During the cut-over | After a week |
|---|---|---|---|
| MX | Google's records | Replace all with the new records | Verify no Google MX remains |
| SPF (TXT) | Includes Google's SPF | Include both senders | Remove Google's `include:` if nothing sends through it |
| DKIM | Google's selector | Add the new key beside it | Remove the old key once nothing signs with it |
| DMARC | Often `p=none` | Keep as is | Tighten when reports are clean |

## What breaks, and where does it go?

Moving the MX does not move your configuration. Check each item below before cancelling anything.

| Thing in Workspace | What happens | What to do |
|---|---|---|
| Aliases | They stop receiving | Recreate each as an address or alias on the new side |
| Google Groups used as `support@` | They stop receiving | Replace with a shared mailbox; see [migrating aliases, groups and shared mailboxes](/blog/migrating-aliases-groups-shared-mailboxes) |
| Forwarding rules and filters | They stay behind in Gmail | Recreate the rules you still need |
| Calendar invites and Meet links | Unaffected by mail routing | Keep Workspace for these, or move them separately |
| Apps sending as your domain | May fail SPF or DKIM | Update each one, or confirm it still authenticates |

One gotcha: while Workspace users still exist on the domain, mail between them can be delivered inside Google without consulting your MX at all. If someone reports that internal mail goes missing after the cut-over, check Google's routing and user settings before blaming DNS.

## How do you roll back if the cut-over goes wrong?

Put Google's MX records back. That is the whole procedure, and it works only because you kept the Workspace account active and lowered the TTL beforehand: with a 300-second TTL, resolvers pick the old records up again within minutes. Mail sent during the window lands in one system or the other, never in neither, but you will need to read both inboxes for a while. The [rollback plan](/blog/email-migration-rollback-plan) lists the triggers worth acting on and the ones worth waiting out. Keep the old mailbox read-only afterwards as [handling the old mailbox](/blog/old-mailbox-after-migration) describes, and delete nothing until the archive is exported and you have checked it opens.

## For a week afterwards

- Keep the Workspace account active but stop using it. Late-arriving mail from a resolver with a stale cache still lands somewhere.
- Read your DMARC reports. Anything failing is a system you forgot.
- Check your bounce and complaint numbers. A new sending setup with an old list is where reputation problems start.

## A final check before you cancel

Before you cancel Workspace, confirm four things:

- Every address you created has received a message from outside your domain.
- The DMARC report from the last seven days shows no failing source you do not recognize.
- The Takeout archive opens, and you know where it is stored.
- Nobody on the team is still signed in to Gmail on a phone for that domain.

## What to keep Workspace for

Calendar, Drive, Docs and Meet are not part of Koltrix, and a Workspace account without mail routing is still a valid account. Many teams move only email and keep the rest. That is a perfectly sensible end state and we are not going to pretend otherwise.
