File Share to Google Workspace

System Requirements (Self-Hosted)


  • 64 bit Operating system: Windows Server 2016+ (Clean build recommended)
  • Microsoft .NET Framework 4.8
  • Recommended system specification - Primary Server:
    • 3GHz 8 Core Processor or better
    • 200+GB Disk space
    • 16+GB Memory
  • Recommended system specification - Secondary Server(s):
    • 3GHz 4 Core Processor or better
    • 100GB Disk space
    • 8+GB Memory

If you are looking to complete a 'large migration' (a migration of more than 25,000 users or 10 million objects), refer to the following articles for additional considerations:

If you are storing Drive document mappings and running a large migration, contact the support team.

Required ports

Primary and Secondary servers will communicate with the source and destination platforms, and the CloudM Migrate licensing platform using HTTP/HTTPS. Therefore ports 80 and 443 will need to be open between these environments

The URLs accessed for the license server are as follows.


There is also the following to consider:

  • SQL server runs on TCP 1433 and UDP 1434 - SQL server needs to be installed and set to TCP or UDP on the Primary/SQL Server. For information on setting the TCP to 1433, refer to this following article.
  • Redis runs on port 6379
  • gRPC on the below TCP ports. Note: It is possible to customise these ports when installing via Command Line using the instructions here: Installing / Upgrading from the Command Line 
    30061 (Primary Service)
    30062 (Secondary Service)
    30063 (Results Logs Service)
  • All of Google's API endpoints are listed here:
  • All Microsoft 365 URLs and IP address ranges are listed here:

CloudM Migrate Hosted

CloudM Migrate Hosted makes migration as simple as possible. There are no system requirements or installation, you can simply access the Hosted migration platform and configurations are pre-provisioned. See here for more information.

Source Platform - File System

CloudM Migrate can be used to migrate file system files to Google Drive, Microsoft OneDrive or SharePoint.  Folder structures, files, timestamps and file ACLs can be transferred to the destination system along with many other features.  The sections below describe how to migrate files from a file system to Google Drive or OneDrive / SharePoint.

To migrate a file system, you should first choose File System as the migration source platform.

Migrating to Google Drive

To migrate files to Google Drive, CloudM Migrate must be configured so that it knows the folder path that contains files for each user.

This file path should be specified on the user's tab on a per-user basis.  File paths can be specified as local file paths or UNC file paths (in the form \\server\share\folder\etc).  The ‘Drive’ option must also be selected for each user.

All of the files within the specified folder will be migrated into the user’s Google Drive.  Various choices are available as to how folders are migrated. Files and folders can be migrated to the same folder structure as the file system, files can be migrating into a single collection, a combination of both can be done, or no structure at all can be applied.  See the settings in the Google destination platform settings for more information.

Migrating to OneDrive for Business/Sharepoint

To migrate files to OneDrive/SharePoint, CloudM Migrate must be configured so that it knows the folder path that contains files for each user.

This file path should be specified on the users tab on a per-user basis.  File paths can be specified as local file paths or UNC file paths (in the form \\server\share\folder\etc).  

The ‘Drive’ option must also be selected for each user.  

If migrating to ‘Team Sites’ see Migrating SharePoint Document Libraries

One other setting is required before migrating to OneDrive, which is the ‘SharePoint Admin URL’ setting in the destination platform server settings.  This URL is required to determine the location to perform the required admin tasks as part of a migration.

All of the files within the specified folder will be migrated into the user’s OneDrive or Team Site.  The folder structure of the file system will be preserved during migration.  See the Microsoft 365/OneDrive destination platform settings for more information about other options.

Excluding Folders?

It's not possible to explicitly exclude folders from a File migration. If you require to exclude source folders from such a migration, you can either:

  • Move the unwanted folders, or;
  • Specify a list of the folders (separated by semi-colons) that you do want to migrate under Documents Path (and not include the ones you don't).

Migrating ACLs to Google Drive or Microsoft OneDrive

It is possible to migrate file system ACLs and this should be turned on via ‘File System Document Sharing’ in the File System migration settings.  Note that when migrating to OneDrive, an email notification is not available.

Resolving Permissions to Email Addresses

File system NTFS permissions (ACLs) are always stored on the file as login names like: domain\username.  To migrate them to either destination system, CloudM Migrate must map them to email addresses.  If an ACL cannot be mapped to an email address (by any means) then no ACL is added in the destination account.

Various ways are provided to map file system permissions to email addresses:

  • If the migration station is logged into an Active Directory domain (and the user you run the tool with has permissions) then we attempt to obtain a list of users from Active Directory and map to their email address.  This requires the user to explicitly have an EmailAddress set in Active Directory.  If the workstation is not connected to Active Directory, the option ‘Resolve Email Addresses’ in the File System source migration settings should be turned off.
  • If not logged into AD, or the option to resolve Active Directory Email Addresses is disabled then no mapping to email addresses is done by default and explicit mappings must be provided by a CSV file (see below).
  • When the ACLs are processed, CloudM Migrate uses the address replacement schemes to map to possible email addresses:
    • If an entry has explicitly been specified in the ‘Address Replacements (File)’ option in the Address Replacements settings then it will be explicitly mapped according to the provided mappings. 
      • For example, if you want to map an NTFS permission of domain\paul to, the CSV file should contain an entry of domain\paul,
  • If the resolved permission is an email address (when it was available in Active Directory) and its not been explicitly mapped via a CSV then the domain name will be replaced according to the ‘Address Domain Replacements’ options and the name part of the email will be mapped according to entries on the user tab.
    • For example: The original ACL is domain\paul
    • This was mapped via Active Directory to
    • ‘Address Domain Replacements’ included a mapping from to
    • On the user tab there was a row with an export name of paul and an import name of paul.jones
    • The final ACL email address will be

Advanced Options

While the default options are recommended for the majority of organisations the CloudM Migrate gives users the ability to customise their migration experience. The following are some of the Advanced Options available to customers migrating from a file system.

Active Directory Options

  • Resolve Email Addresses – attempt to resolve NTFS permissions to email addresses. Email addresses for users are obtained from Active Directory and CloudM Migrate must be installed on a workstation connected to Active Directory and logged into Active Directory as a user with permissions to read users from the Directory. If migrating files only from a local workstation, not connected to Active Directory, set this option to false. For more information about how ACLs are mapped, please see the specific section regarding file system migrations.

Document Options

  • File System Document Sharing – specify how to share files migrated from the file system. Note that when migrating to Microsoft OneDrive, email notifications are not sent.
  • Excluded Account Permissions – specify a list of login users who’s file ACLs will be ignored. For example, an ACL for ‘NT AUTHORITY\SYSTEM’ is present on all files. To ignore this ACL, specify this value in this option. In order to help list the possible permissions for a particular system, an option is available in the Tools menu to list all local and Active Directory users under ‘Tools > File System > Export User List’.
  • Migrate Top Level Folder – Migrate the folder hierarchy into a top-level folder named the same as the top-level folder specified in this option. The first top level folder name migrated to will be fixed for future migrations.
  • Set Migrating User as Owner - Change the owner to the migrating user. This setting also ensures that the file owner from the file system is added as a writer at the destination.Troubleshooting

If the path is from a network drive, you need to ensure that you map the network drive exactly per our documentation here.

The CloudM Migrate Service may need to be run using your logged in Windows user or a dedicated account per this article.

Occasionally, CloudM Migrate can have difficulty enumerating a UNC file path. This appears to be caused by an unstable network connection which underpins the UNC path.  Creating a Mapped Drive within Windows to the UNC path can mitigate this issue in some circumstances.

Configure Destination Platform Settings - Google Workspace

Select Google Workspace as your destination platform.

Select where you would like your data to be migrated. If you have purchased Google Vault, you may want to migrate data directly into Google Vault.

To enable Google Vault for your domain, please see this article

Destination_Platform_G_Suite.PNG Select Add Settings.

Enter information for your Google Workspace admin account.


  • Domain Name - The domain name you will be migrating from. This should be the Internet domain name, not the local domain name.
  • Admin Username - An administrator account for the domain specified, this will usually be an email address for a Super Admin.
  • Authentication Method - Set whether to use a P12 key or a JSON key as the authentication method.
  • Service Account Email Address - Before attempting to configure CloudM Migrate, you should have created a Google Cloud platform project and created a service account for it. If you have selected to use a P12 key, you will need to input the service account's email address in this field.
  • Private Key - The file path to the P12 or JSON key that was generated and downloaded when creating the OAuth service account.
  • All Advanced Settings are set to a default value, designed to ensure that your migration will work without additional configuration. You should only edit the Advanced Settings if instructed to by CloudM Support or in a CloudM Knowledge Base article.

Select which items to migrate

It's now time to add which items you'd like to migrate.


To add the items from that you want to migrate from your source platform to your destination platform, select Add items to migrate drop down menu and click on one of the following options:

  • Get Items from source - Get a full list of all items in the source platform.
  • Bulk add / import items - Upload a CSV file to bulk add users.
  • Add User/Resource/ Group/Shared Drive/Team Site/Microsoft Team etc.- Manually add an item of the selected item type.

Selecting a Star next to any specific user or users will prioritize their migration. When a migration starts, threads will be assigned to any starred user first so that their migration can start immediately. 

At this point you can choose what to migrate for each user, you can migrate Mail, Contacts, Calendars, Tasks, Classic Sites, Notes and Channels.

Enter your user's full email address within the Export Name field. If you have already created your Microsoft 365 users, then you will just need to enter their username.

Select how much content to migrate

CloudM Migrate lets you decide how much content to migrate to your domain by specifying required date ranges. 


If you are changing your email address as part of the migration you can verify that the domain names are correct here. You can also specify specific Address Replacements in the respective section of the advanced settings.

Environment Scan

Environment Scan allows you to plan and prepare your migration by performing analysis of your source file and mail environment and reporting important information such as item counts, data volume, permissions, and folder depth.

Reports are produced which can be exported and analysed. Using the information provided you can estimate your migration's duration more accurately, and address any potential issues before your migration even begins.


Selecting Scope of Scan


Depending on your source platform, you can choose to scan files, emails, or both sets of items.


  • Leaving the Report on File Permissions setting unchecked will speed up the Environment Scan process.
  • In order to include Report on File Permissions in the process, you will need to check this setting AND enable Document Sharing (or a setting related to document sharing) in the Source Platform settings. If either is not enabled, the Environment Scan will not scan or report on File Permissions.


Your CloudM Migrate userlist is used to define the scope of the scan. You can choose to scan all accounts from your list, or restrict the scan to users selected for migration.


How to run an Environment Scan

After entering your source and destination server settings, populating your userlist, and configuring your settings, you will be prompted to run an environment scan. It is optional, but recommended for file platforms.

Click Start and then confirm by selecting Start Environment Scan on the pop-up box to begin the scan. CloudM Migrate will connect to your source environment and capture file and / or mail information. This can take up to several hours, depending on the amount of data present.


Once the scan completes, the data is reported on the Environment Scans page and can be exported to file, using the Export Scan Results option.


Start your migration

To begin your migration, select Start.



Review your migration results

During the migration process, CloudM Migrate will report back in real time exactly who is being migrated and the items being processed. All you now need to do is sit back, relax and wait for your migration to complete.

Check the progress of your migration.

Once complete you can download a full report for your migration.

Delta Migrations

CloudM Migrate supports delta migrations of all migration types. To run a delta migration after the first pass, simply start the migration again. Already processed mailbox items will be skipped, and file items will be checked for changes and re-migrated if updated since the previous run. More info:

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