This document provides guidance on migrating from previous versions of SharePoint to SharePoint 2013. It discusses the differences between upgrading and migrating, as well as factors to consider such as third party tools, content changes, authentication changes from classic to claims-based, and service application migrations. Resources are provided for planning each type of migration from previous versions to SharePoint 2013.

3. http://www.explainxkcd.com/wiki/index.php?title=1190:_Time

4. Migration versus Upgrade
Why Upgrade?
3rd Party versus OOTB
Consolidation
Content, Content, Content
Authentication
User Adoption

6. transferring data
minimizing re-engineering
involve downtime
product
replacement of a
http://en.wikipedia.org/wiki/Data_migration
http://en.wikipedia.org/wiki/System_migration
http://en.wikipedia.org/wiki/Upgrade

8. and

11. must

12. 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 / ReGhost.net / GhostHunter Web Parts
Office SharePoint Server 2007
STSADM –o preupgradecheck
SharePoint Server 2010
Test-SPContentDatabase cmdlet
SharePoint Server 2013
Test-SPContentDatabase cmdlet
Other Resources

15. Out of the Box
In-place upgrade
Database Attach
3rd Party

16. 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

19. 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

20. How much data we have and where does it reside?
Considerations for Search
Does your content need to change in the new
system?

21. 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

25. Classic AuthN
Claims AuthN and AuthZ
Integrated Windows AuthN with NTLM / Kerberos
Forms Based AuthN
Trusted Identity Provider (aka SAML &
WS Fed)

28. $> i:0#.w|claimprovider|useraccount != i:0#.f|claimprovider|useraccount

32. Office Clients

33. YES!

35. …so far, the Universe is winning.

37. 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