1. 2007 to 2010 SharePoint Migration Don’t Upgrade Your SharePoint Mess! Joshua Haebets Principal Consultant, Evolve Information Services
2. About Me Principal SharePoint Consultant / Solutions Architect Been working with SharePoint since 2006 Been working with 2010 for 11 months Driven by helping address business problems with SharePoint
3. Introduction Audience Administrators Consultants System architects Project managers Team leaders Goals Learn about new SharePoint 2010 features How to get the most out of your migration efforts
4. Why jump to SharePoint 2010? Take advantage of the new features and capabilities Administration BCS Search Content authoring Social features Browser support / compliance Leverage SharePoint for the first time Keep up with the latest, greatest version Infrastructure
5. How do you work? Browse Using navigation (IA is key) Filter what you see Drill in on libraries and lists Search Results are key Search scopes Refiners
6. 2010 - Browsing Find-ability Metadata Navigation Hierarchies Metadata key filters Term Stores and Managed Metadata Filtering Grouping Tagging
7. 2010 - Searching Search Full text search Wildcard search Refiners / Faceted search
8. Metadata Metadata is data about data Content consumption depends on metadata Metadata is the foundation of all information retrieval Metadata involves Definition - which metadata is important Structure – relationship between metadata and sets of values Administration – configuration, management and control Authoring – provide values for your content
9. Managed Metadata Create terms Manage who can change terms Alert on changes Enforce use Tagging Available to everyone Use common terms Not restricted to SharePoint content
17. OOB SharePoint Upgrade Options In Place Upgrade Pros Farm-wide settings are preserved and upgraded Content is preserved Customization will be (may be) upgraded Cons SQL Server and O/S must be 64 bit Whole system has to be offline Junk in Junk Out BEWARE Database Upgrade Pros Can do multiple database upgrades concurrently Original system can be left online (read-only) No 64/32 bit issues Can gradually upgrade site collections (using URL redirection) Cons Farm-wide settings are not preserved or upgraded Customization will not be upgraded Junk in Junk Out
18. Other Upgrade Options Migration Pros Opportunity to organize and cleanse No 64/32 bit issues Source system can be left on line (migrate at your own pace) Majority of your farm-wide settings can be preserved Cons Additional hardware required Takes longer Migrating to Hosted Pros Opportunity to organize and cleanse No hardware requirements Source system can be left on line (migrate at your own pace) Cons Takes longer Lose control Security
19. SharePoint 2010 Migration Steps Planning / Architecting Implementation Data Migration User Training (remember visual upgrade) Support
20. Don’t upgrade your mess! Take advantage of the new platform Cleanse your content Re-organize migrated content Put it in the right location Tag/Classify It Re-use the data already collected in the old system – possibly in a new way
21. Introduce and apply data retention policies Do you need all your old content? Should it be left in the old system? Should you move it to the new SharePoint? Should some content be backed up and deleted? Should it just be scrapped? Archive old content to other systems Remember the file share problems?
22. Design site hierarchies and lists Place content in the appropriate location Factors that guide the design Search You can make each site have unique search settings. For example, you can specify that a particular site never appears in search results. Templates You can make each site have a unique template Security You can define unique user groups and permissions for each site. Content types You can make each site have unique content types and site columns. Workflows You can make each site have unique workflows. Site layouts You can make unique layouts or master pages available Navigation Web pages You can make each site have aunique welcome page and other pages. Themes You can change colors and fonts on a site.. Language/Regional Setting
23. Design Term Stores and Term Sets Design for reuse in many lists by many users Assign owners Create generic managed metadata fields Analyze whether your old fields (choice, lookup, check-boxes and radio-buttons) should be converted to this new format
24. Define Columns and Content Types Create reusable columns Create reusable content types Rebase existing content types Assign content types to lists Apply best practices and standards Enforce corporate policies
25. Design Content Types Hubs Reuse content types between site collections and web applications Decide which content types will be reused Decide where content types will be managed Promote reusable content types in to the hub
26. During Migration… Define values for fields to support content access and navigation tasks in SP 2010 Preserve existing field values Is your folder hierarchy actually metadata? You may consider making it metadata Map values from the existing fields and lookup lists to the newly designed taxonomy managed metadata fields
27. Conclusions There are good reasons to upgrade to SP2010 Map out your existing environment Site collections Webs Lists Content Types Upgrade is the perfect time to clean things up
Regardless of the reason you decide to upgrade, you may as well take advantage of the migration effort to take advantage of the new SharePoint 2010 features.
Amazon is a great example, do you search or browse
All the features that we discussed depend on metadataGoogle vs. Enterprise is equivalent to “The best answers to a questions” vs “The right answer to the question”
Can be used on the left part of the screen as shown here or as element of a list view. The functionality is the same.
Similar to including metadata fields in a view. Can combine more than one field to filter…
Find-ability is the key to getting the most of SharePoint
For file systems, migration is the only option
For file systems, migration is the only option
PlanningAre you going to take a big bang approach and migrate the entire organization to SharePoint 2010 or take a phased approach and migrate one group at a time?Clearly define what you are migrating? Is it your existing internal SharePoint 2007 Intranet and/or collaboration sites? Custom SharePoint application? Public-facing site? Additional content sources (file systems or legacy applications)?How will existing content be migrated? Do you need to migrate them all? What’s the cost benefit of utilizing a tool to do content migration vs manually doing it?Is your current SharePoint information architecture, site taxonomy and site templates well defined that you can replicate the model in SharePoint 2010?How scalable is the current technical infrastructure (hardware, software, network, etc) for SharePoint 2010?ImplementationDo you have the budget and resources to execute the migrations?Did you allocate sufficient time to execute?Which tools will be used?Test MigrationsData MigrationLive migration vs OfflineWill the users be involvedVerificationSupport
