Don't Just Migrate: Transform Your SharePoint Environment - DevConnections Orlando 2011


Published on

SharePoint migration is as much about taking the opportunity to reorganize as it is about upgrading the platform and software. This presentation outlines some best practices for transforming your SharePoint.

Published in: Technology
  • Be the first to comment

Don't Just Migrate: Transform Your SharePoint Environment - DevConnections Orlando 2011

  1. 1. Don't Just Migrate – Transform Your SharePoint Environment<br />Christian Buckley<br />Axceler<br />@buckleyplanet<br />
  2. 2. Christian Buckley, Director of Product Evangelism at Axceler<br /><ul><li>20+ years in hi-tech
  3. 3. Most recently at Microsoft
  4. 4. Microsoft Managed Services (now BPOS-Dedicated)
  5. 5. Advertising Operations, ad platform API program
  6. 6. Prior to Microsoft, was a senior consultant, working in the software, supply chain, and grid technology spaces focusing on collaboration
  7. 7. Co-founded and sold a collaboration software company to Rational Software. Also co-authored 3 books on software configuration management and defect tracking for Rational and IBM
  8. 8. At another startup (E2open), helped design, build, and deploy a SharePoint-like collaboration platform (Collaboration Manager), managing deployment teams to onboard numerous high-tech manufacturing companies, including Hitachi, Matsushita, Seagate, Nortel, Sony, and Cisco
  9. 9. I live in a small town just east of Seattle, have a daughter in college and 3 boys at home, and I just celebrated my 20th wedding anniversary</li></ul>My background<br />
  10. 10. Improving Collaboration for 16+ Years<br />Mission: To enable enterprises to simplify, optimize, and secure their collaborative platforms<br />Delivered award-winning administration and migration software since 1994<br />Over 2,000 global customers<br />Dramatically improve the management of SharePoint<br />Innovative products that improve security, scalability, reliability, “deployability”<br />Making IT more effective and efficient and lower the total cost of ownership<br />Focus on solving specific SharePoint problems (Administration & Migration)<br />Coach enterprises on SharePoint best practices<br />Give administrators the most innovative tools available<br />Anticipate customers’ needs<br />Deliver best of breed offerings<br />Stay in lock step with SharePoint development and market trends<br />Axceler overview<br />
  11. 11. Why Migrate?<br />
  12. 12. This is your technical migration, i.e. the physical move of content and “bits”<br />
  13. 13. This is the bulk of your migration – the planning, reorganization, and transformation of your legacy SharePoint environment<br />
  14. 14. Microsoft defines migration as three separate activities:<br />The reality is that a single migration usually includes all three<br />What is migration?<br />
  15. 15. What is migration?<br />Moving to the latest, greatest platform<br />Transforming what you did with 2003/2007 to meet your organizational vision<br />
  16. 16. Why migrations are difficult:<br />
  17. 17. Managing a migration is kind of like cooking from a recipe<br />
  18. 18. What is the right recipe for your SharePoint migration?<br />
  19. 19. Recipe for Migration Transformation<br />
  20. 20. 5 Ways to Burn Your Toast<br />(or, avoiding the common pitfalls)<br />
  21. 21. Rush through the process<br />
  22. 22. Don’t identify all of your customizations<br />
  23. 23. <ul><li>What kinds of customizations are on your source system?
  24. 24. UI design
  25. 25. Web parts
  26. 26. Workflows
  27. 27. Line of business applications
  28. 28. 3rd party tools
  29. 29. Custom features
  30. 30. Site definitions
  31. 31. Field types
  32. 32. Custom SharePoint solutions
  33. 33. Any changes to the file system on your SharePoint servers
  34. 34. Pre-Upgrade Check provides some of the analysis
  35. 35. How many of those customizations are outside of the SharePoint framework?
  36. 36. Are there any customizations which can be replaced by out-of-the-box functionality?</li></li></ul><li>Treat all sites the same<br />
  37. 37. Don’t test<br />
  38. 38. Go in without a rollback plan<br />
  39. 39. 9 Ingredients for a Gourmet Migration<br />(or, the benefits of transformation)<br />
  40. 40. Consolidated Content Types<br />
  41. 41. It’s basically a definition of an artifact that can be stored in a SharePoint site. For example:<br />A project document, including<br />File type<br />Date created<br />Author<br />Last modified<br />It is part of a workflow, including<br />Who needs to approve<br />Date of approval<br />It includes information management policies that<br />Cannot be edited once approved<br />
  42. 42. Cleaned Folder Structures<br />
  43. 43. Refined Keyword Taxonomy<br />
  44. 44. Standardized site structure and templates<br />Which SharePoint 2010 Site Template is Right for Me? Todd Baginski,<br />
  45. 45. Sub-Site Templates<br />Team Site<br />Blank Site<br />Document Workspace<br />Blog<br />Group Work Site<br />Visio Process Repository<br />Basic Meeting Workspace<br />Blank Meeting Workspace<br />Decision Meeting Workspace<br />Social Meeting Workspace<br />Multipage Meeting Workspace<br />Assets Web Database<br />Charitable Contributions Web Database<br />Contacts Web Database<br />Issues Web Database<br />Projects Web Database<br />Document Center<br />Records Center<br />Business Intelligence Center<br />My Site Host<br />Personalization Site<br />Enterprise Search Center<br />Basic Search Center<br />FAST Search Center<br />Enterprise Wiki<br />Publishing Portal<br />Publishing Site<br />Publishing Site With Workflow<br />
  46. 46. Consistent navigation<br />
  47. 47. Simplified environment<br />MOSS 2007<br />SPS 2003<br />
  48. 48. Tightened permissions<br />
  49. 49. Leverage new functionality<br />Social tools<br />Service applications<br />Displacing custom code<br />Document IDs<br />Document sets<br />
  50. 50.
  51. 51. SharePoint 2010 offers many services OOTB<br />Search<br />Excel Services<br />BCS<br />Project Server<br />Web Analytics<br />Access<br />Performance Point<br />Visio<br />Word<br />Office Web Apps<br />People<br />These centrally managed services allow for greater control across the enterprise<br />Have your cake and eat it through centrally managed services<br />
  52. 52.
  53. 53.
  54. 54. Improved governance<br />
  55. 55. 6 Keys to Reach Outside the Kitchen<br />(or, things that most developers forget to do, but will make your project successful in the long run)<br />
  56. 56. Build your environment with business solutions in mind<br />What is the entire customer experience?<br />Wait staff<br />Hostess<br />Ambiance<br />Décor<br />Reservation process<br />Use cases<br />Recognition that not everything requires a technical solution<br />
  57. 57. Include your end users<br />
  58. 58. Where end users should be involved:<br /><ul><li>Creation of use cases
  59. 59. Creation of as-is documentation
  60. 60. Prioritization of requirements for to-be environment
  61. 61. They know their content – let them drive
  62. 62. File share migrations, or organization
  63. 63. Taxonomy development
  64. 64. Metadata assignment
  65. 65. Signoff on overall project plan</li></li></ul><li>Map out your information infrastructure<br />
  66. 66. Conduct thorough capacity planning<br />Understand your current environment:<br /><ul><li>Number of users
  67. 67. Number of sites
  68. 68. Number of site collections
  69. 69. Database size
  70. 70. Geographical needs of your organization (how many sites, what are their usage patterns)
  71. 71. Line of business application integration</li></li></ul><li>Think about your future needs:<br /><ul><li>User growth
  72. 72. Estimates on site creation
  73. 73. Estimates on database growth</li></ul>Map out your:<br /><ul><li>Hardware
  74. 74. Topology
  75. 75. Performance requirements
  76. 76. Security requirements
  77. 77. Scalability
  78. 78. Disaster recovery
  79. 79. Business continuity</li></li></ul><li>Build out a balanced schedule<br />
  80. 80. <ul><li>What are the business drivers, not just the technology drivers?
  81. 81. Cost
  82. 82. Time
  83. 83. Resources/People
  84. 84. Do you have a defined project methodology?
  85. 85. The schedule should be defined only after you understand the broader plan, set your priorities, and get management buy-in.</li></li></ul><li>Train people on the new platform<br />
  86. 86. In Conclusion…..<br />(or, the last section before the end of the presentation)<br />
  87. 87. Remember, there is no such thing as a homogenous deployment<br />
  88. 88. Your Feedback is Important<br />Please fill out a session evaluation form drop it off at the conference registration desk.<br />Thank you!<br />
  89. 89. Christian<br />Additional Resources <br />Enabling Social Media through Metadata<br />Managed Metadata in SharePoint 2010, Scott Singleton<br />The Battle for Metadata in SharePoint 2010, Michal Pisarek<br />Contact me<br />