In the Preparation phase of a Microsoft SharePoint migration using Transformer, you will prepare for migration by:
- Configuring Settings Templates
- Configuring Value Maps
- (Optional) Configuring Migration of SharePoint Sites to Google Sites
Configuration - Settings Templates
Settings Templates are a persistent set of configured options that can be applied to Bridges to control migration.
Configuration (simple) - Microsoft SharePoint Settings Template
The Default settings template is included with the Transformation Suite and includes the set of recommended options for migrations between Microsoft SharePoint and G Suite environments.
For simple configurations using the Default settings template, you can proceed to the Configuration - Value Maps section. You will choose the Default template during configuration of Bridges.
Configuration - Value Maps
There are three types of Value Maps that can be applied to Bridges migrating Microsoft SharePoint environments: Location Maps, Role Maps, and User Maps.
A header column is not required for Value Maps or Value Lists.
Creating Value Maps
Please see the Value Maps documentation for instructions on how to create or upload a Value Map.
Location Maps transform the locations of objects migrating from a SharePoint environment.
Location Maps determine how source folder hierarchies are directed to user Drive accounts in the target environment. Location maps easily facilitate re-organization of the source folder hierarchy.
Best Practice: Location Maps should be used to direct content to specified Google Drives, as the target account will become the owner of the content. Location Mapping ensures organizational content remains owned, managed and shared by administrators. Location maps can also be used to migrate individual users' local or network drives to their respective Google Drive storage.
Configuration - Location Maps
Location Maps must be configured using the Transformation Suite Location Maps syntax. If you are simply migrating all Apps from your source users to your new target users, your Location Maps must be in the following format:
- In the above example, all content within the Root Folder which is not explicitly mapped will be migrated to, and consequently, be owned by the systemadmin's Drive account.
- The second string ensures that the Marketing subfolder will be directed to the marketingadmin Drive account, and will not appear in the systemadmin's Drive.
- The third and fourth strings map user1 and user2's personal drives from the source to their respective Drive accounts, with user2 choosing a specific folder within their Drive account to direct their source Drive content to.
User Maps transform user and group references within objects migrating between Microsoft SharePoint and G Suite environments.
User Maps facilitate the transformation of sharing rights assigned to users / groups, creation and modification metadata, and other references that include a username.
Best Practice: User Maps should be used when migrating between Microsoft SharePoint and G Suite environments, as sharing rights and metadata cannot be migrated without them.
Configuration - User Maps
User Maps used by migrations for Microsoft SharePoint environments must be in the following format:
URL Maps transform URL references found in pages migrating between Microsoft SharePoint and G Suite environments.
Best Practice: URL Maps can be used when migrating between Microsoft SharePoint Site Pages and Google Sites Pages, as they are required to correct references that the Transformation Suite cannot automatically resolve.
Configuration - URL Maps
URL Maps used by migrations for Microsoft SharePoint environments can be any URL with valid syntax:
Configuration - Migrating SharePoint Sites to Google Sites
The Transformation Suite provides the ability to migrate SharePoint site pages into Google Sites. Files and folders from SharePoint will be migrated into Google Drive, and web parts in SharePoint that provided a window into the content will be transformed and migrated as Google Sites Gadgets.
If you have already configured a SharePoint to Google Drive migration, you can enable SharePoint site page migration by enabling the option "Create Google Site Page Hierarchy to Mirror SharePoint Web Hierarchy" within the selected Settings Template. If you are using the Default Settings Template, you will be prompted to save a new Settings Template.
The "Create Google Site Page Hierarchy to Mirror SharePoint Web Hierarchy" option is disabled by default, as it is important to understand that it will automatically provision Google Sites before enabling it.
Once the option is enabled, a Location Map must be configured that maps the webs/sites that you wish to copy to the target users in G Suite.
Note: You must create a Location Map that maps the webs/sites that you wish to copy to the Drive Service of the target users. If you map them to sub-folders within Drive, the feature will not work. For example:
Migrating SharePoint Site Page Content
The Transformation Suite can migrate the three types of SharePoint pages. Each type of page has special considerations involved during migration:
|SharePoint Page||Description||Transformation Result|
|Publishing Page||A page in SharePoint that contains HTML content zones and Web Parts.|
|Wiki Home Page||A page in SharePoint that contains HTML content zones and Web Parts. Includes special wiki formatting.|
|Standard Home Page||A page in SharePoint that contains Web Part Zones and Web Parts. A SharePoint Team Site landing page is an example of a Standard Home Page.|
Migrating SharePoint Web Parts
The following SharePoint Web Parts can be transformed and migrated to Google Sites elements and gadgets by the Transformation Suite:
|Web Part||Google Sites Element|
|Content Editor Web Part||HTML content within the Google Sites Page.|
|ListView Web Part||Google Sites Folder Gadget - Displays the Google Drive folder that was created from the migrated SharePoint list|
|Image Viewer Web Part||<Img> tag in the Google Sites Page with the Web Part title migrated into a <div> element above it.|
The Transformation Suite will discover and attempt to correct URLs in HTML page content, <href> attributes, and <src> attributes within SharePoint Site Pages being migrated.
URL Maps can be used to define link correction mappings for the migration.
The Transformation Suite can preserve the permissions present on the source SharePoint Site. User Maps must be used to transform users from the source environment to the target.
Due to Google Sites API limitations, the Transformation Suite can only preserve the permissions at the root level of the Google Sites hierarchy; sub-Pages will inherit permissions from the root.
The Transformation Suite can map themes between SharePoint Pages and Google Sites. Google Sites theme settings can only be configured at the root of the Site, so it is possible only to map a single theme per Site.
Pages without a theme in SharePoint can be mapped to a new Google Sites theme by using the value "Default" for the source.