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.
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.
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.
NOTE: that the Claims option is not supported for this operation.
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.
NOTE: that the Claims option is not supported for this operation.
When you receive a successful connection message proceed to the next step.
4.Click the Load OneDrives from source
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.
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).
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.
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.
|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.
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.
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.
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.
10.Click Finish to begin the migration.