SharePoint Migration empty folders

Question

SharePoint Migration empty folders

PGC-9726 25

I was able to get the migration to run, but why are the folders empty?

(update) I checked the summary report. It shows 20 files scanned and 20 files migrated in a sample run. Yet, the folder in SharePoint is empty. One thing I noticed is some folders have files in the upper folders but not in the lower folders.

I found one folder which was labeled ZPhotos. It was the last folder in the upper level and all the folders and files inside it was copied over. I've not found another folder which had the same success.

Emily Du-MSFT 51,851 Reputation points Microsoft External Staff

2024-01-01T06:58:24.9366667+00:00

What migration tool did you use?

From SharePoint server to online? Or online to online?
Bruno Gomes 111 Reputation points

2024-01-02T02:05:06.58+00:00
It's a common issue, but luckily, there are several potential causes and solutions. Let's explore some possibilities:

1. Content filtering during migration:

Certain migration tools might exclude specific file types or sizes. Double-check your tool's settings for any filters or size limitations.

2. Permissions and folder nesting:

Ensure the migrated user has sufficient permissions to access the lower-level folders and their contents. Consider nested permissions, where access to a parent folder doesn't guarantee access to child folders.

3. Versioning and hidden files:

Check if versioning is enabled in the source and target libraries. In some cases, only the latest version or specific versions might be migrated. Look for hidden files or alternate versions that appear empty but aren't truly empty.

4. Incremental or partial migration:

If using an incremental or partial migration method, empty folders might reflect a staged approach where content will be populated later. Review your migration plan and confirm the expected timeframe for full content migration.

5. Tool-specific errors:

Consult the documentation or support resources for your specific migration tool. Some tools might have known issues with folder structures or specific file types.

Next steps:

Provide more details: Share the name of the migration tool you used, the source and target locations, and any error messages encountered. This helps pinpoint the specific issue.

Run another migration test: Try migrating a smaller set of data, including folders with and without files, to isolate the problem.

Seek community support: Utilize the Q&A forum and reach out to other SharePoint experts for their experiences and potential solutions.

Remember, thoroughly understand your migration tool's functionalities and potential limitations. By providing more context and following these troubleshooting steps, you should be able to identify the cause of empty folders and ensure a successful and complete migration.
PGC-9726 25 Reputation points

2024-01-02T21:09:59.4866667+00:00

I am using the migration tool which is provided within the Office 365 admin section. It is migrating from a local server to the cloud.

When I ran the utility, some of the folders said there were errors. Such as the folders were empty, or the item had an invalid name in SharePoint.

To test the migration, I used a folder which had no errors. To avoid complications with the size of the migration, I picked a folder with 20 files, with only 7.66MB.

I checked the user rights. This user has full rights to the folders. I even tried to migrate one of their personal folders which copied the folder structure but no files, but I'm verifying the rights now.
PGC-9726 25 Reputation points

2024-01-03T18:01:55.41+00:00
So I checked the following items.

Content filtering during migration:

There is no filtering enabled.

Permissions and folder nesting:

We have admin rights to all the folders

Versioning and hidden files:

File versions are not the issue. There are no hidden files.

Incremental or partial migration:

This is not the issue.

Tool-specific errors:

I have checked the documentation. There is nothing that I've tried which explains why a few folders did copy over and others did not.
Emily Du-MSFT 51,851 Reputation points Microsoft External Staff

2024-01-04T09:12:14.2766667+00:00

Please check whether folder or file name has invalid character or too long.

What types of files are contained in the folder that cannot be successfully migrated?

Any error message in the migration logs?
PGC-9726 25 Reputation points

2024-01-08T18:34:33.6633333+00:00

Is the entire length of the path counted as the "too long" error? That could be it.

I do not believe the issue is the characters. The migration tool has a feature to substitute illegal characters with a valid character. I tried this feature, and it did not make a difference.

The folders are filled with a variety of file formats. JPG, GIF, PDF, DOC, MOV, and TXT are just some of the files.

The strange thing is, I tried migrating a folder which gave no errors after I ran the scan. I assumed that it should copy over. It did not do so.

So, one of the folders that successfully migrated was an upper level folder. It was \MPM Property Files\

The files are PDF and are named with numbers (201804131626.pdf) and (3 days to 2016MAR.PDF). I don't see any thing unusual about the naming.

If I go down one more level in the folders I found the following migrated.

MPM Property Files\ZPhotos\

2619_floor_plan + elevation.jpg

If I go lower I find the following migrated

MPM Property Files\ZPhotos\2023\intro pics 04 03

In this folder there are 200 JPG files each named with this type of naming -

20230428_1112309.jpg
PGC-9726 25 Reputation points

2024-01-13T18:01:54.2833333+00:00

Where is the quality of workmanship with Microsoft products? This is ridiculous. I'm about to dump Microsoft Office 365 for Google docs.