Migrating from Google Drive is a straightforward process, whether you’re migrating to another Google Drive, or to SharePoint or OneDrive (or a mix of both). The Cloudiway file migration platform ensures that your file migration runs smoothly and quickly.
File migration is performed in four steps:
In addition, Cloudiway provides some configuration and monitoring tools so you can watch the progress of your migration. This guide explains all the steps required from start to finish.
For more information about security, please refer to this article.
For more information about migration performance, please refer to this article.
4.1. What can be migrated
When migrating from Google Drive, all of the following items can be migrated:
4.2. Migration considerations
Migrating from Google Drive a straightforward process. 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.
This guide is aimed at experienced system administrators who are capable of connecting to remote systems and using a variety of administration tools.
Although we provide support for our own products, we do not provide support for third party products such as PowerShell or server administration of Google.
If you are concerned you might have any difficulty completing these steps, please consider a solution with our consulting team, contactable via email@example.com. This will ensure a fast, cost-effective and stress-free implementation.
5.1. Before you start
Before you start, you will need to ensure you have the details outlined in the following table.
|Cloudiway login||Stores details and provides
communication between the
systems you already use.
|Our extensive knowledge base is
always accessible, with videos,
troubleshooting tools, samples and
|This doesn’t have to be the primary
SharePoint admin account. It does
need to be a user account with
permissions to the SharePoint site
| We recommend you create a migration
account especially for migration. After
all migrations are complete, simply
delete this account. We provide steps
below to help you set up an account if
you don’t already have one.
5.2. Pre-migration checklist
To ensure successful migration, we recommend that you follow the checklist
Prepare any mapping tables for users and groups in CSV format, ready to upload later on.
You need a tenant administrator account to setup the permissions.
5.3. G Suite — Set permissions for the service account
7. Click on the Authorize button
NOTE: 1. Each scope must be separated by a comma.
2. Some scopes require slashes (/) at the end and others don’t: please use the above strings.
3. If you add another scope later, existing scopes will be removed: you need to add the whole list at the same time.
5.4. Office 365 — Permissions
By default, only an individual user has access to his or her OneDrive. Even administrators of the tenant do not have access to users’ OneDrives. Cloudiway takes care of the complex tasks of provisionning OneDrives and setting up permissions.
PreProcessing and Migration use a mix of Graph Apis and CSOM calls.
The migration account must be SharePoint administrator. (in particular to provision the OneDrives and give itself permissions to the OneDrives because the administrator of the tenant can grant themselves permissions to individual drives).
Graph API calls require application permissions on Files.
In particular it requires:
Please follow this KB article to see how you can generate your App ID and App Secret:
6.1. Create your source connector
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, which are configured on apps.cloudiway.com. 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 below to configure your connectors.
6.2. Create your target connector
The Cloudiway platform needs to communicate with both your source and target destinations in order to migrate your data. You have a choice of targets, including Google Drive, OneDrive and SharePoint.
In addition, you can migrate to a mix of both OneDrive account and SharePoint sites. You must set up a target connector for each type of target you wish to migrate to.
Name of the tenant: enter the name of your tenant (ie cloudiwaylab), not cloudiwaylab.com or cloudiwaylab.sharepoint.comFilling this field automatically fills the URL field.
Server Region: Most of the time, keep the default value “Worldwide” except if you have a China, German or US Governmental tenant.
Domain Name: Enter the name of your primary domain.
Migration User: A sharePoint administrator account ( for permissions to run CSOM calls).
User Password: The password of the migration user. This is stored encrypted in EAS 256.
Client ID / Client Secret: Graph API client ID and secrets with permissions to access, groups, users and sites.
See this article for creating the application : https://kb.cloudiway.com/article/azure-apps-registration/
NOTE: Remember, it’s possible to migrate to a mix of both OneDrive accounts and SharePoint sites. If you plan to migrate to both, you will need to create a connector for each target (OneDrive and SharePoint). If, for example, you have two separate SharePoint sites, create a connector for each. Repeat the steps above to create multiple connectors.
6.3. Import or create your users
In order to migrate permissions associated with every file migrated, you can upload your list of users to a mapping table. There are a number of ways to add users to the mapping table. These include:
Regardless, each user will need to be assigned a license type — Trial (limited to 100 MB), Standard, or No License (used for adding users to your mapping table so it’s complete before migration starts). 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.
6.3.1. Option 1: CSV import
If you have a CSV file of all your users, you can upload the file to Cloudiway. The file must have the following fields in the header row:
Note that many browsers limit CSV file uploads to 5000 lines, so files larger than that should be split up and uploaded separately. Data already uploaded will not be overwritten, so you can upload as many files as required.
You might also wish to upload multiple CSV files depending on license type. For example, if some users don’t have a OneDrive but do have files shared with them, you could upload them all within a single CSV file and apply the ‘No license’ option in one go, then upload all OneDrive users and assign the relevant license.
The BatchName field can be left blank. If required, you can use this field to name different batches so they can be run in a certain order. A sample CSV file is available for download during the steps outlined below.
6.3.2. Option 2: Import Users tool
Cloudiway’s Import Users tool helps you to retrieve users from your source tenant. The functionality works via Identity Access Management. The tool requires you to specify any transformation rules you wish to apply. It will then add new users in the File Migration User List view within the Cloudiway platform.
This is an advanced tool that is best used in partnership with Cloudiway consultants. If you are interested in using this option, please get in touch with your Cloudiway contact.
6.3.3. Option 3: Single user creation details
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 get in touch via firstname.lastname@example.org.
6.4. Perform an Audit
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 prior to the general migration because Cloudiway only migrates a file once. Therefore, any folders with alternative targets will take priority.
6.5. Perform Preprocessing
Now that your Cloudiway connectors are set up, 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. When OneDrive is both the source and target, the preprocessing task:
6.6. Choose migration settings
You can choose whether or not to migrate metadata during migration. The following metadata elements can be migrated:
|Created By||Email of the author of the file|
|Created DateTime||Date & time of file creation|
|Modified By||Email of the last user that modified the file|
|Modified DateTime||Date & time of the most recent file edit|
You can also choose whether a file at the target should be kept if a file at the source has an identical name. For example, if menu.docx exists at both the source and target OneDrive, you can choose to discard the file at the target and replace it with the file from the source. If you choose to retain the file, it will be appended with _old, so our example would become menu_old.docx.
This is useful when a user has manually migrated his files manually and started to use them in the target. Without this option, changes in the target would be overwritten by the source
Any files that exist in the target that don’t match file names from the source are always retained.
6.7 Activate and monitor your migration
Now that you have performed all the pre-migration steps within your tenants and within 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 you wish to migrate and click on the 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 of a OneDrive, 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. The platform therefore does not duplicate items in the target.
You can monitor your migration from the dashboard. The Dashboard is available from the Cloudiway File Migration platform. The default screen contains an overview of your migration, including the status of all users, how many files have been migrated, and how many users are left to migrate.
You can click on the Details, Error and Search tabs in the top right corner if you require more detailed information, as well as use the Export option at the bottom of the screen to save your data as a CSV file.
On the Details tab, each user is listed along with the progress of their migration. You can sort the columns to suit your needs, and the columns can be resized.
You can also click on any of the rows to see the log for each migration. Note that the log contains two tabs – Statistics, which is display by default, and Error Items.
The Error tab in the top right corner displays user migrations which might need further attention due to fatal errors or some failures.
The Search tab provides a means for searching for a file based on its name or ID. Partial searches for both are acceptable, and the top five results will be displayed.
Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides and downloads.
Please visit the file migration knowledge base area here:
Please visit the entire knowledge base here (where you can search for keywords or read through topics): http://kb.cloudiway.com/
The knowledge base also contains information on how you can ask for further support, should you require it.