Skip to main content

Migrating Microsoft 365 Public Folders to Google Workspace Groups

This article provides instructions on configuring a migration batch for migrating public folders from Microsoft 365 to Groups in Google Workspace. The setup process outlined here focuses on migrating Mail, this is the only available data type for this scenario.

Before proceeding, ensure you have completed the steps in the Migration Guide to set up your migration project and added users to your migration batch.


1. Adding Entities to Migrate

The Automatic Method (Recommended)

It is possible to automatically populate your Items to migrate list with all public folders from the source, however, there is one prerequisite configuration:

1.1 After creating your Public Folders batch, go to Configuration > Source > Public folders.

1.2 Include public folders in user list: Set to Enabled.

1.3 Public folder username: Enter the username of an admin account at your source.

  • Note: This account must have owner permissions on all of the public folders and subfolders that you plan to migrate.

Public Folders - Get Items From Source.png

1.4 Go back to the Items to migrate screen.

1.5 Click on Add items to migrate > Get items from source.

1.6 The Items to migrate list will now be populated with the public folders from your source.

The Manual Method

When preparing to migrate users to corresponding accounts at the destination, follow the format below:

  • *Export Type: Public folder
  • *Export Name: Path to source public folder
  • *Import Type: Group
  • *Import Name: Destination group email address
  • Given Name: Display name of the destination group
  • Family Name: Not required
  • Documents Path: Not required
  • Documents Destination Path: Not required

*Mandatory Field

Note: Each public folder and sub-folder will need to be added as an item to migrate. Each item will also consume a license. Sub-folders are not included when specifying the parent public folder.

Further instructions on adding entities to your batch can be found here: Adding Items to a migration batch

For each entity added, you can select the specific data types you wish to migrate. Ensure the 'Migrate' checkbox is enabled for all entities you intend to include in the migration run.


2. Configuration Settings

General Settings

In the General Settings section, ensure all domain mappings are configured correctly to facilitate replacing the source domain with the destination domain during the migration.

You can also apply date range filters for various data types to migrate information within a specific timeframe. Specify the date ranges you wish to include.

General Settings

Source Settings

For a standard public folder to Google group migration, it is recommended to keep most of the source settings at their default values. However, you will need to ensure you modify the below.

  • Public folders -> Public folder username: You will need to enter the username of an admin account at your source that has owner permissions on all of the public folders and subfolders that you plan to migrate.

For more information on additional source settings, please refer to the following article:

Microsoft 365 - Source Settings

Destination Settings

For this type of migration, it is generally recommended to retain the default destination settings. However, based on your specific migration requirements, certain settings may need to be adjusted. Details can be found in the article below:

Google Workspace - Destination Settings

Advanced Settings

For a straightforward public folder to Google group migration, most advanced settings can remain at their default values. However, consider the following:

  • Address Replacement: It is highly recommended to upload an address replacement CSV that maps source users, groups and aliases to their corresponding destination users, groups and aliases. For more information, please refer to the Address Replacements article.

3. The Migration Process

For a complete, in-depth guide that covers project planning, user communication, and detailed pre- and post-migration checklists, please review our comprehensive recommended strategy article:

CloudM's Recommended Migration Strategy

Was this article helpful?
1 out of 1 found this helpful