When attempting to migrate a file with version history preserved, the following message is displayed:

The file 'http://sharepoint/Documents/MyFile.docx' could not be found for the version 'x.y'.
​

This error happens because ShareGate Migrate was unable to retrieve the file at the location specified, for the specified version.

This can happen if the file was renamed, moved or deleted since the first time that ShareGate Migrate accessed it (either because someone else was performing changes at the same time as ShareGate Migrate, or because a workflow or an event receiver has automatically renamed, moved or deleted the file).

In some cases, this error can also happen when the file does exist, if SharePoint is returning errors when ShareGate Migrate tries to access the file.
​

Verify if the file exists in SharePoint at the given location.

If the file does not exist and you know it should normally be there, verify if there is a workflow or an event receiver that is set to run automatically under certain circumstances. If so, disable it temporarily during the migration to make sure that it does not interfere with the operations that ShareGate Migrate do.

If the file seems to exist in SharePoint at the right location, you can also verify if the file can be found with SharePoint Designer. In order to do so, you can perform the following steps:
​

If the file is not displayed or gives you an error when trying to export it, this means that there is a problem within SharePoint that makes the file available in the browser, but not available for client applications such as SharePoint Designer or ShareGate Migrate. This would be due to a bug in SharePoint, so we recommend contacting Microsoft support in order to get help on this issue.

If the file is displayed in SharePoint Designer and gives no error, please contact our technical support team and we will gladly help you resolve the issue.