The document provides information about migrating from SharePoint 2010 to SharePoint 2013. It discusses cleaning up the existing SharePoint 2010 environment by auditing and organizing content, configurations, and customizations. It also covers collecting all visual and data structure customizations. The document outlines the steps to migrate including preparing the new SharePoint 2013 environment, upgrading service applications, creating web applications in 2010 mode, attaching content databases, and testing in 2010 mode. It briefly discusses evaluating sites in SharePoint 2013 mode and finalizing the visual upgrade on a site-by-site basis.

1. C D H
No Data Left Behind: A SharePoint 2013 Migration

2. 11/3/2015 2
C D H
Your Presenter
C D H
Julie Boudro
Master SharePoint Consultant & Technician
JulieB@cdh.com
Julie Boudro
»SharePoint Architect
»julieb@cdh.com
» https://www.linkedin.com/pub/julie-boudro/9/677/143

3. 11/3/2015 3
C D H
Today’s Objectives
»Cleaning house, a review of your existing environment
»Packing up, collecting all customizations
»On the move…to SharePoint 2013
Discussion
C D H

4. C D H
Product Lifecycle
» SharePoint 2003
» SharePoint 2007
» SharePoint 2010
» SharePoint 2010 Mainstream
Support
» SharePoint 2013
» SharePoint 2016
»October 1, 2003
»November 2006
»May 12, 2010
»October 13, 2015
»February 28, 2013
»Q2 2016
Dates of Interest Editions
C D H

5. A review of your existing environment
Cleaning House
C D H

6. 11/3/2015 6
C D H
Cleaning House
»Content
»Customizations
»Farm Configurations
»Logical Structure
»Storage
»Authentication
»Branding
Taking Inventory
C D H

7. 11/3/2015 7
C D H
Cleaning House
»Content Audit
» Is there information or sites that
can be deleted
» Inventory types of files
(documents, images, videos)
» Goal is to reduce the overall size of
the database or what is migrated
»Reorganization (upgrades)
» Take the opportunity to break up
large portals into multiple site
collections
» Supports a phased approach for
upgrading
Content
C D H

8. 11/3/2015 8
C D H
Content Planning
Item # Page/Document Name Reference Migrate/Archive/Delete Comments/Notes
1 Corporate Handbook Migrate
2 Benefit summary
Located under HR
network Migrate
Replace with current
year
3 Wellness program information Delete
Program no longer
available
4 Holidays Migrate Listing of dates
5 Paid days off Migrate Listing of dates
6 Company policies Archive
7 Employee Feedback Delete
Content Audit Analysis

9. 11/3/2015 9
C D H
Cleaning House
» Shared Service Providers (2007)
» Service Applications (2010)
» User Profile Properties
» Service Accounts
» Content Databases
» Authentication Provider
» Anonymous Access
» Authentication Types (FBA)
» Blocked file types
» Quotas
» Office Web Apps
» Content sources / Search schema
» Patch level
» Email settings (incoming /outgoing)
Farm Configurations
C D H

10. C D H
Cleaning House
»Number of web applications
»Host name site collections (2010)
»Number of site collections
»Managed paths
»Alternate Access Mappings / IIS
Bindings
»Database sizes
» Double disk space
»Search Index
»Logs
Logical Structure Storage
C D H

11. C D H
Cleaning House
»Kerberos
»Windows Classic (2007 / 2010)
»Forms based authentication
»Custom membership providers
»Third party solutions
»Custom master pages
»Custom page layouts
»CSS / Images
»JavaScript
Authentication Branding
C D H

12. 11/3/2015 12
C D H
Cleaning House
»2010 Document Farm configuration using PowerShell
» https://technet.microsoft.com/en-us/library/ff645391.aspx
» Upgrade planning worksheet for 2013
» http://www.microsoft.com/en-us/download/details.aspx?id=30370
Tools
C D H

13. Collecting all customizations
Packing Up
C D H

14. C D H
Packing Up
»Master pages
»Themes
»Web Pages
»Web Parts
»Custom JavaScript
»Custom CSS files
» Should not affect database
upgrade.
» For site upgrades: likely to
work well in 2010 mode, but
need changes to work in 2013
mode.
» Test carefully in both modes.
Visual Customizations Impact on Upgrade
C D H

15. C D H
Packing Up
»Content types
»List types
»Web Template
»Site definitions
»Unghosted pages
»Can affect database upgrade
if content or list type names
conflict with new content or
list types in the product, or if
templates or definitions are
missing.
Data structure affecting Impact on Upgrade
C D H

16. C D H
Packing Up
»Web services
»Windows services
»HTTP handler
»HTTP module
»Might not be compatible with
SharePoint 2013.
»Test carefully to determine
effect.
»Be prepared to remove or
replace.
Non-visually affecting Impact on Upgrade
C D H

17. C D H
Packing Up
»Third-party add
on’s
»Custom
development
»Farm solutions
»Needs to be upgraded to
new version
»Might not be compatible in
the cloud
»Upgrade & redeploy
Custom Development Impact on Upgrade
C D H

18. 11/3/2015 18
C D H
Packing Up
»Is the customization still
valuable?
»Is the customization well-
designed?
»Keep the customizations, don't
upgrade the sites
»Replace or redo the
customizations
»Discard the customization
Evaluating Customizations
C D H

19. 11/3/2015 19
C D H
Packing Up
» Get list of farm features
» Get-SPFeature | Export-Clixml .Get-SPFeature.xml
» Get list of farm solutions
» Get-SPSolution | Export-Clixml .Get-SPSolution.xml
» Export Farm solutions
» (Get-SPFarm).Solutions | ForEach-Object{$var = (Get-Location).Path + “”+ $_.Name;
$_.SolutionFile.SaveAs($var)}
» Identify missing files
» Test-SPContentDatabase
Tools
C D H

20. 11/3/2015 20
C D H
Packing Up
Creating a customization plan
»https://technet.microsoft.com/en-us/library/cc263203.aspx
Branding Implications
»https://technet.microsoft.com/en-us/library/dn178510.aspx
Resources
C D H

21. C D H
Break

22. SharePoint 2013 and beyond
On the move

23. C D H
On the move
»SharePoint 2003/2007
»SharePoint 2010 to O365
»SharePoint 2010 to 2013
»SharePoint 2013 to O365
»Migrate
»Migrate
»Upgrade
»Migrate
Upgrade or Migrate Best approach
C D HC D H

24. C D H
On the move
»Reorganization
»Staged approach
»Change information architecture
»Bring only what’s relevant
»Third party tool required
»Doesn’t include custom
solutions
»Doesn’t migrate all service
applications
Migration Pros Migration Cons
C D H

25. C D H
On the move
»Prepare the environment
»Site customization planning
» Removed, Redone, Updated
»Security model
»Storage allocation
»Communication Plan
»Develop a migration plan
» Determine site structure
» Data to be migrated
» Is the meta data changing
» Reorganization
» List template remapping
(O365)
Migration Steps
C D H

26. C D H
On the move
» License Model
» Tenant & site collection structure
» Custom development
» Service Applications impact
» Search
» Managed Metadata
» BDC
»Active Directory Integration
»Lightweight administration
»No server side code – CSOM
»No vanity URLs
O365 Considerations
C D H

27. C D H
On the move
»MetaVis
»ShareGate
»AvePoint
»Dell Migration Manager
»Manual migration
Migration Tools
C D H

28. C D H
On the move
»No in-place upgrade
»Environment preparation
» New SQL Server / Instance
» New Web Servers (no more
standalone installations)
» New SharePoint Service Accounts
»Reorganization
»Customizations
»Visual Redesign
»Database backups
»Classic to Claims
»2010 & 2013 Hive
Upgrade Preparation
C D H

29. 11/3/2015 29
C D H
On the move
» 500 users or less
» 2 drives, 100 GB each
» Two-tier server farm
» 64-bit, 4 cores
» SQL 2008 R2 with SP1
» Windows Server 2012
Environment Specifications – Small Farm Server A
Web Front End
12 GB Ram
Server B
Batch processing
20 GB Ram
Server C
SQL Server
32 GB Ram
C D H

30. 11/3/2015 30
C D H
On the move
» 4,000 users or less
» 2 drives, 200 GB each
» Three-tier server farm
» 64-bit, 4 cores
» SQL 2008 R2 with SP1
» Windows Server 2012
Environment Specifications – Medium Server A
Web Front End
12 GB Ram
Server B
Batch processing
20 GB Ram
Server C
SQL Server
32 GB Ram
Server A
Web Front End
12 GB Ram
C D H

31. 11/3/2015 31
C D H
On the move
» 8,000 users or less
» 2 drives, 200 GB each
» Three-tier server farm
» 64-bit, 4 cores
» SQL 2008 R2 with SP1
» Windows Server 2012
Environment Specifications – Large
SharePoint Web Front End Servers
Index Server Distributed
Cache
Central Admin
Service Apps
SharePoint Application Servers
SQL Cluster
C D H

32. 11/3/2015 32
C D H
On the move
1. Install SharePoint Farm
2. Configure Managed Accounts
3. Start the necessary services
» If you are upgrading search database, search will not start via the Services
on Server
» Must use PowerShell
Upgrade Steps
C D H

33. 11/3/2015 33
C D H

34. 11/3/2015 34
C D H
On the move
$SearchInst = Get-SPEnterpriseSearchServiceInstance
# Stores the identity for the Search service instance on this server
as a variable
Start-SPServiceInstance $SearchInst
# Starts the service instance
Starting Search Service (upgrade step only)
C D H

35. C D H
On the move
4. Upgrade Service Applications
» Not all can be upgraded
» Decide to recreate or start new
» PowerShell or GUI
» Secure Store
» Business Data Connectivity (Secure
store must be upgraded first)
» Managed Metadata Web
» PerformancePoint Services
» User Profile
» Search
Upgrade Steps Service Applications
C D H

36. 11/3/2015 36
C D H
On the move
1. Restore SQL backup to empty database
2. PowerShell to create, attach, upgrade Service Application,
» PowerShell to create proxy
3. OR, Can use Central Admin
» Create Service Application, specify application pool
» Enter the restored database name
4. Upgrading Service Applications
C D H

37. 11/3/2015 37
C D H
Same name as
restored DB

38. 11/3/2015 38
C D H
On the move
»Set Application Pool Account
$applicationPool = Get-SPServiceApplicationPool -Identity
'SharePoint Web Services default‘
»Creating Service Application / Upgrade
$sss = New-SPSecureStoreServiceApplication -Name 'Secure Store'
-ApplicationPool $applicationPool -DatabaseName
'SecureStore_Upgrade_DB' –AuditingEnabled
Tools – PowerShell Create/Upgrade Service Applications
C D H

39. 11/3/2015 39
C D H
On the move
»Creating Proxy
$sssp = New-SPSecureStoreServiceApplicationProxy -
Name ProxyName -ServiceApplication $sss -
DefaultProxyGroup
»Upgrade Service Applications Reference
» https://technet.microsoft.com/en-us/library/jj839719.aspx
Tools
C D H

40. 11/3/2015 40
C D H
On the move
5. Deploy features/solutions to the farm
6. Create 2010 Mode Web Applications
» Must be done via PowerShell
» Can be Classic or Claims
7. Attach content databases
» Will act as a fully functioning 2010 Site.
Upgrade Steps
C D H

41. 11/3/2015 41
C D H
On the move
PowerShell to Create 2010 Classic Web Application
New-SPWebApplication -name "ClassicAuthApp" -Port <XX> -
ApplicationPool "ClassicAuthAppPool" -ApplicationPoolAccount
(Get-SPManagedAccount "<domainname><user>")
Test Content Database
Test-SPContentDatabase -Name DatabaseName -WebApplication URL
Tools
C D H

42. 11/3/2015 42
C D H
On the move
Attach Database (will perform an upgrade to 2013 – not visually)
Mount-SPContentDatabase "<ContentDb>" -DatabaseServer
"<DbServer>" -WebApplication http://SiteName
Tools
C D H

43. 11/3/2015 43
C D H
On the move
»Before attach – impact on end users during cut over
»After attach – ability to test
»Cannot create classic web applications via GUI in 2013
8. Convert classic to claims
C D H

44. 11/3/2015 44
C D H
On the move
Convert Web Application to Claims
Convert-SPWebApplication -Identity <yourWebAppUrl> -
To Claims -RetainPermissions [ -Force]
Tools
C D H

45. 11/3/2015 45
C D H
On the move
9. Test (2010 Mode)
» User Access
» Forms / Workflow
» Custom solutions
10.Request evaluation site
collection
Upgrade Steps
C D H

46. 11/3/2015 46
C D H
On the move
»Trial run of the 2013 visual elements
»2010 master pages DO NOT WORK AT ALL
»Custom code running in 2013 mode
»Site Collection by site collection
»Full duplicate size of content database
Evaluation Site Collection
C D H

47. 11/3/2015 47
C D H
On the move
»Greater than 100 GB must be done via PowerShell
»Will lock the site collection during the request = no
access
»Deleted automatically after 30 days
»Timer job runs nightly at 1:00
Evaluation Site Collection
C D H

48. 11/3/2015 48
C D H
On the move
12.Test 2013
13.Finalize visual upgrade on a site collection by site collection
basis
Upgrade Steps
C D H

49. What’s New in 2013 & 2016
Sneak Peak

50. C D H
What’s New
»Content Search
»Community Sites
»Hybrid configurations
»Mobile touch
»Design manager
»Cross site publishing
»Streamlined patch
management
»Role based installations
»Template based site creation
What’s New 2013 What’s New in 2016
C D H

51. C D H
Sneak Peak

52. C D H
Sneak Peak
Administration Compliance
C D H

53. C D H
Sneak Peak
App Launcher

54. 11/3/2015 54
C D H
Sneak Peak
»http://www.microsoft.com/en-
us/download/details.aspx?id=48712
Download 2016 Today!
C D H

55. C D H
Thank you!