Google Drive documents can be embedded in Google Sites.
This document explains how Cloudiway proceeds to migrate those sites and explains the prerequisites.
What is the problem?
Google Site stores the URL of the Google Drive documents embedded in the site.
The URL contains the Google Drive IDs but does not provide any information about the owner.
All we get is the Google Drive ID of each document and from it, it’s not possible to determine the owner or to give permissions to the migration account.
This is the typical error message that you get in the logs:
What is the solution:
Use Cloudiway Site Migration and Cloudiway File Migration together.
During the migration or the audit of the Google Drives (Cloudiway File Migration), Cloudiway platform builds a list of all Google Drive IDs and their respective owners.
From it, Google Site migration is able to determine the owner of each embedded Drive document. The platform can now impersonate the owner and access the document.
Please note that using the File Migration tool will require File migration licenses in extra.
Prerequisites & Process:
- Get standard File migration licenses for each user
- Go to File migration
- Create the users in the File User List
- Run the audit of all Google Drives
- Go to Site migration
- Migrate the Google Sites
- Migrate the Google Drives
Cloudiway migration tool will not duplicate the files: it will not migrate files to both OneDrive and SharePoint. The file will be migrated to the first place. If you migrate the Google sites first, it will be migrated to the SharePoint site and this file will be ignored during the Google Drive migration. On the other side, if you decide to migrate the Google Drives first, the file will be migrated to the OneDrive and ignored during the Google site migration.
If you do not use Cloudiway Site Migration and Cloudiway File Migration together, the Google Drive documents embedded in Google Sites will not be migrated.