FROM GOOGLE DRIVE MIGRATION
1. File migration with Cloudiway
Migrating from Google Drive is a straightforward process, whether you’re migrating to another Google Drive, or SharePoint Sites, OneDrive, Teams (or a mix), or Blob storage. The Cloudiway file migration platform ensures that your file migration runs smoothly and quickly.
File migration is performed in four steps:
- Create the connectors
- Import your user list into the Cloudiway platform
- Perform preprocessing (admin access and target resource creation)
- Migrate
In addition, Cloudiway provides some configuration and monitoring tools so you can observe the progress of your migration. This guide explains all the steps required from start to finish.
1.1. Performance & Security
For more security information, please refer to this article.
For more information about migration performance, please refer to this article.
1.2. License Management
Cloudiway platform automatically assigns the licenses. For more details regarding the license management, check out this page.
1.3. Delta Passes
Delta migration is a Cloudiway functionality that allows you to migrate incrementally. Changes are migrated during delta passes. Deletions are not propagated. Learn more.
1.4. Support
Although we provide support for our products, we do not provide support for third-party products such as PowerShell or server administration of Microsoft or Google products.
2. File migration scope
2.1. What is migrated
You will find the list of what can be migrated from Google Drive on this page: File migration tool.
2.2. Migration considerations
All data can be migrated without any changes to the source structure or permissions. Any users with permissions will need to be listed in a mapping table in order for their permissions to be migrated.
Important: the mapping table must be exhaustive, any missing email address will not be converted, and would end up with loss of file permissions and metadata. Cloudiway automatically populates this mapping table when source Google Drive accounts are discovered by Get List functionality. However, make sure if the mapping table was populated automatically that you are not missing any email address.
2.3. Audience
This guide is aimed at experienced system administrators who are capable of connecting to remote systems and using a variety of administration tools.
If you are concerned you might have any difficulty completing these steps, please consider a solution with our consulting team. This will ensure a fast, cost-effective, and stress-free implementation.
3. Pre-migration configuration
3.1. Before you start
We recommend you create a unique service account, especially for migration. After all migrations are complete, simply delete this account. We provide the steps below to help you set up an account if you don’t already have one.
The migration account (both at the source or target) must not authenticate using SSO or MFA (Multi-Factor Authentication).
You must define a migration account that bypasses SSO (authenticate natively in Google and Office 365) and without MFA activated.
Before you start, you will need to ensure you have the details outlined in the following table.
| Name | Description | Location |
| Cloudiway login | Stores details and provides communication between the systems you already use. |
https://portal.cloudiway.com |
| Help center | Our extensive help center is always accessible, with videos, troubleshooting tools, samples and more. |
https://help.cloudiway.com |
| (to OneDrive, SharePoint, Teams, Blob storage)
SharePoint |
It has to be the primary SharePoint admin account with permissions to the SharePoint site collection. | We recommend you create a migration account, especially for migration. After all migrations are complete, simply delete this account. We provide the steps below to help you set up an account if you don’t already have one. |
| Mapping table and User List (CSV) | Prepare any mapping tables in CSV format, and User List, ready to upload later on. | What Is The Mapping Table Used For? |
4. File Migration User List
4.1. Create Your Connectors
For Cloudiway to migrate your files, it needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors. You will need to set up a connector for each source tenant you wish to migrate and each target tenant that files should be migrated to. Follow the steps from this page to configure your Google Workspace and target connectors.
4.2. Import or create your users
In order to migrate permissions associated with every file migrated, you can upload your list of users. There are a number of ways. These include:
- CSV file import.
- Cloudiway’s mailbox discover tool (Get List).
- Create a single user.
Regardless, each user will need to be assigned a license type — Trial (limited to 100 MB), or Standard. The Cloudiway platform queries your user list (mapping table) when migrating each file so that the correct permissions can be migrated too. It’s therefore important that your user list is fully complete before starting any migration.
Option 1: CSV file import
If you have a CSV file of all your users, you can upload the file to Cloudiway.
1.Ensure you’re still in the File Migration area of portal.cloudiway.com and go to Files > User List
2. Click on Manage on the action bar and select Import
3. If required, click on Download sample CSV and add your users to the CSV file.
4. When you have a complete CSV file with the correct headers, click on the BROWSE button.
5. Locate your CSV file within your own file system, and select it.
6. Select the appropriate connectors in the Source and Target fields
7. Click on the UPLOAD button
If you see any error messages, check your CSV file, and try uploading again.
8. Once the CSV file format is correct, you will see a confirmation message.
Option 2: Get List
Cloudiway’s Get List tool helps you to retrieve users from your source tenant.
Go to Migration, select Get List.
The tool requires you to enter the Source and Target Pool.
Then to specify:
- The Target Recipient Type: OneDrive, SharePoint, or Teams.
- The Matching Rule:
- Mail Exact Match: the source email = the target email (bob.marley@sourcedomain.com > bob.marley@sourcedomain.com)
- Keep Email Prefix Same as Source: only the domain name changed (bob.marley@sourcedomain.com > bob.marley@targetdomain.com)
- FirstName.LastName (i.e. bob.marley@targetdomain.com)
- F.LastName (i.e. b.marley@targetdomain.com)
- FLastName (i.e. bmarley@targetdomain.com)
- LastNameF (i.e. marleyb@targetdomain.com)
- The Target Domain.
It will then add new users in the User List. This is an advanced tool that is best used in partnership with Cloudiway consultants.
Note: you can monitor the progress of this task in the User List: Get List Logs.
Option 3: Create a single user
Click on MANAGE > Create User and enter the following details:
The new user will be added to the User List. Repeat the process if you want to add more users.
Many of our first-time customers create a single user for testing purposes. This provides a means of watching the migration process without affecting all users.
Single users can also be created for migrations affecting just a few users. This is especially useful if you wish to specify different migration locations for individual folders within a OneDrive account.
For example, if you wish to migrate a project folder in Bob’s OneDrive to a SharePoint site and all his other files to OneDrive, you would create an additional user called Bob and specify the target connector as the SharePoint connector you created earlier. Instead of adding Bob’s source and target email addresses, you would add the OneDrive folder name to be migrated after the email address in the Source Email field and the full SharePoint list URL in the Target Email field.
Migrating to different places requires a particular order during migration to avoid files being migrated to the wrong location. For further information, please contact us.
4.3. Exclusion List
If you want to exclude different folders from the migration, enter the folder ID and the folder path.
See the example below, the folder ID is the character chain following folders/ in the URL, the Folder Path is /Test.
5. File Migration Global Settings
Before starting a migration, you can decide if you want, or not to migrate permissions, version history, and how to handle duplicates.
Follow the link below for detailed guidelines:
6. Audit, File Preprocessing and Migration
6.1. Perform an Audit
The audit is optional and purely informative. It consumes the Cloudiway license. You do not have to run it, unless you wish to see how many files and folders you have in the source drive.
Cloudiway’s Audit tool builds a list of all Google Drive IDs and their respective owners, as well as the file location. It also detects Google Drive folders that are heavily shared and that are de facto good candidates for being migrated to SharePoint Online.
You can use the audit results to decide whether you wish to migrate any folders to SharePoint Online. and if so, you can specify the site collection and document library for each folder to be migrated. Within document libraries, folder structures are entirely recreated.
Remember, these folders with specific destinations on SharePoint Online would need to be migrated before the general migration because Cloudiway only migrates a file once. Therefore, any folders with alternative targets will take priority.
1. From the User List area, select the users to audit (you can use the checkbox at the top of the list to select all, which we recommend)
2. From the action bar, click on MIGRATION, then Audit, the status change to FileAudit Scheduled
3. Refresh your page and verify the status
4. If there is an error, click on the file Error status, then Logs to see the Error message. Licenses are missing in this case; contact your sales representative or purchase more licenses on the platform, then try again.
5. For updates, you can refresh the page. To watch the results, click on the FileAudit Success status, then Audit
6.2. Perform Preprocessing
Now that your Cloudiway connectors are set up, and the audit successful, you can run the preprocessing task. The task can be run more than once if required. When Google is used as the source, it verifies that the mapping list matches the accounts declared in Google.
- From the User List area, select the users to preprocess (you can use the checkbox at the top of the list to select all)
- From the action bar, click on MIGRATION, then PreProcessing, the status change to FilePreProcessing Scheduled
- For updates, you can refresh the page, status should be updated to success
6.3. Activate and monitor your migration
Now that you have performed all the pre-migration steps within your tenants and Cloudiway, you’re ready to migrate. We recommend you run a test migration on a single user first to check that your configuration produces the outcome you expect.
To start your migration, select the users or batch and click on MIGRATION, then Start button. Your batch will be scheduled and will begin as soon as resources are available.
Don’t forget that Cloudiway migration platform supports delta passes and that migrations are therefore incremental; every time you restart the migration, only items that haven’t already been copied to the target — or that have been changed since they were copied to the target — will be migrated.
You can monitor your migration from the dashboard. Detailed article, here.
If you require more information, you can click on any of the files in the User List. You can Edit, see the Audit results, Logs, and Statistics.
7. Troubleshooting
Cloudiway provides an extensive help center with many resources, including common error messages, video guides: https://help.cloudiway.com/
The help center also contains information on how you can ask for further support, should you require it.
If you didn’t find a response in this admin guide neither the help center, you could send a ticket from the HELP menu, then Support.
