A Google Workspace migration should be treated as a business transition that includes identity, DNS, historical data, mail flow, applications, devices, training, support, and final validation.
Define the Migration Scope
List the source email system, number of users, mailbox sizes, calendars, contacts, archives, shared mailboxes, public folders, distribution lists, aliases, forwarding, applications, mobile devices, retention, and legal requirements.
Do not assume every source feature has an identical Google Workspace equivalent.
Identify the Source Platform
The source may be Microsoft 365, Exchange Server, another Google Workspace tenant, personal Gmail, an IMAP provider, hosted cPanel mail, Zoho, or another platform.
The available Google or third-party migration tools depend on the source, authentication method, data type, edition, and size.
Choose the Target Google Workspace Edition
Confirm storage, security, retention, investigation, meeting, device, and administrative requirements.
Assign licenses before migrating data to destination users and verify that the subscription supports required migration and post-migration features.
Secure the Destination Tenant
Protect Super Admin accounts, configure 2-Step Verification, recovery, administrator roles, alerts, OAuth controls, Gmail safety, Drive sharing, and device expectations before importing business data.
A migration should not move sensitive information into an unreviewed tenant.
Build the destination before moving the data
Users, groups, aliases, security, shared drives, and mail flow should be designed before the production migration begins.
Inventory Users and Addresses
Create a source-to-destination mapping for every user, group, alias, shared address, room, resource, application sender, and former employee address.
Resolve duplicate names, invalid addresses, domain changes, suspended accounts, and users who should not be migrated.
Decide What Data Will Move
Define whether the project includes email, folders or labels, calendars, contacts, tasks, notes, archives, files, permissions, shared mailboxes, and other data.
Record unsupported items and differences in how source folders, categories, flags, recurring meetings, delegates, and permissions are represented.
Select the Migration Method
Use Google's current migration tools or a qualified migration platform based on the source and requirements. Options can include server-side data migration, client-side tools, APIs, specialized Google migration products, or third-party services.
Confirm authentication, administrator privileges, source throttling, concurrency, data types, logging, retry behavior, and support.
Prepare Source Access
Create or approve the service account, application authorization, impersonation, administrator role, API permission, or user credentials required by the chosen method.
Use the minimum privileges necessary and remove migration access after completion.
Prepare Destination Users
Create users with correct primary addresses, aliases, licenses, organizational units, groups, 2-Step Verification plans, and application access.
Do not send users temporary passwords too early when they are not supposed to begin using Gmail before cutover.
Prepare Shared and Departmental Email
Map shared mailboxes and department addresses to Google Groups, collaborative inboxes, delegation, aliases, routing, or dedicated accounts according to the workflow.
A direct one-to-one mailbox conversion may not provide the best Google Workspace design.
Prepare Calendars and Resources
Inventory personal calendars, shared calendars, rooms, equipment, delegates, recurring events, external invitations, and time zones.
Create resource calendars and test organizer, attendee, conferencing, and update behavior.
Prepare Applications and Devices
Inventory mobile devices, Outlook clients, scanners, printers, websites, accounting systems, customer platforms, monitoring, and applications that send or retrieve mail.
Replace old SMTP and POP or IMAP credentials with an approved Google Workspace design.
Create the Migration Plan
Document discovery, destination build, pilot, initial synchronization, user preparation, final synchronization, MX cutover, validation, support, and source retirement.
Assign owners, dates, success criteria, rollback steps, and communication checkpoints.
Do not schedule a migration around assumptions
Measure mailbox sizes, source limits, migration speed, error rates, DNS timing, and user readiness with a real pilot.
Choose Pilot Users
Select representative users with small and large mailboxes, calendars, contacts, mobile devices, delegates, shared addresses, executives, and ordinary employees.
A pilot containing only one technically experienced user will not reveal every business workflow.
Run the Initial Pilot Migration
Migrate the approved date range and data types. Record duration, throughput, warnings, errors, missing items, duplicates, permissions, and user experience.
Compare source and destination counts using the migration tool's reports and targeted user validation.
Document Data Differences
Source folders may become Gmail labels. Categories, flags, tasks, notes, rules, delegates, signatures, and archives may require separate handling.
Provide users with a clear list of expected differences rather than promising an identical interface.
Plan Incremental Migration
Many projects copy older data before cutover, then synchronize newer messages closer to launch.
Confirm how the chosen tool handles repeated runs, duplicates, deleted source items, changed calendar events, and new mail.
Prepare DNS and Gmail Activation
Record current MX records, lower time-to-live in advance when appropriate, prepare Google recipients, configure Gmail, and save rollback records.
Do not change mail routing until the destination is ready and the cutover is approved.
Prepare Domain Authentication
Inventory all senders, configure SPF, enable DKIM, and establish a staged DMARC policy.
Mail can migrate successfully while outbound messages still fail authentication if applications and vendors are overlooked.
Communicate With Employees
Provide the cutover date, sign-in steps, temporary credential process, 2-Step Verification instructions, mobile setup, application links, expected data differences, training, and support contact.
Tell users when to stop making source-side changes if the migration method requires a freeze or final synchronization window.
Complete Final Synchronization
Run the approved final pass to capture new email, calendar, and contact changes according to the selected tool.
Review errors before changing MX records. Document unresolved items and owners.
Change Mail Routing
Update MX records to the Google-provided targets according to the approved architecture, then complete Gmail activation.
Monitor both source and destination providers during DNS propagation.
Validate Mail Flow
Test internal, external, alias, group, secondary-domain, application, and shared-address delivery. Verify replies and sender authentication.
Use Email Log Search, source logs, message headers, and migration reports.
Validate User Data
Ask pilot and production users to review important folders or labels, recent and older mail, sent mail, calendars, contacts, attachments, and searches.
Track validation by user rather than assuming a successful tool status proves every business-critical item.
Support Mobile and Desktop Changes
Remove or reconfigure old account profiles, add Google Workspace accounts, enroll devices where required, and confirm Calendar and Contacts synchronization.
Plan special support for executives, shared computers, and field employees.
Keep the Source Temporarily
Retain source access for the approved validation and recovery period. Preserve legal, retention, archive, and backup requirements.
Do not continue paying indefinitely without a documented source-retirement date.
Remove Migration Privileges
Revoke service accounts, application permissions, administrator roles, temporary credentials, internet allowlists, and vendor access used for the migration.
Store reports and completion evidence according to the organization's documentation policy.
Complete the Project Review
Confirm mail flow, data counts, user sign-in, 2-Step Verification, devices, applications, domain authentication, shared addresses, source retention, support cases, and unresolved issues.
Document lessons learned and the final environment.
Email Migration Checklist
- Inventory users, data, shared addresses, applications, and devices.
- Select the destination edition and secure the tenant.
- Create source-to-destination identity mappings.
- Define exactly which data types will migrate.
- Select and authorize the correct migration tool.
- Prepare destination users, groups, aliases, and calendars.
- Run a representative pilot.
- Document unsupported and differently represented data.
- Plan incremental and final synchronization.
- Prepare MX records, authentication, communication, and rollback.
- Validate mail flow and user data after cutover.
- Remove temporary access and retire the source deliberately.
Frequently Asked Questions
Does changing MX records migrate old email?
No. MX records direct new inbound messages. Historical email requires a migration tool or another transfer method.
Can Microsoft 365 email be moved to Google Workspace?
Yes. Use a supported Google or qualified migration method and test mail, calendars, contacts, shared workflows, and applications.
Should the old provider be canceled immediately?
No. Keep it for the approved validation and recovery period until migration and mail flow are confirmed.
When Professional Support Helps
Professional support can assess the source, design the destination, run pilots, migrate data, change DNS, validate mail flow, train users, and document source retirement.
Need help applying this?
Set up and migrate Google Workspace with confidence.
J3 Systems Group LLC can plan Google Workspace deployments, verify domains, configure DNS and Gmail, design identities, migrate email and files, validate cutovers, and document the environment.