Migrate Multiple Google Workspace Mailboxes

Understanding why organizations perform bulk mailbox migration helps set clear expectations for the process. Here are some common scenarios:

• Switching from G Suite to Microsoft 365: Many organizations move from Google Workspace to Microsoft 365 to benefit from better integration with tools like Teams, SharePoint, and OneDrive. This makes bulk mailbox migration a frequent requirement.
• Migrating from G Suite to Exchange Server: Businesses may choose to migrate to on-premises Exchange Server for greater control over their email environment, security policies, and data management.
• Migrating from G Suite to IMAP-based Systems: Organizations that use alternative email platforms supporting IMAP often need to migrate multiple mailboxes from Google Workspace while maintaining data accessibility.
• Subscription Changes or Decommissioning G Suite: If a business plans to discontinue Google Workspace, migrating all mailbox data in advance is essential to prevent data loss and ensure continuity.
• Compliance and Data Archiving Requirements: Certain regulatory or business requirements may require email data to be migrated and stored in a different platform for compliance, backup, or long-term archiving.

Use the steps below to migrate mailboxes, contacts, and calendars from Google Workspace to Office 365 with EdbMails.

• Step 1: Download the EdbMails Application

  • Download and install the EdbMails application on your system with reliable internet access to begin the setup.

     Before you proceed, check the system requirements for G Suite migration.

    

  • Start the EdbMails application on your computer.
  • Enter your registered email ID and password, then click ‘Login’. If you haven’t created an account yet, choose ‘Start Your Free Trial’ to access the trial version.
     Note: The trial version provides all key features and allows migration of up to 30 items per folder. For unlimited migration, purchase G Suite Migration license from the EdbMails website.

     Click here to check G Suite Migration pricing details.

    After purchasing the license, close the application and open it again. Then log in using the same email ID and password used during the purchase to activate the license successfully.

    

  • Select the option ‘G Suite Migration’.

    

  • Select ‘G Suite to Office 365 Migration’.

    

  • You can continue with the default job name, or select ‘New Job’ to create and assign a custom name based on your preference.

    

• Step 2: Connect to the Source G Suite Server

  • Enter the admin email address, then click ‘Browse’ to upload the JSON key file downloaded from the Google Cloud Console. After adding the file, click ‘Login’ to establish the connection.

     Steps to create a Google Cloud project and download the JSON key file.

    

  • Once authentication is completed, choose how you want to load the mailboxes:

    i) Load Mailboxes Automatically: After signing in, EdbMails loads and displays available mailboxes automatically, making setup quick and simple. Due to Microsoft API limits, only up to 100 mailboxes may appear. If you have more, use the next option.

    ii) Load Mailboxes using CSV file: If all mailboxes are not listed, choose ‘Load Mailboxes using .CSV file’ to load the required mailboxes.

    iii) Load Mailboxes from Previous List: This lets you reuse a previously saved mailbox list, saving time in repeated migrations.

  • Click ‘Next’ to continue.

    

  • Select one or more mailboxes / folders you want to migrate, then click ‘Next’ to continue.

    

• Step 3: Connect to the target Office 365 server

  • Click ‘Add New Connection’ to create a new connection with the target Office 365 account. If you’ve already connected before, simply choose it from the list and click ‘Connect to Existing’ to continue.

    

  • EdbMails provides flexible migration options by supporting primary mailboxes, archive mailboxes, and public folder migration.
  • Choose the ‘Connect to Primary / Shared Mailbox’ option and proceed by clicking ‘Next’.

    

  • Make sure you’re using a Global Admin account with an active mailbox, as it’s required to auto register the EdbMails application in Entra ID (Azure Active Directory).
  • If you prefer the manual registration option , you can use either a Global Admin account or a user account with full access permissions.
  • Click ‘Login’ to continue.

    

  • Authenticate on Microsoft sign-in page.

    

  • Select one of the methods to load the mailboxes. You can choose ‘Load Mailboxes Automatically’ or load them using a CSV file, then click ‘Next’.

    

• Step 4: Map source and target mailboxes

  • Choose the required mailbox mapping option, then click ‘Continue’.

    

  • EdbMails automatically creates the required mailboxes on your target Office 365 server and assigns the necessary licenses.

      Learn more about automatic mailbox creation in the target Office 365 server.

    

• Step 5: Start G Suite to Office 365 Migration

  • Click the 'Start Migration’ button to initiate the migration process.

    

  • Track the migration status in real time using the progress bar. After the migration completes, EdbMails prompts you to review the results. Click ‘View Logs’ to open the migration report, then sign in to the target server to verify the migrated data.

    

• Ensure a Reliable High-Speed Network: A stable and fast internet connection helps maintain steady migration speed and avoid delays during migration.
• Schedule Migration During Off-Peak Hours: Running migration when user activity is low reduces system load and supports smooth execution with zero downtime.
• Allocate Sufficient System Resources: Ensure your system has enough CPU and memory to handle large mailbox migration without performance issues.
• Track Migration Progress: Regular monitoring helps quickly identify and resolve any issues and keeps the process on track for better results during migration.
• Maintain Source and Target Readiness: Ensure both source and destination servers are responsive and properly configured before starting migration.