sodcalculator

10 Tech How-To

Fix SharePoint Migration Temporary Storage Too Low

Guide 10-45231 · Updated · Step by step

If your SharePoint migration job fails with a “temporary storage on your local computer is too low” error, the fix is to free up disk space on the drive where the migration tool stores its temporary files, or to change the temp file location to a drive with more space. This error is common with the SharePoint Migration Tool (SPMT) and other migration tools that cache files locally before uploading them to SharePoint.

What Causes the Temporary Storage Error

SharePoint migration tools work by reading your source files, creating a local cache of metadata and content, and then uploading that cache to the cloud. The local cache can be large—often several times the size of the actual data you are migrating—because the tool creates temporary databases and file copies to handle errors and retries. When the drive holding this cache runs out of space, the migration job stops with the “temporary storage too low” error.

The error is most common when migrating large folders, file shares, or on-premises SharePoint sites. It can also happen if you have a small system drive (C:) and the tool defaults to using the user profile folder, which is on that drive. Even if you have plenty of space on another drive, the tool won’t use it unless you tell it to.

How to Check Your Current Temp Storage

Before making changes, you need to see how much space is available and where the migration tool is storing its temporary files. The default location for SPMT is usually %USERPROFILE%\AppData\Local\Microsoft\SPMT, but it can vary by tool and version. To check your current free space:

  1. Open File Explorer and right-click on the drive where your user profile is located (usually C:).
  2. Select “Properties” and look at the “Free space” value.
  3. If free space is low (less than 20 GB is often insufficient for large migrations), you need to free up space or change the temp location.

You can also use the Settings app to see storage usage: go to Settings > System > Storage and review what is taking up space on the drive.

How to Fix the Issue

There are two main approaches: free up space on the current drive, or redirect the temp folder to a drive with more capacity. The best fix depends on your situation—if you have another drive with plenty of free space, redirecting is usually the fastest and most reliable option.

Free Up Space on the Temp Drive

  • Delete temporary files using the Disk Cleanup tool (search for “Disk Cleanup” in the Start menu).
  • Clear the Recycle Bin.
  • Uninstall programs you no longer use.
  • Move large files (videos, ISOs, backups) to an external drive or cloud storage.
  • Use the Storage Sense feature in Windows to automatically remove temporary files.

Change the Temp Location in SPMT

In the SharePoint Migration Tool, you can specify a different temporary location when you create a migration job. Look for a field labeled “Temporary location” or “Working folder” in the job settings. Enter a path to a folder on a drive with sufficient space, such as D:\SPMT_Temp. Make sure that drive has at least as much free space as the total size of the data you are migrating, plus a buffer for overhead.

Change the Temp Location via Registry (Advanced)

If your tool doesn’t expose a temp location setting, you can sometimes change it via Windows environment variables. For SPMT, you can set the TEMP and TMP environment variables to a folder on a larger drive. To do this:

  1. Open System Properties (right-click This PC > Properties > Advanced system settings).
  2. Click “Environment Variables” and edit the TEMP and TMP variables for your user.
  3. Set them to a folder on a drive with more space, like D:\Temp.
  4. Restart any open programs, including the migration tool.

Be careful with this approach, as some applications expect the temp folder to be on the system drive. Test that your migration tool still works after the change.

Common Problems and Misconceptions

One common misconception is that the error refers to SharePoint Online’s storage. It does not—the error is about your local computer’s disk space. Another misconception is that you need to increase the page file or RAM. That won’t help; the issue is purely disk space.

A frequent problem is that even after freeing space, the migration fails again because the tool creates a new temp cache for each job, and the previous cache wasn’t cleaned up. After a failed migration, the temp folder may still contain gigabytes of data. You can safely delete the contents of the temp folder (as long as no migration is running) to reclaim that space.

Another issue is that some users try to use a network drive or a USB drive as the temp location. This is not recommended because the migration tool needs fast, reliable local storage. Network drives can cause performance issues and errors. Use an internal drive (SSD preferred) for the temp folder.

How Much Space Do You Actually Need?

The amount of temp space required depends on the size and type of data you are migrating. As a rule of thumb, you should have free space equal to at least 1.5 times the total size of the data you are migrating. For example, if you are migrating 100 GB of files, you should have at least 150 GB of free space on the temp drive. This accounts for the cache, logs, and any temporary copies the tool makes.

If you are migrating a mix of file types, especially large files like videos or databases, you might need more. The tool also needs space for the migration database, which can be sizable. When in doubt, free up as much space as you can, or use a dedicated drive with plenty of capacity.

Alternatives to Local Temp Storage

If you consistently run out of space, consider these alternatives:

  • Use Azure File Sync or a staging area in Azure: Some migration tools allow you to stage data in Azure, reducing local storage requirements. This is more advanced and may require additional setup.
  • Migrate in smaller batches: Instead of migrating a huge folder all at once, break it into smaller jobs. This reduces the peak temp storage usage.
  • Clean up source data: Remove obsolete files or archive them before migration. This reduces the total data size and thus the temp space needed.
  • Use a different migration tool: Some tools are more efficient with local storage. For example, the SharePoint Migration Tool (SPMT) is generally efficient, but other tools like Sharegate or Metalogix may have different caching behaviors. Evaluate your options.

Frequently Asked Questions

Why does the migration tool need so much temp space?

The tool creates a local cache to keep track of what has been migrated, to handle retries, and to temporarily store file content before uploading. This cache can be larger than the source data because it includes metadata, logs, and database files.

Can I use an external hard drive as the temp location?

Yes, but it is not recommended. External drives, especially USB-connected ones, are slower and less reliable. If the drive disconnects during migration, the job will fail. Use an internal SSD or HDD with plenty of free space.

Will changing the TEMP environment variable affect other programs?

It can. Many programs use the TEMP variable for their own temporary files. If you change it, those programs will write to the new location. This is usually fine, but some programs may not work correctly if the new location is not writable or is on a network drive. Test after making the change.

How do I clean up temp files from a failed migration?

Navigate to the temp folder you set in the migration tool (or the default SPMT folder) and delete its contents. Make sure no migration job is currently running. You can also use Disk Cleanup to remove temporary files, but it may not remove all files in the SPMT folder.

What if I still get the error after freeing up space?

Check that the drive you are using for temp storage actually has the free space you think it does. Also, ensure that the temp folder is not set to a location with a quota or permission restriction. Try creating a fresh temp folder and setting it explicitly in the migration tool.

Does this error affect all SharePoint migration tools?

Most migration tools that use a local cache can hit this issue. The exact error message may vary, but the underlying cause is the same: insufficient local disk space for temporary files. The fixes described here apply to most tools.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →