Most Google Workspace migrations that lose mail do not fail during the copy. They fail in the planning: a shared mailbox nobody listed, an alias that stopped resolving, a DNS change made before the last sync, or a subscription cancelled while the final export was still running. This guide walks through the order of work that avoids all of those, whichever platform you are moving to.
Where mail actually goes missing in a migration
Before planning the move, it helps to know the usual failure points. They are almost never exotic.
- Mail that arrives during the switch. Messages delivered to Google after the last sync but before your MX records point at the new platform. If nobody runs a final sync after cutover, those messages stay behind.
- Accounts that were never on the list. Shared inboxes such as accounts@ or info@, former employees' mailboxes kept for records, and Google Groups that behave like mailboxes. If they are not inventoried, they are not migrated.
- Labels that do not translate cleanly. Gmail uses labels, not folders. One message can carry several labels, and over IMAP each label appears as a folder, so the same message can arrive several times or land in an unexpected place.
- Everything that is not email. Calendars, contacts, filters, signatures, delegated access and auto-forwarding rules are separate data. A mailbox can move perfectly while the team still loses its meetings and address book.
- Access that disappears too early. Google's organisation-wide export needs an active subscription, and deleted data is not included unless Google Vault was retaining it. Cancelling before verification closes the door on recovery.
Every step below exists to close one of these gaps.
Step 1: Take a complete inventory
Start in the Google Admin console and build a single sheet that lists everything that has to exist on the other side. At minimum:
- Every user account, including suspended and archived users, with mailbox size. Large mailboxes drive the timeline more than user count does.
- Shared and role mailboxes, and who needs access to each.
- Aliases and alternate domains. Every address mail is delivered to, not only primary addresses. A missed alias is the quietest way to lose mail, because senders get no error until the old platform is switched off.
- Google Groups used as distribution lists or collaborative inboxes, with their members and posting permissions.
- Delegation and forwarding. Assistants with access to an executive's mailbox, and any rules that forward mail outside the organisation.
- Devices and integrations. Scanners, CRM systems, websites and applications that send mail through Google's servers. Each one needs new SMTP settings on cutover day.
- Retention and legal holds. If Vault holds or retention rules apply, decide with whoever owns compliance how that history will be kept before anything is moved.
Agree on scope at this stage too. Some organisations move every message ever received; others move a set number of years and archive the rest. Both are valid, but the decision should be made deliberately, not discovered afterwards.
Step 2: Choose how the data will move
There are three common ways to get mail out of Google Workspace. Most migrations use more than one.
IMAP mailbox sync
A migration tool connects to each Google mailbox and to the new mailbox and copies messages across. This is the usual method for live migrations, because it can be run several times: a bulk pass first, then smaller delta passes that only copy what has arrived since. Since March 2025, Google no longer accepts password-only sign-in for IMAP on Workspace accounts, so the tool must authenticate with OAuth. Confirm that before you start. Google also applies daily IMAP bandwidth limits per user, so very large mailboxes are synced over several days.
Admin data export
A super administrator can use Google's Data Export tool to export the whole organisation's data. It is useful as a complete archive and as insurance, but it is not a live migration method. Google states that the export is available no earlier than 48 hours after it starts, typically takes around 72 hours, can take up to 14 days, and that files in the default storage are deleted 60 days after the export begins. The admin account must have 2-Step Verification turned on and, in most cases, be at least 30 days old.
Google Takeout per user
Individual users can export their own Gmail, Calendar and Contacts through Takeout, if the administrator allows it. It works for a handful of mailboxes but becomes hard to control across a whole team.
A sensible default for most organisations is IMAP sync for the move itself, plus one full admin export kept as an archive until the project is closed.
Step 3: Prepare the destination before any mail moves
The new platform should be fully ready before the first message is copied:
- Create every user, shared mailbox, alias and distribution list from your inventory.
- Add and verify your domain on the new platform without changing MX records yet.
- Prepare SPF, DKIM and DMARC records for the new platform, so outgoing mail is trusted from the first day.
- Lower the TTL on your MX records to a short value at least a day or two before cutover, so the change takes effect quickly when you make it.
- Decide how Gmail labels will map to folders, and how to treat the "All Mail" view, which contains every message and will create duplicates if copied alongside the label folders.
If the destination is ARCO Mail, our team handles this preparation during discovery, including the label-to-folder mapping and the deployment choice between on-premise, private cloud or hosted. The ARCO Mail vs Google Workspace page explains how the two platforms differ.
Working through this in your own environment?
Send us the context and we'll tell you plainly what we'd do first — and whether it's a fit for us at all.
Talk to our teamStep 4: Sync, cut over, then sync again
The sequence that prevents lost mail is simple and should not be shortened:
- Pilot. Migrate two or three real mailboxes, including one large one. Check folder structure, attachments, read status and calendar items with the people who own them.
- Bulk sync. Copy historical mail for everyone while users keep working on Google. Nobody notices this stage.
- Delta syncs. Re-run the sync to pick up new mail, ideally the day before cutover so the final pass is small.
- Cutover. Change the MX records to the new platform, usually at the end of a working day or before a weekend. Update SMTP settings on devices and applications at the same time.
- Final sync. Once the MX change has spread, run one more pass from Google. This collects anything delivered to the old mailboxes while DNS was updating, which is exactly the mail that is lost when this step is skipped.
- Reconnect clients. Users sign in on desktop and mobile with the new settings. Short written instructions per device type save a lot of support time.
Calendars, contacts and everything else
Mail is the visible part; these items are the ones people complain about in the first week:
- Calendars. Export calendars as iCalendar files or migrate them with a tool that supports calendar data. Recurring meetings that others organised may need to be re-sent by the organiser, so warn people in advance.
- Contacts. Personal contacts export as vCard or CSV. The organisation-wide directory is rebuilt from your user list on the new platform.
- Filters and signatures. These are rarely migrated automatically. Ask users to note important filters before cutover, and set signatures centrally if the new platform allows it.
- Drive files. Google Drive is a separate migration. Decide whether files stay in Google, move to the new platform's file storage, or move somewhere else, and make sure links in old emails are considered.
- Delegated access. Re-grant mailbox and calendar delegation on the new platform on cutover day, so assistants are not locked out.
Step 5: Verify before you switch Google off
Do not cancel the Google subscription the day after cutover. Keep it running until verification is signed off. A practical checklist:
- Compare message counts per mailbox between Google and the new platform, allowing for any label duplicates you chose to remove.
- Ask each department head to confirm that a sample of old threads, attachments and calendar entries are present.
- Send test mail to every alias and distribution list from an outside address.
- Check that SPF, DKIM and DMARC pass for outgoing mail.
- Confirm that the archive export, if you took one, is downloaded and stored somewhere you control.
- Remove Google's servers from your SPF record only once nothing sends through Google any more.
When all of that is done, the Google accounts can be closed with confidence rather than hope.
What to do next
If you are planning a move away from Google Workspace, the most useful first step is the inventory in Step 1. It tells you how large the job really is, which mailboxes carry the risk and how long the sync will take. Bring that list, or even a rough version of it, to a conversation with us and we will tell you plainly how we would run the migration, whether ARCO Mail fits your needs, and what a realistic timeline looks like. If you are still comparing platforms, start with ARCO Mail vs Google Workspace or our business email service, then contact our team.