{"id":16,"date":"2009-08-08T01:51:30","date_gmt":"2009-08-07T20:21:30","guid":{"rendered":"http:\/\/vyapin.com\/blogs\/?p=16"},"modified":"2021-05-28T12:53:29","modified_gmt":"2021-05-28T12:53:29","slug":"challenges-when-migrating-sharepoint-document-files-and-folders","status":"publish","type":"post","link":"https:\/\/www.vyapinsoftware.com\/blog\/challenges-when-migrating-sharepoint-document-files-and-folders","title":{"rendered":"Challenges when migrating SharePoint document files and folders"},"content":{"rendered":"

There are several challenges when migrating documents to Microsoft SharePoint<\/a>. While these challenges can be overcome, they are a real pain if the migration source, content and file systems are not SharePoint friendly.\u00a0 We will discuss below some of the common ones here.<\/span><\/span>\u00a0Folders and files exist in several sources – file shares, web-based sources, network \/ backup drives, personal drives etc.<\/span><\/span><\/p>\n

1.\u00a0 Dealing with Special characters and Lengths in Folder and File names<\/strong><\/span><\/span><\/p>\n

SharePoint does not accept certain special characters (tilde, number sign, percent, ampersand, asterisk, braces, backslash, colon, angle brackets, question mark, slash, pipe, quotation mark – ~, #, %, &, *, {, , ;, <, ?, \/, |, “). Hm… that’s a lot of special characters and certainly, it is not\u00a0that uncommon to find some of these in filenames in file systems. Also, SharePoint does not allow folder and file name lengths to be longer than 128 characters in WSS 3.0. These aspects alone can be such a pain during migration of folders & files that contain special characters and long names. Windows folder \/ file names with special characters have to be replaced with SharePoint acceptable characters to avoid manual work in renaming folders and files.\u00a0 For files that contain special characters based on certain logic or a set of rules, this can easily be dealt with by using scripts or some tools. However, if the files contain special characters in a random manner with no orderliness about them, it can be a laborious task to rename the folders and files before migrating them to SharePoint. Similarly, long folder and file names have to be truncated to the prescribed length before moving them to SharePoint. A few nasty folders \/ files in random can put a spoke in a well planned, large and orderly migration. Here are two useful links to know more about SharePoint special characters, limits on URL lengths and long filenames.<\/span><\/span><\/p>\n

https:\/\/support.microsoft.com\/en-us\/kb\/905231<\/a><\/p>\n

2. Maintaining the same folder \/ file structure when migrating to SharePoint <\/strong><\/span><\/span><\/p>\n

Most companies will want to retain the same structures for files and folders to maintain operational consistency as well as business continuity. For example, an organization currently using a traditional Windows based file server platform for document collaboration could be deploying SharePoint as the collaboration platform for the users. In such situation, it will be easier to maintain the same folder and file structure in the newly setup SharePoint library without changing the user experience in handling folders and files. It makes the navigation intuitive, eases migration process, minimizes user training and improves operational efficiency.<\/span><\/span><\/p>\n

3.\u00a0Migrating a select set\u00a0of document types \/ formats such as doc, xls, ppt, jpeg, dwg, pdf etc. <\/strong><\/span><\/span><\/p>\n

Sometimes, only documents of certain types (or formats) need to be moved to SharePoint libraries depending on the document templates or content types or file types allowed to enhance the document management framework. Everything else needs to be filtered. To selectively move files based on their types will require some programming, especially so if there are large folder trees (nested folders).<\/span><\/span><\/p>\n

4. Migrating a large number of unstructured and poorly managed files.<\/strong> <\/span><\/p>\n

From the perspective of file contents, business relevance and usage patterns,\u00a0migrating a large number of unstructured and poorly managed files (remember some of those legacy file systems?)\u00a0to a structured, organized and searchable framework within SharePoint is not easy. A lot of planning and meticulous reorg of files and folders is a must. This essentially means\u00a0that there will be\u00a0frequent rework of mapping and remapping the source\u00a0folders and the destination\u00a0libraries. The migration has to be broken down to several different tasks (batch processes), with several different rules to process the files and folders.<\/span><\/p>\n

5. Using a mass document migration application to work off your desktop instead of running right on the SharePoint servers directly. <\/strong><\/span><\/span><\/p>\n

If you are using third-party tools for SharePoint migration<\/strong><\/a>, a solution that can run either on the desktop and or on the server will be ideal. Take the case of incremental migrations. The SharePoint server could already be in production mode while several different libraries in SharePoint could still be under migration. Server performance will be compromised if the migrating application is going to run on the server. It is better if the application runs on a desktop performing actions like data cleansing, processing etc. and just do a final bulk upload into SharePoint.<\/span><\/span><\/p>\n

6. Migrating and tagging the tens of thousands of documents from your legacy file folders into your new SharePoint repository while retaining the existing taxonomy or migrate to a new taxonomy.\u00a0 <\/span><\/span><\/strong><\/p>\n

Most file system users will not be familiar with the concept of document metadata. They are more familiar with the term file properties. The concept of document metadata originates from Document Management Systems (DMS), where documents are stored and made searchable on a wider set of keywords and phrases. Document libraries in SharePoint are akin to Document Management Systems in the way they store documents and properties for search and retrieval. However, these properties need to be presented to SharePoint during migration in a certain manner that makes the search and retrieval more powerful and elegant.\u00a0 You may migrate \/ propagate metadata fields from the document properties stored within the file or using an external metadata file \/ database.\u00a0 Mapping and tagging existing file properties and adding additional properties to documents in SharePoint, especially for a well structured taxonomy can be a laborious process.<\/span><\/span><\/p>\n

7. Retaining (carry forward) the Created Date and Last Modified file attributes from the file system to maintain business continuity for users and minimize user training when collaborating in the new SharePoint environment.<\/span><\/span><\/strong><\/p>\n

This is another challenge that is constantly faced by SharePoint users. There are plenty of business reasons to retain the same Date field values once the documents have been migrated to SharePoint. Unfortunately, SharePoint falls short in this aspect and you need third-party tools or some in-house programming to carry forward the original date fields for documents.<\/span><\/p>\n

8. Automating the migration process to reduce the time necessary and labor involved to move large file repositories to SharePoint.<\/strong><\/span><\/span><\/p>\n

Almost all mid-sized to large-sized migrations require automation, especially when incremental\/batch migrations from different sources take place. Automated batch jobs help you to take complete control of the migration process by handling errors and triggering events that can be managed efficiently. Otherwise, you have to spend hours on ad-hoc problems and tracking down repetitive errors thrown by non-automated migrations.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

There are several challenges when migrating documents to Microsoft SharePoint. While these challenges can be overcome, they are a real pain if the migration source, content and file systems are not SharePoint friendly.\u00a0 We will discuss below some of the common ones here.\u00a0Folders and files exist in several sources – file shares, web-based sources, network […]<\/p>\n","protected":false},"author":1,"featured_media":7283,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[146],"tags":[140,60,64],"class_list":["post-16","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-do-you-know","tag-dockit-migrator","tag-sharepoint-content-migration","tag-sharepoint-migration"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/posts\/16","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/comments?post=16"}],"version-history":[{"count":5,"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/posts\/16\/revisions"}],"predecessor-version":[{"id":7380,"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/posts\/16\/revisions\/7380"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/media\/7283"}],"wp:attachment":[{"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/media?parent=16"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/categories?post=16"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vyapinsoftware.com\/blog\/wp-json\/wp\/v2\/tags?post=16"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}