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

Copy File Shares to an Office 365 Group

This option provides the ability to bulk upload networked file system content into an Office 365 Group Site's Documents library.  

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 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 networked file system path and the corresponding Office 365 Group Name.

·The Office 365 Group and its Site must already exist.

Once the requirements above are satisfied, you can proceed with your File Share to Office 365 Group Site migration.

1.Switch to the Drives tab and click the Copy File Share dropdown and then the "Copy File Shares to Office 365 Group" migration button.
Copy FileShare to office01

2.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 Office2

3.In the Map File System to Groups section, load the file that maps the relationship between the networked file system drives and the corresponding Office 365 Group Name.  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 Office 365 Group Site's "Documents" library.
Click here to download an example mapping file.
copy fileshare to microsoft teams03

4.After the mapping file is loaded, click the Check for Office 365 Groups 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 Office 365 Group and its Site.
copy fileshare to microsoft teams004

The following results can be displayed in the "Group Site Exists" column:

·Yes - The Group has been found in this Office 365 Tenant and this Group's Site has already been provisioned.

·No - The Group has been found in this Office 365 Tenant, but this Group's Site has not yet been provisioned.

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

After the validation process, select from the all the valid mappings from the list to include in this operation and click Next to continue.

5.If required, modify your Content Option settings​ as described below.
copy fileshare to Office3

Include sub-folders - When enabled, this option will include the root folder and all sub-folders in the defined source path.  When disabled, only the root folder will be included in the migration.

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).

Remove Folder Structure - Enable this option to exclude all source folder structure.  All folder content will be migrated into the destination location without their parent folders.

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 - 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.

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. 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: 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.

6.Click Finish to begin the migration.

Copy File Share to Microsoft Teams

This option provides the ability to bulk upload networked file system content into an Microsoft Team File Library.  

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 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 networked file system path and the corresponding Microsoft Teams Name.

·The Microsoft Team must already exist.

Once the requirements above are satisfied, you can proceed with your File Share to Office 365 Group Site migration.

1.Switch to the Drives tab and click the Copy File Share dropdown and then the "Copy File Shares to Microsoft Teams" migration button.
copy fileshare to microsoft teams01

2.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 microsoft teams02

3.In the Map File System to Groups section, load the file that maps the relationship between the networked file system drives and the corresponding Microsoft Teams.  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 Microsoft Teams channel.
Click here to download an example mapping file.
copy fileshare to microsoft teams03

4.After the mapping file is loaded, click the Check for Microsoft Teams button to run a validation test.  This option is designed to validate the existence of the mapped user in Microsoft Teams and also to check for the availability of each Team.
copy fileshare to microsoft teams004

The following results can be displayed in the "MS Team Exists" column:

·Yes - The Group has been found in this Office 365 Tenant and this Group's Site has already been provisioned.

·No - The Group has been found in this Office 365 Tenant, but this Group's Site has not yet been provisioned.

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

After the validation process, select from the all the valid mappings from the list to include in this operation and click Next to continue.

5.If required, modify your Content Option settings as described below.
copy fileshare to Office3

Include sub-folders - When enabled, this option will include the root folder and all sub-folders in the defined source path.  When disabled, only the root folder will be included in the migration.

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).

Remove Folder Structure - Enable this option to exclude all source folder structure.  All folder content will be migrated into the destination location without their parent folders.

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 - 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.

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.

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.

6.Click Finish to begin the migration.

Copy My Sites to OneDrive for Business

A simple, Administrator driven wizard is provided to bulk migrate the lists and content from legacy on-premise SharePoint My Sites to OneDrive for Business sites in Office 365.  In order to successfully configure and run this operation, you will need to be able to authenticate against the on-premise Central Admin page with a Farm Admin account (full control to all My Sites) as well as a Global Administrator in the Office 365 tenant.  A mapping file may also be needed in order to resolve the user accounts between the source and destination locations.

This operation has the following requirements for use:

·The account used to perform the migration needs to have at least Owner permissions to each users' My Site.

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

·The person performing the migration will need to know the relationship (mapping) between each user's My Site account 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.Switch to the Drives tab in Essentials for Office 365 and click the button Copy My Sites to OneDrive, located in the ribbon.
copy mysites to onedrive1

2.When the wizard appears, begin by entering the SharePoint Admin URL - This will be the URL to the on-premise SharePoint Central Admin page that hosts the My Sites.  Once the URL is entered, click the Connect button, enter a valid Farm Admin account and click Connect.  When you receive a successful connection message proceed to the next parameter.
copy mysites to onedrive2

3.Enter the URL for the SharePoint Admin Center in Office 365.  Once the URL is entered, click the Connect button, enter a valid Global Admin account and click Connect. Note: that the Claims option is not supported for this operation. When you receive a successful connection message proceed to the next step.
copy mysites to onedrive3

4.Click the Load from SharePoint button.  This step will connect to your source Farm and retrieve a list of available web applications.  From this list, select the web application that hosts your My Sites and click OK.
copy mysites to onedrive4

5.The wizard will now load a list of available My Sites into the table.  Depending on the amount of My Sites within this web application, this may be a time consuming operation.

6.Check the box next to each My Sites that you would like to include with this operation and then click Next.
copy mysites to onedrive5

7.On the second page of the wizard, if a user mapping file is required, check the box next to Re-Map Users and then load the mapping file (for more information on how to create a user mapping file please see the User Mapping section).
copy mysites to onedrive6

8.Click the Check for users personal sites button.  This operation will verify that the user account listed in the mapping file was found in Office 365 and it will also determine if the user's OneDrive for Business site is currently provisioned.
copy mysites to onedrive7

§If the user is valid in Office 365 but does not currently have a OneDrive for Business site, please check the option labeled "Create personal sites for the selected users" which will instruct the software to provision the necessary sites.

9.Click Next to continue.

10.The final page provides a few options to configure how the content portion of the operation should be configured.

Content Options
copy mysites to onedrive8


Copy Sub-Sites - Enable this option to include all sub-sites of the current site in this operation.

Copy Permissions - This option will enable the transfer of internally shared permissions from the source to OneDrive for Business. For source Google Drive migrations, this will include internally shared folder and item-level permissions. For source SharePoint My Site migrations, this will include internally shared site, list and item level permissions. For source Box migratons, this will include internally shared folder collaborators. For source Dropbox migrations, this will include internally shared folder permissions.
 
Deferred Group Copy - Selecting Deferred Group Copy will only copy Permissions Groups that are used within the site(s) you are copying. Selecting Copy Site Groups will copy all Groups across the entire site collection.

info

NOTE:

1.Using Deferred Group Copy can be time consuming and result in slower migration performance.

2.Copying Permissions Groups requires elevated privileges within SharePoint.

Copy Content - enabling this option will copy all of the content from your My Sites to your OneDrive. You can further specify if you would like to include all versions of the content from your My Sites, or only the specified most recent versions.
 
Incremental Copy - Incremental or delta migrations are an important and powerful option for large or ongoing projects and migration validation. Once enabled this option will migrate new, modified or versioned content from the source to the destination, capturing changes made by users during the previous migration. The value entered into the "Last" field will limit the amount of content examined to the time period specified, starting at present time. To perform an incremental migration, enter the amount of time to include and select the appropriate time period in days, weeks or months. Incremental migration is designed to be used in scenarios where the destination is not being modifed. To perform a delta migration, enter zero in the field and select days as the time period. Delta migration is designed to be used in scenarios where both the source and destination may be modified during the course of the migration. Please note that a delta migration compares dates between source and destination to determine which content to include, so it will take more time to process than an incremental migration.

info

NOTE: The Overwrite if File Exists parameter will be disabled if this option is selected.


Skip files greater than - When enabled, this option will skip any source files that are greater than the value specified (in MB or GB). An entry will be added to the post-migration log indicating which file(s) were skipped due to this configuration.

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.

Re-Map Site and List Templates - This feature allows for the re-mapping of list or site templates. Download the Site and List Template Report. To do this:

1.Right click on a site in the Navigation View and go to Reports > SharePoint Site and Templates(csv). Alternatively choose the Reports Menu and then choose the Site and List Templates button on the ribbon. Enter a file name and select a location to download the CSV report, then select "Save".

2.Open and review the template report. Choose the Source Template ID and the Target Template ID you would like to Re-Map.

3.Create a new CSV file and insert the Source template ID into column A, and the Target template ID into Column B. Save the new CSV file.

4.During a copy operation, select Re-Map Site and List Templates, and then choose "Load". Select the new CSV file containing Source Template ID and Target Template ID. Once you are satisfied with your settings, press the "Next" button located at the bottom of the window to continue to the Summary window. Review your migration settings one more time and press the "Finish" button to initiate the operation.

Advanced Options
copy mysites 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. 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.

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.

11.Click Finish to begin the migration.

Copy OneDrive for Business to OneDrive for Business

A simple Administrator driven wizard is provided to bulk migrate the Documents library content from the OneDrive for Business sites in one Office 365 tenant into the appropriate OneDrive for Business Documents library in another Office 365 tenant.  In order to successfully configure and run this operation, you will need to be able to authenticate against both SharePoint Admin Center portals in Office 365 using a Global Administrator login.  A mapping file may also be needed in order to resolve the user accounts between the source and destination tenants.

This operation has the following requirements for use:

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

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

·The person performing the migration will need to know the relationship (mapping) between the user accounts in the source and target Office 365 tenants.

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

info

NOTE: To perform this operation using the Hyper Migration feature, you must first activate the feature in Profile Manager. Please see the OneDrive to OneDrive Hyper Migration Configuration section.

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

1.Switch to the Drives tab in the Essentials console and click the button "Copy OneDrives to OneDrives" located in the ribbon.
copy onedrive to onedrive1

2.When the wizard appears, enter a SharePoint Admin  Center URL for the source Office 365. Once the URL is entered, click the Connect button, enter a valid Global Admin account and click Connect.

info

NOTE: that the Claims option is not supported for this operation.  

copy onedrive to onedrive2
When you receive a successful connection message proceed to the next parameter.

3.Enter a SharePoint Admin Center URL for the target Office 365.  Once the URL is entered, click the Connect button, enter a valid Global Admin account and click Connect.

info

NOTE: that the Claims option is not supported for this operation.

 
copy onedrive to onedrive3
When you receive a successful connection message proceed to the next step.

4.Click the Load OneDrives from source
copy onedrive to onedrive4

5.In the table, a list of currently provisioned OneDrive for Business sites will be loaded.  Check the box next to each OneDrive for Business site that will be included with this operation. Click Next to continue.
copy onedrive to onedrive5

6.On the second page of the wizard, if a user mapping file is required, check the box next to Re-Map Users and then load the mapping file (For an overview on how to create a CSV mapping file for your users, please see the User Mapping section).
copy onedrive to onedrive6

7.Click the Check for users personal sites button.  This operation will verify that the user account listed in the mapping file was found in the target Office 365 and it will also determine if the user's OneDrive for Business site is currently provisioned.
copy onedrive to onedrive7
If the user is valid in Office 365 but does not currently have a OneDrive for Business site, please check the option labeled "Create personal sites for the selected users" which will instruct the software to provision the necessary sites.

8.Click Next to continue.

9.The final page provides a few options to configure how the content portion of the operation should be configured.

Content Options
copy onedrive to onedrive8

Copy Sub-Sites - Enable this option to include all sub-sites of the current site in this operation.

Copy Permissions - This option will enable the transfer of internally shared permissions from the source to OneDrive for Business. For source Google Drive migrations, this will include internally shared folder and item-level permissions. For source SharePoint My Site migrations, this will include internally shared site, list and item level permissions. For source Box migratons, this will include internally shared folder collaborators. For source Dropbox migrations, this will include internally shared folder permissions.

Copy Content - Enabling this option will copy all of the content from your Source to your Target. You can further specify if you would like to include all versions of the content from your source, or only the specified most recent versions.

 
Overwrite if file exists - In a version library, selecting the "Overwrite if File Exists" option does not overwrite the files already in SharePoint. SharePoint will append these to the list as new versions.
 
Incremental Copy - Incremental or delta migrations are an important and powerful option for large or ongoing projects and migration validation. Once enabled this option will migrate new, modified or versioned content from the source to the destination, capturing changes made by users during the previous migration. The value entered into the "Last" field will limit the amount of content examined to the time period specified, starting at present time. To perform an incremental migration, enter the amount of time to include and select the appropriate time period in days, weeks or months. Incremental migration is designed to be used in scenarios where the destination is not being modifed. To perform a delta migration, enter zero in the field and select days as the time period. Delta migration is designed to be used in scenarios where both the source and destination may be modified during the course of the migration. Please note that a delta migration compares dates between source and destination to determine which content to include, so it will take more time to process than an incremental migration.

info

NOTE: The Overwrite if File Exists parameter will be disabled if this option is selected.


Skip files greater than - When enabled, this option will skip any source files that are greater than the value specified (in MB or GB). An entry will be added to the post-migration log indicating which file(s) were skipped due to this configuration.
 
Re-Map Site and List Templates - This feature allows for the re-mapping of list or site templates. Download the Site and List Template Report. To do this:

1.Right click on a site in the Navigation View and go to Reports > SharePoint Site and Templates(csv). Alternatively choose the Reports Menu and then choose the Site and List Templates button on the ribbon. Enter a file name and select a location to download the CSV report, then select "Save".

2.Open and review the template report. Choose the Source Template ID and the Target Template ID you would like to Re-Map.

3.Create a new CSV file and insert the Source template ID into column A, and the Target template ID into Column B. Save the new CSV file.

4.During a copy operation, select Re-Map Site and List Templates, and then choose "Load". Select the new CSV file containing Source Template ID and Target Template ID. Once you are satisfied with your settings, press the "Next" button located at the bottom of the window to continue to the Summary window. Review your migration settings one more time and press the "Finish" button to initiate the operation.

Advanced Options
copy onedrive 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. 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.

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.

10.Click Finish to begin the migration.

Related Documents