Google Sites and SharePoint Sites are two different systems. Cloudiway Site migration proceeds by equivalence to migrate the different Google elements to SharePoint. This article explains the operation of Google Sites migration.
Once you’ve configured your Site settings on the Cloudiway platform, you can launch the Migrate task. The Migrate task is the mechanism that will dump your data from the source Site and write them to the target SharePoint Site.
During the Migrate task, actions are going to be performed on the source, on the target, and on the Cloudiway platform.
Cloudiway Site migration is read-only to the source: no data is altered.
The Site migration tool will read the specific Google Site to migrate in two ways:
– with a service account
– with an administrator account
A Google service account must be created to enable Google APIs. Google APIs allow access to Google Sites elements like embedded Google Drives, Site Menu, Google Site pages… Nevertheless, all the Sites elements are not accessible nor entirely retrievable by Google APIs (e.g.: list of Google Sites, Site pages, table of content …). To work around this lack, the tool uses an administrator account that will have access to the admin sections of the Google Site.
The retrieved Site elements are stored in a volatile cache that is dumped on the Cloudiway platform.
The volatile cache is loaded to the platform. The platform sorts the Site elements by migration priority. Then these elements are migrated to their SharePoint equivalents. See in section 4 what is migrated and the equivalence to SharePoint.
Site elements contents (e.g.: HTML content, document contents …) are not modified but migrated as such to the target SharePoint.
Once the migration is completed, the cache is deleted, no data is stored on the Cloudiway platform.
Each google Site elements are converted to its SharePoint equivalent.
The migration tool uses the administrator account to write on the target SharePoint.
For some google elements, we migrate directly html contents to SharePoint. As explained in section 2.3, the platform does not modify any of these contents. But any Site migration user must keep in mind that SharePoint may adapt these contents to make them fit its environment.
Google and SharePoint have architectural differences. The following chart shows the difference between Google Sites and SharePoint Sites: hierarchical vs flat organization.
In SharePoint, Sites are hierarchically organized. A SharePoint Sites tenant is a set of Site collections. Each Site collection contains a root Site (the top Site). The top Site may have several subsites which also may have subsites and so on.
Unlike in SharePoint, Google Sites are organized directly in a flat way in the tenant. The notion of subsite does not exist in Google Sites.
The Site can be migrated either to the root Site of a specific SharePoint Site collection or in the first level subsite of a SharePoint Site collection.
Given a Google Site entitled Site1 with Site URL like https://sites.google.com/a/domain/site1. The following table lists the possible migration location with Cloudiway Sites migration.
|Target name||Target collection||Migrate to the root||Migrate to subsite|
*for security reason, Cloudiway platform does not allow to migrate directly to the primary site’s topsite/rootsite (https://company.SharePoint.com)
4.1. To a specific existing Site collection’s root Site: at the top Site
Since Google Sites are flat organized, you can migrate each Google Site in a SharePoint Site collection, at the top Site.
The Site collection’s topsite must be provisioned in SharePoint central administration.
4.2. To a specific existing Site collection’s subsite
All the Google Sites can also be migrated all at once in a Site collection subsites. Cloudiway Site migration tool creates as much SharePoint subsites as the number of Google Sites to migrate.
4.3. To both to remediate your Sites architecture
You may also want to categorize your Sites in SharePoint. Given in source five Sites that are related to the sales department and you want to group them in one Site collection in SharePoint. This is possible with Cloudiway Sites migration. You can totally remediate your Sites architecture as shown in figure 3 below.
Cloudiway Site migration migrates the following Google elements:
5.1. Vertical navigation bar
5.2. Horizontal navigation bar
All permissions are migrated :
– Permissions on users : are mapped to existing users in SharePoint.
– Permissions on groups : are mapped to existing Office 365 groups in SharePoint.
– Permissions on the domain : is mapped to the SharePoint default everyone group in target.
5.4. Site content
Images, formatting, and so on are preserved.
5.5. Welcome Page
The welcome page is the first page displayed when browsing the Site URL. This page is set during migration.
Internal URLs are rewritten during the migration. URLs pointing to internal documents, pages, or lists will point to the target location of the documents, Site pages or list in SharePoint.
5.7. Web pages
A web page is the simplest kind of page. You can write content, embed gadgets, and arrange it however you like. The web page has standard formatting controls like bold, italic, and underline, bullets, and more. You can attach documents from your hard drive to the bottom of the page, and you can let other Site collaborators comment on your pages. Google Sites periodically saves versions of your page as you make ‘Edit’, so it’s easy to go back to earlier versions of the page to make comparisons or undo changes.
Much like a blog, announcement pages display posts you make to the page in chronological order, starting with the most recent. For example, an announcement page would be great for keeping a record of weekly meeting notes, while providing quick access to the most recent meeting info.
5.9. File cabinet
File cabinet pages let you store and organize files from your computer’s hard drive, making it an easy way to share files with other users of your Site. Anyone subscribed to the page will be notified when files are added, changed, or removed.
5.10. List page
List pages let you make and organize lists of information. Items on the list are easy to add, edit, and remove, and viewers of the list can sort it by any column. Like the file cabinet page, subscribers are notified when items are added, changed, or removed.
5.11. Google Gadgets
To easily embed rich media, retrieve feeds, or perform simple tasks like managing a to-do list, you can insert gadgets into your Google Site.
|sites-embed-type-toc||Table of content|
|recent-list-items||Recent List Items|
|recent-files||Recent Updated Files|
5.12. Viewers of documents
Viewers of documents can be displayed inline through wopiframes.
6.1. Hierarchical hierarchy vs flat hierarchy
Google Site has a hierarchical organization of the pages.
Each page can contain subpages and is organized in a tree:
SharePoint stores the page in a flat library.
To avoid page name conflicts, Cloudiway Migration renames the pages in the following way: “mainpage-subpage”
In Google Sites, the depth of menus is unlimited.
In SharePoint, the depth of menus is limited to 2.
Nodes in the menu with a depth hierarchy greater than 2 are not migrated.
As a solution, you might envisage manually removing the default SharePoint QuickLaunch menu and replace it by a webpart text editor.
In this webpart, you can build your menu.
Google menu control can contain text. The SharePoint menus cannot. Text content in the Google Site menu control is lost.
The logo of the Site is not migrated.
Programmatically, this would require to modify the master page of the SharePoint Site.
6.4. Gadgets and Webparts
Google gadgets that do not have webparts equivalents are not migrated.
6.5. Announcement pages attachments
Announcements are migrated to SharePoint discussion board. If there are attachments to the post, since discussion boards do not support attachments, they are not displayed directly in the post. To work around this SharePoint limitations, announcements attachments are migrated in a SharePoint library with the post title.
6.6. Google Drive Files embedded in Google Sites
Google Drive documents can be embedded in Google Sites.
Google Site stores the URL of the Google drive documents embedded in the Site. The URL contains the Google drive ID’s 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 and to give permissions to the migration account.
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. 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 (if the migration account does not have by default access to the files).