Cutover G Suite to Microsoft 365 Migration - Email, Contacts, and Calendars

This service migrates user email messages, email folders, contacts, and calendars from G Suite to Microsoft 365 / Exchange Online. IT Partner also configures the destination Microsoft 365 tenant, creates and configures users, assigns licenses, prepares the migration plan, starts and controls the migration, and provides a closeout report.

Email messages, email folders, contacts, and calendars are migrated. Google Tasks is not migrated — Microsoft's native migration tools do not support it. Google Drive data, Google Sites, corporate documents, desktop software settings, and other data are not included; Drive migration is a separate SKU and Google Forms migration can be added as an extra-cost item.

Contacts and calendars — yes: this service covers email, email folders, contacts, and calendars. Google Tasks — no: Microsoft's native migration tools do not support migrating Google Tasks. Google Drive data is also not included and requires a separate SKU.

Any additional services outside the stated email, contact, and calendar migration scope should be confirmed with IT Partner before the engagement.

The stated service duration is 1 week. The actual plan may vary depending on your environment, mailbox volume, readiness, and required coordination, so timing should be confirmed during the kickoff and planning process.

The service manager listed for this offering is Mike Mackey. During the engagement, IT Partner coordinates the migration activities according to the agreed plan and project milestones.

You need a Microsoft 365 tenant with Exchange Online licenses, access to your email domain DNS zone, administrator access to G Suite, and a paid Google Workspace / G Suite environment. Free Gmail accounts are not supported.

Regular, non-paid Google apps or Gmail accounts do not have administrative credentials; if such accounts must be migrated, they require individual usernames and passwords for each account, and Google may temporarily lock the account.

The engagement typically includes a kickoff meeting, source system health check, user creation or AD Connect configuration, migration start, migration verification, MX record cutover to Microsoft 365, final migration, and issue verification/fixing. The implementation plan may vary depending on your needs, so detailed milestone timing should be confirmed with IT Partner.

The stated objective is to migrate G Suite mailboxes to Microsoft 365 without downtime or data loss and with minimal user disruption. Because DNS changes, mailbox access changes, and client readiness can affect the user experience, the exact business impact should be reviewed during planning.

Mail flow is cut over by changing the domain’s MX record to the new Microsoft 365 tenant. The client is responsible for performing required internal and external DNS changes, while IT Partner includes the MX record cutover step in the migration plan.

IT Partner gathers information, verifies the original G Suite environment, configures the Microsoft 365 tenant, creates and configures users, assigns licenses, creates the migration plan, provides informational messages for users, and starts and controls the data migration process. IT Partner also provides a project closeout report after completion.

The client must provide a dedicated point of contact, coordinate internal resources and schedules, review deliverables, provide admin access to the source system or user passwords, perform DNS changes, identify high-risk users, and ensure required access is enabled for all users. These responsibilities are required because the migration depends on access, scheduling, DNS control, and user readiness.

No, informing users about the migration is not included as a managed client communication activity. IT Partner provides informational messages for users, but the client is responsible for distributing communications and coordinating staff schedules.

No. The service requires that you already have a Microsoft 365 tenant with Exchange Online licenses. IT Partner can assign licenses as part of the migration work, but the licenses themselves are a prerequisite and are not included in the migration price.

This service can migrate a maximum of 500,000 items from a user mailbox, and email is migrated from newest to oldest. The largest individual email that can be migrated is 35 MB.

Gmail uses labels rather than a true folder hierarchy, while IMAP clients such as Outlook present labels as folders. Because one Gmail message can have multiple labels, the same message may be downloaded multiple times into Microsoft 365 folders, which can increase storage usage and may not perfectly reproduce the Gmail label experience.

The project is considered successful when all mailboxes are moved to Microsoft 365. The stated results also include users being able to access Exchange Online from desktops, mobile phones, and tablets, in-scope email, contacts, and calendars being accessible, necessary transport rules working, mail being sent and received, and Exchange Online Protection being configured and working.

IT Partner provides a project closeout report indicating the final project status, acceptance criteria matching, any outstanding issues, and the final budget. The expected deliverables also include the configured Microsoft 365 tenant, configured users, assigned licenses, migration plan, user informational messages, and controlled migration of email, email folders, contacts, and calendars.

Customer team training and more extensive documentation are not included in the base service. They may be available for an additional fee, so they should be requested and scoped separately with IT Partner.