SPMT Error help

The second message, “Not all the items in the package have been migrated,” is usually just a result of the first error. Start with the disk-space message.

Try these steps:

1. Open the SharePoint admin center > Active sites and select the exact destination site used in SPMT. Check both Storage used and Storage limit. If the site uses a manual limit, increase it and leave some extra space for the migration.
2. Check the tenant’s total SharePoint storage. Even if the site looks almost empty, it cannot grow when the tenant-wide storage pool is full.
3. Check what is already using the site’s space. Old file versions, both stages of the Recycle Bin and the Preservation Hold Library all count toward storage. Only delete retained content if your organization’s retention rules allow it.
4. Check the computer running SPMT. Make sure the C drive and temporary folder have enough free space because SPMT creates a local package before uploading it.
5. In SPMT, open the failed task and select View report. Find the first failed item and note its full error, time and correlation ID. The first error is normally the useful one; later items may only show the general package error.
6. Update SPMT, then retry one failed library in smaller batches, such as one top-level folder at a time. Once the cause is fixed, run an incremental migration so SPMT only retries the missing or changed content.

If the target site, tenant and local computer all have enough space but the same error continues, raise a Microsoft 365 support case. Include the SPMT report, correlation ID, failure time and destination site address, because Microsoft may need to correct the site’s backend storage information.