Presentation given 9/11/2010 at SharePoint Saturday East Bay in San Ramon, California.
The majority of a migration effort has nothing to do with the actual technical move of content and bits, but is a planning activity. This presentation walks through 11 areas of focus, sharing best practices.
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
11 Strategic Considerations for SharePoint Migrations
1. 11 Strategic Considerations for SharePoint Migration Christian BuckleyDirector, Product EvangelismAxceler (echoTechnology) @buckleyplanet http://buckleyplanet.net
2. Content Why this presentation is important The “standard” answers to upgrade and migration Wit and humor, obscure references to bad 80’s movies 11 strategies you should consider as part of your planning Online and offline resources
3. Why is this presentation important? Most content focused on the technical aspects of migration Migrations are not so much about the technical act of moving the data (although very important), but more about the planning that goes into preparing for the migration
4. Why is this presentation important? It’s not about the minutia of scripting methods to execute a hybrid database attach upgrade of your environment We’re here to discuss the sometimes technical, but much more “hip” exercise of proper migration planning This is the Jack Bauer of migration presentations, people My weapon today…….PowerPoint
5. What is migration? Microsoft defines migration as three separate activities: The reality is that a single migration may include all three concepts
6. What is migration? Moving to the latest, greatest platform Transforming what you did with 2003/2007 to meet your organizational vision
8. What are the Microsoft options? I’m my own best friend!
9.
10.
11.
12. 11 strategies you should consider as part of your migration planning Understand the as-is and to-be environments Conduct proper capacity planning Understand the customizations on your source system Understand the migration schedule Plan for the right kind of migration Plan for file shares Plan for tagging, metadata, and taxonomy Understand centrally managed and decentralized environments Stage your platform for migration Decide where and when to involve the users Determine that your migration is successful
18. What are the organizational “must have” requirements
19.
20. Strategy #1: Understand as-is and to-be environments Anders Rask, Upgrading SharePoint 2007 to SharePoint 2010
21. Strategy #1: Understand as-is and to-be environments What is your goal? What is your mission statement (Just kidding) What are you key use cases? What are your priorities?
22.
23. It’s as much about retooling current sites and content as it is about deploying new technology
90. Clean and organize content first, then move to a new structure in SharePoint
91. Migrate content in waves, using the iterations to sort through and organize your content while in transit, moving some content as-is, reorganizing and transforming othersTo be honest, option 3 is very difficult to manage in SharePoint, but 3rd party tools do a great job here
93. Strategy #7: Plan for tagging, metadata, and taxonomy In Biology, taxonomy is the science dealing with the description, identification, naming, and classification of organisms. “however, the term is now applied in a wider, more general sense and now may refer to a classification of things, as well as to the principles underlying such a classification.” “Metadata provides context for data. Metadata is used to facilitate the understanding, characteristics, and management usage of data. The metadata required for effective data management varies with the type of data and context of use.”Wikipedia.org
98. Authors don’t apply metadata= “shotgun” approach to search OR Authors apply metadata without common classification = better search, but worse authoring experience
101. As a result, poor portal adoption and low user satisfactionStrategy #7: Plan for tagging, metadata, and taxonomy
102. Strategy #7: Plan for tagging, metadata, and taxonomy What is your broader strategy for tagging, metadata and taxonomy?
103. Strategy #7: Plan for tagging, metadata, and taxonomy Map out your high level taxonomy (web applications and site collections) and schemas (Content Types) Understand the as-is and to-be, and how it relates to your metadata With Managed Metadata Service in 2010, it is critical that you set up a governance model to guide this process, or it will quickly get out of hand
105. Strategy #8: Understand centrally managed and decentralized environments Where does innovation come from in your organization? What is the intent of your system? How you architect your solution will impact how you migrate your current environment
109. Sites and Site Collections can consume these services, within certain boundariesYou still need to understand the administrative impacts You need to clearly define roles / service owners Define your governance model / change control board
119. Strategy #10: Decide where and when to involve users Strategy #10: Decide where and when to involve users
120. Strategy #10: Decide where and when to involve users This is the most fluid of the strategic considerations, as it really just depends At a high-level, end users who participate in the creation of a system are more likely to accept / support that system once deployed
137. Please be sure to fill out your session evaluation! Drop me a line at cbuck@axceler.comVisit my blog http://buckleyplanet.netFollow me @buckleyplanet
I was going to include a picture of Brad Pitt, but then I thought – ok, maybe not that cool.
“While Microsoft can provide options for automating migration, these options work best with implementations which have no customizations and a simple structure.” Stephen Cummins, echoTechnologyThe challenge is to do this quickly, so that you minimize user impact and environment downtime.
SharePoint 2010 replaces the SSP concept with service applications, each creating several databases. These services include Search Service application User profiles Service application Excel Service application App Registry (for backwards compatibility)(Joel Oleson, SharePoint 2010: Best Practices to Upgrade and Migrate, pg. 69)Visual Upgrade includes three options: Display the previous UIPreview the new UI Use the new UI
Microsoft’s easy-to-follow guides. Point and click.There are a number of risks with In Place upgrade: 1) your system will be down, and if the migration does not go well – it could be down for a while 2) disk space will be impacted. You really don’t know how much space is needed 3) no rollback. Doh!With either migration method, you do have a Visual Upgrade, which basically replaces your gradual upgrade in 2007. This allows you to migrate, and through Central Administration, preview your 2007 sites in the 2010 template before committing yourself to it. So you can keep what works, and slowly make the changes over time.
My background is technical project management. My company comes from a service background, and our team has participated in hundreds of migrations. From this experience, we’ve created a list of strategic considerations that will help ensure that your migrations are successful.I’d like to walk through them in detail, and I want your thoughts and feedback.And up front, aside from this presentation being available post-conference, I’d like to provide you with a free download of our 11 Strategic Considerations Checklist.
Before I go through this list, I would like to point out that many of these items have circular dependencies. They need to be done in parallel. They’re not meant to be run in order necessarily, but to help guide your planning activities and make your plan more robust and thorough.
Refer to ondemand event by Dux Raymond Sy about SharePoint project planning
Refer to ondemand event by Dux Raymond Sy about SharePoint project planning
There is some consideration of in-place versus database attach, or some hybrid approach.
A strong value proposition of SharePoint is the ability to better organize your content, improve discoverability, and clarify authorship and accessibility by mapping to SharePoint’s permissions. However, one of the primary reasons for delaying a file share migration is the need to go through and “clean up” content so that it can better fit into the SharePoint paradigm. As with any spring cleaning, migrating your file shares presents an opportunity for users and administrators to clean up document versions, reorganize folder structures, clarify content ownership, and update relevant metadata. But is it easier to clean up this content inside or outside of SharePoint?
Why a tortoise? This big guy is from the Galapagos Islands. I was thinking about Darwin’s classification of animals on the islands. Well – specifically, I was thinking about the movie Master and Commander with Russell Crowe and how they stopped on the islands and then had discussions about Darwin, classifications and taxonomy… but that’s neither here nor there.
More of a centrally managed portal, where innovation is more managed as a process?A decentralized model where innovation is driven from the bottom up by the end users?