Practical Google Workspace migration advice for SMB admins: pick the right tool by source and scale, run a 3 to 5 user pilot, and set up backups.

If you’re moving under 1,000 users from Exchange, IMAP or another Google Workspace account, the Admin console’s data migration service handles it. PST files and Outlook profiles need GWMMO. Anything past 1,000 users or genuinely complex, spanning Exchange, SharePoint and file shares together, calls for Google Workspace Migrate, usually with partner support. Your first move today: confirm super admin access and line up a five-person pilot group before you touch a single mailbox.

TL;DR:

Self-service migration tools handle up to 1,000 users; larger or complex migrations typically require Google Workspace Migrate with partner support.

Confirm super admin credentials, API scopes, bandwidth, and storage estimates before starting to avoid delays or failures during migration.

Conduct a thorough inventory, run pilot migrations on a small user group, and verify permissions and data integrity before full deployment.

Use GWMMO for PST and Outlook profiles, the Admin console for IMAP mail, and advanced methods for shared drives with complex permission structures.

Always set up a reliable backup strategy within the first week, conduct test restores, and understand that exports are for egress, not long-term protection.

Hostme

Make Your Migration Run Smoothly

Hostme provides tailored IT support for cloud migrations, troubleshooting, AI setup, and staff training for Irish small businesses.

Get tailored IT support

Which Google Workspace migration tool fits your source and scale?
Your step-by-step Google Workspace data migration checklist
GWMMO, data migration service and Workspace Migrate: what to watch for
Moving Drive files and shared drives without losing structure
Why exports alone aren’t a backup, and what to do instead
Hostme perspective: what we see in small-business migrations
How Hostme handles Google Workspace migration for you
Key official documentation and tools to consult
Sources

Which Google Workspace migration tool fits your source and scale?

The right tool depends on where your data lives and how many people you’re moving, not on which product Google markets loudest.

Exchange or Exchange Online → the built-in data migration service handles most cases; larger or messier Exchange environments sometimes need the advanced migration method.
PST files and Outlook profiles → GWMMO (Google Workspace Migration for Microsoft Outlook) is Google’s recommended tool, and it’s built specifically for this job.
SharePoint and OneDrive → Drive import paths cover standard folder structures, though shared libraries with complex permissions often need the advanced route.
IMAP-based mail (including many hosted email providers) → the Admin console’s data import tool.
Google-to-Google moves (a rebranding, an acquisition, a domain consolidation) → typically the simplest case, handled through the same Admin console tools.

Scale matters as much as source. Google’s own migration product matrix maps data sources and user counts to the right product, and it draws a clear line: self-service tools comfortably cover 1 to 1,000 users, while anything above that threshold is designed around Google Workspace Migrate. Many small offices typically finish an email migration using self-service tools within a short time frame. A 3,000-seat organisation with multiple Exchange servers and legacy PST archives is a different project entirely, and usually needs specialist infrastructure.

Before you start anything, confirm four things: super admin credentials with two-step verification enabled, the right API scopes or service accounts provisioned, enough bandwidth to move your data volume without throttling, and a realistic estimate of total mailbox and Drive storage. Skipping this step is where most self-managed migrations lose their first week.

Your step-by-step Google Workspace data migration checklist

A migration that goes smoothly almost always follows the same sequence, and skipping steps is what causes the 2am phone calls.

Inventory everything first. List every user, mailbox size, Drive usage figure, shared drive, and any chat history or retention obligation you need to preserve.
Run your preflight checks. Confirm Workspace licences are provisioned, plan your DNS changes in advance, check for bandwidth limits or throttling risk, and set up the service accounts you’ll need for importing email with the data import tool.
Pilot with 3 to 5 real users. Run a full import for this group, verify mail routing and Drive access work correctly, and confirm the delta import process catches new mail arriving during the test.
Migrate in bulk, then sync the delta. Schedule the main import, monitor its progress, run delta syncs to catch anything sent after the initial pull, then plan your MX record change for the actual cutover window.
Verify after cutover. Check mail flow end to end, confirm delegated accounts still work, audit Drive permissions, and get information out to your users.

Pro Tip: Run your pilot group’s delta sync at least twice before the full migration. The second run almost always surfaces a permissions or routing issue the first one missed, and it’s far cheaper to find that with five users than with five hundred.

GWMMO, data migration service and Workspace Migrate: what to watch for

Each tool has its own quirks, and most of the support tickets we see trace back to one of these getting missed.

GWMMO comes as either an EXE or MSI installer, and the MSI is the one to choose for any deployment across multiple machines via group policy. Split PST files larger than a few gigabytes before importing; oversized files are the most common cause of stalled transfers. GWMMO moves mail and labels reliably, but it does not touch Drive files or calendar data, so plan a separate path for those.
The Admin console data migration service relies on CSV import maps for bulk user mapping, and its self-service path is built around migrations up to roughly 1,000 users. Delta imports after the initial run catch mail that arrived during migration, so schedule at least one before cutover.
Google Workspace Migrate needs real infrastructure: Windows server nodes, a database, and node servers configured to Google’s system requirements. This complexity is exactly why organisations running large or multi-source migrations frequently bring in a partner rather than building the setup from scratch in-house.
The Data Export tool writes your organisation’s data to a Google Cloud Storage bucket, and export runtime can stretch to several days for large accounts. The detail that catches people out: exported data is automatically deleted after 60 days unless you’ve configured your own storage bucket to receive it.

That 60-day window is the single most misunderstood fact in this entire process, and it shapes how you should think about backups later in this guide.

Moving Drive files and shared drives without losing structure

Standard folder structures from OneDrive or SharePoint generally move cleanly through the default import path. Shared libraries with nested permission layers, external sharing links, or unusual ownership structures usually need the advanced import method instead, which gives you finer control over how ownership and access map across.

Preserving shared-drive membership properly means mapping service accounts correctly before you migrate, and transferring file ownership deliberately rather than letting it default to whoever runs the import.

Two limitations are worth flagging to your team in advance:

Version history doesn’t always carry across intact, particularly from older file-sharing systems.
Permission edge cases (external guest access, unusual sharing links) can behave unpredictably and need a manual check.

Run a permissions audit immediately after migration and tell affected users what changed, rather than letting them discover a broken share link themselves.

Why exports alone aren’t a backup, and what to do instead

Why exports alone aren't a backup, and what to do instead — overview diagram

Verification is not optional. Check mailbox counts against your inventory, spot-check a sample of messages for content and attachments, confirm calendar events transferred correctly, audit Drive permissions, and test that delegated access still functions for anyone who needs it.

Here’s the part that catches SMBs out: Google’s Data Export tool and its 60-day auto-deletion rule exist for data egress, not ongoing protection, and Google’s own Trash retention is short-term by design, not a safety net. Third-party backup services provide scheduled, granular restores and considerably longer retention windows, which matters for ransomware recovery and compliance requirements. Options range from cloud SaaS backup platforms to NAS-based workflows like Synology’s Active Backup for teams that already run on-site storage.

Confirm mailbox and Drive counts against your original inventory.
Audit shared drive and delegated-access permissions post-migration.
Set up a genuine backup solution within the first week, not the first month.

Pro Tip: Test a full restore from your backup solution within the first fortnight of setting it up, not when you actually need it. A backup you’ve never restored from is a guess, not a plan.

Hostme perspective: what we see in small-business migrations

The migrations that go wrong for small businesses almost never fail on the big Exchange or PST steps. They fail on incomplete user inventories and shared-drive permissions nobody checked until a client couldn’t open a folder. Hands-on support during the pilot and early verification stages catches these before they become a disrupted Monday morning for your whole team.

— Konrad

How Hostme handles Google Workspace migration for you

Professional help is the alternative to spending your own week buried in Admin console settings for a migration you’ll only ever do once. Instead of piecing together GWMMO installers, CSV import maps and delta sync schedules yourself, you get someone who’s done this before, working through it directly with you.

Hostme

The approach is straightforward: assess your current setup and data sources, run a small pilot group first, migrate the rest once that pilot’s verified clean, check mail flow and Drive permissions properly, then walk your staff through what’s changed. For a sole trader or small team, that means someone else absorbing the technical risk and the hours, not you learning Google’s migration product matrix at 11pm the night before cutover. It also means getting your backup strategy sorted properly from day one, rather than discovering the 60-day export deletion rule the hard way.

If you’re planning a move to Google Workspace, or you’re partway through one and it’s stalled, get in touch with Hostme’s IT support team and we’ll talk through what your migration actually needs.