Canberra SPUG - February 2014 - Pitfalls of Migrating to SharePoint 2013


Published on

Organisations of all sizes are begging their technical departments to setup SharePoint 2013 (and in some cases 2010!) so that they're able to make use of some of the capabilities introduced within the SharePoint platform. While designing, implementing, configuring and deploying a system in and of itself has its own set of challenges, migrating into that shiny, new environment can be even more difficult.

In this session, Scott Hoag will share some of his experiences and lessons learned tips, tricks and pointers for ensuring that you've considered the various aspects and challenges that arise during a migration effort. Further, as a bonus we’ll discuss strategies for how to not fall prey to some of these pitfalls, but demonstrate that you're a well-rounded professional that's thought things through before pressing the enter key.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Canberra SPUG - February 2014 - Pitfalls of Migrating to SharePoint 2013

  1. 1. Migration versus Upgrade Why Upgrade? 3rd Party versus OOTB Consolidation Content, Content, Content Authentication User Adoption
  2. 2. transferring data re-engineering product minimizing involve downtime replacement of a
  3. 3. and
  4. 4. must
  5. 5. Version Migration Preparation SharePoint Portal Server 2001 Hire a consultant Consider a 3rd party migration tool Windows SharePoint Services 3.0 Hire a consultant Prescan.exe / / GhostHunter Web Parts Office SharePoint Server 2007 STSADM –o preupgradecheck SharePoint Server 2010 Test-SPContentDatabase cmdlet SharePoint Server 2013 Test-SPContentDatabase cmdlet Other Resources
  6. 6. Out of the Box In-place upgrade Database Attach 3rd Party
  7. 7. Database Attach Service Applications New hardware Only Access Services Business Data Connectivity* Excel Services Managed Metadata Performance Point Search Service Secure Store State Service Usage and Health Data User Profile Service Visio Graphics Web Analytics Word Automation Hybrid
  8. 8. Do you have existing systems / applications that will also be migrated into SharePoint? Do we need to (un)consolidate? Does your existing taxonomy fit in the new system? Customisations
  9. 9. How much data we have and where does it reside? Considerations for Search Does your content need to change in the new system?
  10. 10. Identify 3rd party tools/web parts/etc. that are installed in your current farm Don’t forget your non-SharePoint data… Lotus WebSphere Drupal DotNetNuke Alfresco Legacy HTML Non-OCR’d Text Documents Orchard
  11. 11. Classic AuthN Claims AuthN and AuthZ Integrated Windows AuthN with NTLM / Kerberos Forms Based AuthN Trusted Identity Provider (aka SAML & WS Fed)
  12. 12. $> i:0#.w|claimprovider|useraccount != i:0#.f|claimprovider|useraccount
  13. 13. Office Clients
  14. 14. YES!
  15. 15. …so far, the Universe is winning.
  16. 16. Geoff Evelyn - Sample Project Plans Technical Diagrams for SharePoint 2013 Hardware and software requirements for SharePoint 2013 Upgrade Service Applications to SharePoint 2013 Migrate from classic-mode to claims-based authentication in SharePoint 2013 Checklist for database-attach upgrade (SharePoint 2013) Claims Based AuthN Resources (TechNet Wiki) Plan for user authentication methods in SharePoint 2013 Discover SharePoint Productivity Hub Office 365 Change Management Guide for the Enterprise AIIM Industry Watch – SharePoint 2013