Google Sites Migration FAQ
Which Google Site versions are supported?
There are three types of Google sites. These are listed below, along with explanatory text and the expected migration results.
- Legacy sites.
- Not supported.
- Explanation: These are sites that were created many years ago. The current Google Sites REST API is unable to access these legacy sites, and thus they cannot be migrated using MigrationWiz.
- Migration result: If a migration attempt is made, no sites will discovered, and an error message will be returned. The error will state: "No sites are under this domain."
- Explanation: The existing Google Sites REST API only works with the sites created prior to Nov. 2016.
- Migration result: Google calls these "Classic Sites", and they are fully supported for migration.
- Not supported.
- Explanation: Any site created after Nov. 2016 is automatically considered to be a New site. The existing Google API does not work properly with a New site, and so New Sites are not supported for migration.
- Migration result: If a migration attempt is made, the file cabinets within the Site will become anonymous, so there will not be an ID/Name to use to retrieve the file folder via the Google API.
Is there an audit feature (or other means) that informs users about the composition of the Source Google site and that reports the items that will and will not migrate?
There is no pre migration assessment tool available for Google Sites. Post migration, users can turn on the Audit Logging feature to get detailed reports on what the migration has done, but this is after the fact. Additionally, our GUI-based reporting will list all files that failed to migrate. These can be reviewed by clicking on the line item within your MigrationWiz project dashboard, and then reviewing the items listed under the section labeled: Migration Errors.
Is it possible to migrate from Google Sites to SharePoint where the Source has more than two levels of hierarchy? And if so, is custom navigation added?
Google Sites migration does not interact with or construct navigation links. Rather, it simply deposits migrated items into the selected SharePoint site library. The migration tool maintains the directory structure to whatever level they were at the Source, but the customer is expected to build out the site.
Is there a way to migrate Google Groups to Office 365 Groups using Google Sites Migration?
No. This is not part of the migration scope.
Is Google Sites Migration to SharePoint Online available for purchase now?
Yes. You can obtain the appropriate licenses by contacting the BitTitan sales team at Sales@BitTitan.com. For more information about licenses, see the Knowledge Base article How Do I Purchase Google Site Migration Licenses?
Are evaluation licenses available for migration testing?
Yes. Our sales team can provide you with evaluation licenses to test your migrations. Contact the BitTitan sales team at Sales@BitTitan.com. For more information about Google Sites Migration, see the Knowledge Base article Google Sites to SharePoint Online Migration Guide.
Which types of Google Sites content can be migrated to SharePoint using Google Sites Migration?
Migrating content from Google Sites to SharePoint Online works only for Google files that are in file cabinet containers.
Is it possible to migrate files that are hosted on Google Drive, but published on a Google Site, to a SharePoint document library?
It is possible to migrate these to SharePoint so long as the files on the Google Site are in a Google file cabinet.
Note: Only Google Sites files that are in a Google file cabinet library can be migrated using Google Sites Migration.
Can Google Sites Migration migrate widgets?
No. These are not supported.
Can Google Sites Migration migrate user permissions?
Yes. Google Sites Migration migrates both documents and permissions. However, users associated with permissions must already exist on the Destination prior to starting the migration, or the migration will fail.