Last Updated on May 18, 2022 by rudyooms
This blog will be about the steps you need to take BEFORE you migrate your on-premise file server to Sharepoint/Onedrive/teams.
In one of my last blogs, I showed you the importance of making sure you don’t exceed the 255 characters when you are working with OneDrive and how you could solve this.
This blog above is based on what you could do AFTER the migration, now it’s time to talk about what you can do BEFORE the migration.
I will divide this blog into multiple parts
Again, the limitations, you really need to beware of are the Character limit and the File limit.
1.The Character Limits:
I will show you which limitations to expect when you are migrating. We could start off with the number of characters and the invalid characters. You need to make sure there are:
*no invalid characters
*no long file names.
1.1. Long file name
When your users are going to use OneDrive (For a good user experience, I would strongly recommend it) you need to scan the folder first for long file names.
The first tool you need to use is the Path scan tool, it can easily scan your whole directory and create a list in txt format.
As shown above, this file exceeds 254 characters. When scanning the folder keep in mind the folder/file path will be longer when you mount the sites in onedrive. This is because c:\users, your username and company name will be added to the filepath.
It’s best practice to lower the scan to 200/220 characters, so you are sure you will not have any problems.
But this tool does not scan for invalid characters, so what else can we use?
1.2. Invalid Characters
In the past, you could use the SharePoint migration tool to migrate your data but now you can use the Migration Manager.
There are some benefits when you use this tool, it scans for the SharePoint path limit (400 characters) and it scans for invalid characters.
When you use the “scan only” function, it will only perform a scan and you can download a zip file with the item failure summary in it.
This report shows us two things:
Sharepoint’s long file path.
Just copy-paste it into notepad, you will know the number of characters
Now we have some more information, about which files and folders would break we can report it back to the owner of the files. You will need to inform the users so they can make some changes.
Maybe instead of changing only the file which exceeds the limit, he or she could change the folder structure itself to make 100% sure there are no problems left when you migrate. You will keep in mind the rule of 3 when changing the file structure. Please make sure you don’t nest more folders than 3 layers deep.
When you apply the rule of three you are also saving time for your users because each time, they don’t have to be clicking 10 or 20 times to reach their final destination.
Now we know, exceeding the 255 characters we also need to beware of the file limits out there. We don’t need to forget what can happen with the performance or permissions when are choosing to sync a lot of files.
- 300.000 Files in total
- 100.000 Files in one Sharepoint Library
- Onedrive 64 Bits?
2.1. 300.000K Files
This one is definitely the worst. You really don’t want to sync more than 300.000k files in the one drive client. When syncing more than 300k files, there could be some performance issues. There is a nice .dat file inside the %localappdata%\Microsoft\OneDrive\settings\Business1 folder, when it exceeds 2 GB…. you can guess what will happen.
Using files on demand to connect to a folder instead of syncing all the files at once will improve the experience and performance, so please turn it on.
Counting the number of files is not that hard. You need to assume everyone wants to sync as much of the team libraries to their device, so please advise your customer to only sync what is needed, nothing more and again turn on files on demand. One thing is for sure, they are going to call you when OneDrive stops working.
Now we are for certain, that syncing too many files is not the best practice what are the options before we migrate? In the blog I mentioned earlier I showed you how you can resolve it after the migration.
Maybe we could make sure the old and forgotten files are not available to sync? You need to archive or delete inactive files before you migrate. Just like counting the number of files, just search and create a nice report for files that haven’t been touched for 10 years and ask the users responsible if the data is still necessary.
2.2.100K files in a library/folder
But what will happen with permissions when you have a lot of file items inside a library/list or folder?
Again, lesson learned. You don’t want to have a folder/list or library with more than 100.000 items in it.
2.3. OneDrive x64!
Please take a look at my blog about the 64 bits OneDrive Client because the 64 bits version of OneDrive will fix some stuff…. not all… but… it performs better
You don’t want to migrate without scanning and learning about your data first, just clicking down the migration manager wizard and pressing okay/okay and migrating overnight is not best practice.
If you don’t want to be afraid about the migration itself, you need to scan the data first and beware of the limits!!
- File path length limit –> Number of three!
- Invalid character’s –> Change them!
- Number of files –> Archive/Delete/Files on demand/Onedrive Shortcuts!
And this sums it all up…? Nope, I still didn’t talk about data governance! Please take a look at some of my blog posts about securing your data