It's official, I have started working on the Transportation Safety Board of Canada strategy to migrate their SharePoint 2007 intranet platform over to SharePoint 2010. TSB's SharePoint environment is highly customized, and development best practices have not been followed in many areas. This blog serie is intended to describe and related all steps undertaken by our organization to upgrade our platform to 2010. Hopefully it will save somebody else the trouble of figuring out how to upgrade their own customized SharePoint environment.
Before I get started, here's a bit of background info as to where our organization stands. Since 2005, the TSB has been leveraging the SharePoint plas a case management system to manage investigation related materials. In April 2010, the platform was migrated over to a MOSS 2007 server. It was decided at the time that an in-place upgrade was not feasible, and that it was better to build a new server completely, and develop a custom tool to migrate all existing information over. Some of the 2003 customization was dropped during the migration process to give place to some of the new out-of-the-box features offered, however, it is estimated that about 70% of the overall solution is still custom. When I say customization, I mean custom web parts, custom event handlers, custom timer jobs, custom workflows, and custom master pages & style. The migration to 2007 was very painful for the users because they needed to adapt to many new features and components.
Having wrote the business case for our SharePoint 2010 upgrade project, here is the objectives/goal of the project:
Improve the [SharePoint] system by upgrading its technological platform while limiting the impact on the user community.
My next post will describe the steps undertaken by the team to upgrade the current system using the Database Attach Approach.
No comments:
Post a Comment