Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.2.3 - User Guide

Metalogix Essentials for Office 365 User Guide
Administrator Architect Backup
Interface Overview Common Functions
Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Hyper Backup Creating a Full Backup Creating an Update Backup Creating an Exchange Online Mailbox Backup Creating an Office 365 Group Backup Creating a OneDrive for Business Backup Backup Resume Backup Search Restore from Backup Scheduling Backup Jobs Import/Export Backup Archives Moving the Backup Location Backup Project Conversion
Drives
Interface Overview Common Functions
Connecting to Drives Copy Google Drives to OneDrive for Business Copy Google Drive to an Office 365 Group Copy Google Drive to Microsoft Teams Copy File Shares to OneDrive for Business Copy File Shares to SharePoint Online Copy File Shares to an Office 365 Group Copy File Share to Microsoft Teams Copy My Sites to OneDrive for Business Copy OneDrive for Business to OneDrive for Business Copy Box to OneDrive for Business Copy Box to SharePoint Online Copy Box to an Office 365 Group Copy Box to Microsoft Teams Copy Dropbox Business to OneDrive for Business Copy Dropbox to an Office 365 Group Copy Dropbox to Microsoft Teams OneDrive Management Progress Tab Hyper Migration Path Length Overflow
File Manager Informant Migrator
Interface Common Functions
Connect to SharePoint and OneDrive for Business Copy Sites Live Compare Copy Lists and Libraries Copy, Move, and Tag SharePoint Content Copy Alerts Pre-Migration Analysis Azure Turbo Mode In-Place Tagging of SharePoint Items Incremental Copy Nintex Workflow Migration Orphaned Users Copy Preserving Content Authorship and Approve/Reject Statuses Reprocess Failed Items Save Site to XML Using Scripts and Integration With Windows Task Scheduler
Profile and Global Variables Public Folders for SharePoint Reporting and Re-Mapping Users and Templates Security Manager Term Store Manager Scripts Wizards Appendix

Unsupported Objects for Migrating Google Drive to Office 365

The following Google Drive objects and scenarios are not supported when migrating to OneDrive for Business.

·Content scenarios

oContent within or shared from a user account which is currently in a "Suspended" state.

oContent that is linked, synchronized or referenced in a second or more Google Drive folders will be copied as individual, discrete files to each of their respective locations in OneDrive for Business.  Their linked, synchronized or referenced configuration from Google will not be maintained and duplicate files may therefore be created in OneDrive for Business.

§To prevent duplicate files from being created, the option "Include First Reference File Only" has been added. When this option is enabled only the first returned reference of these linked files will be migrated.  All other references will be skipped and an appropriate message will be added to the log file as shown below:

"Skipped copying /GoogleDriveObjectPath because it is another reference object to a file and the option to include only the first reference was selected."

oDocuments within a user's Google Drive that are owned by this user, but are not "Shared From" this user (this is related to the prior use of Google's "Transfer Ownership" function) will be skipped.  This logic applies to documents only, folders will still be migrated.

·Folder colors

·Google Forms

·Google My Maps and other connected Apps

·Google Photos

·Inline file comments (November 11, 2016 update: inline file comments now supported for Google Docs, Sheets and Slides only)

·"Link sharing" settings are not retained

oThe two link sharing options listed below will not be retained due to native OneDrive for Business permissions.

§Anyone with the link

§Anyone at MyCompany with the link

The following error message will appear in the log when file with either of those link sharing are processed:

"Google "with the link" sharing was not processed on object /objectPath, and should therefore be manually recreated post migration."

·Objects in the "Trash"

·Shared Permissions (Google Drive to Office 365 Group Sites only)

·Shared Permissions or meta-data associated with external users will not be retained.

·Starred or Favorite label on content

oThe item can be migrated, however this label is not retained.

Copy Google Drive to Microsoft Teams

This option allows administrators to move content from multiple Google Drives to Microsoft Teams in a single operation.

info

NOTE: If you have not already performed the prerequisite steps in Google, please go to this section first.  Once the prerequisite configuration is complete, return here to continue with the migration.

This operation has the following requirements for use:

·The Google Drive pre-requisites must be configured successfully prior to the migration.

·The account used to perform the migration into Microsoft Teams needs to be a Global Administrator in this Office 365 tenant.

·The person performing the migration will need to know the relationship (user mapping) between each source Google Drive account and their corresponding Microsoft Teams group name and Office 365 user account.

·The Microsoft Team Group must already exist.

To migrate the content of multiple Google Drives to Microsoft Team Groups, perform the following:

1.On the Drives tab click Copy Google Drive and select "Copy Google Drive to Microsoft Teams".
copy google to microsoft teams01
The Google Drives to Microsoft Teams Migrator wizard opens.

2.Select a Profile and provide your Google Admin login, P12 Key File and Service Account in the Google connection parameters area. This information is gathered directly from your Google environment, so if you have not already please refer to this section for the required steps.  Once the values are entered, click Connect.  If you receive any message other than Successfully connected to Google Drive, double check the prerequisite steps and then entered values.  If you are still experiencing issues, please contact Support for assistance.
copy google to microsoft teams02

3.Specify your tenant SharePoint Administration Center URL​ and then click Connect.  When prompted, enter your Office 365 Global Administrator login and password. Click Connect. If you receive any message other than Successfully connected to SharePoint Admin URL, double check the URL and make sure you are supplying a Global Administrator login for this tenant.  If you are still experiencing issues, please contact Support for further assistance.
copy google to microsoft teams03

4.Click Load from Google to load a list of available Google Drive accounts from your environment.

info

NOTE: For a large number of Google Drives (>1000), the Load from Google option may take several minutes to complete.

copy google to microsoft teams04

5.S​elect the Google Drive accounts that you wish to include with this migration and click Next to continue.

6.Check the Re-Map Users option and load your Group mapping CSV file (Please see this section for instructions on how to create a CSV Group Mapping file for Google Drive to Microsoft Teams, user mapping may also be included in this CSV)
copy google to microsoft teams05
The CSV for Group mapping is required so that the software can properly resolve the differences between your users' Google account and the corresponding Microsoft Teams Group name as well as maintain content authorship.  If your user accounts differ between Google Drive and Microsoft Teams then you will want to add your user mapping to this same file.  In the example below, lines 1-3 illustrate mapping a source Google Drive to an Microsoft Teams Group by name while lines 4-5 in the same file are used to map the Google user accounts to their respective Office 365 user accounts to maintain item authorship.
 
sales@company.com,MicrosoftTeams Group Name
marketing@company.com,MicrosoftTeams MarketingGroup
IT@company.com,IT Group
scott@company.com,swilson@contoso.com
bill@company.com,bgeorge@contoso.com
 
If you wish to migrate one or more source accounts to a single Group library while also remapping the user account for the purpose of metadata and sharing, please use the following format in your mapping file.
 
user@google.com,MicrosoftTeamsGroupName(user@contoso.com)
 
The software will migrate the content from the source drive "user@google.com" to the Documents library in the group "MicrosoftTeamsGroupName".  The metadata and shared permissions of Google user "user@google.com" will be mapped to the Office 365 user account "user@contoso.com".

7.Click Check MS Team in order to begin the validation process​. This process will validate that the supplied user mapping is correct (Office 365 Groups were located) and check to determine if each Group currently has a Site provisioned.  Click Next.
copy google to microsoft teams06
If the group is not found, you may continue however no content for this mapping will be migrated.  Alternatively, you may go back one page and remove the selected source Google Drive or modify your mapping file, reload the CSV and click the Check MS Team button again.

8.If necessary, change content and file format conversion options as described below.
 
Content Options
copy google to microsoft teams9

Copy Content - A flag to determine if content is or is not included with this operation.  When not included the remainder of the options will become disabled.

Include Versions - The process in which Google revision history will be converted into Microsoft Teams versions.  Please note that this option is only referring to the major revisions (those shown as the "less detailed revisions") and not those that are automatically generated within Google Drives (those shown as the "more detailed" revisions).

Incremental Copy - When enabled, the migration process will identify and migrate only that content which was created, modified or versioned within the defined interval (days, weeks or months).
 
Skip files greater than - This provides the functionality to skip all files larger than the value specified.  Unit of measure is configured for MB or GB.
 
Migrate to folder - When this option is enabled, you can create a (or use an existing) root folder structure in the destination library where your source content will be migrated. You will need to define the path like this example:

/My Source Content/2017

In the above example, the folder "My Source Content" and subfolder "2017" will be created in the root library of your destination and all source content will be migrated to this folder location.

Skipped Non-Owned Objects - This addresses the possible scenario where content exists in the user's Google Drive "My Drive" area which is not owned by this user.  Skipping these objects will prevent duplicate content from being migrated to the destination.

Include First Reference File Only - This option addresses the possible scenario where a user creates reference objects (links using Shift + Z in Google Drive) of a file in various locations throughout their Google Drive environment.  Skipping these additional references will prevent duplicate files from being migrated to the destination by migrating only the first reference found.  Please note that the "first" reference is defined by a list of parent folders returned from Google Drive and the first may not always be the same one on subsequent or incremental migrations.  Please also note this option is only applicable to files, all referenced folders will be copied.

Include Orphaned Files - For the purpose of this option, an orphaned file is defined as a file that was created in a folder that was shared with this user and after the file was created, their permission to the shared folder was removed.  The file still exists in the user's Google Drive, however it does not reside in any visible folder path and can only be located using the Google Drive Search Bar.  When this option is enabled, the migration will identify these orphaned files and migrate them to the mapped Office 365 Group Site's Documents library.  In this library, a new folder named "Orphaned Files" will be created which will contain all the migrated orphaned files.

info

NOTE: The use of this option can decrease overall migration performance.

Apply Filter - Optionally, select from a series of filterable parameters to include or exclude specific content during migration.

Format Conversion:
Copy Google to OneDrive8

This set of options allows you to determine how Google formatted content will be converted into Microsoft compatible content.

Advanced Options:
Copy Google to OneDrive9

Enable Azure Turbo Mode - When enabled, this option utilizes Microsoft's SharePoint Online Migration API to increase the migration performance and throughput. A recommendation for optimal use of this API is larger sets of data; the more content, the better the throughput. Because this API uses Azure storage as a staging area for the migration, it requires that you provide an Azure storage location. The options are to either utilize Microsoft supplied storage or to provide your own Azure storage location. If you wish to use your own Azure account, you must provide both the Azure Account Name as well as the corresponding Access Key. If you cannot supply this information, please search our online Knowledge Base, User Manual, or contact Support for additional information before proceeding or consider using the Microsoft Supplied Storage option. For more information please see the Azure Turbo Mode section.

Create User Specific Log File - If you would like a user specific log file (.txt format) created for each migrated Google Drive, that will be saved directly to that Group's "Documents" library, check this option before you finish.  This log file will contain all the content that was included in the migration with both source and target URLs as well as any file renaming that took place and skipped files due to lack of ownership.

info

NOTE: Content permissions are not migrated because Office 365 Group permissions are maintained and enforced by the group membership and its roles (Owners, Members and Guests).

9.Click Finish to begin the migration process.

Please visit the following link to view the list of unsupported Google Drive objects.

Please visit the following link for an overview on how to script and schedule jobs such as Copying Google Drive to Microsoft Teams.

Copy File Shares to OneDrive for Business

When licensed, Metalogix Essentials File Manager provides the ability to bulk upload user's networked file system drives into their respective OneDrive for Business Document library in your Office 365 tenant.  This operation has the following requirements for use:

·The account used to perform the upload needs to have access and at least Read permissions from this computer to all the user's networked file system drives.

·The account used to perform the upload needs to be a Global Administrator in this Office 365 tenant.

·The person performing the upload will need to know the relationship (mapping) between each user's networked file system drive and their corresponding Office 365 user account.

·Each user account must have either a SharePoint or OneDrive license assigned to it in Office 365.

Once the requirements above are satisfied, you can proceed with utilizing the bulk upload functionality.

1.To access the wizard, first switch to the Drives tab in the Essentials for Office 365 application.

2.Click the "Copy File Shares" button and select Copy file Shares to OneDrive. This will open the wizard.
Copy FileShare to OneDrive01

3.Enter the URL to the SharePoint Admin Center in your Office 365 tenant.  Click the Connect button and then enter the Username and Password of your Global Administrator to authenticate.  The SharePoint Admin Center URL will look similar to this: https://YourTenant-admin.sharepoint.com
Copy FileShare to OneDrive2

4.In the Map File System to Users section, load the CSV file that maps the relationship between the networked file system drives and the corresponding Office 365 user account.  During upload all the content, files, and sub-folders (if configured), will be migrated from within the root of this network path and uploaded into the user's OneDrive for Business "Documents" library.

info

NOTE: Click here to download an example mapping file.

5.After the mapping file is loaded, click the Check for Users Personal Sites button to run a validation test.  This option is designed to validate the existence of the mapped user in Office 365 and also to check for the availability of each user's OneDrive for Business.
Copy FileShare to OneDrive3
The following results can be displayed in the "OneDrive Exists" column:

·Yes - The user account has been found in this Office 365 Tenant and this user's OneDrive for Business has already been provisioned.

·No - The user account has been found in this Office 365 Tenant, but this user's OneDrive for Business has not yet been provisioned.

·Invalid User - The user account was not found in this Office 365 Tenant and therefore cannot be included with this operation as currently mapped.

6.After the validation process, select all the valid users from the list which you wish to include in this operation and click Next to continue.

7.On the following page of the wizard, you are presented with a few choices dealing with the content that is to be uploaded.  Select the options required, as described below.
Copy FileShare to OneDrive4

Include sub-folders:  When enabled this will include the content (files and folders) within all the root folders.  When disabled, only the root level content (files and folders) of this location will be included.

Overwrite if files exist:  If a file of the same name already exists in the OneDrive's Documents library, this option will overwrite that file with the current one from the file system.

Incremental Copy:  There are multiple scenarios where an ability to re-copy changes (from the source environment to the target) rather than re-copying all the content is preferable and necessary.  This function allows user's to continue working on their networked drives or in their OneDrives while the migration is performed and then at a later date, the tool can be used to identify and migrate newly created or modified content.  Incremental Copy uses a 'Last <N> Days/Weeks/Months' method to identify and migrate this content starting at the time of execution.  Click here for additional information about Incremental Copy.

Copy Permissions: This setting copies NTFS File System folder permissions when copying file system content to SharePoint libraries or when importing files from the file system using CSV Spreadsheet for metadata.

Remove Folder Structure:  Provides the ability to exclude folders and include only their content, from the upload process.

Migrate to Folder: When this option is enabled, you can create a (or use an existing) root folder structure in the destination library where your source content will be migrated. You will need to define the path like this example:

/My Source Content/2017

In the above example, the folder "My Source Content" and subfolder "2017" will be created in the root library of your destination and all source content will be migrated to this folder location.

Apply Filter:  Creates and assign any number of filter parameters to be used to include or exclude content from the upload process, including but not limited to file extensions, size and dates.

Re-map Users:  If the user accounts within your local file system differ from those in Office 365, this option provides the ability to map the differences so the tool can properly retain the Created/Modified By authorship information and permissions.  Please note that source file shares account are read in the following format and this should be used when creating your user mapping file. domain\user01,user01@contoso.com.  You should also add any necessary Groups to this mapping file too. domain\ADMarketingGroup,Marketing

Enable Azure Turbo Mode: When enabled, this option utilizes Microsoft's SharePoint Online Migration API to increase the migration performance and throughput. A recommendation for optimal use of this API is larger sets of data; the more content, the better the throughput. Please review the User Manual for additional information as well as recommended configuration as this process is a resource intensive operation.

Because this API uses Azure storage as a staging area for the migration, it requires that you provide an Azure storage location. The options are to either utilize Microsoft supplied storage or to provide your own Azure storage location. If you wish to use your own Azure account, you must provide both the Azure Account Name as well as the corresponding Acces Key. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding or consider using the Microsoft Supplied Storage option. For more information please see the Azure Turbo Mode section.

info

NOTE: this function is optional and is only used to increase the migration performance to SharePoint Online or OneDrive for Business in Office 365. It does not provide any additional functionality that is not available when this option is disabled.

·Microsoft Provided Storage: This option allows you to use Microsoft provided Azure storage instead of providing your own for the purpose of utilizing Azure Turbo Mode.

info

NOTE: the migration end result will not differ regardless of your selection between Microsoft or User provided storage.

·User Provided Storage: This option allows you to provide your own Azure Storage instead of using one provided by Microsoft for the purpose of utilizing Azure Turbo Mode. It requires that you provide both your Azure Blob Storage Account Name as well as its corresponding Access Key by clicking the "Select" button to the right. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding. Note:

info

NOTE: that the migration end result will not differ regardless of your selection between Microsoft or User provided storage.

oDefer Upload to Azure: When enabled, this option does not upload and immediately queue the import process from Azure storage, but rather saves the packages to a file location to then be uploaded and imported at a later time. This will allow you to use another application (at any time) to upload the content to Azure.

§To make use of the Deferred Upload option, the following process takes place:

1.First, you should setup the operation as usual using the Azure Turbo option.

2.Then, check the Defer Upload to Azure option and then Select the location where you wish to store the packages. Please be sure that there is enough disk space to accommodate all the packages that will be created.

3.During this process, the packages will be created, saved to this location and empty containers will also be created in your Azure storage.

4.After the operation completes, you will need to upload (using whichever upload utility you choose) the contents of each local folder into the appropriate Azure container. The folder names created in your local file location will be named exactly the same as the containers in Azure.

5.Once all the content from each folder is uploaded to the appropriate container in Azure storage, open the Azure Turbo Queue and choose the Refresh option.

6.Select one or more of the "Pending" jobs, right click and choose Process. The Import process has now begun and the jobs should soon switch to the status Queued.

8.Click Finish to begin the migration.

Copy File Shares to SharePoint Online

This option allows Local and Office 365 administrators to migrate folders (and their subfolders and files) from within multiple local files shares or network drives to one or more document libraries in a SharePoint Online Site Collection.

This operation has the following requirements for use:

·The account used to perform the migration from the File Shares needs to have at least Read permissions to every object in the source path.

·The account used to perform the migration into SharePoint Online needs to have at minimuim Designer permissions to the destination Site Collection.  Full Control or Site Collection Administrator are recommended to avoid potential permission related issues during migration.

·The person performing the migration will need to know the relationship (user mapping) between each user's local user account and their corresponding Office 365 user account.

·The destination sites and libraries must exist in SharePoint Online prior to migration.

Once the requirements above are satisified, you can proceed with your File Share to SharePoint Online migration.

1.To access the wizard, first switch to the Drives tab in the Essentials for Office 365 application.

2.Click the "Copy File Shares" drop down and then select the Copy File Shares to SharePoint option. This will open the wizard.
Copy FileShare to sharepoint01

3.Enter the URL for the SharePoint Site you wish to copy your File Share to. Click the Connect button. If prompted, enter the Username and Password credentials for the SharePoint site.spsadmin.
copy fileshare to sharepoint2

4.Load the Map file share to sharepoint CSV file. This option is required in order to map which folders from your local or network drives are migrated into which specific document library in your SharePoint Online site(s).  Create and load a CSV formatted to include the following 4 headers and is specific to a single target SharePoint Online root location as defined in the SharePoint Site field above.

info

NOTE: When connecting to a SharePoint Online Site in this step, please be aware that you may migrate content into any library within this site or any sub-site beneath it. If you want to migrate content to a different site collection, then you will need to configure a second migration.

·Source Path - This column defines the path to the root folder (including all its child content) from the local or network drive that you wish to migrate.

·Target SharePoint Site - This column defines the site or sub-site you wish to use as your destination location.  If you want to migrate to the root site as defined in the SharePoint Site URL, then simply enter a forward slash (/) in this column.  If you wish to migrate to a sub-site of the root, then enter the relative path to your sub-site starting at the root level (i.e.  /subsite1/subsite2).  Please note that each defined target site or sub-site must already exist in SharePoint Online as this process will not create this new site.  This will then result in an error during migration.

·Target SharePoint List - This column defines the document library you wish to use as your destination list.  Please enter the library's Display Name into this column.  Please note that each defined target library must already exist in SharePoint Online as this process will not create this new library.  This will then result in an error during migration.

·Target folder path - This column defines the folder that you would like to use as your destination location.  If you want to migrate to the root of the library defined in the Target SharePoint List column, then simply enter a forward slash (/) in this column.  If you wish to migrate to a sub-folder of the root, then enter the relative path to your sub-folder starting at the root level (i.e.  /folder1/folder2).

info

NOTE: A sample CSV file can be downloaded from here and used as an example template.  Please do not modify the first row (headers) of the CSV file, but do modify the remaining values starting in the second row to meet your needs.

5.Once you have Loaded a CSV file, the table in the wizard will be populated. you must select at least one row in the table to copy over in order to be able to select Next and move forward in the wizard.
copy fileshare to sharepoint3
 

6.On the following page of the wizard, you are presented with a few choices dealing with the content that is to be uploaded.  Select the options required, as described below.

Content Options:
copy fileshare to sharepoint5

Overwrite if file exists - If the content already exists in the destination location, this option determines whether the operation will overwrite this content in the destination or to skip it.

Incremental Copy - When enabled, the migration process will identify and migrate only that content which was created or modified within the defined interval (days, weeks or months).

Copy Permissions - Enable this option to include NTFS permissions with this operation.

Defer Required Fields - Content will be uploaded/copied even if required fields are left empty.

Apply Filter - Optionally, select from a series of filterable parameters to include or exclude specific content during migration.

Re-Map Users - If necessary, create and load a user mapping file to be used for both permissions and metadata.  User accounts as well as domain groups should be included in this CSV mapping file.

Skip files greater than - This provides the functionality to skip all files larger than the value specified.  Unit of measure is configured for MB or GB.
 
Advanced Options:
copy fileshare to sharepoint6
 

Enable Azure Turbo Mode: When enabled, this option utilizes Microsoft's SharePoint Online Migration API to increase the migration performance and throughput. A recommendation for optimal use of this API is larger sets of data; the more content, the better the throughput. Please review the User Manual for additional information as well as recommended configuration as this process is a resource intensive operation.

Because this API uses Azure storage as a staging area for the migration, it requires that you provide an Azure storage location. The options are to either utilize Microsoft supplied storage or to provide your own Azure storage location. If you wish to use your own Azure account, you must provide both the Azure Account Name as well as the corresponding Acces Key. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding or consider using the Microsoft Supplied Storage option. For more information please see the Azure Turbo Mode section.

info

NOTE: this function is optional and is only used to increase the migration performance to SharePoint Online or OneDrive for Business in Office 365. It does not provide any additional functionality that is not available when this option is disabled.

·Microsoft Provided Storage: This option allows you to use Microsoft provided Azure storage instead of providing your own for the purpose of utilizing Azure Turbo Mode.

info

NOTE: the migration end result will not differ regardless of your selection between Microsoft or User provided storage.

·User Provided Storage: This option allows you to provide your own Azure Storage instead of using one provided by Microsoft for the purpose of utilizing Azure Turbo Mode. It requires that you provide both your Azure Blob Storage Account Name as well as its corresponding Access Key by clicking the "Select" button to the right. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding.

info

NOTE: that the migration end result will not differ regardless of your selection between Microsoft or User provided storage.

·Defer Upload to Azure: When enabled, this option does not upload and immediately queue the import process from Azure storage, but rather saves the packages to a file location to then be uploaded and imported at a later time. This will allow you to use another application (at any time) to upload the content to Azure.

§To make use of the Deferred Upload option, the following process takes place:

1.First, you should setup the operation as usual using the Azure Turbo option.

2.Then, check the Defer Upload to Azure option and then Select the location where you wish to store the packages. Please be sure that there is enough disk space to accommodate all the packages that will be created.

3.During this process, the packages will be created, saved to this location and empty containers will also be created in your Azure storage.

4.After the operation completes, you will need to upload (using whichever upload utility you choose) the contents of each local folder into the appropriate Azure container. The folder names created in your local file location will be named exactly the same as the containers in Azure.

5.Once all the content from each folder is uploaded to the appropriate container in Azure storage, open the Azure Turbo Queue and choose the Refresh option.

6.Select one or more of the "Pending" jobs, right click and choose Process. The Import process has now begun and the jobs should soon switch to the status Queued.

7.Click Finish to begin the migration.

Related Documents