It seems most companies around the world get SharePoint to replace their fileshares. It’s the entry point for many businesses. The classic mistake most make however, is treating SharePoint like a fileshare.
The worst thing you can do is just upload your fileshares into SharePoint without any kind of analysis or clean up. It’s junk in, junk out. If you can’t find anything on your fileshares now, what makes you think it will be any better in SharePoint if you don’t classify things properly first?
The following at minimum needs to be addressed first :
- You need to decide what data you’re going to keep and for how long.
- What types of files can be migrated over? Are PST’s, videos, sound files and photos allowed?
- Where it will be stored and who will be responsible for maintaining it?
- How will it be categorized and who will determine the taxonomy?
- Who will have access to what and at what permissions level?
- If you’re going to SharePoint 2013, do you allow the external sharing of your documents? And if so to whom and by whom?
- Are you bound by legislation that requires records management and has this been built in?
- Will things all still be in Word or Excel format; or can they be converted to site pages and lists instead?
- Do you know what libraries need versioning and which ones don’t?
- If you’re going to migrate them regardless, do you have special software installed that can extract metadata for you?
- What about naming standards – what date standard do you employ as it affects how you sort your documents after bulk uploading them.
- Have documents with special characters been addressed? The “&” symbol is in many Excel doc names and SharePoint doesn’t like those.
- What size are the documents? Is the default upload limit of 50MB going to suffice?
If you’re migrating your fileshares onto SharePoint without asking at least these basic questions, you’re just performing a tickbox exercise and the platform is highly unlikely to be successful.
Telling your users you will be switching off the fileshares by X date and they better have moved their stuff to SharePoint by then, is the perfect way to ensure a failed implementation if you have not empowered them and planned the environment properly first.