There’s plenty of technical articles discussing what tool to use, what commands to use, what products to use and more in the face of migrating one or more SharePoint environments from 2007 to 2010. This article describes the process that a SharePoint Architect would need to define with the SharePoint Administrator to ensure there is a plan which covers:
- What will be migrated
- What environments will need to be in place
- What Risks have been investigated
- What teams are involved
- What Third Party systems have been investigated
Note that this document as said is not a click here click there guide – neither does it advocate any particular tool to use (ok so I have used content db shift as an example), but what it is there to do is to help you focus on the areas that the stakeholders will need to know – things like ‘When does this take place’, ‘What features for my web application will be available’, ‘How will the backup work’, ‘Is DR going to be in place’ and many more.
Below is my thoughts, broken into section. For those of the more graphically minded nature a mind map is here: https://serviceautomation.online/wp-content/uploads/2012/03/SharePoint2007to2010Migration.swf