Troubleshooting common SPMT issues and errors
This article describes common issues and errors you may encounter when using the SharePoint Migration Tool (SPMT).
Note
For help on SPMT installation issues, see: Troubleshooting SPMT installation issues
Common error messages
| Message | Do this |
|---|---|
| We are unable to connect to the site you provided | Check if the list exists or if you can access it in the source site and target site from your computer. Confirm you have signed into SPMT with an account that has access to the site. Confirm the URL you entered is correct and follows the proper format. Example: <spam><spam>https://<spam><spam>contoso.sharepoint.com/teams/SiteTitle<spam><spam> |
| Invalid source folder | Confirm the path you entered is correct and follows the proper format Confirm the user of SPMT has read access to the folder. |
| The site cannot be created or updated | Confirm that you have permissions to create the site and that the URL is valid If the site exists, confirm you're the site collection administrator If it still fails, create the site manually and point the migration tool to this newly created site. |
| Scan file failure: The folder name is invalid | See Invalid file names and file types in OneDrive and SharePoint. |
| Scan file failure: Target path is too long | See Invalid file names and file types in OneDrive and SharePoint. The entire path, including the file name, must contain fewer than 400 characters for OneDrive, OneDrive, and SharePoint. |
| Scan File Failure: Not enough disk space to pack the file | The disk space available for the migration working folder is too small for the size of your source file. Enlarge your size of your working folder try again. |
| Packaging failure: Cannot open file | Packaging failed due to non-existing source. Check if you can access the source root folder. |
| A duplicate task has already been created. | The CSV file used to do bulk migration can't have duplicate entries. Remove the duplicate line(s) and try again. |
| The parent folder was not migrated | The parent folder wasn't migrated, therefore all items under the folder failed to migrate. Check your parent folder and retry your migration. |
| Task #, parameter 1. The source path should not be empty | Confirm that the source path column in the CSV file has a value. |
| Task #, parameter 4. The target URL is an invalid URL | Confirm that the target url column in the CSV file has a value and is valid. |
| Task #, parameter 5. The target list should not be empty | Confirm that the target list column in the CSV file has a value. |
| Admin permissions are required to migrate this content into OneDrive. | Check that the account used to migrate content has permissions on the destination OneDrive. |
SPMT error codes
| Error Code | Recommended action |
|---|---|
| 0x0201000D | Check if the list exists or if you can access it in the source site and target site. |
| 0x02050008 | Unable to access your local storage. Restart your migration. |
| 0x02010023 | Your source list template isn't supported. Try another. |
| 0x0201000C | Check your credentials and then reenter your username and password. |
| 0x02010017 | You must be a site collection admin. |
| 0x02060009 | 1 - The site collection can't be created because the URL is already in use or an invalid URL. |
| 2 - The site collection can't be created because the URL contains invalid character. | |
| 3 - The site collection can't be created or updated. | |
| 0x02060007 | 1 - The site collection can't be created because the URL is already in use or an invalid URL. |
| 2 - The site collection can't be created because the URL contains invalid character. | |
| 0x02010018 | 1 - Check your credentials and then try again. |
| 2 - A problem occurred accessing SharePoint. Check your credentials and try again. | |
| 3 - A problem occurred accessing SharePoint. Check your credentials and your network connection and try again. | |
| 4 - A problem occurred accessing SharePoint. Check your credentials and your site URL for accuracy and try again. | |
| 5 - A problem occurred accessing SharePoint. Check your credentials and the format of your URL. Retry. | |
| 6 - A problem occurred accessing SharePoint. Check your credentials and try again. If the problem continues, create a support case. | |
| 7 - A problem occurred accessing SharePoint. Check your credentials and try opening your site in a browser. | |
| 0x0204000A | Can't create package file. All files and folders in the SPMT working folder, %appdata%\Microsoft\MigrationToolStorage, must be closed. Restart your migration. |
| 0x02030001 | 1 - Check your credentials. Restart your migration. |
| 2 - Check your credentials. Restart your migration. | |
| 3 - Check your credentials and your network connection. Restart your migration. | |
| 4 - Check your credentials and your site URL. Restart your migration. | |
| 5 - Check your credentials and the format of your URL. Restart your migration. | |
| 6 - Check your credentials and restart your migration. If the message persists, create a support case. | |
| 7 - Check your credentials and try opening your site in a browser. Restart your migration. | |
| 0x02010008 | Confirm the path and format of the user mapping file and that you have permission to access it. |
| 0x02050001 | All files and folders in the SPMT working folder, %appdata%\Microsoft\MigrationToolStorage, must be closed. Restart your migration. |
| 0x02010002 | Check your network status. If you can access the source sites from a browser, then create a support case. |
| 0x02010010 | Make sure the source list and target list have the same template. |
| 0x0204000D | All files and folders in the SPMT working folder, %appdata%\Microsoft\MigrationToolStorage, must be closed during migration. Restart your migration. |
| 0x02040012 | The temporary storage on your local computer is too low. SPMT caches the package on the working folder. Expand your temporary storage and retry. |
| 0x02030003 | There are too many items with unique permissions. Simplify your permissions list by reducing the number of unique permissions. Retry your migration. |
| 0x02050001 | Local storage file is corrupted. The working folder was touched or modified during the migration. Retry your migration. |
| 0x02080001 | The file in the package has been changed or deleted while uploading. All files and folders in the SPMT working folder, %appdata%\Microsoft\MigrationToolStorage, must be closed. Restart your migration. |
| 0x02010006 | The source SharePoint site doesn't have any defined role definitions. Check to see if your role exists when accessing source site. |
| 0x02040009 | The package can't be created because the directory can't be found. All files and folders in the SPMT working folder, %appdata%\Microsoft\MigrationToolStorage, must be closed. Restart your migration. |
| 0x02010020 | Disable migrating version history in SPMT settings or enable versioning in SPO. |
| 0x0201000E | Check if the global setting has filtered out special characters in the target path or if the path has unsupported characters. |
| 0x02010016 | We're unable to find your SharePoint Server user. Make sure you're a site collection admin. |
| 0X0201000F | Invalid site URL. Check if the site URL is valid. Try to access the URL via a browser. |
| 0x0207001 | You do not have access to the task folder. Check if you can access %appdata%\Microsoft\MigrationToolStorage. |
| 0x01410010 | A failure occurred because of missing dependencies on list items. Check the FailureSummaryReport.csv for details. Check if the dependencies have been included in your migration scope. |
| 0x01510001 | Packages failed to upload. If you have customized Azure Storage, check if you can access the Azure Storage and check if you can access the target site. Try migrating again. |
| 0x01510001 | Failed to Upload the Job to Server: Upload file failed during migration. |
| 0x02070009 | Several packages failed to upload. Pause the task and check your network connection. |
| 0x01710009 | A failure occurred due to job end failures; some items failed in the package. Restart migration. |
| 0x01710009 | Errors or timeout for Server Processing the file: Not all the items in the package have been migrated. |
| 0x01610001 | The Azure container is expired. Retry migration task. |
| 0x01710006 | Errors or timeout for Server Processing the file: Job Fatal Error. |
| 0x01710004 | Errors or timeout for Server Processing the file. Fail to look up folder name. The item may exist in other list or site in the same site collection. Or the item is in the recycle bin. |
| 0x0131000D | Could not get all list item versions; tool sends request to fetch item versions, but nothing is returned. This error can occur when the download link is different between the common file and .aspx file. This case is fixed in 4.x version. |
| 0x0131000F | Failed to Read the file. File is checked out. |
| 0x0111000A | Scan File Failure: File size exceeds limit. See Release Notes: SharePoint Migration Tool (SPMT) for current limits. |
Navigation errors
| Error | Reason | Action |
|---|---|---|
| This navigation node contains an invalid URL: cannot find the object this URL points to. | SharePoint validates the URL before it creates the navigation node. If the URL represents a SharePoint object and the object can't be found, SharePoint rejects the node creation query with this error. The object can't be found if the target of the URL was deleted, moved, not migrated yet, or migrated in previous task where the URL mapping can't be recognized in current job. | Use the same URL mapping between multiple tasks. For example: Task 1: http://domain/original_path/site -> http://domain/new_path/site Task 2: http://domain/original_path/site2 -> http://domain/new_path/site2. Run another task to migrate Navigation nodes pointing to objects that weren't migrated previously. Manually created the node in target site. |
| The navigation settings are highly customized. Currently it's not supported. | Global and current site navigation can only be migrated if its value matches a predefined template. Otherwise, the value is recognized as highly customized and won't be migrated. | Change the global and current navigation to use one of the predefined templates. See Site settings -> Look and Feel -> Navigation. Manually edit the setting on target site. |
| Could not get target Term Store ID. The taxonomy provider of web navigation settings cannot be updated. | Because the global and/or current site navigation settings is set to "Managed Navigation," the term store scanner was unable to get the target term store ID. Term store scanner fails to get the target term store ID if Managed Metadata Services isn't properly configured. | Learn more at SPMT Managed Metadata Migration. |
| The taxonomy provider term set ID of web navigation settings is invalid. | As the global or current site navigation settings are set to "Managed Navigation", the term store scanner couldn't map the term set ID. | Confirm that the setting on the source site is valid and the term set was successfully migrated. |
| To update web navigation settings, you need following permissions: Add and Customize Pages. | The SharePoint account used for migration doesn't have permission to edit site navigation settings. | Grant "Add and Customize Pages" permission to this account. |
Taxonomy errors
| Error | Reason | Action |
|---|---|---|
| Migrate term store failed due to permission issue. | The user isn't a term store admin. | In the SharePoint Admin Center, select Classic features, and then under Term store, select Open. Select the term store you want to migrate, then add the current user as a Term Store administrator. |
| Migrate term store failed due to lack of working languages. | Not all working languages of source term store exist in the target term store. | Go to SharePoint site setting. Under Site Administration, select Term store management. Select the term store you want to update, select, and add all the languages existing in source term store to the target working language panel. |
| Migrate term store failed due to default term store does not exist. | There isn't a default site collection term store at SP on-prem. | Go to SharePoint Server (on-premises) Central Administration, manage service application under Application Management, edit the properties of Managed Metadata Service Connection. Select the This service application is the default storage location for column specific term sets. |
| Migrate term store failed due to several default term stores exist. | There are several default site collection term stores existing at SP on-prem. | Go to SharePoint OnPrem Central Administration, manage service application under Application Management, choose one Managed Metadata Service Connection as default term store. Deselect This service application is the default storage location for column specific term sets of other Managed Metadata Service Connections. |
| Migrate pinned term failed due to its source term does not exist. | In some cases, the pinned term is in global term set (available for all sites connecting to this Managed Metadata Service Application), and the source term is in local term set (available for users of this site collection). SPMT will migrate the global terms first, and then migrate the local ones. If the source term is in the local set and the pinned term is in the global set, the local source term won't be migrated before SPMT attempts to migrate the pinned global term. | Because the source local term migrated in the previous action, migrate again to include the pinned global term. |
Web part errors
| Error | Reason | Action |
|---|---|---|
| Migration not supported web part | Currently, SPMT doesn't support this web part. | Check the list of currently supported web parts: SPMT supported web parts. |
| Migration failed due to referring list is missing | The list hasn't been added to the task list. | Check your web part and the referring list to ensure it's in your migration scope. |
| Migration failed due to page being customized | SPMT currently doesn't support customized page migration. | Restore the page's template page by using SharePoint Designer and restart your migration. |
| Migration failed due to page migration failed | Migration of the page failed, and all the web parts on that page. | Retry migrating the failed page. If the page succeeds, then all the web parts on that page will successfully migrate. |
| Migration failed due to it is an unsafe web part and the server setting 'NoScript' | When the setting NoScript is turned on in the target SharePoint site, the web parts are considered to be unsafe as they could have the ability to execute JavaScript scripts or other code. Web parts will be blocked from migrating. | Turn off the NoScript setting on the target SharePoint site so that these web parts will be unblocked. Important: Your site may be at risk if you turn off the settings. For more information, see Allow or prevent custom script. |
| Migration failed due to invalid XML definition | The XsltListView web part and ListView web part contain an XML definition that is critical for the migration of these web parts. Sometimes the XML definition is invalid because of upgrading issues or server errors. | Delete the failed web part from the SharePoint Server source page. Re-add it and try the migration again. |
| Migration failed due to invalid assembly name | The assembly name of the web part is critical for SPMT to migrate the web part. If the assembly of the web part can't be parsed from its SOAP response, the migration fails. | Check whether this web part is a supported "out-of-the box" (OOTB) web part. If it's supported, file a bug and we'll investigate. However, if the web part is a third-party web part, it isn't supported. |
| Migration failed due to web part connection failure. | The web part is connected to another web part that failed to migrate, causing both to fail. | Make sure the connected web part is migrated successfully. Retry your migration. |
| Migration failed due to unable to map user | If the User field is a property of the web part, SPMT will attempt to map the user on the source web part (usually an on-premises user) to a user on the target SharePoint site. This error occurs when SPMT can't map to the user. | Confirm that Microsoft Entra ID is used to sync all on-premises users to SharePoint. |