\n\nSharePoint is a web-based platform introduced by Microsoft to meet the \ncollaboration requirements of organizations. Effective collaboration and\n sharing of documents among employees is vital to the success of an \norganization. By implementing SharePoint, organizations reduce their \noperational costs and improve productivity.\n\n
\n\nWhile implementing SharePoint, organizations needs to move all their \nshared content from File Servers to SharePoint. The decisions to migrate\n data from a known platform to a new one is really a tough one. Once \ndecision has been taken, you need to go through a lengthy procedure that\n mostly involve the following steps:\n\n
\n\n1. Requirement analysis\n\n2. Migration planning\n\n3. Pre-migration analysis\n\n4. Migration\n\n5. Migration validation\n\n
<\/p>\n\n\n\n
\n\n\nSharePoint is relatively a new product that is emerging and evolving \ngradually to a mature collaboration and content management platform. \nBefore adopting it in your organization, you should know what it is for,\n how it can be utilized effectively, and how suitable is it for your \norganization. \n\nAt first you should decide whether you need an on-premises deployment or\n a SharePoint Online subscription (SharePoint Online is available as a \nstand-alone product and as a part of Office 365 Suite). There should be a\n clarity regarding what need to be moved to the SharePoint from File \nServers. And most importantly, you should understand the limitations of \nSharePoint.\n\n<\/p>\n\n\n\n
\n\nThere are different approaches to File Server to SharePoint migration \nprocess. Careful planning simplifies the migration process very much. \nSome organizations like to move the entire content to SharePoint in a \nsingle attempt. But many organizations like to do it many phases. Also, \nthe organization need to take a decision regarding the timing of \nmigration \u2013 whether to continue with the migration in working hours or \npause it. \n\n
\n\nYou need to plan the SharePoint information architecture depending on \nthe requirements of the organization. Design the architecture according\n to the data you have. Decide on how to organize SharePoint lists and \nlibraries, how to place data\/content on sites and libraries, and who \nwill have access to these lists and libraries. You can have multiple \nsites and libraries for the better organization of the content.\n\n
\n\nInformation mapping is an important part of the migration. Decide on \nwhich content should go to a particular site or library. You need to \nplan Content Types accordingly.\n<\/p>\n\n\n\n
\n\nA pre-migration analysis checks for possible troubles that may happen \nduring the actual migration. A fair understanding of SharePoint \nconfiguration\/subscription plan, and SharePoint Limits and Boundaries \nwill help you to understand and fix most of the possible issues in \nadvance. While migrating content to SharePoint, one should keep an eye \non the volume of the data, file sizes, number of items, file and folder \nnames, etc. because of many restrictions enforced by SharePoint. Some \ncommon issues faced in SharePoint migration are mentioned below.\n\n
\n\nBased on your on-premises infrastructure, or your cloud subscription \nplan, you will be having a limit on the volume of data you can migrate \nto the SharePoint. You cannot migrate more data without ensuring \nadditional storage space. And if the number of items you migrate is \nlarger, you may have to restructure the SharePoint to accommodate the \nadditional items. \n\n
\n\nWhile naming a file path, file, folder etc. in SharePoint, you need to \nremember many things. There is a limit to the number of characters \npossible in a SharePoint URL. Also, many characters and end strings are \ninvalid in SharePoint. If you have file or folder names with such \ncharacters and end strings, you need to change them before the \nmigration. Also, some file types are blocked in SharePoint, and you \ncannot migrate them to SharePoint at all. \n\n
<\/p>\n\n\n\n
\n\nIdeally you should move only the shared data from File Server to \nSharePoint (Public folders of Exchange Server\/Office 365 also can be \nmoved to SharePoint as they are used by all). You need to configure the \nSharePoint environment as per requirement. Migration can be done in \ndifferent ways:\n\n \n\nAfter the migration, you need to ensure that migration has been \naccomplished successfully. This can be done by comparing the SharePoint \ncontent with the old source. You need to check whether all the data has \nbeen migrated. Special care should be given to the migration of meta \ndata and version history. You can double-check the inference by taking \nfeedbacks from site owners. Also, after the migration you can think of \nrestructuring the content if changes seem necessary. And finally, the \nend users should be given necessary training as SharePoint is a new \nplatform for them. \n\n<\/p>\n","protected":false},"excerpt":{"rendered":" SharePoint is a web-based platform introduced by Microsoft to meet the collaboration requirements of organizations. Effective collaboration and sharing of documents among employees is vital to the success of an organization. By implementing SharePoint, organizations reduce their operational costs and improve productivity. While implementing SharePoint, organizations needs to move all their shared content from File […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-757","post","type-post","status-publish","format-standard","hentry","category-sharepoint-server"],"yoast_head":"\n
\n\n\u2022 Manual migration<\/strong> \u2013 manual methods are preferred only when the volume of the data to be migrated is small. \n\n\u2022 Migration using professional migration tools<\/strong>\n – Professional SharePoint Migration tools are preferred when the volume\n of the data is very large. Such tools perform pre-migration analysis \nand automates the migration process. They usually provide the facility \nto schedule the migration too. Before purchasing a tool, go through the \nproduct details and try its trial version if available. \n<\/p>\n\n\n\n\nMigration validation<\/h3>\n\n\n\n