General

Saketa turbo migration boosts up the migration speed to SharePoint online by leveraging the new O365 Migration API and Azure.

This results in fast and hassle-free migration even with huge data.

How It works

The content will be first uploaded to Azure storage and from their azure will migrate the content to SharePoint online or OneDrive for Business. Once the migration to SharePoint is completed the data that is uploaded to azure will be cleared.

Prerequisites

• User must have Microsoft Azure storage account
• Destination connected site should be SharePoint Online.
• User should have site collection admin privileges in the destination connected site.

Create Azure storage Account

We need to create general-purpose v2 storage account in the Azure portal to use the Saketa turbo Migration.

To create this account, please follow the steps mentioned in the article Create Storage account.

Get the Access key for storage Account

We need to get the access key for the storage account to be used in Saketa turbo migrator.

Please follow the below steps to obtain the Storage Account name and Access key.

1. Sign in to the Azure dashboard.
2. In the navigation pane, click on All Resources.
3. Choose the desired storage account.
4. Click on the Key icon to view the access keys for the storage account.

   Note: Each storage account has two storage access keys. Any of them can be used.

5. To copy a storage access key, click on the Copy icon next to the key you want to copy.

Enable Saketa Turbo Migration

Once you obtain the access keys for the storage account you can configure Turbo Migration in Saketa Migrator.

Steps to enable turbo migration

1. Click the settings icon at the bottom left of the Saketa Migrator.
2. Click on the Migration Speed tab and click on Click Here to Add button under Saketa Turbo Migration to Office 365.
3. A popup appears where we can provide the storage account name and storage account access key which we have retrieved earlier from azure.
4. Once you click on the Add button the storage account will be added successfully. The turbo feature will now be available for all new migrations.

Post Migration check option gives a detailed report of all the warnings and errors that are encountered during an ongoing migration. URLs of all the warnings and errors are included in a report and can be found in the Reports option.

When the internet connection is lost, migration will be paused and a pop-up will be displayed stating Connection lost. All the data that is migrated will be saved at the destination. Migration will resume once the connection is restored.

Many features will be deprecated when a new version of SharePoint is released. Therefore, it is sometimes difficult to map source templates with destination templates. But, the new version will have an alternate option. We recommend that you choose the template that is the most suitable to your source site’s template and map it.

There is no restriction to the number of migration sessions you want to schedule

Please do not switch off your PC while the migration is in progress. Doing so will stop the migration and thus, no further data will be migrated. However, all the data that is previously migrated will be intact.

Yes, you can migrate data from SharePoint 2010 to SharePoint 2016 directly.

The Saketa SharePoint Migrator is a comprehensive migration tool that has been developed for migrating data from a SharePoint Site, File System or Cloud.

In general, please note that the speed of migration depends on the following factors.

1. Time taken by the SharePoint servers at the source and destination to service a request

If there is any delay in a response from the source or target servers, this will impact the speed of the migration. Some of the reasons for the slow response are

• Large number of users using source and target SharePoint farms.
• Large number of migration sessions on a single farm
• Problems with the load balancing server.

2. Network speed

Network speed plays a very big role in data transmission from source to target. Poor network connectivity will adversely affect the speed of data migration. For better performance , 50 MBPS network speed is recommended

3. Insufficient memory in the machine, where the Saketa Migrator is being run

The recommended memory size is 16GB for better performance.

4. Type of SharePoint objects and data we are migrating

The speed of the migration for SharePoint objects and file streams is not same. Migrating SharePoint objects ( like content types, site columns, lists, libraries, managed metadata, workflows etc.) to a target site takes more time than migrating file streams.

Example:

This point is best illustrated with an example. Migrating 20 site content types, with each content type containing more than 30 site columns (the storage size of 20 content types in content DB is approximately 100Kb) takes approximately 10 minutes, but to migrate 1GB single file take only 8 minutes.

Similarly, a migration involving a large number of list items will take longer than migrating large volume of file streams.  

Saketa SharePoint Migrator operates in two-speed modes: Normal and Turbo. You can substantially increase the speed of migration using the Turbo Mode, provided you have a verified Azure account.

Normal Mode: All migrations are in the normal mode by default. The speed in this mode is highly dependent on the speed of the internet.

Turbo Mode: Turbo Mode will be enabled only when the destination site is SharePoint online and the user has a verified Microsoft Azure account. All the data will be transferred into the Azure account and then migrated to the destination site.

Saketa SharePoint Migrator supports the following versions of SharePoint: 2007, 2010, 2013, 2016 and Office 365. Data can be migrated from SharePoint 2007 but cannot be migrated to SharePoint 2007.

All the different versions of a file will be migrated to the File System and for each version of the file, there will be one file created, with its original title and will be numbered accordingly, in the File System.

Example: If the name of the original file in SharePoint is Migrate and the file has five versions, then after migrating to a File System, all the versions of the file will be named as Migrate (1), Migrate (2), Migrate (3), Migrate (4) and Migrate (5).

Yes, you can. In the copy options pop-up, disable the List/Library Content option present under Keep the following objects option.

When the internet connection is lost, migration will be paused and a pop-up will be displayed stating Connection lost. All the data that is migrated will be saved at the destination. Migration will resume once the connection is restored.

Please follow these steps to install Saketa SharePoint Migrator on your system.

1. Go to saketa.com
2. Navigate to Migrator
3. Click Try Now
4. Sign up for Saketa Migrator
5. Download and install the tool.

You are all set to start your migration journey.

Saketa SharePoint Migrator is a tool developed exclusively to migrate content from multiple platforms like File System, SharePoint, and Cloud to SharePoint.