This guide provides detailed instructions on configuring a migration batch to move users' file data from a File System source to Google Workspace users using CloudM Migrate. The process specifically covers migrating documents.
Before you begin, ensure you have already set up your migration project and created a user batch as outlined in our Migration Guide.
Prerequisites
- The service account running the migration service must have full control of the migrating files.
- If you are migrating files from network drives, please see Configuring Mapped Network Drives.
1. Adding Entities to Your Batch
Before configuring migration settings, you must add entities (users and their data) to your migration batch. This step defines what data will be migrated and its destination. Use the following format for each entity you add:
-
*Export Type:
User - *Export Name: The primary email address of the source user.
-
*Import Type:
User - *Import Name: The primary email address of the destination user.
- Given Name: User's first name at the destination (leave blank if the user already exists at the destination)
- User's surname at the destination (leave blank if the user already exists at the destination)
-
*Documents Path: The path to the source folder on your file system (e.g.,
C:\Users\JohnDoe\Documentsor\\Server\Share\JohnDoe). - Documents Destination Path: [Optional] Specify a folder name within the destination user's My Drive to migrate the documents to. If left blank, documents will go to the root of the user's My Drive.
* Mandatory field
For further instructions on adding entities to your batch, refer to: Adding Items to a migration batch
Once entities are added, ensure the 'Migrate' checkbox is enabled for all entities you intend to include in the migration run. You should also select Drive to be migrated.
2. Configuration Settings
After adding users to your batch, the next step is to review and configure the migration settings. These settings are organized into several sections:
General Settings
- Review Domain Names: Correctly configure all domain mappings. This is essential for replacing the source domain with the destination domain on email addresses and permissions during the migration.
- Date Filters: You can apply date range filters to migrate data created within a specific timeframe. If no filter is set, all items will be migrated regardless of their age.
Source Platform Settings
Settings specific to File System as a source are accessible and configurable through the File System - Source Connection Setup article.
Destination Platform Settings
For migrations from File System to Google Workspace users, it's generally recommended to retain the default destination settings for optimal behavior. However, there may be instances where you need to adjust certain settings. For a detailed explanation of each destination setting, please refer to the article below article. Document and User settings are key focal points:
Google Workspace - Destination Settings
Advanced Settings
- File System Permissions: First, refer to the following article which explicitly explains how to map file system permissions (ACLs) to Google Workspace users and/or groups:
-
Address Replacement CSV: Uploading an Address Replacement CSV file is critical for maintaining data fidelity. This file maps all source user email addresses (or user names from file system ACLs) to their new destination addresses.
- Why is this important? This process ensures that permissions on shared files, calendar entries, and other collaborative content are correctly re-assigned to the new user accounts. Without it, users may lose access to shared data or errors may occur during the migration process.
- For more information, refer to the Address Replacements article.
The necessary settings may vary based on the specific entity type and the stage of the migration process. We recommend reviewing the links in the previous sections to identify your specific migration scenario and ensure all settings are appropriately configured.
3. The Migration Process (Overall Strategy)
For a complete, in-depth guide that covers project planning, user communication, and detailed pre- and post-migration checklists for your entire migration project, please review our comprehensive recommended strategy article: