The document discusses several pitfalls to consider when migrating to Microsoft SharePoint 2013. It covers the differences between migration and upgrade, reasons for upgrading like improvements and supportability. Key aspects that need planning include training, communication, content strategy, and user support. Technical requirements for both SharePoint and SQL Server need reviewing. The document also discusses authentication changes, dealing with content, search, and 3rd party tools and data. Careful planning of the project, testing, and mitigation of issues are advised to avoid problems.

1. Pitfalls of Migrating to SharePoint
2013
Scott Hoag
Applied Information Sciences
Gold Sponsors Silver Sponsors Bronze Sponsors

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

4. Data migration is the process of transferring data between storage types,
formats, or computer systems.
System migration involves moving a set of instructions or programs from
one platform to another, minimizing re-engineering.
The term upgrade refers to the replacement of a product with a newer
version of the same product.
http://en.wikipedia.org/wiki/Data_migration
http://en.wikipedia.org/wiki/System_migration
http://en.wikipedia.org/wiki/Upgrade

6. Why Should We Upgrade?
End-user improvements
Architectural considerations
Licensing, Maintenance and
Supportability

8. Do you have a…
 Training Plan
 Communications Plan
 Content Migration Strategy
 User Support Plan
 Business Case

9. Technical Requirements for SharePoint

10. Technical Requirements for SQL
must

11. Platform Considerations
Version Migration Preparation
Other Resources
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
TechNet Documentation (Capacity Planning / Hardware and Software Requirements)
Blogs
Metalogix Migration Expert (no cost)

13. Still more to consider…
SharePoint in the Cloud
Hybrid
Windows Server Support
SQL Server Support
Browser Support

14. Disaster Recovery Impacts
Do you have plans?
Have you tested your plans?
Mirroring? Clustering? Log Shipping?
Regression Plans?

15. 3rd Party Tools versus Out of the Box
Out of the Box
3rd Party

16. Database Attach Upgrade
Only Business Data Connectivity
Managed Metadata
Performance Point
Search Service
Secure Store
User Profile Service

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

20. What About Search?

21. You’re not done yet…
3rd Party Tools
Non-SharePoint Data

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

23. Why Choose Claims?
It’s the new old shiny
Microsoft recommends it for new implementations
Multiple Authentication Providers – One URL
Handy for extranets and partner access…
Role Based and Attribute Based Access Control
Vive la Fédération!

24. Considerations When Choosing…
Business Functionality Issues with Claims
Additional setup required for IWA Claims
Secure Store can be handy for FBA & SAML
Forms Based AuthN
Your developers should give you a TIP!

25. What is the Impact?
Classic to Classic
Classic to Claims
Client Certificate AuthN

26. AuthN/AuthZ Decisions

28. Pitfall Mitigation Check
Project Plan
Implementation Strategy
Training Plan
Communications Plan
Content Inventory
Defined IA/Taxonomy
Defined AuthN/AuthZ Strategy
Scriptable/Repeatable Process
Tested x3 (at least)
Upgraded Browsers
Upgraded Office Clients
Acquired New Hardware
Built for Extensibility
Aligning to The Business™

29. SharePoint Implementations today consist of a race
between Architects, Developers and IT Pros striving
to build well planned out, bigger and better idiot-proof
solutions, and the Universe trying to produce
requirements of entropy with bigger and better
idiots.
…so far, the Universe is winning.

31. Question and Answer

32. Thanks for listening
Remember to submit your feedback so you go in the draw to win prizes at
the end of the day
Gold Sponsors Silver Sponsors Bronze Sponsors

33. Reference
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