Microsoft 365 Migration

Fix SPMT Error: Content You Provided Cannot Be Found in Migration

Khadija Khan Oct 12, 2026 868 views

Question details

Users encounter a 'Content you provided cannot be found' error when attempting to migrate data from SharePoint 2010 to Microsoft 365 using the SharePoint Migration Tool (SPMT).

How to Fix SPMT Error: Content You Provided Cannot Be Found

Product: SharePoint Migration Tool
Device & OS: not provided
Scenario: Migrating site collections from a SharePoint 2010 on-premises server to a Microsoft 365 environment.
Observed behavior: The migration tool halts and displays an error message indicating the provided content cannot be found. This often affects specific web application root site collections while others migrate normally.

Before you start

Ensure that your migration account possesses Site Collection Administrator privileges on both the source SharePoint 2010 environment and the target Microsoft 365 destination.

Solution 1Recommended

Verify Site URLs and Permissions

Check if the issue is isolated to a specific root site collection and verify that the provided URL is completely accurate and fully accessible.

Often, SPMT errors are triggered by minor discrepancies in the URL format or insufficient access rights at the site collection level.

Validate the source URL

Open a web browser and navigate directly to the SharePoint 2010 source URL you entered in the SPMT. Ensure it resolves correctly without redirects.

Check administrator permissions

Log into the SharePoint 2010 Central Administration, go to Application Management, and verify your account is listed as a Site Collection Administrator for the failing site.

Test alternative site collections

Attempt to migrate a different site collection within the same web application to determine if the error is localized to a single site or affects the entire application.

URL Formatting: Ensure you are using the correct protocol (HTTP vs. HTTPS) and do not include trailing slashes or sub-page paths unless specifically migrating a single list.

Solution 2

Request Official Microsoft Support

Escalate the issue to the SharePoint Migration team if troubleshooting site permissions and URLs does not resolve the error.

Free Microsoft Office alternative

Maintain Productivity with WPS Office During Complex Migrations

Server migrations and SharePoint troubleshooting can temporarily restrict access to your online documents. Ensure your daily productivity remains uninterrupted by using WPS Office. As a lightweight, highly compatible alternative to Microsoft Office, WPS Office allows you to edit, save, and manage your local files effortlessly while server issues are resolved.

1. Download the software: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to complete the setup.
3. Open your documents: Launch WPS Office to instantly open and edit your existing Microsoft Office files without formatting loss.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats (.docx, .xlsx, .pptx).Lightweight installation and familiar interface, requiring no learning curve.Seamless offline document editing to keep you productive during cloud migration downtimes.Completely free to use for everyday document creation and editing.

Frequently Asked Questions

Why does SPMT say the content cannot be found when the site exists?

This error typically occurs due to permission mismatches, incorrect URL formatting (such as missing HTTP/HTTPS), or corrupted root site collections in the source SharePoint 2010 environment that prevent SPMT from reading the site architecture.

Can I migrate specific document libraries if the entire site collection fails?

Yes. Instead of entering the root site collection URL, you can input the specific URL of a list or document library into the SharePoint Migration Tool to see if it bypasses the root-level error.

Where can I find the SPMT error logs for more details?

You can review the SPMT failure logs located in the migration task's designated report folder on your machine. Open the FailureSummary.csv or ItemFailureReport.csv files to view detailed error codes and pinpoint the exact point of failure.

Migration & Recovery