SharePoint Migration Tool Errors and Re-migration of Failed SharePoint Migration Items/files



Re-migration of Failed SharePoint Migration Items is an essential step to validate the completion of a migration process.

When you are doing a bulk SharePoint migration , getting the copy of the entire SharePoint site in one go without losing a single file/list item is uncertain most of the time due to various reasons. Some of the possible reasons for files/items failure include throttling, missing parent folders, blocked file types, missing content types, etc.

Consider, after migration of a SharePoint resource, you are left with 200 files missing each belonging to different source folders that are to be migrated to different target locations. To get them copied to the destination, it’s not feasible to migrate the entire SharePoint resource again.



Now there comes the need for migrating only the failed files.

Generally, to migrate only the failed items, you will do the following:

Connect to the source and destination connections.
Drill down the source resource.
Drill down to the folder of the failed items and select the item.
Configure the migration options and then copy them.
For each failed file, you must repeat the steps 3 and 4. the migration report and check for the failed items

If you have 2-3 files missing, repeating the same work is not a problem.



But it will be tedious doing it for 200 times in this scenario, even more, if you have more items/files failed in other bulk migrations.

Considering this, Saketa Migrator has developed a new syntax for the Copy-Content cmdlet specifically for the migration of failed items to avoid the repetitive work for the users and thereby saving your time.

With this syntax, you can migrate the items from different source locations to different target locations at one go and can avoid manual drill down to each location and migrating them one by one.

To Re-migration of Failed SharePoint Migration Items/files using Saketa Shell:
To re-migrate the failed SharePoint migration items/files of a completed migration, you can use the Copy-SKTContent cmdlet available as part of Saketa SharePoint migration PowerShell cmdlets. as you can follow the below steps.

1.Get the failed items details from a migration exported to excel. To export the failed items, you can do one of the following.

Open migration session report of the failed migration and filter only the error items from all the report items and export them to excel.
Or else you can run Post Migration , filter the error items and export the report in excel format.
2. Using Saketa shell, Connect to the source connection  and Get a list/library from the source.

3. Connect to the destination connection   and Get a list/library from the destination.

4. Pass the exported excel file path using the parameter ‘ExcelFilePath’ and other required parameters to Copy-SKTContent cmdlet as shown in the below image.

5. Run this script in Saketa PowerShell .


Sample Script:  Copy the script and modify it to work for your need by editing the parameter values for site URLs, list ids, and excel file path.

$sourceConnection = Connect-SKTSite -Url “sample.sharepoint.com/sites/sourcesite/ ” -Username “user” -Password “password”



$destinationConnection = Connect-SKTSite -Url “sample.sharepoint.com/sites/d…ationsite/ ” -Username “user” -Password “password”



$sourceList = Get-SKTList -ID “583637ad-b40f-4344-a3f8-376937a3a5e5” -Connection $sourceConnection

$destinationList = Get-SKTList -ID “425637ad-b40f-4374-a3f8-376be7a3a5f2″ -Connection

$destinationConnection

Copy-SKTContent -ExcelFilePath ”D:\ExcelFilePath.xlsx” -SheetName ”AllData” -SourcePathColumn ”SourcePath” -DestinationPathColumn ”destinationpath”  -SourceList $sourceList -SourceConnection $sourceConnection  -DestinationList $destinationList -DestinationConnection $destinationConnection