Migrations are a messy business and continue to be deliver blows and bruises for those of you considering, delivering and recovering from them.
I am working on a process that I have learned over the years and will be exposing this over several entries.
Take the time to do a good "Analysis" and what does that really mean.
- Need a deep understanding of the Target Environment
- What are the reserved Field Names
- What are the built in Content Types
- What Features have been replaced, depricated and added
- Shared Service Providers (SSP) for Service Applications
- Metadata and the Term Store
- Social Tagging
- Is the content standardized
- What are the business drivers behind the migration
- What works today
- Ensure you don't remove functionality that is critical to the business
- What doesn't work today
- It is important to fix this but pick the low hanging fruit first
- What can be left behind and what should be moved forward
- How many versions are really necessary
- What are the blocked file types
- What is the size limitation
- What is the range both type and date that needs to be moved
- What are the compliance or retention policies
This is a limited subset of the Full Analysis but should be enough to get you started.
In the next entry we will discuss rationalization and reporting and how that makes or breaks your project.