This guide shows how to migrate G Suite to Office 365 for a small business with no full-time administrator, using the wizards in the Microsoft 365 admin center. G Suite is now called Google Workspace and Office 365 is now Microsoft 365, but the steps below are what you will see today. If you want the full enterprise procedure, read the G Suite to Office 365 migration pillar guide; this article is the short, weekend-sized version.
The plan is laid out as days: two evenings of preparation, a Friday start, a weekend of copying and a Monday cutover. Treat the timing as a suggestion, because copy speed depends on mailbox size and on Google's quotas, not on the calendar.
Who this is for and what you will have at the end
This is for an office of roughly 5 to 50 people where one person, often the owner or an office manager, does the IT. You have a Google Workspace domain, you have a Microsoft 365 subscription (or are about to buy one) and you can edit the DNS records for your domain.
At the end you will have every mailbox, calendar and contact list in Exchange Online, shared Drive content in OneDrive or SharePoint, MX records pointing to Microsoft 365, and a short list of things you rebuilt by hand. For budgeting and licensing prices, see the migration cost and timeline post rather than this one. For a printable version of the steps, use the migration checklist.
If you have only two or three users, pause first. Microsoft's own documentation says a very small business with a few users should consider a different method, such as importing to Outlook from a PST file. The tools in this article make sense once the manual work would exceed the setup work.
Choose your tool in two minutes
Microsoft offers several paths. For a small business, the choice is mostly decided by how many mailboxes your Google domain has.
| Situation | Tool | Where you start |
|---|---|---|
| 1,000 or fewer Google mailboxes | Simplified Gmail Migration (SGM) | Microsoft 365 admin center, consolidated Google migration page |
| More than 1,000 mailboxes | Batch migration in the Exchange admin center | Exchange admin center, Migration |
| Mail only, simple needs | IMAP migration | Exchange admin center |
| Drive files | Migration Manager | Microsoft 365 admin center, Setup, Migration resources |
According to the consolidated Microsoft page, when you choose to migrate mail the tool counts users in the source domain and sends you to SGM for 1,000 or fewer, or to the large-tenant experience above that. You do not choose between them; you can only plan for which one you will land in. Microsoft's SGM page also carried a note that the feature was waiting on worldwide availability when it was written, so if your admin center sends you to the batch tool instead, follow the Exchange admin center steps further down.
Two evenings before: prepare Microsoft 365 and Google
Do these steps on weeknights so the weekend is only copying.
Lower the DNS risk
Find where your DNS is hosted and confirm you can log in. Microsoft's pages warn that DNS changes can take anywhere from a minute to 72 hours depending on the registrar. Many DNS hosts also let you shorten the MX record's time to live (TTL) ahead of a cutover; that is general DNS practice rather than a Microsoft instruction, so check your host's options.
Create the Microsoft 365 users
Create each user in the Microsoft 365 admin center with the same address they use in Google, for example [email protected]. Do not assign a license yet if you are following the batch route: Microsoft states that for the batch tool you assign Exchange licenses after the batch starts and the mail users convert to mailboxes, within 30 days. Check the SGM prompts for its own licensing requirements when you reach them, since the SGM page does not list them.
Allow forwarding if you use the batch route
Under the batch route, Microsoft says to allow the required forwarding in both Google Workspace and Exchange Online before starting a batch. Exchange outbound spam policies, Remote Domain settings and mail flow rules can each block it, and any exception needs your security administrator's approval. If your business is small enough that you are the security administrator, record the exception and the date.
Declutter Google
Delete what nobody needs: old shared drives, abandoned accounts, huge attachments. Less data means a shorter weekend. Also locate orphaned Drive files. Microsoft states that unorganized or orphaned files are not scanned, migrated or listed in migration reports, so decide how to preserve any you need.
Check Microsoft's MRM guidance
Microsoft's limitations section recommends disabling messaging records management (MRM) and archival policies before migrating, because items deleted or archived by those policies show up as "missing" in migration checks. A new small tenant usually has nothing custom here; just do not enable a retention policy mid-migration.
Friday evening: connect Google and start mail
Sign in and let the app do the setup (SGM route)
Per Microsoft's SGM page, the flow runs in this order:
- Sign in to Google with migration admin credentials.
- The tool reads the mailbox count and routes you to SGM if it is 1,000 or fewer.
- Install the Google Marketplace app named "Microsoft 365 Mail Migration". The app performs the setup tasks in the Google Admin console that the older tool left to you.
- Return to the Microsoft 365 admin center and confirm your Google credentials again.
- Review the source scan, which lists mailboxes and their sizes.
- Choose one, many or all mailboxes to migrate.
Notice what you control in each workflow: the duration of data (all or a date range), the type of data (mail, calendar, contacts, rules, permissions, delegates) and which labels or folders to migrate. Microsoft describes a separate workflow for large mailboxes, defined as over 80 GB.
Run a pilot first
Select one or two mailboxes, preferably yours and someone patient. Start with a date range if you want a quick result. After they finish, open Outlook and check folders, calendar and contacts before selecting everyone.
The batch route, if you were sent there
If you land in the batch tool, the Exchange admin center steps from Microsoft's page are:
- In the Exchange admin center, select Migration, then Add migration batch.
- Name the batch and, under Select the mailbox migration path, choose Migration to Exchange Online.
- For Migration type, choose Google Workspace (Gmail) migration.
- On Prerequisites for Google Workspace migration, select Start and sign in with your Google admin account.
- Complete the four required Google tasks, note the ClientID and Scope, and authorize them under API Clients with Add new.
- Create a migration endpoint, import the JSON key and a CSV with an
EmailAddressheader. - On Move configuration, enter the routing domain, then save.
This route also needs two routing subdomains, one for mail going to Microsoft 365 and one back to Google, which is why SGM is easier for a small office. The detailed procedure is in the email migration walkthrough.
Saturday: copy Drive with Migration Manager
Mail and Drive can copy at the same time, but start Drive after mail is running so you can watch both.
- In the Microsoft 365 admin center, go to Setup, then Migration resources.
- Under Self-service migration and import tools, select Explore migration & imports tools, then Google Workspace.
- Select Connect to Google Workspace, then Install and authorize. Sign in as a Google Workspace super administrator and choose the organization-wide install option, such as Admin install or Domain install.
- Back on the Install the migration app page, select Next, then Sign in to Google Workspace and finish.
- On the Drives tab, select the drives, select Scan, wait for Ready to migrate, then select Copy to Drive migrations.
- On Drive migrations, check the destination paths, select the drives, then select Migrate.
Microsoft notes that Migration Manager Lite can guide eligible tenants through this without the separate scan and copy steps, so your screens may be shorter. For standard projects with OneDrive destinations, each user's OneDrive must exist before you assign destinations. If it does not, pre-provision it.
Know the Drive defaults
- Originals stay in Google Drive. Google-native files are exported to Microsoft Office or other supported formats.
- File-level permissions are not migrated by default. Files inherit the destination folder's permissions, so test with a representative user.
- Only the latest file version is copied by default.
- A task can show Completed while unsupported items were skipped, so download the summary and detailed reports.
Sunday: rebuild what the tools skip
Use Sunday for the manual list. From the limitations table in Microsoft's Google Workspace migration page:
| Data type | Not migrated |
|---|---|
| Vacation settings, automatic reply settings | |
| Meeting rooms | Room bookings |
| Calendar | Shared calendars and event colors |
| Contacts | Gmail tags, contact URLs, custom tags; more than three email addresses per contact |
Rules do migrate but stay turned off by default, so ask each person to review them in Outlook before enabling them. Recreate the shared calendars and room resources in Exchange Online. Google Groups and shared inboxes such as sales@ are not covered by the mail migration either; the shared mailbox versus Microsoft 365 group comparison helps you pick the replacement.
The largest single message that can migrate follows your tenant's transport configuration, 35 MB by default. A few oversized messages may fail; list them and decide whether anyone needs them.
Monday: complete, switch MX, tell people
When every mailbox has migrated, choose Complete Migration in SGM. Microsoft says the option is available only after all mailboxes are done. You are then asked to change DNS entries at your registrar so new mail comes to Exchange Online, and to confirm that you did. On the batch route, select Complete migration batch once the batch shows Synced, wait for Completed, then connect the primary domain to Microsoft 365 to change the MX records.
SGM keeps syncing new mail that lands in Google for 72 hours after you confirm the DNS change. Do not cancel Google before that window ends. The cutover checklist covers Autodiscover, SPF and test messages.
Send staff a short note before Monday: new sign-in address, how to set up Outlook, what to do with their phone, and what was not migrated. The Drive side is explained in the Google Drive to OneDrive guide.
Verify
Ask three people to check these in Outlook on Monday afternoon:
- The newest message in their Inbox from Friday also appears, and a message sent to them from outside arrives in Exchange Online.
- Recurring meetings show at the right times.
- Contacts are present, with a note of any contact that had more than three addresses.
- Their files open from OneDrive or the SharePoint library you assigned.
Troubleshooting
| Symptom | Likely cause and fix |
|---|---|
| SGM never appears and you see the batch tool | Your Google domain has more than 1,000 mailboxes, or the feature is not yet available to your tenant. Use the batch steps. |
| Mail still goes to Google after Monday | DNS can take from a minute to 72 hours. Check the MX at your DNS host and wait; SGM keeps syncing. |
| Items flagged as "missing" | An MRM or archival policy deleted or archived them. Microsoft recommends disabling those policies before migration. |
| Drive task shows Completed but files are absent | Unsupported items are skipped. Open the detailed report. |
| Migrated users cannot use their new mailbox | On the batch route, assign Exchange licenses within 30 days of the batch start. |
| Forwarding blocked on the batch route | Check Exchange outbound spam policy, Remote Domain settings and mail flow rules. |
Closing checklist
- DNS access confirmed and MX TTL lowered.
- Users created in Microsoft 365; licenses handled per your route.
- Orphaned Drive files located; unneeded data deleted.
- Pilot mailboxes verified in Outlook.
- Mail and Drive migrations finished, reports downloaded.
- Room bookings, shared calendars, responders and groups rebuilt.
- MX switched, 72 hours elapsed, Google data exported before cancellation.
What we checked
- Opened "Simplified Gmail Migration (SGM) for Small and Medium Businesses" on learn.microsoft.com on 2026-11-16 (page updated 2026-07-28) and copied the 14-step flow, the 1,000-mailbox threshold, the 80 GB large-mailbox workflow and the 72-hour post-DNS sync.
- Cross-checked the 1,000-mailbox threshold against the "Migrate data from Google Workspace to Microsoft 365" page (updated 2026-08-03); both agree, though the SGM page says "<=1000" and the consolidated page says "less than 1000 seats" in one sentence.
- Opened "Migrate Google files to Microsoft 365 for business" (updated 2026-10-30) and quoted the menu path Setup > Migration resources, the Drives tab labels, and the defaults on versions and file-level permissions.
- Opened "Perform a Google Workspace migration" (updated 2026-10-14) and copied the limitations table and the 35 MB default message size.
- Opened "Migrate business email and calendar from Google Workspace" (updated 2026-10-30) and confirmed the Exchange admin center batch labels, the 30-day license window and the very-small-business PST suggestion.
- Documented output: none shown; Microsoft publishes no console output for these wizards, and no commands appear in this article.
- Not checked: no Google Workspace or Microsoft 365 tenant was used, so the screens were not seen. The day-by-day schedule is our planning suggestion, not a Microsoft timeline. Steps follow Microsoft's documentation as of 2026-11-16.
Last tested: 2026-11-16
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.