Migrator

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.

SharePoint Inventory/File System Inventory is an estimation of source content or an analysis report of the data in the source, based on some pre-defined parameters.

Some of these pre-defined parameters are: File size, Exceed URL, Blocked extension etc.,

Please follow these steps when you need to edit an already scheduled job:

• Open Schedule Migration.

• Click the edit icon in the scheduled

• Change the Schedule Interval to your requirement.

• Update the changes.

Data will be migrated in accordance with the changes made.

This happens when the tool is not open or an instance of the same job is in running state. Kindly ensure that the tool is open during the migration period.

The following migrations can be scheduled using Saketa SharePoint Migrator:

SharePoint module:

• Site contents in Site Object Migration
• Export from SharePoint

File System module:

• Import to SharePoint
• Import using External metadata
• Import Excel data to SharePoint list

No, a new instance of a job will not start if an instance is running for more than an hour for an hourly migration.

Completed job:

When a single instance of a scheduled job is migrated, the instance will be moved to the Completed tab. The job will be moved back to the Scheduled tab.

Expired job:

A scheduled job will be moved to the Expired tab after the end date of the scheduled migration.

For example, if a job is scheduled for a periodic migration and the end date is given as 27/09/2018, the instances of the job will be migrated and their status will be reflected as completed in the Completed tab until 27/09/2018. After 27/09/2018, the job will not be migrated and it will be moved to the Expired tab, automatically

Yes, you can migrate your One Drive for Business site as a normal sub web to an existing site collection.

Follow these steps to migrate My sites using Saketa SharePoint Migrator.

1. Connect to the central admin site.
2. Drill down to My site hosted web app at the source and the
3. Check the My site box at the source site.

Select the required my sites and click copy

Yes, you can run a Pre-migration check for Content migration.

Yes, One Drive for Business Site migration is supported by Saketa SharePoint Migrator. Follow these steps to migrate sites from your One Drive for Business account to SharePoint:

• Choose Site objects migration.
• Connect to Tenant admin connections at the source and the destination.
• Select your One Drive for Business site and start migration.

There are many parameters considered in the Pre-check of a Web. Kindly go through the Pre-migration check option in the copy options pop up for your better understanding.

This is used for making Bulk Changes in the Term properties by exporting terms to an Excel sheet. This Excel sheet can later be imported using Import from Excel option.

Yes, you can migrate terms directly to any term set.

Follow these steps to migrate multiple term sets from different term groups:

1. Select multiple term sets from different term groups.

2.  Select the destination term group and start migrating

Yes, you can migrate multiple term groups at a go using Saketa SharePoint Migrator.

Yes, Saketa SharePoint Migrator does migrate web parts that are added to the home page and the default aspx pages.

App web parts will be added to the destination page. But, this is possible, only if the app web parts are already available at the destination web. Please note that dependency lists are not migrated during Content migration.

No, Saketa SharePoint Migrator does not support the migration of user coded web parts.

Yes, migration of Web parts that are added to List/library views is supported by Saketa SharePoint Migrator.  You need to enable the option “Do you want to migrate web parts?” in list views and forms in the copy options pop up.

This is because, workflow tasks will not be associated with the workflow instances after migration. These workflow tasks are created by running a SharePoint Workflow instance itself.

Note- Before Migration, you should ensure, that, all workflow instances are completed as we cannot preserve workflow instances after migration.

The user should manually configure the OOTB workflows after migration, at the destination to use them again. For more information on this, kindly get in touch with the Saketa Support team.

Yes, your workflows will be migrated successfully to the destination site. That option is given to migrate workflows on dependencies.

Note– User and Group mapping or other copy options are useful whenever there are dependencies related to workflows. If there are no dependencies in the workflow, then, these options are not essential.

This can happen because of one of the following two scenarios:

• In the first scenario, when the workflow option is disabled in the Copy options pop up, it is possible for some of the workflows to go missing at the destination. To avoid this, simply enable the Workflow option in the Copy options pop up, before migrating a list/library.
• In the second scenario, the workflows are configured for No instance at the source. Try changing this configuration at the source before migrating to prevent missing workflows.

Yes, migration of all the workflows created by SharePoint designer is supported by Saketa SharePoint Migrator. However, kindly note that they should be properly attached/published at the source.

No, you cannot. Saketa SharePoint Migrator does not support the migration of code workflows.

Cloud Inventory is an estimation of source content or an analysis report of the data in the source, based on some pre-defined parameters. Some of these pre-defined parameters are: File size, Exceed URL, Blocked extension etc.,

Whenever the URL limit exceeds the maximum limit, you can choose to shorten it by clicking the shorten URL option in the copy options pop up. Files belonging to the URL in the exceeded part are migrated to the root site of the file.

Yes, you can reconnect with a different account in Cloud storage migration.  Click connect with another account at the top of the view explorer. You will be redirected to the login page immediately.

Please check the permissions of the files, when this error is shown.

No, you cannot migrate data from SharePoint to Cloud storage. Only Cloud storage to SharePoint migration is supported by Saketa SharePoint Migrator.

Saketa SharePoint Migrator supports the following Cloud storages:

1. Google Drive
2. DropBox
3. One Drive
4. Box

Yes, you can. You can choose the Do you want to import in a sequential order? option in the copy options pop up before importing.

Yes, you can. Please choose the schedule option in the copy options pop up and select the option that matches your requirement.

No, you cannot. Only List items can be imported using this option.

Yes, you can. Please choose Preserve Attachments in the copy options pop up in Import Excel Data to SharePoint list in the File System module.

xls, xlsx, .cvs and xlsm are the extension types that are supported by the Excel importer.

There can be two reasons for this:  

1) User may not be available at the destination.

2)  User and group mapping is already done from source to destination.

The flatten hierarchy option is available in the Export from SharePoint module. Follow these options to use this option:

1. Enable Export Subwebs in the copy options pop up.

    2. Enable Do you want to flatten hierarchy by exporting all subwebs into the root level of the selected location in the File System?

Yes, it is. While exporting libraries or sites, you can enable/disable this option. You can also provide a custom number to the version that needs to be exported.

Yes, you can. Please choose the Import Using External Metadata option in the File System to SharePoint module.

Yes, the attachments of the list items will be preserved automatically.

For some files, the created date is more recent than the modified date. In such a case, all the migrated files’ modified date will be assigned the created date of the file, by default.

This will be expected if the user does not have sufficient permissions. Kindly check the permission on the drive which is connected to the File System.

Yes, it is possible by disabling the Do you want to create new item versions for this update option in the Edit options pop up.

No, the user must check in the file before making any changes.

Yes, you can. Please select the Do you want to update items based on authors and editors under Exclude rules in the Copy options pop up in the Bulk Update List/Library Metadata module.

Yes, you can.

Please follow these steps:

1. Connect the site and drill down into the required library.
2. Select files and click Start Update button.
3. Enable the Do you want to exclude files based on extensions? option in the edit options pop up in the Bulk Update List/Library Metadata module.

The Export to Excel and Import from Excel options allows users to transfer metadata or extract metadata to/from an Excel sheet. You can also edit this metadata, based on your requirement.

Yes, you can. By default, the author and time stamps for any item/file will be preserved.

Yes, there is. Please select the Copy and Replace option in the copy options pop up.

While migrating content, select the Map Content Type option in the copy options pop up. You can easily map the required content type using this option.

Please follow these steps to map content types:

1. In the copy, options pop up, click Map Content Types.

2.In Destination List Content Types section, all the available content type in destination list will be displayed. Map the required content types and click save.

Yes, you can. Migration of content is not dependent on the templates of lists/libraries.

No, Subsite templates cannot be mapped with Site collection templates. This is because, while creating a Subsite, Site collection templates will not be available.

Dependencies will not be modified if they are already present at the destination. To update a particular list, please migrate that particular dependency list individually.

Yes, InfoPath form migration is supported by Saketa SharePoint Migrator.

Choose the Incremental Load option when you want to migrate files/folder/Items that are created/modified within a specific date range.

This option is supported by  Site Object Migration (List/Library & Web) and Content Migration.

Please select the option Copy if newer in the copy options pop up, if you wish to migrate only the recently updated files/items.

Yes, this option will work for dependency lists.

No, the metadata of the previous version will be preserved in the first version of the available version of the file, at the destination.

You will have access to all the features of Saketa SharePoint Migrator, except the turbo speed mode feature.

Yes, you can purchase license for some specific features of Migrator and not the other ones. To avail, kindly get in touch with the Saketa Support team.

Kindly get in touch with the Saketa Support team.

You can only access one PC with the license key you were provided. In case you need access to multiple systems, kindly get in touch with the Saketa Support team.

If not, kindly follow these steps:  

1. Click Settings option on the tool’s landing page.  
2. Click About option.  
3. Click Release key, if you want to stop using that PC.  
4. Repeat steps 1 and 2 in the other PC.
5.  Click Update License and enter your license key, to continue using Saketa Migrator.

Yes, you can migrate a custom web part with migrator. Enable the Do you want to migrate Webparts in List Views and Forms? Feature in the copy options pop-up.

The Select Language drop-down provides a list of all the languages in which the tool can be displayed.

Note: Selecting any language will only display the tool in the selected language’s script but will not be translated.

When the ‘Combine with Site name’ option is selected while migrating a site, all lists/libraries will be migrated to the destination site and there will not be a separate URL for the migrated site at the destination.

Yes, you can migrate InfoPath forms with migrator.

Data that is in the check-out mode in a SharePoint site is considered as unsaved data in pre-migration and post-migration.

The incremental load option is provided to reduce manual effort. Choose this option if you want to migrate items that are created/modified within a specific range of dates.

The Item Already Exists section deals with what needs to be done when an item that is being migrated is already present in the destination. The section has the following five options:

Don’t copy: Select this option if the item already exists at the destination site and you don’t want to copy it again.

Copy and Replace: Select this option if the item already exists at the destination site, but, you want to replace it with the item present at the source site.

Keep both: Select this option when the item already exists at the destination site and the source site, but, you want to migrate the item present in the source site anyway. The item at the source site will be migrated to the destination site with the same name and will be numbered accordingly.

Copy if newer: Select this option if you want to migrate the item at the source site that is updated/modified after the same item already migrated to the destination site.

Merge: Select this option if you want to merge the item at the source site with the item at the destination site.

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.

This option is useful when files are stored in different sites and need to be migrated. It discovers all the sites that are reachable at that time, i.e., only sites which are servers that are online at that time will be shown. It excluded sites that cannot be reached at that time. Sites which are stored in servers that are offline or down will not be shown.

Yes, the files will be migrated even if the URL exceeds more than 256 characters. But, such files, whose URLs exceed the 256-character limit will be migrated to the root folder of the files. Their path will be clearly logged in the Reports section.

Yes, you can. Choose between Copy to current web and Choose a location under the How to manage copy dependencies? option in the copy options pop-up.

Yes, you can change the name of a list/library in the tool before migration. In the copy options pop-up of the Migrate SharePoint Site Objects option, change the title and URL of the list/library you wish to change before proceeding to migrate.

Data cannot be migrated in such an event and an appropriate error message will be displayed.

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.

You can keep both the versions at the destination site. Choose the option Keep Both in the copy options pop-up.

The original version of the item/file will be migrated with its original title. The updated version of the item/file will be migrated as original title (1).

There is no upper limit to migrate the updated/modified versions. You can migrate as many versions as needed.

You can preserve the previously configured permissions at the destination site and completely ignore the source site’s ‘Unique Permissions’. Disable the Preserve Unique Permissions option in the copy options pop-up.

Yes, you can preserve Unique Permissions. Enable the Preserve Unique Permissions option in the copy options pop-up.

Yes, you can limit the versions of documents. Kindly follow these steps to limit the number of versions of documents at the destination site:

1. Choose either Migrate SharePoint Site Objects or Migrate SharePoint Content option under the SharePoint module, depending on your requirement.
2. When the copy options pop-up displays, enable the option Limit to the number of latest versions.
3. Type in the number of versions you require.
4. Customize the rest of the options and click copy.

Yes, you can. Check the Migrate as a Subsite option in the copy options pop- up (By default, the option is already checked. Uncheck it if necessary).

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.

Yes, it is possible. Select Migrate SharePoint Site Objects or Migrate SharePoint Content, based on your requirement, in the SharePoint module. Go to Copy Options pop-up and select the required options.

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

 There are two methods to establish a connection between the source and the destination.

Method 11: Directly from the migrations tab

1. Open the Saketa Migrator
2. Click search
3. Click new connection
4. Add source and destination connections

Method 2: From the Connection Manager

1. Open the Saketa Migrator
2. Go to settings
3. Navigate to Connection Manager
4. Click Add Connection
5. Enter source and destination URLs and add the connections

Yes, you will be notified. All the errors and warnings can be accessed from the Reports section

Yes, you will. Saketa SharePoint Migrator keeps a detailed record of all the migration sessions including the amount of data migrated on a particular date. These reports provide a detailed analysis of all the data that is successfully migrated as well as the data that could not be migrated, along with specific reasons. These reports can be accessed from the Reports section.

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 schedule migrations as per your convenience. Please follow these steps to schedule a migration:

1. On the Saketa Migrator, go to copy options pop-up.
2. Enable the ‘Schedule’
3. Enter the required time and date in the options and schedule sessions.

The migrations will start at the mentioned times.

You can migrate up to 5GB of data during the free trial.

Extension of trial period depends on the user and their requirement. Please contact Saketa Support for further details.

The free trial period is for a week (7 days).

Kindly get in touch with the Saketa sales team by dropping an email to us at sales@saketa.com. We will get back to you with the pricing details.

Please follow these steps to add an Azure account in Migrator:

1. Open the Saketa Migrator
2. Click on ‘Settings’
3. Navigate to ‘Speed’ tab
4. Click on ‘Click here to add’
5. Enter the ‘Account name and Account Key’
6. Click on ‘ADD’

The user must have a Microsoft Azure account to use this mode and the destination should be SharePoint online.

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.

For a purchased license, you can migrate unlimited amount of data using the Saketa Migrator. For a trial license, we do cap the amount of data that can be migrated to 5 GB.

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.