Fix SharePoint Migration Tool Copying Structure but Not Content
Question details
The user needs to resolve an issue where the SharePoint Migration Tool successfully creates the destination list structure but fails to migrate the list content, returning a general SERVER ERROR.
- Product
- SharePoint Migration Tool (SPMT)
- Device & OS
- not provided
- Scenario
- Migrating SharePoint list data from a source environment to a destination SharePoint site using SPMT.
- Observed behavior
- The migration tool creates the list columns and structure at the destination but fails to transfer the actual list items, generating a SERVER ERROR during the process.
Ensure you are using the latest version of the SharePoint Migration Tool and that your Microsoft 365 administrator account has 'Site Collection Admin' rights on the destination site.
Analyze SPMT Migration Logs and Verify Permissions
Check the detailed failure logs generated by SPMT to identify specific item-level errors and ensure that the migration account has the necessary permissions.
A general SERVER ERROR often indicates underlying permission issues, unsupported column types, or network timeouts during the item transfer phase. The SPMT logs provide the exact error codes needed to pinpoint the failure.
Navigate to the folder where your SPMT logs are saved. By default, this is located in `%appdata%\Microsoft\MigrationTool\` or the custom path you specified during the migration setup.
Open the `ItemFailureReport.csv` and `FailureSummary.csv` files. Look for specific error messages or HTTP status codes next to the list items that failed to migrate.
Check that the account running the migration has at least 'Read' access to the source list items and 'Full Control' or 'Site Collection Administrator' rights on the destination SharePoint site.
After addressing any permission gaps or corrupted list items identified in the logs, open SPMT and click 'Run' to resume or retry the migration task.
Contact Microsoft Support via Microsoft 365 Admin Center
If the logs indicate a backend server issue or if the problem persists, escalate the issue to Microsoft Support for advanced diagnostics.
Simplify Your Document Workflow with WPS Office
If managing Microsoft 365 migrations and complex SharePoint environments feels overwhelming, consider a more straightforward solution for your daily document needs. WPS Office is a lightweight, fully-featured office suite that makes creating, editing, and sharing documents effortless.
- 1. Download the Installer: Visit the official WPS Office website and click the 'Free Download' button.
- 2. Install WPS Office: Run the downloaded executable file and follow the simple on-screen instructions to complete the installation.
- 3. Open Your Files: Launch WPS Office and directly open your existing Microsoft Office documents to enjoy a seamless editing experience.
Frequently Asked Questions
Why does the SharePoint Migration Tool only migrate list columns but not the rows?
This usually happens when there is a mismatch in supported column types, if the list exceeds lookup threshold limits, or if the source list items contain corrupted data or unsupported attachments that trigger a server error during data transfer.
Where can I find the exact server error details for SPMT?
Detailed error logs can be found in the `ItemFailureReport.csv` and `StructureFailureReport.csv` files. These are located in the SPMT reporting folder, which is generated locally on your machine after a migration task completes or fails.
Does the SharePoint Migration Tool require a specific account type?
Yes. The account running SPMT must be at least a SharePoint Administrator or Global Administrator in the destination Microsoft 365 tenant. It also requires the necessary read permissions on the source SharePoint server or file share.
What should I do if a server error prevents migration in Microsoft 365?
First, ensure your firewall or network is not blocking Microsoft 365 endpoints. Check the Microsoft 365 admin center for any active service health degradation. If the issue is persistent, compile your SPMT error logs and contact Microsoft Support.
