Home >Documents >#EuropeanSP--11 Strategic Considerations for SharePoint Migrations

#EuropeanSP--11 Strategic Considerations for SharePoint Migrations

Date post:08-Dec-2014
View:2,162 times
Download:5 times
Share this document with a friend
  • 1. 11 Strategic Considerations for SharePoint MigrationsChristian [email protected] @buckleyPLANET

2. My BackgroundChristian Buckley, Director of Product Evangelism at Axceler Most recently at Microsoft Microsoft Managed Services (now BPOS-Dedicated) Advertising Operations, ad platform API program Prior to Microsoft, was a senior consultant, working in the software, supply chain, and gridtechnology spaces focusing on collaboration Co-founded and sold a collaboration software company to Rational Software. Also co-authored3 books on software configuration management and defect tracking for Rational and IBM At another startup (E2open), helped design, build, and deploy aSharePoint-like collaboration platform (Collaboration Manager), managingdeployment teams to onboard numerous high-tech manufacturing companies,including Hitachi, Matsushita, Seagate, Nortel, Sony, and Cisco I live in a small town just east of Seattle, have a daughter in college and 3 boys at home 3. Axceler Overview Improving Collaboration for 16+ Years Mission: To enable enterprises to simplify, optimize, andsecure their collaborative platforms Delivered award-winning administration and migrationsoftware since 1994 Over 2,000 global customers Dramatically improve the managementof SharePoint Innovative products that improve security, scalability,reliability, deployability Making IT more effective and efficient and lower the totalcost of ownership Focus on solving specific SharePoint problems(Administration & Migration) Coach enterprises on SharePoint best practices Give administrators the most innovative tools available Anticipate customers needs Deliver best of breed offerings Stay in lock step with SharePoint development and market trends 4. Why is this presentation important? Most content focused on the technical aspects of migration Migrations are not so much about the technical act of movingthe data (although very important), but more about the planningthat goes into preparing for the migrationEmail CellTwitterBlog 5. Email 10/19/2011 Cell Twitter Blog 5 6. Despair.comEmail 10/19/2011 Cell Twitter Blog6 7. This is your technical migration, i.e. thephysical move of content and bitsEmailCell [email protected] 425.246.2823 @buckleyplanet http://buckleyplanet.net 8. This is the bulk of your migration the planning,reorganization, andtransformation of your legacy SharePointenvironment10/19/20118 9. What is migration? Microsoft defines migration as three separate activities: MoveMigrateUpgrade Use the procedures for Use the procedures for Use the procedures for moving a farm ormigrating a farm orupgrading a farm or components when you components when youcomponents when you are changing to different are changing to aare changing to a hardware. For example,different platform ordifferent version of use these procedures if operating system. ForOffice SharePoint Server you move to computers example, use these 2007. that have fasterprocedures if you processors or larger hard change from Microsoft disks.SQL Server 2005 to SQL Server 2008. The reality is that a single migration may includeall three concepts 10. What is migration? 11. Why migrations are difficult:MigrationsMigrationsMigrations are Migrations areare phased are iterative error pronenot the end goal How and what you Your planning should not There is no easy button Proper planning andmigrate should not bebe limited by the number for migration. You can run change managementdetermined by theof migration attempts youa dozen pre-migrationpolicies will help you to betechnology you use itsmake, or by the volume ofchecks and still run intosuccessful with yourabout matching the needs content being moved. A problems. Admins and end current and futureand timing of your content healthy migrationusers do things that are migrations. The goalsowners and teams. Arecognizes the need to not by the book. should be a stablemigration should betest the waters, to move Customizations. Thirdenvironment, relevantflexible, moving sites and sites, content and party tools. Line of metadata, discoverablecontent based on end usercustomizations in waves, business applications that content, and happy endneeds, not the limitations allowing users to test and run under the radar. users.of the technology. provide feedback. 12. What are the Microsoft options? 13. EmailCell [email protected] 425.246.2823 @buckleyplanet http://buckleyplanet.net 14. EmailCell [email protected] 425.246.2823 @buckleyplanet http://buckleyplanet.net 15. EmailCell [email protected] 425.246.2823 @buckleyplanet http://buckleyplanet.net 16. For more information Contact me at Christian Buckley, [email protected], 425-246-2823 On Twitter at @buckleyplanet Resources available from Axceler.com White papersMastering SharePoint Migration PlanningThe Insiders Guide to Upgrading to SharePoint 2010What to Look for in a SharePoint Management ToolThe Five Secrets to Controlling Your SharePoint Environment Tools ReadyPoint (free) Davinci Migrator echo for SharePoint 2007 17. EmailCell [email protected] 425.246.2823 @buckleyplanet http://buckleyplanet.net 18. 11 strategies you shouldconsider as part of yourmigration planning1.Understand the as-is and to-be environments2.Conduct proper capacity planning3.Understand the customizations on your source system4.Understand the migration schedule5.Plan for the right kind of migration6.Plan for file shares7.Plan for tagging, metadata, and taxonomy8.Understand centrally managed and decentralized environments9.Stage your platform for migration10. Decide where and when to involve the users11. Determine that your migration is successful 19. Strategy #1:Understand as-is and to-beenvironmentsEmail Email Cell Twitter CellTwitterBlog Blog 20. Strategy #1: Understand as-isand to-be environmentsA migration is an extensive business analyst activity Prior to any system redesign, understand yourenvironmentgoals and purpose: What works What doesnt work What are the organizationalmust have requirements What are the nice to have features Based on these requirements, you need to model outthe to be environment 21. The tendency is to jump to solutionsbefore you understand the problem 22. 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? 23. Strategy #1: Understand as-is and to-be environments Migration is about transformingyour existing system to meetoperational needs. Its as much about retooling current sites andcontent as it is about deploying newtechnology Dont just tear down and rebuild if theressomething to be saved. Understand what youhave to work with, have a vision for what itshould look like, and move the pieces thatshould be moved 24. Strategy #2:Conduct propercapacity planning10/19/201124 25. Strategy #2: Conduct proper capacity planning Understand your current environment: Number of users Number of sites Number of site collections Database size Geographical needs of your organization (how many sites, what are their usage patterns) Line of business application integration 26. Strategy #2: Conduct propercapacity planning Think about your future needs: User growth Estimates on site creation Estimates on database growth Security and Search needs 27. Strategy #2: Conduct propercapacity planning Map out your: Hardware Topology Performance requirements Security requirements Scalability Disaster recovery Business continuity 28. Strategy #3:Understand thecustomizations on yoursource system 10/19/201128 29. Strategy #3: Understand the customizations on your source system Pre-Upgrade Check provides some of the analysis: Searches content sources and start addresses Outlines Office Server topology Identifies servers in the current farm Lists SharePoint version and list of components running in the farm Outlines supported upgrade types Provides Site Definition and Feature information Details language pack information Identifies Alternate Access Mappings that will need to be recreated Outlines Customized List Views (these will not be upgraded) Outlines Customized Field Types (these will not be upgraded) Identifies WSS Search topology Provides list of Content Databases and SQL server locationJoel Oleson, SharePoint 2010: Best Practices to Upgrade and Migrate 30. 10/19/2011 31. Strategy #3: Understand the customizations on your source system What kinds of customizations are on your source system? UI design Web parts Workflows Line of business applications 3rd party tools Custom features Site definitions Field types Custom SharePoint solutions Any changes to the file system on your SharePoint servers Pre-Upgrade Check provides some of the analysis How many of those customizations areoutside of the SharePoint framework? Are there any customizations which canbe replaced by out-of-the-box functionality? 32. Strategy #4:Understand the migration schedule10/19/201132 33. Strategy #4: Understand the migration schedule What are the business drivers, not just thetechnology drivers? Cost Time Resources/People Do you have a defined project methodology? How long per phase, what is moved,what are the priorities? The schedule should be defined only after you understand the future state, setpriorities, and get management buy-in. In short, what is the scope? 34. Strategy #5: Plan for the right10/19/2011 kind of migration34 35. Strategy #5: Plan for the right kind of migration Does the migration plan include content, sites, metadata,and/or solutions? Each one brings with it a set of requirements and decisions What is the end goal? Is it a straight dump of everything, andyoull clean up later, or do you need to restructure? Is your strategy the same for various organizations, differentsite collections, or farms? 36. St

Popular Tags:

Click here to load reader

Embed Size (px)