1. | Lausanne Successful Migration to SharePoint 2013 - Planning Considerations & Migration Strategies Roberto V. Delgado Sr. Technical Solutions Professional @AvePoint

2. Agenda Design Goals for SharePoint 2013 5’ Upgrades Farm Upgrade Overview10’ Site Collection Upgrades20’ Upgrade and Migration Strategies5’ General Recommendations10’ Q&A 10’

3. About me: Roberto V. Delgado Roberto.delgado @avepoint.com

4. Design Goals for 2013 Upgrades Safer upgrades Removal of in-place version to version upgrades (Note: Build to build in-place upgrades still work fine) Adding site collection health checks Adding evaluation sites to allow preview of what upgrade will do Reduced outage duration Separating database upgrade from site collection upgrade (*saves ~2/3 upgrade time) Mitigate more outages with read only time providing air cover for operations Power to the people Let site collection admins control their own destiny (*within farm admin controlled limits) Tell users what’s happening using upgrade email messages and system status bar

5. | Lausanne Farm Upgrade Overview

6. Prepare

7. Detach and Re-attach Databases

8. PowerShell Command

9. Recap Upgrade Stages

10. Demo: Farm Upgrade

11. | Lausanne Site Collection Upgrades

12. Deferred Site Collection Upgrade Eliminate big bang upgrades Upgrade database now, upgrade site collections later Keep existing customizations, updated ones can wait Move forward at a manageable pace Initially let users stay with 2010 experience: Stay with the familiar Keep using existing customizations Gradually move users over to 2013 experience: As training occurs (e.g. incrementally for each team) As users decide to adopt new experience/features As new version compatible customizations are available Provide self-service site collection upgrade capability Site collection admins can easily do the upgrade Admins can still do upgrades or prevent users from doing them

13. Site Collection Health Checks Rules can detect and in some cases repair issues Rules can exist for use in 14 and/or 15 modes Same or different rules may apply Can be run without doing upgrade Give advanced notice of potential future issues

14. Evaluation Site Collections Copy of existing site collection Copy not intended for long term use; Evaluation site collection cannot become permanent Version upgraded automatically as default Copy made using snapshot or site collection backup/restore Can only have one evaluation site collection for a given source site collection Self-service creation only for small site collections Maximum size configurable by farm admin controlled web application level settings Large ones need farm admin to do create the evaluation site collection Farm admin can copy any site collection as an evaluation site collection PowerShell command to Request-SPUpgradeEvaluationSite queues creation Evaluation site collections expire Expiration date tracked on each evaluation site collection Expiration date based on creation date and farm admin controlled expiry delay

15. Demo: Site Collection Upgrade

16. Summary of Farm Upgrade

18. | Lausanne Upgrade and Migration Strategies

20. Migration with Third Party Tools ConsPros  Any size environment, from single server farm to large, distributed farms  Restructuring content  Preservation of any metadata or security  Mappings (Templates, users, field types, content types…)  Direct migration from 2007 to 2013  Pre-scan to determine content & customizations  Granular migration  Virtually no downtime  Applicable to non- SharePoint repositories  Incremental migrations  Costs associated with purchasing of additional software  Training Best For SharePoint Administrator installs the new version on separate hardware or a separate farm, and migrates content and users using 3 rd Party Tool

21. Our Strengths: About AvePoint Technologies Services SolutionsPartners CommunitySupport

22. | Lausanne General Recommendations

23. Best practices

24. | Lausanne Q&A