Stephen Elop, President of the Microsoft Business Division, announced the launch of Office 2010 and SharePoint 2010 on May 12, 2010 at 8 a.m PST or 11 a.m. EST last week. As a result, there is sure to be a wave of organizations migrating from SharePoint 2007 to 2010 as there was when 2007 was released; but what issues should be considered before undertaking a SharePoint migration?
Gartner have urged enterprises to avoid the use of customizations as much as possible, since this was a real pain point during the 2003 to 2007 SharePoint migration surge. They also suggest that organizations should consider using one of the many content migration tools available; these tools will not nullify the labour costs involved when undertaking a content migration – they can however significantly reduce them, by ensuring that only the required content is migrated.
By undertaking a full content analysis of your content prior to migration, you ensure that content that is no longer required for the business is not unnecessarily migrated to your new repository. It is essential to prioritize content, authorize and make decisions as to deleting old, redundant files or creating new ones. This will ensure that all content meets both corporate and technical standards, while guaranteeing that content is not weighing down the data structures and back up abilities of your new SharePoint environment.
You may also want to consider companies with experience of SharePoint if you’re considering an enterprise-scale data migration.
Gartner have urged enterprises to avoid the use of customizations as much as possible, since this was a real pain point during the 2003 to 2007 SharePoint migration surge. They also suggest that organizations should consider using one of the many content migration tools available; these tools will not nullify the labour costs involved when undertaking a content migration – they can however significantly reduce them, by ensuring that only the required content is migrated.
By undertaking a full content analysis of your content prior to migration, you ensure that content that is no longer required for the business is not unnecessarily migrated to your new repository. It is essential to prioritize content, authorize and make decisions as to deleting old, redundant files or creating new ones. This will ensure that all content meets both corporate and technical standards, while guaranteeing that content is not weighing down the data structures and back up abilities of your new SharePoint environment.
You may also want to consider companies with experience of SharePoint if you’re considering an enterprise-scale data migration.
Powered by Compendium
Comments for Migrations From MOSS 2007 to SharePoint 2010