The company I work for is currently in the planning stages of a MOSS to 2010 migration (we have a business critical environment with >500 users to port). With this in mind I was wondering what are some of the less known problems you have found or tricks you know for making this transition go easier?
|
|
What we've done in some cases is to put up a SharePoint 2010 site somewhere (separate from the actual new environment) and put up a survey or discussion board there. Survey can be pretty much anything, but if you can figure a good survey that is related to MOSS or SP2010, maybe asking "what could be improved in the current environment", etc. Then you just sit and wait for the people to say certain unpleasant things of the current environment and try to turn those around how SP2010 will improve those. Another benefit of that is that people will use SP2010 to fill in that survey. Regarding discussions, it can be again anything, but can be related to the survey, or some company event. Idea is just to get people into SP2010 and familiarize with it without even realizing it. You can think of similar things with other SP2010 functionalities. |
||||
|
|
|
Familiarity - make sure you have a plan to give users time to adjust to the new look, behaviour (eg. ribbon) and layout. Plan training sessions to allow users to translate their existing skills from 2007 to 2010 (e.g. changing list views). Use SharePoint 2010 functionality to keep the existing visual styles to help manage the changeover. From a technical standpoint, review and test customisations before the deployment, and check for any content dependencies on customisations too. Even if you don't plan to port a customisation over, how will that effect existing lists? |
|||||
|
|
Had similar experience. My 5 cents:
|
||||
|
|