SP Saturday Presentation - Migrating to SharePoint 2010
- 1. 2007 to 2010 SharePoint Migration – Don’t Upgrade Your SharePoint Mess!(200)Steve Pogrebivsky
- 2. Welcome to Houston SharePoint SaturdayThank you for being a part of the first ever SharePoint Saturday for the greater Houston area!Please turn off all electronic devices or set them to vibrate.If you must take a phone call, please do so in the hall so as not to disturb others.Thanks to our Platinum Sponsors:
- 3. About MeSteve Pogrebivsky, MetaVis Technologies, IncProfessional Interests Enterprise Content Management (ECM)Product DevelopmentBackgroundMetaVis Architect Suite: information architecture modeling, classification and migration in SharePointPathBuilder: Integration Server in ECM area: SharePoint, Documentum, Livelink, Lotus, eRoom
- 4. AgendaWhat is Metadata?Key SharePoint 2010 Features SP 2010 Migration/Upgrade OptionsMigration ActivitiesTake advantage of the new platformQ&A
- 5. IntroductionAudienceAdministratorsConsultantsSystem architectsProject managersTeam leadersGoalsWhat is metadata and why is it important?Learn about new SharePoint 2010 features around metadata and find-abilityHow to get the most out of your migration into SharePoint 2010Presentation is based on our experience
- 6. MetadataMetadata is data about dataContent Consumptions depends on metadataMetadata is the foundation of all information retrieval (ontopia.net)Metadata involvesDefinition - which metadata is importantStructure – relationship between metadata and sets of valuesAdministration – configuration and managementAuthoring – provide values for your contentGoogle vs. Enterprise search
- 7. Search
- 8. Why jump to SharePoint 2010?Take advantage of the new features and capabilitiesAdministrationBrandingContent authoringMulti-browser supportContent Consumption*Leverage SharePoint for the first timeKeep up with the latest, greatest versionInfrastructure
- 9. Content Consumption FeaturesSearchFull text searchFaceted searchFind-abilityNavigationFilteringGroupingAuto Classification
- 10. Key SharePoint 2010 FeaturesMetadata Navigation HierarchiesMetadata key filtersTerm Stores and Managed Metadata/KeywordsSearch Refinement PanelList Views Group By Navigation
- 13. Term Stores and Managed Metadata
- 15. List View Group By Navigation
- 16. OOB SharePoint Upgrade OptionsIn Place UpgradeProsFarm-wide settings are preserved and upgradedContent is preserved Customization will be (may be) upgradedConsSQL Server and O/S must be 64 bitWhole system has to be offlineJunk in Junk OutDatabase UpgradeProsCan do multiple database upgrades concurrentlyOriginal system can be left online (read-only)No 64/32 bit issuesConsFarm-wide settings are not preserved or upgradedCustomization will not be upgradedJunk in Junk Outhttp://technet.microsoft.com/en-us/library/cc263447(office.14).aspx
- 17. Other Upgrade OptionsMigrationProsOpportunity to organize and cleanseNo 64/32 bit issuesSource system can be left on line (migrate at your own pace)Majority of your farm-wide settings can be preservedConsAdditional hardware requiredTakes longerMigrating to HostedProsOpportunity to organize and cleanseNo hardware requirements Source system can be left on line (migrate at your own pace)ConsTakes longerLose controlSecurityFarm-wide settings have to be re-created
- 18. SharePoint 2010 Migration StepsPlanningImplementationData MigrationUser TrainingSupport
- 19. Don’t upgrade your mess!Take advantage of the new platformCleanse your contentRe-organize migrated contentPut it in the right locationTag/Classify ItRe-use the data already collected in the old system – possibly in a new way
- 20. Introduce and apply data retention policiesDo 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
- 21. TaxonomyTaxonomy is the practice and science of classification (wikipedia)Location Taxonomy defines physical location of items and documents. site collections, sites, sub-sites, lists, libraries and foldersInformation Taxonomy defines metadatafields and hierarchy of content types in sites, sub-sites, lists and libraries as well as actual field values assigned to SharePoint items and documents
- 22. Design site hierarchies and listsPlace content in the appropriate locationFactors that guide the designSearch 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 templateSecurity 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 availableNavigation Web pages You can make each site have a unique welcome page and other pages.Themes You can change colors and fonts on a site.. Language/Regional Setting
- 23. Design Term Stores and Term SetsDesign for reuse in many lists by many usersCreate generic managed metadata fieldsAnalyze whether your old fields (choice, lookup, check-boxes and radio-buttons) should be converted to this new format
- 24. Define Columns and Content TypesCreate reusable columnsCreate reusable content typesRebase existing content typesAssign content types to listsApply best practices and standardsEnforce corporate policies
- 25. Design Content Types HubsReuse content types between site collectionsDecide which content types will be reusedDecide where content types will be managedPromote reusable content types in to the hub
- 26. Design Navigation StructuresList Views with Group By clausesMetadata Navigation HierarchiesMetadata Key FiltersRefinement Panel
- 27. During Migration…Define values for fields to support content access and navigation tasks in SP 2010Preserve existing field valuesIs your folder hierarchy actually metadata? You may consider making it metadataMap values from the existing fields and lookup lists to the newly designed taxonomy managed metadata fields
- 28. ConclusionsThere are good reasons to upgrade to SP2010!So, if you are going to take the plunge, why not take the opportunity to clean your mess?
- 29. Q&AQuestionsSteve Pogrebivsky Email: stevep@metavistech.comTwitter: @metavistechWEB: www.metavistech.com
- 30. Session EvaluationPlease complete and turn in your Session Evaluation Form so we can improve future events.Presenter:Steve PogrebivskySession Name:2007 to 2010 SharePoint Migration
- 31. Thanks to our Sponsors
Editor's Notes
- #7: 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”
- #9: 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.
- #11: Need to add the part about auto classification with drop box and folder inheritance
- #12: Can be used on theleft part of the screen as shown here or as element of a list view. The functionality is the same.
- #13: Similar to including metadata fields in a view. Can combine more than one field to filter…
- #14: Vocabulary can be controlled or uncontrolled (user can enter new terms)
- #15: The refinement panel shows you the categories (or metatdata) for the first 50 items in the results list Built in filters include type, site, author, modified date, and location but you can customize itCan search across site collection
- #16: Find-ability is the key to getting the most of SharePoint
- #17: For file systems, migration is the only option
- #18: For file systems, migration is the only option
- #19: 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
- #21: Other steps to consider when upgrading
- #22: Authoring of metadataSharePoint offer 2 types of taxonomies – Location and Information taxonomies