1. What you need to know before
upgrading
SharePoint 2010
Feb 2012
Prepared By: Suzanne George
Suzanne.George@perficient.com
Sr. Architect
Perficient - Microsoft West Region

3. About Perficient
Leading Technology Consulting & Solutions Firm
• Founded in 1997
Project size, Breadth of Expertise
• $240MM+ in annualized Revenue
• Over 1,400 highly-experienced Consultants
• 19 Locations across North America
• 80+% of Revenue from recurring Clients
• Served over 400 Clients in past 12 months
Software Solutions Expertise, including:
• Enterprise Portals & Content Management
• SOA, EAI and BPM
• e-Commerce and Product Information Mgmt Depth of Expertise, Efficiency & Value,
• Business Intelligence/ETL Client Importance
• Customer Relationship Management
• User Experience/UCD
• Significant Integration Expertise
Key Differentiators
• Focused expertise, lower cost, faster time-to-value
• IT Solutions with Business Focus
• National consultants overlay Local delivery model
• Mature, proven Project Methodology
• Global Development Centers in China & Europe
• Healthcare Thought Leadership
3

4. Agenda
• Learn
• Build a business justification
• Develop a roadmap
• Governance
• Plan / Test / Implement
• Validate
• Evolve
• Summary
4

5. Know your SharePoint..
The more you understand the new features of SharePoint
and its improvements/features the smoother your upgrade
will be.
• Key point to remember
– SharePoint is an enabling framework which connects the
Microsoft Product line such as SQL Server, Project Server,
etc.
• Know your SharePoint
– Terminology
• http://msdn.microsoft.com/en-us/library/ee556558.aspx
– Versions - go beyond „cool‟ and determine what you need
• Which version do I need? CALs?
• http://sharepoint.microsoft.com/en-us/buy/Pages/Editions-
Comparison.aspx
– Features – which features will be implemented when?
• Use the crawl, walk, run methodology
– Physical location – Will the farm be hosted or in-house and
what will the SLA be?
5

7. Roadmap Planning
Define the business roadmap – The key to minimize risks and
surprises is planning. In most cases the SharePoint upgrade is
not a “double-click” process.
If you fail to plan, then you plan to fail!
• Run a cost-analysis to understand the cost-benefit of
upgrading. Stay focused! SharePoint is a framework
and contains lots of features – prioritize those benefits!
• Training, training, training!! Your staff need to either a)
have months to research (ie: Bing!) how to handle the
upgrade or you need to get training. This includes
Administrators, Developers, End-Users, etc.
• Inventory your current system – take time to look at
your current system (even if it is paper-based) and
determine what features of 2010 you will need to
implement, then update your project plan.
• Have a backup plan – Things happen, take longer, and
don‟t work as expected so plan for Murphy should the
worse case scenario happen. Further, at each project
milestone meet with all parties to discuss Go-no-Go.
• Get a second line of defense – In other words find
someone who has done this before.
7

8. Costs involved
What is the costs involved to upgrade? Answer: Depends…
• SharePoint 2010 licensing
– depends on your version …
– Cost calculator by Bamboo
http://community.bamboosolutions.com/blogs/sharepoint-
2010-price-calculator/default.aspx
• Hardware upgrade needs
– do you need to upgrade your hardware to 64 bit? Memory?
– Development environment
– UAT/staging environment
– Production environment
• Development Tools
– Visual Studio 2010, TFS 2010, ReSharper, SQL server
2008R2
– Migration tools – roll your own or use 3rd party product?
– Upgrade desktops/laptops/etc
8

9. Cost continues
Often forgotten or not defined costs…
• New installation budget 25 man weeks of effort for a
basic install / configure
– Project management, basic governance
– Development – design, integration, code, QA
– Administration
• Custom webparts
– Custom webparts – budget 1-2 weeks for each (some will
take less, some will take more)
• Administration
– Migration of data – depends on upgrade method – budget
2+ weeks depending
– Are you restructuring your site map?
• Consultants
– Do you need extra resources to make this happen
– The unexpected consultant - “The Wolf”
• UAT / QA testing
– Users of the application testing
– Load testing/performance
9

10. SharePoint Roadmap Process
Education and Business Analysis Technical Analysis Roadmap
Demonstrations Development
•Generic •Gather and •Understanding •Prioritize
Overview of analyze: of current contextualized
SharePoint •Information application requirements
•Specific review used in daily portfolio •Assignment of
of relevant activities •Review of projects into
functionality •Internal and Architectural program plan
•Anecdotal external user standards •Risk mitigation
evidence of groups •Map and benefit
relevant best •Operational requirements to analysis
practices and system technologies •Estimate phase
procedures interaction dependencies
and durations
Gain Understanding of Requirements Applied
SharePoint to SharePoint Context
Organizational Needs Clear Vision Developed
Defined and Presented
10

11. An example roadmap
Q1 Q2 Q3 Q4
Roadmap Planning, Communication and Oversight
Foundation (Global Support)
• Functional Use Cases / Wireframes • Technical Architecture (Prod, QA, Dev)
• Program Planning • Branding Standards
• Governance • Development Standards
• Information Architecture • Security Model
• Taxonomy • DR, HA and Archive Architecture
• Multilingual Architecture • User Acceptance Planning and Testing
• Base Site Structure
• Search
• UX Branding Migration (SharePoint 2010)
• Training Plan • Current State Content and Customization Analysis
• Organizational Plan • Current State Security and Access Model
• Communications Plan • Current State Data Usage and Access Analysis
• Usage Questionnaire Completion
• Foundation Gap Analysis
Value Applications
• Migration Plan
• Migration Execution • Transaction Integration
• Migration Acceptance Testing • Business Intelligence
• BPM
• Search Results
• Personalization
Transition
• Notes Applications • Performance Testing
• CRM • Go Live Planning and Support
• Extranet /Internet • User, Admin and Dev Training
• RIA • User, Admin and Dev Doc’s
• Mobile • Production Support
11

12. Prioritized / Risk Adjusted Requirements Example
12

13. Example of a migration project plan
13
2011 Perficient, Inc. All rights reserved.

14. Governance
SharePoint can make a good process better and a bad
process worse…
• What is governance?
– Policies, roles, responsibilities, and processes that
guide, direct, and control how an organization's business
divisions and IT teams cooperate to achieve business goals.
• Define business process first – implement second
– Organizations try to implement SharePoint 2010 to solve
business processes which have not been defined yet.
• Don‟t get complicated – keep it simple, improve and
add as business needs require.
• MSDN has a good governance policy you can modify
– http://technet.microsoft.com/en-us/library/cc262900.aspx
• Hire a consultant?
14

15. Preparation - Find issues before you upgrade
Issues do not disappear when you upgrade, make sure
they are resolved (if possible) in your current
environment.
• Verify your existing SharePoint 2007 environment is up
to date with patches
• Use the pre-upgrade check on your existing system and
resolve any issues – check for missing features and
custom field errors
• Check for broken links in existing sites
• Review and identify all customizations – make sure you
have the code and/or installer for each!
• Optimize your large lists
• Optimize your content databases
• Upgrade to 64 bit environment
• Understand any/all UI changes and authentication
methods
15

16. Upgrade Philosophy
Some ideas which will help you during the upgrade
process
• Detect and Discuss issues early
– Report critical issues early
• Do NOT implement a solution which will lose data
– Keep as much of your content and settings as possible
• Minimize downtime
• Continue when possible
• Be reentrant
• Keep the administrator / architect informed
16

17. Content Migration Methodology
Content Proposed
Content Approved Map to Platform Current State
Analysis Migration Legacy Content
Valuation To (Gap Analysis)
Report Inventory List Transformation
Process Migrate Taxonomy, Pages, Documents,
Assets, Tools
Include HTM and
Content asset URLs
Active Content Identification
Content
Metadata
Migration
Content
Mgmt.
Tools
Publishing Content Owners
Staging Content <<Lead – Content Analyst>> Platform
Authoring Team; Web
Managers; QA Team; Readiness
Migration Tech Lead Platform Architects
Governance Development Lifecycle
1
WIP Content <<Lead – Platform Leadership>> Content Owners
IT Team Deployment Lifecycle
<<Leads – Business Analyst,
Taxonomist, CMS Architect,
Approval Lifecycle
Production Platform
5
Dev Leads>>
2 Migration
WCM Test
Drive
Process
404 Validation & Lifecycle
Legacy Content Archived
Platform
Ready
3
Content Migration 4 Content
Processing Preparation
Nav
Migration Tech Team;
Metadata Migration Authoring
Taxonomy GWO / IT
Team; QA Team
Master
<<Lead – CMS Migration Process Leader>> Inventory
Content /
<<Lead – Legacy Content Architect>> List
Assets
Documents
CMS Platform Iterations
Manual content
authoring
Prepare Migration {Client} HTML
Release Change Asset & Content Validate, Correct,
Preparation Processing
Final Quality Set – for publishing Import Transform and
Complete Evaluation
Assurance to the runtime Processing Chunk Tag
repository (if Processing
Quality Assurance Page
needed) on migration Exceptions
content and
attribute tagging CMS Import Tools
17
2010 Perficient, Inc. Confidential. All rights reserved.

18. Execute Upgrade / Next Steps
Build / Upgrade Farms Minimize downtime
•Services farm •Use read only with fallback
•Content farm environment
•Build for upgrade parallelism
Deploy customizations Monitor progress
•Use Solutions whenever •Watch upgrade status indicators
possible •Ensure upgrade process is on
schedule
Assessment Maintenance
•Review deployment •Administration
•Review new feature requests •Development – Bug Fix
18

19. Summary
Path to successful upgrade/implementation
• Learn
• Build a business justification
• Develop a roadmap
• Governance
• Plan / Test / Implement
• Validate
• Evolve
A successful upgrade can only be developed with the
commitment of management and staff.
• Access – provide access to business and technical teams that
have the knowledge to provide the necessary input
• Flexibility – grant flexibility to team members schedules to
attend meetings and collaborate on concepts
• Responsive Decision Making - empower teams to make
responsive decisions on behalf of the organization
• Governance Board – oversight of a governance board to
review and provide direction
• Collaboration – engage in the roadmap process with a highly
interactive approach
19

20. Client Roster
Partial Client List
20

21. www.TriStateSharePoint.org

22. Thank you!
For further information, please contact:
Suzanne George
Suzanne.George@perficient.com
Sr. Architect
Perficient - Microsoft West Region
Twitter: spgenie
22