Any guidelines anyone can share regarding the time to migrate a very large 2007 and 2010 farm to 2013...I know there are many variables and tools available...details welcomed!
Please provide
your suggestions / advice / recommendations by means of COMMENTS
Gather environment information:
ReplyDelete----------------------------------
-Number of sites
-Number of databases
-Number of users
Gather Settings:
------------------
-Alternate access mappings
-Authentication providers and
-authentication modes that are being used
-Quota templates
-Managed paths
-Self-service site management settings
-Incoming and outgoing e-mail settings
-Customizations
-Certificates
-Check for and repair all database consistency errors.
-Turn off Web Analytics service application
-Remove PowerPoint Broadcast Sites
Tools:
ReplyDelete- No direct migration from 2007 to 2013 out of the box, have to use 2010,
- Sharegate as first "good enough" tool - it is really nice,
- AvePoint DocAve as more advanced,
- Database attach as most robust,
There are others, but I have no experience.
Some tips:
- Design new SharePoint 2013 and approach it as completely new system. There are a lot of differences between 2007, 2010 and 2013. Especially consider which services you need to deploy and which services you want to plan to deploy in future.
There are few services which deployment needs some attention.
- Take some time to design new a information architecture - consider how to limit the number of web applications (this really can hit performance), use host named site collections.
- Test farm design, deployment process and impact of migration process on live farm.
- Prepare to rollback/fallback to original site before migration,
- With large amount of data, delta/differential migration is something what you probably need,
- Secure "powershell master" resources, you will need a lot of scripts,
- The most tricky thing - prepare for transition period, when you have to run two farms at the same time. Make this period as short as possible. Probably you will need some redirection pages as URLs will be changed. Test the user experience and make the users aware on what is going on, when, why and what they can expect.
Migration is good opportunity to reorganize sites and remove obsolete ones and to take advantage of new capabilities. So this does not have to be one to one migration.
I have a complete set of documents (or almost complete) for SharePoint 2013 farm design (50k users), plus some information about migration (from 2007), but I cannot just share it as they contain customer specific information etc. But I can use them as a base for creating new ones. If you are interested send me a message.
Mapping your content will be essential, especially if there are metadata changes or updates. Also, you'll want to carefully evaluate the site templates you're using and determine if those templates will make sense going forward. For our upgrade we had several decision points because we were using templates (workspaces for example) there are de-emphasized in SharePoint 2013. Not to mention that there are better tools in place for some of those functions in 2013.
ReplyDeleteMigrate from standard authentication to claims authentication is a key topic if you have a large user base
ReplyDeleteYou should look at migrating and reorganizing at the same time. I've worked with a large state agency and helped them move from 2007 to 2013 and the biggest piece wasn't moving, it was planning the move. So in terms of time I wouldn't try to do this in two weeks. Unless you are talking about one small farm, and even then it still could take longer.
ReplyDeleteNo one likes to talk about planning, but when it comes to making such a leap in platforms, the worst thing you can do is not plan. The migration itself isn't hard at all and with a good 3rd party tool such as AvePoint's DocAve, it takes most of the headache out.
The biggest thing about migrating is the content, the information/logical architecture and really ensuring that the farm is built to support the needs of the business. I've seen companies stand up farms that sit and do nothing and then I've seen farms that scream for more resources because it was overloaded once all the content was migrated.
Evaluate the business needs, how the business is using SharePoint today versus how it wants to use it in the future and plan that out in the technical designs of the farm. Once all that has been done, then you can look at migrating and that's when the fun begin. In reality a lot of the content just should not be migrated. Getting users to let go and remove what isn't needed is a big chunk of migrating.
At Summit 7 we deal with that all the time and I get to sit down and help business people understand just what they are trying to achieve. Once that hurdle is done, everything else is easy. So in long to answer your question, a good migration normally takes about 3 to 6 months if the farm is large enough and all parties decide to play together and by the same rules.