SP Saturday Presentation - Migrating to SharePoint 2010


Published on

Migrating from SharePoint 2007 to 2010 - Don\'t Upgrade Your Mess

From SharePoint Saturday Houston, May 1, 2010

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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”
  • 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.
  • Need to add the part about auto classification with drop box and folder inheritance
  • Can be used on theleft 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…
  • Vocabulary can be controlled or uncontrolled (user can enter new terms)
  • 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
  • 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
  • Other steps to consider when upgrading
  • Authoring of metadataSharePoint offer 2 types of taxonomies – Location and Information taxonomies
  • SP Saturday Presentation - Migrating to SharePoint 2010

    1. 1. 2007 to 2010 SharePoint Migration – Don’t Upgrade Your SharePoint Mess!(200)<br />Steve Pogrebivsky<br />
    2. 2. Welcome to Houston SharePoint Saturday<br />Thank you for being a part of the first ever SharePoint Saturday for the greater Houston area!<br />Please turn off all electronic devices or set them to vibrate.<br />If you must take a phone call, please do so in the hall so as not to disturb others.<br />Thanks to our Platinum Sponsors:<br />
    3. 3. About Me<br />Steve Pogrebivsky, MetaVis Technologies, Inc<br />Professional Interests <br />Enterprise Content Management (ECM)<br />Product Development<br />Background<br />MetaVis Architect Suite: information architecture modeling, classification and migration in SharePoint<br />PathBuilder: Integration Server in ECM area: SharePoint, Documentum, Livelink, Lotus, eRoom<br />
    4. 4. Agenda<br />What is Metadata?<br />Key SharePoint 2010 Features <br />SP 2010 Migration/Upgrade Options<br />Migration Activities<br />Take advantage of the new platform<br />Q&A<br />
    5. 5. Introduction<br />Audience<br />Administrators<br />Consultants<br />System architects<br />Project managers<br />Team leaders<br />Goals<br />What is metadata and why is it important?<br />Learn about new SharePoint 2010 features around metadata and find-ability<br />How to get the most out of your migration into SharePoint 2010<br />Presentation is based on our experience<br />
    6. 6. Metadata<br />Metadata is data about data<br />Content Consumptions depends on metadata<br />Metadata is the foundation of all information retrieval (ontopia.net)<br />Metadata involves<br />Definition - which metadata is important<br />Structure – relationship between metadata and sets of values<br />Administration – configuration and management<br />Authoring – provide values for your content<br />Google vs. Enterprise search<br />
    7. 7. Search<br />
    8. 8. Why jump to SharePoint 2010?<br />Take advantage of the new features and capabilities<br />Administration<br />Branding<br />Content authoring<br />Multi-browser support<br />Content Consumption*<br />Leverage SharePoint for the first time<br />Keep up with the latest, greatest version<br />Infrastructure<br />
    9. 9. Content Consumption Features<br />Search<br />Full text search<br />Faceted search<br />Find-ability<br />Navigation<br />Filtering<br />Grouping<br />Auto Classification<br />
    10. 10. Key SharePoint 2010 Features<br />Metadata Navigation Hierarchies<br />Metadata key filters<br />Term Stores and Managed Metadata/Keywords<br />Search Refinement Panel<br />List Views Group By Navigation<br />
    11. 11. Metadata Navigation Hierarchies<br />
    12. 12. Metadata Key Filters<br />
    13. 13. Term Stores and Managed Metadata<br />
    14. 14. Search Refinement Panel<br />
    15. 15. List View Group By Navigation<br />
    16. 16. OOB SharePoint Upgrade Options<br />In Place Upgrade<br />Pros<br />Farm-wide settings are preserved and upgraded<br />Content is preserved <br />Customization will be (may be) upgraded<br />Cons<br />SQL Server and O/S must be 64 bit<br />Whole system has to be offline<br />Junk in  Junk Out<br />Database Upgrade<br />Pros<br />Can do multiple database upgrades concurrently<br />Original system can be left online (read-only)<br />No 64/32 bit issues<br />Cons<br />Farm-wide settings are not preserved or upgraded<br />Customization will not be upgraded<br />Junk in  Junk Out<br />http://technet.microsoft.com/en-us/library/cc263447(office.14).aspx<br />
    17. 17. Other Upgrade Options<br />Migration<br />Pros<br />Opportunity to organize and cleanse<br />No 64/32 bit issues<br />Source system can be left on line (migrate at your own pace)<br />Majority of your farm-wide settings can be preserved<br />Cons<br />Additional hardware required<br />Takes longer<br />Migrating to Hosted<br />Pros<br />Opportunity to organize and cleanse<br />No hardware requirements <br />Source system can be left on line (migrate at your own pace)<br />Cons<br />Takes longer<br />Lose control<br />Security<br />Farm-wide settings have to be re-created<br />
    18. 18. SharePoint 2010 Migration Steps<br />Planning<br />Implementation<br />Data Migration<br />User Training<br />Support<br />
    19. 19. Don’t upgrade your mess!<br />Take advantage of the new platform<br />Cleanse your content<br />Re-organize migrated content<br />Put it in the right location<br />Tag/Classify It<br />Re-use the data already collected in the old system – possibly in a new way<br />
    20. 20. Introduce and apply data retention policies<br />Do you need all your old content?<br />Should it be left in the old system?<br />Should you move it to the new SharePoint?<br />Should some content be backed up and deleted?<br />Should it just be scrapped?<br />Archive old content to other systems<br />
    21. 21. Taxonomy<br />Taxonomy is the practice and science of classification (wikipedia)<br />Location Taxonomy defines physical location of items and documents. <br />site collections, sites, sub-sites, lists, libraries and folders<br />Information Taxonomy defines metadata<br />fields and hierarchy of content types in sites, sub-sites, lists and libraries as well as actual field values assigned to SharePoint items and documents<br />
    22. 22. Design site hierarchies and lists<br />Place content in the appropriate location<br />Factors that guide the design<br />Search   You can make each site have unique search settings. For example, you can specify that a particular site never appears in search results.<br />Templates   You can make each site have a unique template<br />Security   You can define unique user groups and permissions for each site. <br />Content types   You can make each site have unique content types and site columns.<br />Workflows   You can make each site have unique workflows.<br />Site layouts   You can make unique layouts or master pages available<br />Navigation <br />Web pages   You can make each site have a unique welcome page and other pages.<br />Themes   You can change colors and fonts on a site.. <br />Language/Regional Setting<br />
    23. 23. Design Term Stores and Term Sets<br />Design for reuse in many lists by many users<br />Create generic managed metadata fields<br />Analyze whether your old fields (choice, lookup, check-boxes and radio-buttons) should be converted to this new format<br />
    24. 24. Define Columns and Content Types<br />Create reusable columns<br />Create reusable content types<br />Rebase existing content types<br />Assign content types to lists<br />Apply best practices and standards<br />Enforce corporate policies<br />
    25. 25. Design Content Types Hubs<br />Reuse content types between site collections<br />Decide which content types will be reused<br />Decide where content types will be managed<br />Promote reusable content types in to the hub<br />
    26. 26. Design Navigation Structures<br />List Views with Group By clauses<br />Metadata Navigation Hierarchies<br />Metadata Key Filters<br />Refinement Panel<br />
    27. 27. During Migration…<br />Define values for fields to support content access and navigation tasks in SP 2010<br />Preserve existing field values<br />Is your folder hierarchy actually metadata? You may consider making it metadata<br />Map values from the existing fields and lookup lists to the newly designed taxonomy managed metadata fields<br />
    28. 28. Conclusions<br />There are good reasons to upgrade to SP2010!<br />So, if you are going to take the plunge, why not take the opportunity to clean your mess?<br />
    29. 29. Q&A<br />Questions<br />Steve Pogrebivsky <br />Email: stevep@metavistech.com<br />Twitter: @metavistech<br />WEB: www.metavistech.com<br />
    30. 30. Session Evaluation<br />Please complete and turn in your Session Evaluation Form so we can improve future events.<br />Presenter:<br />Steve Pogrebivsky<br />Session Name:<br />2007 to 2010 SharePoint Migration<br />
    31. 31. Thanks to our Sponsors<br />