Posted By: Staci Davidson
Date: January 1, 2016 at 10:39 pm
When moving large amounts of data during a migration from an older version of SharePoint to a newer version, a few couple factors come into play:
In on-premise scenarios, Network latency can be minimal since data is typically being moved within the same LAN. However, network latency becomes a HUGE issue when attempting to migrate large amounts of data (typically 500+ GB) from an on-premise environment to SharePoint Online.
Detailed instructions for migrating large amounts of data to SharePoint Online can be found here:
Two options are presented in these links include:
Typically, Focal Point has utilized two options for migrating content to SharePoint Online and OneDrive for Business. It should also be noted that a combination of these options could be used to move content to SharePoint/OneDrive.
***It should be noted that Microsoft recommends moving data less than 10TB should be migrated using the network upload approach.
A benefit of using the network upload is the ability to batch import data over a night or weekend based on the amount of data being moved. There is still the upfront data preparation requirement, however.
The largest downside of using the drive shipping approach is the amount of time between when the data is prepped and shipped and when the data is available within SharePoint Online. Unfortunately, Microsoft does not offer any commitment on how long it will take for the data to become available once it is shipped and received.
In order for this approach to be successful, a schedule would need to be established over a period of time due to the time it takes to migrate content to Office 365 over the network one file/object at a time. At a high level, this process would appear as follows:
Due to the time it would take to move large amounts to SharePoint Online using ShareGate, it is unlikely that this option will be used as the primary form of migration but will rather be used to support the Drive Shipping or Network Upload approach.